SQL Server Assertion: File: <subpmgr.cpp>

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

Data Corruption Issues

SQL Server Assertion: File: <subpmgr.cpp>

Author

Topic

uofmoo
Starting Member

6 Posts

Posted - 2009-01-19 : 02:10:14

Every few days for a couple weeks now we are getting production SQL Server randomly shutting itself down.

The 3 errors we receive in the Application Logs:
(1) SQL Server Assertion: File: <subpmgr.cpp>, line=1814 Failed Assertion = 'SOS_Task::GetCurrent() == m_parentTask'. 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.
(2) A system assertion check has failed. Check the SQL Server error log for details
(3) SQL Server Assertion: File: <subpmgr.cpp>, line=753 Failed Assertion = 'SOS_Task::GetCurrent() == m_parentTask'. 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 have run DBCC CHECKDB on all databases and they return no errors or consistency problems. I don't see any hardware problems in device manager or in the logs. It appears this happens at night but not always at the same time (9pm, 1am, etc).

Advice?
Troubleshooting help?

System:
Windows NT 5.2 Build 3790: SP1
SQL Server 2005 9.00.2153.00 X86

This is a system that I have taken over recently, and just about everyone and their dog have access to it, but it is critical to the business (go figure). We ordered new servers but a migration will take some time. Anything we can do in the meantime? Is there a way to send myself an alert when it shuts down so I can restart the service? Is there reason to be rebooting the server each time (as per "restart the server" in the error message)?

Thanks!!!

paulrandal
Yak with Vast SQL Skills

899 Posts

Posted - 2009-01-19 : 11:15:33

Call Product Support - this looks like a bug.

Paul S. Randal, Managing Director, SQLskills.com (www.SQLskills.com/blogs/paul)
SQL Server MVP, Contributing Editor of TechNet Magazine
Author of SQL 2005 DBCC CHECKDB/repair code
Author & Instructor of Microsoft Certified Master - Database course

sunil_mouje
Starting Member

1 Post

Posted - 2010-03-22 : 01:41:37

Hi,

did you find solution to this problem. We have the same problem.

Sunil

GilaMonster
Master Smack Fu Yak Hacker

4507 Posts

Posted - 2010-03-22 : 03:40:47

Same advice as Paul gave. Call customer support.

--
Gail Shaw
SQL Server MVP

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources