[2 days left] What’s wrong with your cloud strategy? Learn why multicloud solutions matter with Nimble Storage.Register Now

x
?
Solved

SBS 2003 Server Status Report critical error

Posted on 2009-03-30
3
Medium Priority
?
609 Views
Last Modified: 2012-05-06
I am running WSUS 2.0 on SBS 2003.  Over the last month or so, every few days I receive the following critical error in my Server Status Report:

Server Status Report:
  URL: http://localhost/monitoring/perf.aspx?reportMode=1&allHours=1 
  Error Message: Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
  Stack Trace: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, TdsParserState state)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, TdsParserState state)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
at System.Data.SqlClient.TdsParser.ReadNetlib(Int32 bytesExpected)
at System.Data.SqlClient.TdsParser.ReadBuffer()
at System.Data.SqlClient.TdsParser.ReadByteArray(Byte[] buff, Int32 offset, Int32 len)
at System.Data.SqlClient.TdsParser.ReadString(Int32 length)
at System.Data.SqlClient.TdsParser.ReadValue(_SqlMetaData md, Int32 length)
at System.Data.SqlClient.TdsParser.ProcessRow(_SqlMetaData[] columns, Object[] buffer, Int32[] map, Boolean useSQLTypes)
at System.Data.SqlClient.SqlDataReader.PrepareRecord(Int32 i)
at System.Data.SqlClient.SqlDataReader.GetValue(Int32 i)
at Microsoft.UpdateServices.Internal.DatabaseAccess.GenericReadableRow.ReadRow(IDataRecord record)
at Microsoft.UpdateServices.Internal.MultipleResultSetsSPHandler.ExecuteStoredProcedure(DBConnection connection)
at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler, Int32 queryTimeoutInSeconds)
at Microsoft.UpdateServices.Internal.GenericDataAccess.ExecuteSP(String spName, DBParameterCollection args, IExecuteSPHandler handler)
at Microsoft.UpdateServices.Internal.DataAccess.ExecuteSPMultipleResultSets(String spName, DBParameterCollection args, Type[] resultTypes)
at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPCompleteUpdatesResult(String spName, DBParameterCollection args)
at Microsoft.UpdateServices.Internal.DatabaseAccess.AdminDataAccess.ExecuteSPGetAllUpdates(String preferredCulture, Int32 approvedStates, DateTime fromSyncDate, DateTime toSyncDate, Guid[] updateCategoryIds, Guid[] updateClassificationIds, Int32 publicationState)
at Microsoft.UpdateServices.Internal.BaseApi.Update.GetAll(ApprovedStates approvedStates, DateTime fromSyncDate, DateTime toSyncDate, UpdateCategoryCollection updateCategories, UpdateClassificationCollection updateClassifications, ExtendedPublicationState publicationState)
at Microsoft.UpdateServices.Internal.BaseApi.Update.GetAll(ApprovedStates approvedStates, DateTime fromSyncDate, DateTime toSyncDate, UpdateCategoryCollection updateCategories, UpdateClassificationCollection updateClassifications)
at Microsoft.UpdateServices.Internal.BaseApi.UpdateServer.GetUpdates(ApprovedStates approvedStates, DateTime fromSyncDate, DateTime toSyncDate, UpdateCategoryCollection updateCategories, UpdateClassificationCollection updateClassifications)
at Microsoft.SBS.UpdateServices.DataProvider.GetScheduledUpdates()
at Microsoft.SBS.UpdateServices.StatusPage.Utility.GetStatusItems()
at usage.frmPerf.PopulateStatusItems()
at usage.frmPerf.renderReportWorker()
at usage.frmPerf.renderReport()

I receive a daily email of this report and when the error has occurred, the email says "The page cannot be displayed" and asks that I check a number of items.  I have researched this issue previously and have tried a number of things suggested solutions including re-running the ,"Set up Monitoring Reports and Alerts" wizard, running WSUSUtil deleteunneededrevisions, and restarting the server.  The day after running any of these, everything appears fine, but the following day the error recurs. Can someone please tell me what's happening here and  provide a long term solution?  Thanks.
Michael
0
Comment
Question by:msklein
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 47

Expert Comment

by:Donald Stewart
ID: 24021253
From here:

http://www.wsus.info/forums/lofiversion/index.php?t6658.html

Timeout Expired Error

Here is a break down of the fix:

1) Create a text file named addDeploymentIndex.sql

2) Add the following text to the sql file:
    USE SUSDB
    GO
    BEGIN TRAN
    IF NOT EXISTS (SELECT * FROM sysindexes where name='nc7DeploymentRevision')
    BEGIN
         CREATE NONCLUSTERED INDEX nc7DeploymentRevision ON dbo.tbDeployment(RevisionID, TargetGroupID, ActionID)
    END
    COMMIT TRAN
    GO
(note: the "create nonclusted" line probably word wrapped in this post... it will need to be one long line ending with "actionid)")

3) Place the file in c:\program files\update services\tools\osql.

4) On the WSUS server, open the command prompt and move to the osql directory. Run the following command:

    osql -E -S%servername%\WSUS -n -b -i addDeploymentIndex.sql

(note: %servername% is the name of your wsus server... there is no space between -S and the name, but I'm not sure if it is case sensitive or not... i used all caps for the name, and it seemed to work)

5) The script will run, then return you to command prompt. You will not get any notification if it was successful, but it will notify you if there are errors.

 You will need to run this script on each of your WSUS servers that are using MSDE, then synch them. You should see and immediate speed difference in approvals and server synchs. I hope this information helps!
0
 

Author Comment

by:msklein
ID: 24988676
It has taken me this long to try your solution as the error has started occurring every day.  I copied and pasted everything you wrote and ran as you suggested.  Unfortunately, it didn't correct the problem.  I used the non-fully qualified name for the server, i.e., I used SERVER01 instead of SERVER01.company.local.  Would this have made a difference?
0
 
LVL 47

Accepted Solution

by:
Donald Stewart earned 2000 total points
ID: 24990635
Upgrade your WSUS to version 3.0 and this should resolve the issue
 
http://www.microsoft.com/downloads/details.aspx?FamilyId=F87B4C5E-4161-48AF-9FF8-A96993C688DF&displaylang=en 
0

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Introduction At 19:33 (UST) on Tuesday 21st September the long awaited email arrived with the subject title of “ANNOUNCING THE AVAILABILITY OF WINDOWS SBS 7 PREVIEW”.  It was time to drop whatever I was doing and dedicate as much bandwidth as possi…
The problem of the system drive in SBS 2003 getting full continues to be an issue, even though SBS 2008 and SBS 2011 are both in the market place.  There are several solutions to this, including adding additional drive space or using third party uti…
In this video, Percona Director of Solution Engineering Jon Tobin discusses the function and features of Percona Server for MongoDB. How Percona can help Percona can help you determine if Percona Server for MongoDB is the right solution for …
In this video, Percona Solutions Engineer Barrett Chambers discusses some of the basic syntax differences between MySQL and MongoDB. To learn more check out our webinar on MongoDB administration for MySQL DBA: https://www.percona.com/resources/we…
Suggested Courses

656 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question