Problems with SQL mail

I have just setup a Windows 2003 Server with SQL 2000 (sp 3a) and Outlook
2000. I am trying to get SQL Mail working on this box but keep getting the
following message.
Error 18025: xp_test_mapi_profile : failed with mail error 0x80040111
I used to have this setup on a Windows 2000 Server box and it worked spot
on. Can anybody offer any advice? I have logged in as the user the SQL
services run as and setup a mail profile, e-mail works fine as this user. I
have also tried Outlook 2002 and got the same message. Rebooted the server
several times too.
thanks
GavSQL Mail can be a real bear to get working. I have not used it since I
stumbled upon XPSMTP -- http://sqldev.net/xp/xpsmtp.htm
XPSMTP does not have the "plug and play" behavior that SQL Mail has but it
is very powerful and it just works. By plug and play I am referring to
things like automated job failure notification. Instead of clicking on
"notify operator on error" you have to create a job step that you call on
failure. The job step will call xp_smtp_sendmail with the appropriate
parameters.
Keith
"Gav" <gavin.metcalfe@.nospam.portakabin.com> wrote in message
news:d1bip6$rtu$1@.newsreaderg1.core.theplanet.net...
> I have just setup a Windows 2003 Server with SQL 2000 (sp 3a) and Outlook
> 2000. I am trying to get SQL Mail working on this box but keep getting the
> following message.
> Error 18025: xp_test_mapi_profile : failed with mail error 0x80040111
> I used to have this setup on a Windows 2000 Server box and it worked spot
> on. Can anybody offer any advice? I have logged in as the user the SQL
> services run as and setup a mail profile, e-mail works fine as this user.
I
> have also tried Outlook 2002 and got the same message. Rebooted the server
> several times too.
> thanks
> Gav
>|||You have to log into the server as the SQL Server service account and use
the Control Panel Mail properties to configure a mail profile. Then you
have to launch Outlook for the first time to get through all of the initial
dialogue.
As far as xpsmtp is concerned, that's great but can't be used by SQL Agent
mail. So, you have no alerts and no job status reports unless you hand code
EVERYTHING.
Sincerely,
Anthony Thomas
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:eW7SCzuKFHA.592@.TK2MSFTNGP10.phx.gbl...
SQL Mail can be a real bear to get working. I have not used it since I
stumbled upon XPSMTP -- http://sqldev.net/xp/xpsmtp.htm
XPSMTP does not have the "plug and play" behavior that SQL Mail has but it
is very powerful and it just works. By plug and play I am referring to
things like automated job failure notification. Instead of clicking on
"notify operator on error" you have to create a job step that you call on
failure. The job step will call xp_smtp_sendmail with the appropriate
parameters.
Keith
"Gav" <gavin.metcalfe@.nospam.portakabin.com> wrote in message
news:d1bip6$rtu$1@.newsreaderg1.core.theplanet.net...
> I have just setup a Windows 2003 Server with SQL 2000 (sp 3a) and Outlook
> 2000. I am trying to get SQL Mail working on this box but keep getting the
> following message.
> Error 18025: xp_test_mapi_profile : failed with mail error 0x80040111
> I used to have this setup on a Windows 2000 Server box and it worked spot
> on. Can anybody offer any advice? I have logged in as the user the SQL
> services run as and setup a mail profile, e-mail works fine as this user.
I
> have also tried Outlook 2002 and got the same message. Rebooted the server
> several times too.
> thanks
> Gav
>|||If Microsoft would like to work on a "thorn in your XXX" problem with SQL
Server I vote for SQL Mail. I've had problems with SQL Mail since day one
and it should be a no brainer. I had mine set up on the SQL Servers I deal
with and after many hours finally got it to work with about 90% reliability.
We recently upgraded our Exchange server to 2003 and changed the name of the
email server, but now SQL Mail does NOT work. I can log in to the SQL
server under the domain account the service is running under, make the
changes to the Outlook client, send emails, get all the cute little SQL Mail
Test buttons to work, actually send an email using xp_sendmail, etc, etc,
etc but when it comes to "needing" it to work, it does not. All my
scheduled jobs and all the alerts I have set to notify of production issues
have yet to work. When I stop the SQL Agent service and restart it, I get
flooded with all the emails that should have been sent. I wouldn't recommend
the MAPI SQL Mail to anyone.
I've recently installed the xpsmtp on the servers and it works EVERY time.
I'm making the changes to all the processes I would like to have an email
notification from to use the smtp email - it's a pain, but it's reliable.
"Keith Kratochvil" <sqlguy.back2u@.comcast.net> wrote in message
news:eW7SCzuKFHA.592@.TK2MSFTNGP10.phx.gbl...
> SQL Mail can be a real bear to get working. I have not used it since I
> stumbled upon XPSMTP -- http://sqldev.net/xp/xpsmtp.htm
> XPSMTP does not have the "plug and play" behavior that SQL Mail has but it
> is very powerful and it just works. By plug and play I am referring to
> things like automated job failure notification. Instead of clicking on
> "notify operator on error" you have to create a job step that you call on
> failure. The job step will call xp_smtp_sendmail with the appropriate
> parameters.
> --
> Keith
>
> "Gav" <gavin.metcalfe@.nospam.portakabin.com> wrote in message
> news:d1bip6$rtu$1@.newsreaderg1.core.theplanet.net...
> I
>|||Microsoft must be aware of the problems with the current implementation of
SQLMail.
SQLiMail is slated be included within the next version of SQLServer. Here
are a few links:
http://www.microsoft.com/technet/co...5/tnt1-133.mspx
http://www.microsoft.com/technet/pr...ql/SQL0113.mspx
http://www.microsoft.com/technet/co...ql/sql1209.mspx
Keith
"cw" <cwilson@.3mc.com> wrote in message
news:OfHtdr8KFHA.4092@.tk2msftngp13.phx.gbl...
> If Microsoft would like to work on a "thorn in your XXX" problem with SQL
> Server I vote for SQL Mail. I've had problems with SQL Mail since day one
> and it should be a no brainer. I had mine set up on the SQL Servers I
deal
> with and after many hours finally got it to work with about 90%
reliability.
> We recently upgraded our Exchange server to 2003 and changed the name of
the
> email server, but now SQL Mail does NOT work. I can log in to the SQL
> server under the domain account the service is running under, make the
> changes to the Outlook client, send emails, get all the cute little SQL
Mail
> Test buttons to work, actually send an email using xp_sendmail, etc, etc,
> etc but when it comes to "needing" it to work, it does not. All my
> scheduled jobs and all the alerts I have set to notify of production
issues
> have yet to work. When I stop the SQL Agent service and restart it, I get
> flooded with all the emails that should have been sent. I wouldn't
recommend
> the MAPI SQL Mail to anyone.
> I've recently installed the xpsmtp on the servers and it works EVERY time.
> I'm making the changes to all the processes I would like to have an email
> notification from to use the smtp email - it's a pain, but it's reliable.