November 12, 2008 at 12:42 pm
While calling a remote store proc, i.e.
insert into table (col_1, col_2, ... , col_x)
execute remoteservername.remotedb.dbo.sp_get_some_data
I got the following error:
Event Type: Error
Event Source: MSSQLSERVER
Event Category: (2)
Event ID: 17066
Date: 11/12/2008
Time: 11:09:56 AM
User: PFSNET\SRVADMIN
Computer: MAC-2K-SRVR
Description:
SQL Server Assertion: File: FHasWorkspaceRef ()'. This error may be timing-related. If the error persists after rerunning the statement, use DBCC CHECKDB to check the database for structural integrity, or restart the server to ensure in-memory data structures are not corrupted.
---------
I happened to have that particular call in a try/catch block, and this is what the catch caught:
ERROR_NUMBER: 3985
SEVERITY: 16
ERROR LINE: 71
ERROR MESSAGE: An error occurred during the changing of transaction context. This is usually caused by low memory in the system. Try to free up more memory.
I've run the DBCC check and everything looks good, and as far as I can tell I've got tons of free memory on that box. Was just curious if anyone had ever seen that error. It's a new one on me.
The Redneck DBA
November 12, 2008 at 12:45 pm
Never seen that. Can you reboot to see if it clears? I know that's not a good way to handle this, but I'm curious to see if it goes away and if this can be reproduced.
November 12, 2008 at 12:59 pm
Had quick look around it seems to be from linked server
November 12, 2008 at 1:00 pm
I'll see if our hardware guys are cool with a reboot.
I've re-run that query many times and can't get it to reproduce. But then that would be too easy.
The Redneck DBA
November 12, 2008 at 1:04 pm
TRACEY (11/12/2008)
Had quick look around it seems to be from linked server
Interesting. I hadn't seen that one. It doesn't 100% match my symptoms, but I've got 2/3.
I have Cum. update 8, and this says Cum. 9 fixes it.
I was just eyeballing SP3 and wondering when it's going to move out of CTP status and be ready for prime time. Perhaps that will fix it.
The Redneck DBA
November 12, 2008 at 1:12 pm
Reboot always fixes it - could have just been a record that was trying to be hit and deleted something like that....I would do a dbcc checkdb on the database also just to make sure no hinky errors too.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply