January 13, 2009 at 3:41 pm
We are getting different errror on application server log. The errors are as follows
Error msg1:
1/13/2009 7:53:28 PM:File Error - Handle Work Item Failed: Exception - System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Error msg2:
1/6/2009 9:07:32 AM:Exception Error - Workflow 00000000-0000-0000-0000-000000000000 ServicesExceptionNotHandled: System.Data.SqlClient.SqlException: A transport-level error has occurred when sending the request to the server. (provider: TCP Provider, error: 0 - An existing connection was forcibly closed by the remote host.)
Error msg3:
1/9/2009 6:03:08 AM:Exception Error - Workflow 80f35c78-9dc0-4ceb-8e39-98309db49ea9 WorkflowTerminated: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> BlueDot.Mnow.Server.DataAccess.RepositoryFailureException: Unexpected error occurred in the database server ---> System.Data.SqlClient.SqlException: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Is there anything i can check on the database server? I think there is not much to check on sql server side because error occurs only one or twice a week. Rest of the time the connection is fine.
There are two instance of Ent sql server installed on the server Both working on port 1433.
I think it is a network issue or application issue. I would really appreciate if anyone can help me with this.
January 14, 2009 at 1:38 pm
Sorry about the wrong information. Default instance is running on port 1433 and named instance is running on dynamic port.
January 14, 2009 at 1:41 pm
The connection of the The App was killed !
You should start by verifying what was going on on the server at that time!
* Noel
January 14, 2009 at 1:51 pm
The message saying the connection was forcefully closed usually means that either the connection was explicitly killed by someone, or the query hit a high severity error and was disconnected.
Both of those will be reflected in the SQL error log. Check there.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 14, 2009 at 2:06 pm
How can i verify what is going on the server? I checked the error log, there is nothing there.
Should I turn on the profiler? What event should i capture in profiler?
January 14, 2009 at 2:58 pm
I set the profiler to audit fail login, login, sql:batchstarting, sql:batchcompleted.
Do i need to collect some other events?
January 14, 2009 at 11:55 pm
The error events. Exception, errorlog, user error message, attention. There may be some others worth checking.
How long are you planning running profiler for?
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
January 15, 2009 at 8:39 am
I have set the profiler for error event.
I am planning to run profiler until erorr occurs again and application stops sending updates. Is that OK?
January 19, 2009 at 10:34 am
what event i have to start to collect information regarding network issues?
I hope this is not sql server isssues or port issue.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply