We're moving a SQL 2005/Windows 2003 process to SQL 2008 R2/Windows 2008 and are having a devil of a time making it work. It runs in 2005 just dandy. SQL Server 2008 R2 (64-bit) is running on a virtual machine, everything is new.
Standard SQL server install. No service packs.
I'm running several stored procedures from one script from SSMS. The script pretty much bombs after the same Stored Proc everytime, although not always. The sql error message is as follows:
- A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)
Why would it disconnect and reconnect in the middle of the script?
Perhaps a red herring but the one of the steps before the error happens is a clr stored proc job surrounded by SQL code that turns Trustworthy On/Changes Owner to 'sa' and back (Owner to NT Authority\System / Trustworthy
A real head scratcher.
Error in Windows Application Log
Faulting application name: sqlservr.exe, version: 2009.100.1600.1, time stamp: 0x4bb6b40b<
View Complete Post