SQLMail not able to send with Outlook

We are attempting to configure SQLMail to be able to notify our Database administrator of important SQL events through e-mail and net send.  We are having an issue that is preventing us from getting this configured.  We've gone over the Microsoft article about troubleshooting this and I think we have everything setup but apparently something is wrong.  We are using SQL 7 and Exchange 2000. Here is an e-mail from her about our current situation.

I’m trying to set up the email alerts when SQL has problems.  I cannot get the email to send.  I have made an account for SQL called SQLMail that is a System Admin in SQL, is how SQLserver service is started.  We use Outlook so the profile in SQL Mail configuration shows Outlook and starts and stops the Mapi service fine.  (We had tried to use SQLMail as the profile in the configuration but it would not start then, had a mapi failure (error 22030 A Mapi Error (Error number 273) occurred: MapilogonEx failed due to Mapi error 273).  So we currently have the server logged in as SQLMail (which is a domain account), SQLMail is running the SQLserver service, the SQLmail configuration is set to Outlook and the SQLserver Agent is started with SQLmail.   The Operator I have set up is SQLmail as well and I get an error [Error 22022: SQLServerAgent mail session is not running; check the mail profile and/or the SQLServerAgent service startup account in the SQLServerAgent Properties Dialog.

I’ve tried setting myself up at the operator as well and gotten no where, I get the same error.  I’ve looked on line and as far as I can tell have incorporated everything suggested in the KB’s from Microsoft.  

Both SQL services are set to start as our SQLMail account which has domain administrator rights, Outlook is configured with a special profile for SQLMail and it can open and send messages just fine manually. The net send option under our Operators works, it is only the e-mail that is not.  Is there something that we are missing that can be causing this or other things we can check to get this up and running?  
LVL 17
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Melih SARICAOwnerCommented:
Check these links

http://support.microsoft.com/default.aspx?scid=kb;en-us;315886  //INF: Common SQL Mail Problems

http://support.microsoft.com/default.aspx?scid=kb;en-us;263556 // INF: How to Configure SQL Mail

http://support.microsoft.com/default.aspx?scid=kb;en-us;311231 // INF: Frequently Asked Questions - SQL Server - SQL Mail



Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Eagle6990Author Commented:
Sorry I'm just now getting back to this.  Been playing with it all week.  According to one of the Microsoft articles, Outlook 2002 has some increased security that could cause issue, so I uninstalled it, rebooted the server and installed Outlook 2000.  

Following this article, here is my config: http://support.microsoft.com/default.aspx?scid=kb;en-us;315886

1) Outlook 2000 installed on SQL 7 SP4
2) Outlook is configured and works properly with my Exchange 2000 server.
3) Configured
4) Both SQLAgent and SQL Server are starting with our new domain account SQLMail
5) SQLMail account has an Exchange mailbox that is configured and working properly.  the SQLMail service is running properly
6) I can login as SQLMail and open Outlook just fine with no issues.  Mail is flowing in and out of this account
7) AhHa!  There is where my problem for the time being was.  SQLAgent did not have the proper MAPI profile selected even though SQLMail did.  

Now my mail is flowing.  Excellent!
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.