Terry Good 
Australia
Member since
1/9/2007
Platinum Membership
Posts: 11
 |
| 7/24/2008 07:02 AM |
|
Hello,
I hope someone can help please.
I have an SBS Server 2003 R2 that has been working fine.
Last week the server had a bit of a hiccup and had to be restarted after a lockup.
Since then the SBS monitoring refuses to work and the daily reports only send out the following:
The page cannot be displayed
An error occurred on the page you are trying to view.
--------------------------------------------------------------------------------
To work around this problem, perform the following steps. After each step, try again to access the page.
Ensure that the MSSQL$SBSMONITORING service is started.
Ensure that the server is not low on memory or disk space.
Restart the server.
Verify that the server is functional and that there are no system-wide problems.
Run the Set Up Monitoring Reports and Alerts task in the Server Management Monitoring and Reporting taskpad.
I have done all of the above..
The services are all started and running but no reports are being generated.
Does anyone have any ideas on how to fix this.
Thanks in advance
Terry
|
|
|
|
|
|
John Wilt
United States
Member since
5/21/2008
Registered Users
Posts: 12
|
| 7/24/2008 04:39 PM |
|
| I had a similar problem, but that is a different topic. Make sure the directories are still there, c:\program files\ms sql server\mssql$sbsmonitoring\data, make sure the DB are in there and there are are permissions on the folder. Anything in the event log? |
|
|
|
|
|
Terry Good
Australia
Member since
1/9/2007
Platinum Membership
Posts: 11
|
| 7/25/2008 02:20 AM |
|
Thanks for the reply John,
The data bases seem to be Ok and permissions OK.
The problem started about the same time as the File Replication Service gave a low disk space error.
I got the client to delete some files and they now have nearly 4Gb Free Space (8% of drive size). No error message.
If I try to view the performance report via remote access it just times out.
I can look at the health monitor and get all green ticks..
I have attaced the performance report error message from server below:
Event Type: Error
Event Source: ServerStatusReports
Event Category: None
Event ID: 1
Date: 25/07/2008
Time: 6:03:14 AM
User: N/A
Computer: SERVER
Description:
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()
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
I have no idea where to start looking??
|
|
|
|
|
|
Dave Whyte
United Kingdom
Member since
1/4/2006
Registered Users
Posts: 6
|
| 7/25/2008 05:26 PM |
|
Hi,
I have exactly the same problem.
Could it be an issue with some of the recent SQL updates?
Are you using WSUS 3?
Did you reecently install updates?
Cheers,
Dave |
|
|
|
|
|
Steve McGrath
United States
Member since
6/23/2006
Platinum Membership
Posts: 49
|
| 7/28/2008 04:34 AM |
|
Me too, same error messages, tried the recommended fixes several time with no luck.
Started happening on two systems about 2 weeks ago or so.
Steve
|
|
|
|
|
|
Terry Good
Australia
Member since
1/9/2007
Platinum Membership
Posts: 11
|
| 7/28/2008 08:44 AM |
|
I have checked a lot of websites that host SBS issues and it would appear we are not on our own.
Not neccesarily that everyone gets the same error, some are getting companyweb errors as well.
Only thing thats common is that it was after the 15th of July.
I have another server that has developed the same issue after a reboot over the weekend.
Just hope that someone can sort it out soon.
|
|
|
|
|
|
Stephen Mullens
Melbourne
Member since
12/31/2006
Registered Users
Posts: 23
|
| 7/28/2008 02:57 PM |
|
Hi All
I have had this happen on 4 servers around the same time (only the monitoring) i assume it is a update that causes as the 4 servers i had updated had this problem, the 2 i have not are fine
I have fixed 2, another one will do tomorrow hopefully
To fix i uninstalled monitoring, 'Add/remove programs' then 'Windows small Buisness server' 'change/remove'
i set to Maintenance then remove Monitoring features only
i also removed the related Sql service, then i did a reboot i also ensured the following folder was removed once restarted(i had to delete on mine)
location for me was 'C:\Program Files\Microsoft Windows Small Business Server\Monitoring' (you may wish to rename instead)
i also made sure the monitoring folder was removed in IIS
then i reloaded using the method as above,(requires Disk 2)
I had to do twice on one server as it removed the Health Monitor, second time it reloaded
has been good since 2 out of 2 so far
Regards
Steve
|
|
|
|
|
|
Allan Brownsdon
Australia
Member since
1/8/2007
Platinum Membership
Posts: 96
|
| 7/30/2008 06:22 AM |
|
Hi Stephen et al,
A relief to know that others are struggling with this one also. I have not yet tried your fix, but am unclear about how to remove the "related SQL service" can you enlighten me please. Also can you clarify which version of WSUS you are using please.
More generally, I think the problem is related to an attempt to install patch KB948110. This fails on my server, but the problem occurred immediately after my first attempt to install the patch. Researching this failure suggests that many people are having problems with SBS and this patch and it is unclear how or whether we should install this patch. As far as I can tell this is a particular problem if we have a third party SQL service with a secured password. SOPHOS???? I'm not very clued in to SQL so making sense of all this does my head in. Anyone got any clues about this and whether it is related?
|
|
|
|
|
|
Dave Whyte
United Kingdom
Member since
1/4/2006
Registered Users
Posts: 6
|
| 7/30/2008 06:41 AM |
|
Hi all,
Has anyone having this problem had any other SQL symptoms?
However, these caps are now being ignored by some of the SQL instances, especially WSUS. It is capped at 256Mb but regularily grows to 300+. Firewall (ISA as a Premium box) is capped at 128 but grows to 150+. This is causing Allocated Memory warnings.
This has only started happening since the Monitoring issue and several patches including the mentioned SQL patch.
Thanks,
Dave
|
|
|
|
|
|
John Wilt
United States
Member since
5/21/2008
Registered Users
Posts: 12
|
| 7/30/2008 09:21 PM |
|
Well, you can adjust those warnings!! Also, I don't think that cap is a total max, I have seen servers fluctuate even with the cap. Now if you set that cap to like 150 and its 600 then I would worry.
My newest development is one of my servers asks for login information to view the reports. It doesn't matter what account I use, I can't login! I have gone under add/remove-windows sbs and removed monitoring for now. Gonna go back when I get time and put it back on. This server is a WSUS server |
|
|
|
|
|
Arco van de Weg
New Zealand
Member since
8/1/2008
Registered Users
Posts: 2
|
| 8/01/2008 10:28 PM |
|
Hello,
Had the same problem after applying some Windows security updates on SBS Std R2 at one customer, fortunately not with my other 4 customers.
Will try the fix suggested.
Also started to get the allocated memory messages as mentioned by others
Arkie
|
|
|
|
|
|
Dave Whyte
United Kingdom
Member since
1/4/2006
Registered Users
Posts: 6
|
| 8/12/2008 11:43 PM |
|
Hi all,
I have fixed the problem by running the 'Server Cleanup Wizaed' in WSUS console.
Also checked SQL memory issues and as John Wilst suggested, the memory allocated to each instance has settled down.
Try running the cleanup wizard with just the first box ticked, it may take overnight to run.
Dave
|
|
|
|
|
|
Allan Brownsdon
Australia
Member since
1/8/2007
Platinum Membership
Posts: 96
|
| 8/13/2008 09:28 AM |
|
Hi Dave,
Are you referring to WSUS 3.0? I'm still running WSUS 2.0 and could not find a cleanup wizard anywhere.
thanks, Allan
|
|
|
|
|
|
Arco van de Weg
New Zealand
Member since
8/1/2008
Registered Users
Posts: 2
|
| 8/13/2008 09:31 PM |
|
Hello Dave,
The one customer that has the problem is the only one running WSUS 2.0 all others are WSUS 3.0.
Arkie |
|
|
|
|
|
Dave Whyte
United Kingdom
Member since
1/4/2006
Registered Users
Posts: 6
|
| 8/13/2008 09:54 PM |
|
Hi Allan (and all), 
Yes, sorry I am referring to WSUS 3.0,
WSUS 2 needs command line stuff to do the cleanup.
Have a look at this:
and this:
Dave
|
|
|
|
|
|
Steve McGrath
United States
Member since
6/23/2006
Platinum Membership
Posts: 49
|
| 8/14/2008 09:19 PM |
|
This does seem like a patch issue. I have tow systems that were patch regularly and had the same problem at the same time, around mid-July. A third system that has not been patched in a while has not suffered from that problem.
However, using the Server Cleanup Wizard in WSUS 3.O does seem to have cured the problem on the first system that I tried it on. The wizard ran for more than a day and a half and finally terminated with a message that it lost connection. Even before it finished, hoewver, the monitoring function was back.
Steve
|
|
|
|
|
|
Allan Brownsdon
Australia
Member since
1/8/2007
Platinum Membership
Posts: 96
|
| 9/09/2008 07:13 AM |
|
I know this thread is a bit old now but wanted to report back and also to ask some advice.
Only this last weekend did I get a chance to follow up on this and I could not get WSUS 2.0 to cleanup following these links. I ran the WSUSUtil several (4 or 5) times and it would always timeout without completing. Finally in desperation I uninstalled it and installed WSUS 3.0. Having done so, I decided to try uninstalling 3.0 and reinstalling 2.0, but 2.0 would not reinstall. It failed reporting an "unexpected error". I think the WSUS 3.0 install left a SSEE instance and that prevented 2.0 from installing the WSMDE instance. Anyway I finally reinstalled the 3.0 version and upgraded it to SP1. Monitoring is back.
Unfortunately, the way I've gone about this results in System Manager reporting that update services is not available and a Blue shield in reports. Is there a way to get WSUS 3.0 into System Manager? (I should also add that I had to install it on another drive as it required more space than I had available.)
Regardless, is there a primer somewhere for the best way to configure 3.0 for use on SBS as I am unclear about the best way to set things up to approximate the convenience of the original integrated system?
|
|
|
|
|
|
Marina Roos
The Netherlands
Member since
3/24/2005
Forum Admins
Posts: 12626
|
|
Allan Brownsdon
Australia
Member since
1/8/2007
Platinum Membership
Posts: 96
|
| 9/12/2008 02:20 AM |
|
Thanks Marina, I knew that but it wouldn't work for me. It just failed (with no apparent reason in the logs etc). I think the WSUS problem which caused the Monitoring issue somehow got in the way. So the only way I could install it was to uninstall 2.0 first. Now I cannot uninstall 3.0 to reinstall 2.0 to attempt again to follow the preferred update procedure.
I might try again to uninstall 3.0 and get 2.0 back in and then try the update again. There is some information somewhere in the MS Knowledgebase about that - I'll need to find it again.
I'll report back.
|
|
|
|
|
|
Allan Brownsdon
Australia
Member since
1/8/2007
Platinum Membership
Posts: 96
|
| 9/12/2008 03:07 AM |
|
Marina,
Just one more thing...
From the technet article cc708091 it appears that what I am going to need to do is:
1. uninstall WSUS 3.0 SP1
2. uninstall all of the R2 technologies
3. reinstall all of the R2 technologies again (in maintenance mode ????)
4. upgrade WSUS 2.0 to 3.0 SP1
Is this correct. Can I not just uninstall 3.0 SP1 and then reinstall WSUS 2.0 before then running the upgrade process?
This whole approach seems rather like drastic surgery and a little more complex than I feel comfortable with. Is this something that you could do remotely via paid support?
regards,
Allan
|
|
|
|
|
|