SQL2005 database mailer problem

Hi there,

Got a 2005 SP1 SQL box, with database mailer giving problems. In the sysmail_event_log is has

1) Exception Information =================== Exception Type: System.NullReferenceException Message: Object reference not set to an instance of an object. Data: System.Collections.ListDictionaryInternal TargetSite: Microsoft.SqlServer.Management.SqlIMail.Server.Objects.Account GetAccount(Int32) HelpLink: NULL Source: DatabaseMailEngine StackTrace Information =================== at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.DataAccessAdapter.GetAccount(Int32 accountID) at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.SessionManager.GetAccount(Int32 accountID) at Microsoft.SqlServer.Management.SqlIMail.Server.Controller.CommandFactory.CreateSendMailCommand(DBSession dbSession) at Microsoft.SqlServer.Management.SqlIMail.Server.Controller.CommandFactory.CreateCommand(DBSession dbSession) at Microsoft.SqlServer.Management.SqlIMail.Server.Controller.CommandRunner.Run(DBSession db) at Microsoft.SqlServer.Management.SqlIMail.IMailProcess.ThreadCallBack.MailOperation(Object o)

Error: 14667, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.

whenever it is trying to send an email. The only way to get this to start sending mail is to run the databasemail90.exe file, so the profiles security etc seem ok. It's just that after the SQL box gets restarted

that it gives all these problems and then it needs some tinkering before it starts to work again.

So anybody got any ideas or tops on what can be done to help sort this out?

Thanks!

[1729 byte] By [TheVB] at [2007-12-22]
# 1
I'm having same exact issue. Opened a case with MS today. On the phone 3+ hours with no luck yet. They are looking into it. How exactly did you run the databasemail90.exe? i tried from command prompt as well as double-clicking in Windows and no mail yet. If I get this resolved, I'll post back
UDSMR at 2007-8-30 > top of Msdn Tech,SQL Server,SQL Server Setup & Upgrade...
# 2

Got same issue!!

tried running that file no help although I seem to be able to make it work by trying different accounts to send the mail but once box is restarted email won't work.

any resolution ?

baseballguru at 2007-8-30 > top of Msdn Tech,SQL Server,SQL Server Setup & Upgrade...
# 3

I also have contatced Microsoft and spent about 2 hours run test apps and sending then logs and other data for them to look through.

Still no resolution insight.

baseballguru at 2007-8-30 > top of Msdn Tech,SQL Server,SQL Server Setup & Upgrade...
# 4
well apparently MS has reproduced the error. the tech left me a vm late last night. i will follow up with him today and post back any details.
UDSMR at 2007-8-30 > top of Msdn Tech,SQL Server,SQL Server Setup & Upgrade...
# 5
Well after countless hours on the phone with MS (probably 40+ hours), it appears the issue is because of our firewall. I am sending the email from a remote network through my local SMTP server (Not Exchange). There is a known issue with ESMTP and PIX firewalls. We are using a PIX 515E. The SMTP log on the mail server kept showing XXXX instead of EHLO when the connection came from the remote SQL server. I typed the following on my pix and i can successfully send mail no fixup protocol smtp 25. There is also a MS article (of course nobody there directed me to it) at this site : http://support.microsoft.com/kb/320027. I really hope this info helps. I'm finding out if adding that command will impact my security from the firewall side. I will try to post back.
UDSMR at 2007-8-30 > top of Msdn Tech,SQL Server,SQL Server Setup & Upgrade...
# 6

The article is no longer available. I have the same error with mirroring rather than mailer.

I just got this error on a mirrored server; which caused the princliple databases to suspend, disconnect and one to go into recovery. Rebooted the mirrored server and the principle databases synced up again. {flacky}

Error: 17300, Severity: 16, State: 1. (Params:). The error is printed in terse mode because there was error during formatting. Tracing, ETW, notifications etc are skipped.

hizzel at 2007-8-30 > top of Msdn Tech,SQL Server,SQL Server Setup & Upgrade...

SQL Server

Site Classified