July 20, 2010 at 2:12 pm
Hi everyone, we recently just upgraded our exchange server to Exchange 2010, and I've been migrating our mailboxes over to the new server slowly but surely. (we were running Exchange 2003). I just migrated our sql mail mailbox, and ever since, all of our mail notifications from SQL have broken. I've logged in as a user with permissions to the mailbox, logged into Outlook 2007 locally on the sql server and successfully sent and received e-mail with the e-mail profile used by our SQL jobs. However, everytime we try to test the mail profile in SQL Server Agent properties, we get the following error:
TITLE: Microsoft SQL Server Management Studio
------------------------------
Test mail profile failed for JobServer 'SERVER-sql'. (Microsoft.SqlServer.Smo)
------------------------------
ADDITIONAL INFORMATION:
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
------------------------------
SQLServerAgent Error: MapiLogonEx Failed due to MAPI error 1541: MAPI is not initialized properly. (Microsoft SQL Server, Error: 22022)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.4053&EvtSrc=MSSQLServer&EvtID=22022&LinkId=20476
------------------------------
BUTTONS:
OK
------------------------------
And, if we just try an xp_startmail, it fails with the following error:
xp_sendmail: failed with mail error 0x80040605
Any help with this would be greatly appreciated. Thanks!
-Kevin
July 20, 2010 at 2:47 pm
Is this SQL 2000 or SQL 2005?
If SQL 2005, have you considered using DBMail instead?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 20, 2010 at 2:50 pm
Hi, sorry. It's SQL 2005 Standard. We really haven't looked into using DBMail...all of our mail jobs have been written with SQLMail in mind. Any thoughts?
July 20, 2010 at 3:17 pm
What version of Outlook (MAPI Client) are you using? Have you checked to ensure it (the version of Outlook on your SQL Server) is compatible with Exchange 2010?
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 20, 2010 at 3:22 pm
I'm currently running Outlook 2007. We were using Outlook 2003, but when we upgraded to Exchange 2010, it forced us to upgrade the local MAPI client to Outlook 2007. I'm going to try to install the SP2 for Office 2007 right now to see if that helps any.
Also, I'm able to go in to Outlook and send/receive e-mails just fine with this account. It's only in SQL that I'm getting the MAPI errors.
-Kevin
July 20, 2010 at 3:31 pm
Try verifying the permissions. Some may have been updated with the upgrade to Exchange 2010.
http://support.microsoft.com/kb/293422/EN-US/
This link is for SQL 2000 - but applies to Exchange permissions.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
July 20, 2010 at 3:55 pm
First of all, thanks for your help. I've tried setting the permissions for send-as nearly everywhere I can, and it still doesn't let me use the account for SQL Mail.
I'm still getting the same error when I try doing the "TEST" button, and when I try to manually do an xp_stopmail and xp_startmail, I'm still getting failed with mail error 0x80040111.
-Kevin
Viewing 7 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply