Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Timeout expired. The timeout period elapsed prior to completion of the operation or the server is...


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

Author
Message
Mani-584606
Mani-584606
Mr or Mrs. 500
Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)Mr or Mrs. 500 (590 reputation)

Group: General Forum Members
Points: 590 Visits: 1998
Hi,

We have log shipping configured in SQL Server 2008 R2 SP2.

Log shipping copy job is failing and I'm getting the below error most of the times when I'm trying to see the view history for that job.

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

and sometimes it's showing the actual error as below:

Message
2012-08-07 13:01:52.03 *** Error: The handle is invalid.
(mscorlib) ***


Please advise.
Orlando Colamatteo
Orlando Colamatteo
SSCrazy Eights
SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)

Group: General Forum Members
Points: 8249 Visits: 14368
This may be the GUI tming out trying to build the job history due to too much volume, or a slow or overburdened server. Does your server generate a lot of job history? When is the last time you cleaned it out?

-- delete all job history older than a couple weeks, adjust to suit

DECLARE @dt DATETIME ;
SET @dt = DATEADD(day, -15, GETDATE())

EXEC msdb.dbo.sp_purge_jobhistory
@oldest_date = @dt ;
GO



__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
pnaveenkumar.reddy405
pnaveenkumar.reddy405
Grasshopper
Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)

Group: General Forum Members
Points: 13 Visits: 45
even i am facing the same problem..and the sql server machines i have are..newly created ones,how do i have any job history....?
please recommend any other solution....
thank you
P.Naveen kumar reddy
Orlando Colamatteo
Orlando Colamatteo
SSCrazy Eights
SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)

Group: General Forum Members
Points: 8249 Visits: 14368
How new? Log Shipping jobs can fill up the job history in a hurry. So can jobs with very frequent schedules, e.g. run every 15 seconds. Have you checked the job history directly via the tables in msdb? There are many reasons why the UI can timeout. Is your server extremely busy?

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
pnaveenkumar.reddy405
pnaveenkumar.reddy405
Grasshopper
Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)

Group: General Forum Members
Points: 13 Visits: 45
not at all busy......it's all a new configured ones....no transaction ran except a few before a full backup taken.....no work currently is being done on it.............?
Orlando Colamatteo
Orlando Colamatteo
SSCrazy Eights
SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)

Group: General Forum Members
Points: 8249 Visits: 14368
Did you check the job tables to see what was in them? If you're running replication or log shipping or other subsystems you might be surprised at what is in there.

Like I said, if it's not job history it could be any number of other things including your install of SSMS or other client/network conditions.

Google for ssms times out job history and you may find a nice workaround or two that you like better.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
pnaveenkumar.reddy405
pnaveenkumar.reddy405
Grasshopper
Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)

Group: General Forum Members
Points: 13 Visits: 45
yes i did check everything.....after all i didn't configure any.....?i have all protocols,remote admin connections,query governor cost limit enabled for sure.....
Orlando Colamatteo
Orlando Colamatteo
SSCrazy Eights
SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)

Group: General Forum Members
Points: 8249 Visits: 14368
All I can say is look for a workaround because there is no way for us to know what is happening in your environment as there are too many variables.

If you see the results of the link I posted there is a Connect item open for this exact issue and Microsoft says performance was improved in SSMS 2012.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
pnaveenkumar.reddy405
pnaveenkumar.reddy405
Grasshopper
Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)Grasshopper (13 reputation)

Group: General Forum Members
Points: 13 Visits: 45
a last thing....what would be the possible error reason for a newly installed sql server machine with no job alerts n nothing in it....?if i am configuring it for the first time.............?
thank you
P.Naveen kumar reddy
Orlando Colamatteo
Orlando Colamatteo
SSCrazy Eights
SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)SSCrazy Eights (8.2K reputation)

Group: General Forum Members
Points: 8249 Visits: 14368
Could be lots of things. Some are related to SQL Server, some related to your environment at large, e.g. network issues, slow server in general due to non SQL Server processes, blocking on the server due to activity in msdb although you're saying there are no scheduled jobs (which begs the question, why are you trying to view job history). The issue you're experiencing is usually related to an over-abundance of job history, however if that is not the issue then there are simply too many possibilities and without having direct access to your environment to start testing some things I cannot even venture a valid guess at what it could be...good luck.

__________________________________________________________________________________________________
There are no special teachers of virtue, because virtue is taught by the whole community. --Plato
Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search