Error: 3910, Severity: 16, State: 1

Question

Error: 3910, Severity: 16, State: 1

gary1

SSC-Insane

Points: 21152
More actions
March 2, 2015 at 10:11 am

#295673

Hi,
We have SQL Server 2008 R2 with SP3. We are getting below error in errorlog. Can you please advise if it is a known bug?
2015-02-28 07:30:44.53 spid109 DBCC CHECKDB (DB1) WITH all_errormsgs, no_infomsgs, data_purity executed by abc\sqlservice found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 3 seconds. Internal database snapshot has split point LSN = 0000002f:000199ca:0001 and first LSN = 0000002f:000199c9:0001.
2015-02-28 07:33:09.60 spid11s Error: 3910, Severity: 16, State: 1.
2015-02-28 07:33:09.60 spid11s Transaction context in use by another session.
2015-02-28 07:33:09.60 spid12s Error: 3910, Severity: 16, State: 1.
2015-02-28 07:33:09.60 spid12s Transaction context in use by another session.
Thanks

Viewing 6 posts - 1 through 5 (of 5 total)

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

sql-lover SSCoach Points: 18530 More actions · Answer 1

gary1 (3/2/2015)
Hi,
We have SQL Server 2008 R2 with SP3. We are getting below error in errorlog. Can you please advise if it is a known bug?
2015-02-28 07:30:44.53 spid109 DBCC CHECKDB (DB1) WITH all_errormsgs, no_infomsgs, data_purity executed by abc\sqlservice found 0 errors and repaired 0 errors. Elapsed time: 0 hours 0 minutes 3 seconds. Internal database snapshot has split point LSN = 0000002f:000199ca:0001 and first LSN = 0000002f:000199c9:0001.
2015-02-28 07:33:09.60 spid11s Error: 3910, Severity: 16, State: 1.
2015-02-28 07:33:09.60 spid11s Transaction context in use by another session.
2015-02-28 07:33:09.60 spid12s Error: 3910, Severity: 16, State: 1.
2015-02-28 07:33:09.60 spid12s Transaction context in use by another session.
Thanks

What makes you believe is a bug? Did you have that error before or just now? How long ago that you upgraded to SP3?

Also, did you run a DBCC CHECKDB or DBCC UPDATEUSAGE yourself against that database? If you did, what was the result?

gary1 SSC-Insane Points: 21152 More actions · Answer 2

DBCC completed with no errors. Do you know what will be possible cause for this error?

Michael L John One Orange Chip Points: 27042 More actions · Answer 3

There are a number of references to this error, all related to the use if linked servers and how SQL Server handles loopback calls.

http://sqlblog.com/blogs/linchi_shea/archive/2009/12/18/the-transact-sql-prime-directive-a-bad-example.aspx

https://social.msdn.microsoft.com/Forums/sqlserver/en-US/13b6fa12-13a2-41e1-a581-3295adbccf69/transaction-context-in-use-by-another-session

There are more, Google this.

The thing that throws me about this error is that the spid is 11, which is a system SPID.

Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/

gary1 SSC-Insane Points: 21152 More actions · Answer 4

We are not using linked servers. This sql instances hosts SharePoint Databases.

Michael L John One Orange Chip Points: 27042 More actions · Answer 5

Well, looking on MS's support site, and a few other sites, this is typically caused by a linked server, or, MSDTC.

Run this:

SELECT @@SERVERNAME

And this

SELECT * FROM sysservers

Does the result from the first query match the first entry of the second?

Michael L John
If you assassinate a DBA, would you pull a trigger?
To properly post on a forum:
http://www.sqlservercentral.com/articles/61537/