: xp_smtp_sendmail error on windows server 2005 (x64) n sql server 2005 (64 bit)

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.. thanks for help in advance

Hi,

I have also had some problems with xp_smtp_sendmail in SQL 2005.

But now SQL 2005 supports the use of SMTP email with out the need for a MAPI client. There is minor set up and then you can use the procedure msdb.dbo.sp_send_dbmail. It works basically like xp_smtp_sendmail.

To set up database mail you need to first make sure that Database Mail is enabled in the MS SQL server 2005 Surface Area configuration. Then go into SQL server management studio under Management and right click on Database Mail and select Configure Database Mail.

Here are a couple of links http://www.sqlservercentral.com/columnists/cBunch/introtodatabasemailinsql2005.asp

http://www.databasejournal.com/features/mssql/article.php/3626056

|||Very helpful information, it helped me a lot.. Thank you|||

can you really to send e-mails on 64-bit version?

could you help me in this case?

answer me plz!

|||

I use msdb.dbo.sp_send_dbmail.

It is easier and works better...

|||"msdb.dbo.sp_send_dbmail" works on 64-bit without any errors?
how do you tune environment of SQL Server 2005 (64-bit) for working with "msdb.dbo.sp_send_dbmail"?

could you get me helping article?
|||

This is easy, I will look for an article tomorrow, but for now just do this

Get a SMTP server that you can connect to and you know you have privledges on use outlook express to test it, or some other pop client.

Once you know you have a 'working' smtp server that you can connect to. Set up DBMAIL

to do this just open up the 'Management' folder and right click on dbmail, stomp thru the menu's to set up an account and a profile.

Test this profile by again right clicking on the dbmail icon under the managment folder of your server, and do a "test email" and select your profile check your reciepent's mailbox for the mail. If it doesn't work check the history on the same icon.

Once you KNOW that works....

Then go to the msdb database and drill down to the msdb.dbo.sp_send_dbmail script it to a query window so that you can find all the variables you can give to the stored procedure when you call it.. Like @.profile, @.recepients, @.body, @.subject etc...

Then try to send a message thru your query window and you are done....

That is the short version... I will look for 8X10 glossies tomorrow, and post...

Best Regards,

Dow

|||i've done like you wrote.
outlook has sent the e-mails from this computer (64-bit).

but i've got this error:

Date 2007-04-19 10:00:41
Log Database Mail (Database Mail Log)

Log ID 49
Process ID 4556
Mail Item ID 20
Last Modified 2007-04-19 10:00:41
Last Modified By sa

Message
The mail could not be sent to the recipients because of the mail server failure. (Sending Mail using Account 2 (2007-04-19T10:00:40). Exception Message: Could not connect to mail server. (An established connection was aborted by the software in your host machine).
)

i cannot find in internet some clarifying answer about this problem
|||

Okay, so you KNOW you can send mail thru your SMTP server from the very same box that you have sql loaded on.

Therefore, what dbmail is complaining about, if you are doing the send test message step, then the account you are using cannot

authenticate with the SMTP server. Since you KNOW you have sent SMTP mail from the same nic card to the smtp server you know that there is no network issues or server issues. The problem MUST be with the way that you have answered the questions on the ACCOUNT.

Now is your SMTP server a unix type or a windows type? If it is a unix type then make sure you set the username and password are set exactly like you did for the test with the outlook client. and you don't use the secure socket layer setting. If you smtp server will allow anonymous use that.

notice your error is telling you that it cannot connect. Also make sure you have put the correct NAME for the server and you are using the correct port, the default port is 25...

You are almost there, don't give up...

|||GUYS!!!!!!

It WORK!!!

See:

Database Mail in SQL Server 2005
www.databasejournal.com/features/mssql/article.php/3626056
|||

Hi, guys!

I have another problem with SQL Server 2005 & Mail & 64-bit.

I can sent e-mail from SQL Server 2005, but how can i receive e-mail from internet to SQL Server 2005?

I've got the answer:

Msg 17938, Level 16, State 0, Line 0
SQL Mail does not work with the 64-bit version of SQL Server

Help me plz.

|||DatabaseMail is an SMTP client only, which means that is can send but not receive emails. Receiving emails requires POP3 or IMAP support. SQLMail has that built-in, but is being depreciated in coming versions of SQL Server so you'll want to stay away from that implementation.

SQLMail is available in the 32-bit version of SQL Server 2005, but not in the 64-bit version.

HTH...

Joe|||I was wondering if you have a fix to the error on sending mail using the windows vista edition using the windows mail. I love the mail program but can only receive. Get an error report about the port 25. Thanks for any help I can get.

.Net Stored Procedures on IA64 SSAS

Does anybody know if it is possible to call .Net stored procedures from a 64 bit Analysis Services Installation? Unfortunately the .Net stored procedures which we are trying to use target the x86 platform and not IA64.

(The procedures use an ODBC driver that is only available to 32 bit applications.)

Any information would be appreciated. The trial and error process gives me an MDX error that says that my stored procedures cannot be found. However, SSAS lets me add the x86 assembly to my database without any problem.

You can't cross 32/64 bit process boundaries within a single process this way. You can't try to load 32bit stored procedure into 64 bit process. Analysis Server is not checking the target platform you compiled you SP for on load, but later as you can see it fails to load it.

If you absolutely must to use the 32bit ODBC driver, you have an option of installing 32bit AS on 64bit platform. But that is highly unintuitive. Take a look if you can find native 64bit version of OLEDB provider instead of using 32bit ODBC driver.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||I also would like to add here, that unless you are using COM based sprocs (which are off by default), the .NET sprocs are platform agnostic, just like .NET itself. You can take sproc .NET assembly and deploy it to either 32 or 64 bit server without recompilation - it should work fine.

**HAVE NULL AND NOT DUBLICATED VALUES IN COL**

In my opinon the best way of doing this would be through
an 'INSTEAD OF INSERT' trigger.
If you give a bit more on the requirements I can help with
the code, for instance can you have two of...
105,'Tom',null
105,'Tom',null
In the table ?
Peter
"Choose a job you love, and you will never have to work a
day in your life."
Confucius

>--Original Message--
>Hi
>I'm using SQL 2000,how is it possible to control a value
of column to get
>the ollowing result?
>Emp (EmpId PK,EmpName,EmpCode)
>EmpId EmpName EmpCode
>-- -- --
>100 John 3
>101 Anne 5
>102 Robert null
>103 Jennifer null
>104 Peter 78
>I want to have some NULLs or a unique number in EmpCode
column as above,
>I tried to define Uniqe index or constraint but it wasn't
successfull
>because of null,
>now how can I prevent of inserting a record of
(105,'Tom',3) and not prevent
>of inserting a record like (105,'Tom',null)
>Any help would be greatly thankful.
>
>.
>No, we can't have
> 105,'Tom',null
> 105,'Tom',null
cause the first column is a PK,
"Peter The Spate" <anonymous@.discussions.microsoft.com> wrote in message
news:204701c5141e$26f85330$a501280a@.phx.gbl...
> In my opinon the best way of doing this would be through
> an 'INSTEAD OF INSERT' trigger.
> If you give a bit more on the requirements I can help with
> the code, for instance can you have two of...
> 105,'Tom',null
> 105,'Tom',null
> In the table ?
> Peter
> "Choose a job you love, and you will never have to work a
> day in your life."
> Confucius
>
> of column to get
> column as above,
> successfull
> (105,'Tom',3) and not prevent