SQL Mail error with Outlook 2003 client

Question

SQL Mail error with Outlook 2003 client

aboehm

SSC Journeyman

Points: 86
More actions
January 10, 2006 at 6:41 am

#152696

I'm attempting to setup a new SQL Server. It is SQL Server 2003 Enterprise Edition, 3a. The Outlook Client is 2003. We haven't used Outlook 2003 in conjunction with SQLMail in the past.
The profile tests fine, SQL Mail can be started and stopped without an issue and SQL Agent is able to send mail, but xp_sendmail fails with the following error:
Server: Msg 18025, Level 16, State 1, Line 0
xp_sendmail: failed with mail error 0x80070005
Worked with MS Support for 4 hours yesterday, getting nowhere fast. Does anyone else have SQLMail working with Outlook 2003 client? Any hints?

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply

Joe Nakanishi-3 SSC Eights! Points: 828 More actions · Answer 1

Assuming you meant SQL Server 2000. I'm running Outlook 2003 on my WS with SQL 2000 with no issues.

Did you set up the mail profile for SQL Server Agent? From EM right click on SQL Server Agent...properties...general tab (middle of the page). The outlook profile should be for the account that SQL Server Agent is running under.

You may also want to make sure that Outlook is set as your default email application. Easiest way is to open IE...tools...internet options...programs tab...make sure e-mail is set to Outlook.

There's always the dreaded uninstall/reinstall of outlook (ugh).

aboehm SSC Journeyman Points: 86 More actions · Answer 2

Yes, sorry. It is SQL Server 2000 Enterprise Edition service pack 3a using Outlook 2003.

The SQL Agent mail is fine with alerts being able to send mail. The Outlook client on the server was fine and is able to send and receive email using the SQL Server service domain user. It was the SQL Service connection to that same profile that wasn't working. (ex. xp_sendmail through Query Analyzer)

MS Support Virtual Meeting'ed into our network and checked out the SQL Server, Outlook Client, domain accounts used for the SQL Services, Exchange and Active Directory settings and found everything to be configure properly. They are puzzled as well.

We've re-installed the Outlook Client and still have the same issue. Next step MS recommends is re-installing SQL Server which is a shame as there was already a bunch of stuff on this server and the current project is on a tight time line.

Thanks for the input. It is good to know that someone else at least has SQLMail working with the Outlook 2003 client.

miked9999 SSChasing Mays Points: 625 More actions · Answer 3

We encountered the same error on a server using outlook 2003.

This is due to the use of Outlook 2003 as the mail client. Outlook was configured to use Cached Exchange Mode. This means that all mail is read from and written to a local cache before being sent to the exchange server.

In this case there were two instances on the one server using the same mail profile. Both SQL Server instances are running under the domain administrator account and using the same MAPI profile. Also, the domain administrator can open the Outlook using the same profile. This means that all three processes are potentially accessing the same Outlook Cache, and potentially at the same time. This caused the MAPI process to fail in SQL Server.

I reconfigured the Outlook MAPI profile so that Cached Exchange Mode is not used, and restarted both instances of SQL Server. This allowed the creditor emails to be sent from Maze.