September 6, 2012 at 7:46 pm
hello,
there were SAN issues on the server where E: and F: became unavailable.
we realized this when the log backups were failing.
now that the drives are back online this is the error when a db is being accessed:
[font="Courier New"]Msg 233, Level 20, State 0, Line 0
A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
[/font]
is a SQL Server instance restart all that is needed?
I'm worried the databases would come up as suspect.
thank you
September 6, 2012 at 10:03 pm
I think that you would be OK to simply restart SQL Server.
However, to be safe, take a backup of the files on drive E: and F: first (with SQL Server stopped). That way, if something isn't quite right you do have a chance to try again.
September 7, 2012 at 1:42 am
sierra4 (9/6/2012)
hello,there were SAN issues on the server where E: and F: became unavailable.
we realized this when the log backups were failing.
now that the drives are back online this is the error when a db is being accessed:
[font="Courier New"]Msg 233, Level 20, State 0, Line 0
A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)
[/font]
is a SQL Server instance restart all that is needed?
I'm worried the databases would come up as suspect.
thank you
Your SSMS session is disconnected, close SSMS and re open and then connect reconnect to the server
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply