Transport-level error has occurred...No Process is on the other end of the pipe upon first ExecuteQuery() after successful connect.

Question

I’m running MS SQL Server 2005, Express Edition, SP3 on Windows XP.  Local connections only. 
In preparation to restore a database, I use IWSQLDMOServer::KillProcesses() to allow the database restore.  (IWSQLSMOResore::SQLRestore())   The restore is successful and I appear to be able to connect OK.  (No error indication on the
connect)  However, the first time I try to use the database via an ExecuteQuery() the call fails and the connection state is changed to Closed.  I also get the “Transport-level error has occurred...No Process is on the other end of the pipe” exception.
Closing and restarting the application fixes the problem.
Also, disconnecting and reconnecting twice before the ExecuteQuery() call also fixes the problem. 
So, I can hide the problem by connecting twice, but I am hoping there is a better solution.
Walter Eykel

Answer 1

It appers when you connect for the restore process, you are opening a different session than that of the original one, with a different database context.
The first time you try to execute a query, you attempt to use the session that was open BEFORE the KillProcesses() call and therefore was killed. By the time you run the first time, your client is informed that the previous session is no longer available.
In the second time, as your client was informed that the original session was killed, it opens a new one.
Its the same behavior as in SSMS.
As a workaround, you could change your database context of your
current session to a base that wont be restored, call the restore methods, and then switch back to the original database context.