Time out replicate in lower environment

Question

1.00/5 (2 votes)

See more:

Hi All,

I have one scheduled job which is running every day at a scheduled time. It started suddenly throwing the time out error since a week. I changed the application to send a stack trace to me in mail so that I can debug it. Below is the stack trace.

===Stack Trace===
   at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()
   at System.Data.SqlClient.SqlDataReader.get_MetaData()
   at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
   at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result)
   at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method)
   at System.Data.SqlClient.SqlCommand.ExecuteReader()
   at ABC.Program.Run_Report() in XXX.exe :line 8122

===Error Message===
Timeout expired.  The timeout period elapsed prior to completion of the operation or the server is not responding.

===Error Source===
.Net SqlClient Data Provider

I am unable to replicate the issue in UAT server . Can some one please help me in understanding this stack trace so that I can replicate it.

Posted 3-Aug-15 13:32pm

Prashant Bangaluru

Updated 1-Oct-15 19:02pm

v2

Add a Solution

Comments

ZurdoDev 3-Aug-15 19:41pm

SQL is timing out.

Prashant Bangaluru 3-Aug-15 19:43pm

Thanks for your comments. Is it because of query taking long time or any deadlocks?

ZurdoDev 3-Aug-15 19:45pm

No way to tell from this. Timeouts can results from either long time or deadlocks. I'd suggest looking in your sql logs as well to see if there is more details.

Prashant Bangaluru 3-Aug-15 19:59pm

Oh yeah.. Thanks for that.. I will verify the logs and update you.

Prashant Bangaluru 3-Aug-15 21:21pm

Hi Ryan, Looks like these details are not logged neither in SQL log nor in EventViewer.
Do you have any idea how to get that?

barneyman 3-Aug-15 22:27pm

sql server profiler

SundararamanS 4-Aug-15 1:31am

right ...please check this https://msdn.microsoft.com/en-us/library/ms181091.aspx
&& https://msdn.microsoft.com/en-us/library/ms189604.aspx

Prashant Bangaluru 2-Sep-15 23:09pm

Sorry the job runs monthly once .. I ran the profiles but ddnt find anything.. How can I share the profiler details here

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Member 12003400 · Answer 1 · 2015-10-03T01:23:00

Solution 2

Certain possibilities,
1. SQL query taking too long
2. Dead lock

First use sql logger.
Find specific one by one query, try to run in sql and check how much time it is taking to execute,
Try to write your query with nolock function, which will resolve your deadlock problem.

Posted 3-Oct-15 1:23am

Member 12003400

Updated 3-Oct-15 1:50am

v4