November 17, 2005 at 8:25 am
Does anyone have experience configuring sqlmail or sqlserveragent mail when your Exchange server is in a seperate (non-trusted) domain from your SQL server (2000)?
I've logged on to the SQL Server as the domain account that my SQLServer Agent is configured to logon as. This account is a member of the Local Admins group on the SQL Server. I can create a profile using control panel - mail, and logon using outlook. But when I configure the SQL Server agent to use this profile, and hit TEST, I get an "Error 22022: SQLServerAgent Error: Unable to get the default MAPI Message Store due to MAPI error 285: The Microsoft Exchange Server computer is not available. Either there are network problems or the Microsoft Exchange Server computer is down for maintenance." Neither of these two assumptions are correct. I can pull up outlook using the same profile and login and it works fine.
My thinking is that, because of the un-trusted domain element, when the SQL Server Agent tries to initiate a MAPI session, it's being prompted for a password (albeit you cannot see this).
Anyone with a similar configuration out there?
Regards -
Tim
November 18, 2005 at 10:13 am
Can't help with what you are doing but this article worked for me. Doesn't use SQLMail but smtp.
http://www.sqlservercentral.com/scripts/contributions/510.asp
November 18, 2005 at 2:23 pm
Open the MSSQLSERVER service on your desktop and change the login to "This account", then enter your domain login.
May 15, 2006 at 8:56 am
We're also getting the same errors on a few servers and are currently researching. We recently upgraded to Exchange 2003 and added Active Directory. We're also using a variety of Outlook client versions so I don't believe the problem is with one particular version. The crazy thing is that sometimes SQLAgent mail works and sometimes it doesn't. A couple of weeks ago about a dozen servers were having problems and now they are mysteriously working again. Currently there are 8 servers having problems--probably 4 of them haven't been working the whole time. I'm going to have our Server admins check for errors in Active Directory & Exchange to see what they can come up with. I read a thread somewhere that says Outlook 2003 doesn't work with SQL 2000, but 6 of the servers having issues don't use that version. I hope to find something soon 'cause it's giving me a headache 🙂
May 15, 2006 at 9:01 am
The SQL Service, SQL Agent must START under a domain account that HAS a mail profile on server.
Vasc
May 15, 2006 at 9:08 am
Yes of course. SQL mail has been running fine here for 7 years and since all of the above recnet changes it has been having problems. A server admin said he saw some errors either in Active Directory or Exchange so I'm waiting to get more information from him. If it's anything useful, I'll post again.
January 22, 2008 at 1:20 am
I have solve this problem, please visit http://support.microsoft.com/kb/263556
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply