February 2, 2009 at 12:13 pm
We have sql server 2005 with SP2. All of a sudden , we are unable to access any of the databases. I went into the box and looked at the services. The services were running fine. But our applications are unable to access the server. When i try to connect using Management studio I'm getting the following error "[298] SQLServer Error: 233, Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]" . I thought this is a memory issue. But our server is configured for AWE and the max memory option is set to 26 gigs. I'm unable to figure out what caused this. Someone please help.
February 2, 2009 at 12:21 pm
When you configured SQL Server 2005 did you enable DAC? If so, can you connect using it?
February 2, 2009 at 12:29 pm
No I did not. But even if I have enabled DAC, I have restart the service with flag 7806 right. When I restart the service, my sql server started working.
February 2, 2009 at 12:38 pm
I think that may only be true on Express. I have DAC enabled on our servers and have tested connection to it without having to restart the servers with a trace flag.
February 2, 2009 at 12:39 pm
Ok I will try that. But do you know why i get the error with the sql server that I mentioned before?
February 2, 2009 at 12:39 pm
Yes, Lynn is correct. No need for the trace flag.
Do you have any errors in the SQL Server Error Log or the Windows application log?
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
February 2, 2009 at 12:46 pm
Not an error I have experienced. I'm with DavidB, what do the SQL Server and Windows logs show at the time the server stopped responding?
February 2, 2009 at 12:54 pm
[252] Failed to retrieve operator 1 from the server
[298] SQLServer Error: 233, Shared Memory Provider: No process is on the other end of the pipe. [SQLSTATE 08S01]
Message
[298] SQLServer Error: 233, Communication link failure [SQLSTATE 08S01]
[382] Logon to server 'MDTDB1' failed (ConnAttemptCachableOp)
This what I found in error log.
In windows event 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: ].
February 2, 2009 at 1:02 pm
Just a note, but just because AWE is enabled and you have 26 Gig allocated doesn't mean that you are covered completely from the memory needs of an instance. There are many things that actually just operate in the Virtual Address Space which is only 2 Gig in the 32 Bit environment so, there could still be memory pressure occurring on the instance. There are some pretty solid white papers and blogs on MS related sites to help diagnose some of these items which might be worthwhile to look into.
Hope this helps. I can try to dig up some links if you can't come up with anything.
David
@SQLTentmaker“He is no fool who gives what he cannot keep to gain that which he cannot lose” - Jim Elliot
February 2, 2009 at 1:09 pm
SQL Server failed with error code 0xc0000000 to spawn a thread to process a new login or connection.
I have seen that error when other processes consume lots of memory and leave SQL Server in a bad state.
Like, copying Backup Files from the Server to a share, sp_OA procedures etc...
* Noel
February 2, 2009 at 1:13 pm
We have logshipping going on in our database. Do you think that might have caused this issue? Other than that we don't have anything going on at the time this happened. Also our whole server is dedicated to this one isntance.
Viewing 11 posts - 1 through 10 (of 10 total)
You must be logged in to reply to this topic. Login to reply