February 9, 2007 at 5:54 am
| hi, i have an application that was running successfully on sql server 2000 x86 machine but now its been migrated to sql server 2005(64 bit) with windows 2003 server x64 machine. And now the xp_smtp_sendmail is not working when called through sql server even declare @rc int exec @rc = master.dbo.xp_smtp_sendmail @server = 'my.server.com', @port = 25, @ping = 1 select RC = @rc wont work it would give error that could not load the dll or one of its module not a valid win32 application. but its working fine in x86 win server 2003 n sql server 2005 machine when i run dependency walkthrough it, it shows some dlls missing i have also read that in syswow64 can run only those application that are not running in kernel mode. what might be the problem...or should i look for another alternative.. |
February 9, 2007 at 7:08 am
Not really the answer you want but in sql server 2005 using database mail is much more efficient as it uses service broker and is therefore asynchronous in nature. Also it avoids the scheduling issues that calling extended procedures cause.
Anyway this is what i did when i migrated to sql server 2005 and have found the new database mail fucntionality to be much more efficient.
hth
David
February 9, 2007 at 7:37 am
Thanks David,
Ya i m now working on Database Mail, created an account and profile.. i have a virtual server setup on my IIS.
All is working fine for first domain but its not working for another domain although i m connected to corp net, the error is its sending my mail to badmail directory of mailroot, i guess its reverse looking for my domain which is not registered on internet as i m on microsoft corp net , this is what i think. how do i disable this behaviour or any other option?
Have you ever encountered this problem anytime.
Viewing 3 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply