January 12, 2010 at 12:21 am
hi to all,
i faced the situation is my production server is unexpectedly stopped, in my error log
SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems. [CLIENT: <local machine>]
Error: 17189, Severity: 16, State: 1.
this error was repeated so many times,
After some memory related checks,
"Message
There is insufficient system memory to run this query."
this is repeating.
and then
"During undoing of a logged operation in database 'tempdb', an error occurred at log record ID (224678:376:186). Typically, the specific failure is logged previously as an error in the Windows Event Log service. Restore the database or file from a backup, or repair the database."
"SQL Server must shut down in order to recover a database (database ID 2). The database is either a user database that could not be shut down or a system database. Restart SQL Server. If the database fails to recover after another startup, repair or restore the database."
what may be the cause?
Please help me.
🙂
January 12, 2010 at 12:39 am
Try checking with the system memory.
Set TempDB recovery mode to Simple.
Check the drives have enough space.
Cheers,
- Win.
" Have a great day "
January 12, 2010 at 12:43 am
thanks,
but all are well( as u said) , drivers memory is free, and tempdb in simple mode only,
🙂
January 12, 2010 at 1:29 am
Try to update the Services LogOn password again, if the services are running with any LogOn account. Restart the services once updated.
What is the exact error msg you are facing when u try to restart the services.
Post Windows log error and SQL error as well.
Cheers,
- Win.
" Have a great day "
January 12, 2010 at 1:48 am
it was started(manually restarted the service), but why it was unexpectedly stopped.
🙂
January 12, 2010 at 2:17 am
Check SQL Server Erroor Log for the exact error and reason.
Cheers,
- Win.
" Have a great day "
January 12, 2010 at 9:01 pm
hi,
these are the error what i observed in error log,
SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems. [CLIENT: <local machine>]
Failed Virtual Allocate Bytes: FAIL_VIRTUAL_RESERVE 1048576
Downgrading backup log buffers from 1024K to 64K
SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection. Check the SQL Server error log and the Windows event logs for information about possible related problems. [CLIENT: <local machine>]
There is insufficient system memory to run this query.
The Server was unable to load the SSL provider needed to login. SSL is used to encrypt either the login sequence or all communications, depending on how the administrator has configured the server. See Books Online for information on this error message: 0xe. [CLIENT: <local machine>]
Server is running low on virtual address space or machine is running low on virtual memory. Reserved memory used 1 times since startup. Cancel query and re-run, decrease server load, or cancel other applications.
🙂
January 12, 2010 at 9:33 pm
To check the memory usage of SQL Server, you can just simply look into Task Manager for SQL Server Memory and CPU utilization.
Pretty good error... let me check if i can provide any info...
Keep trying to find the cause...
Cheers,
- Win.
" Have a great day "
January 12, 2010 at 9:36 pm
But i can say a bit....
In your case restart of SQL Server services is not a final solution, you have to assess the baseline of performance monitoring of your application usage during less traffic hours & busy hours. For more information on Memory refer to
http://sqlserver-qa.net/blogs/perftune/archive/tags/memory/default.aspx links
http://www.sqlservermart.com/resources/SynAttackProtect.aspx
Just a try , hope these helps.
Cheers,
- Win.
" Have a great day "
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply