Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2006-10-02 : 07:55:53
|
| Scott writes "Hello!We've devoted a resource to this today, as my initial belief was that it's something easy that we're overlooking. But, we've scoured the Web and all of your links above. People are talking about the issue, but no one has posted a solution.The scneario is that we have a production Web application that until last weekend had a SQL 2000 back end. This weekend we installed a new instance of SQL 2005 and everything works (we tested in a sandbox environment, but someone must not have load tested enough) and never saw these exceptions. So, after the upgrade we now receive 100's of thexe excptions per day from our application:1. A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)2. A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The specified network name is no longer available.)The OS is MS Windows Server 2003 and the SQL Server version is SQL 2005 (we do not receive this exception in 2000 with the same application in front of it)After folling the instructions above (to search the world before posting here, this was the only post that seemed to make progress, but it was left unanswered:http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=134053&SiteID=17&PageID=1Thanks for any help!" |
|
|
|
|
|
transport-level error after creating new SQL 2005 instance.