June 28, 2013 at 6:42 am
Hi,
I have a new
Microsoft SQL Server 2012 (SP1) - 11.0.3000.0 (X64)
Oct 19 2012 13:38:57
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1)
While trying to alter sp_db_mail, my dbmail stopped working. I am getting below error in logs:
Message
1) Exception Information
===================
Exception Type: Microsoft.SqlServer.Management.SqlIMail.Server.Common.BaseException
Message: The Transaction not longer valid.
Data: System.Collections.ListDictionaryInternal
TargetSite: Void ValidateConnectionAndTransaction()
HelpLink: NULL
Source: DatabaseMailEngine
StackTrace Information
===================
at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.ConnectionManager.ValidateConnectionAndTransaction()
at Microsoft.SqlServer.Management.SqlIMail.Server.DataAccess.ConnectionManager.RollbackTransaction()
at Microsoft.SqlServer.Management.SqlIMail.IMailProcess.QueueItemProcesser.GetDataFromQueue(DataAccessAdapter da, Int32 lifetimeMinimumSec)
at Microsoft.SqlServer.Management.SqlIMail.IMailProcess.QueueItemProcesser.ProcessQueueItems(String dbName, String dbServerName, Int32 lifetimeMinimumSec, LogLevel loggingLevel, Byte[] encryptionKey, Int32 connectionTimeout)
Steps I have tried after this issue:
1) Recreated send_db_mail procedure from instance running on 2012
2) Stopped and Started DB mail using sysmail_stop_sp and sysmail_start_sp
3) Checked that service broker is running
4) SMTP is working fine as DBMAIL using this SMTP on other server are running fine
5) Deleted all unsent emails
6) Rebooted the server/services/agent
7) Anti-virus also seems to be okay as only this server is throwing errors
8) Replaced databasemail.exe and other *.dll's from other 2012 server
Any help would be appreciated!
Thanks
Cheers
August 13, 2013 at 5:07 am
Hello,
i have the exact same scenario and problem.
Browsed the web for days and only found outdated threads (2008... 2005... 2003).
Can someone provide an idea?
Thx
P
August 13, 2013 at 5:26 am
Some people are plain lucky.... This was a pre production box... I solved this by Reinstalling SQL server 😀
Cheers
August 13, 2013 at 6:36 am
Somehow I had this ...feeling..., that it would be the ..."solution"... 😛 (as always)
Anyway thanks.
At least this gives my mind a little peace... and a task for next nightshift 😉
Regards
Peter
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply