kdubendorf
asked on
SBS 2003 Monitoring and Reporting Problems
I have an SBS 2003 SP2 server that gives me a "The page cannot be displayed" message when I go to Monitoring and Reporting in Server Management. It runs WSIS 2.0 which also has problems. WSUS 2.0 sort of works but seems to have too many items to update to run properly (over 20,000). I've applied all of the Microsoft Patchs to the server.
I"ve run into this problem with SBS 2003 servers running WSUS 3.0. Cleaning up the WSUS 3.0 database solved my problem there. Unfortunately the WSUS 2.0 database doesn't seem to have the features available to clean it. I've tried running wsusutil but it will time out mid cleaning.
How can I get monitoring and reporting working again?
I"ve run into this problem with SBS 2003 servers running WSUS 3.0. Cleaning up the WSUS 3.0 database solved my problem there. Unfortunately the WSUS 2.0 database doesn't seem to have the features available to clean it. I've tried running wsusutil but it will time out mid cleaning.
How can I get monitoring and reporting working again?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Actually this link mentions little on WSUS 2.0 and doesn't reference codeplex at all. Do you have a recommended link for that?
ASKER
I went hunting for codeplex and found a wsus_cleanup_cl.exe tool. To me it appears to be written for WSUS 3.0. I am getting the following error message:
Unhandled Exception: System.IO.FileNotFoundExce
embly 'Microsoft.UpdateServices.
utral, PublicKeyToken=31bf3856ad3
annot find the file specified.
File name: 'Microsoft.UpdateServices.
re=neutral, PublicKeyToken=31bf3856ad3
at WSUS_Cleanup_CL.Class1.Mai
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\M
icrosoft\Fusion!EnableLog]
Note: There is some performance penalty associated with assembly bind failure lo
gging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\F
ion!EnableLog].
I am executing this from c:\.
Thanks.
I am not sure what to tell you about a program that is not supported any longer. Perhaps go back to uninstall/reinstall then immediately upgrade to WSUS 3.2.
But before you do that, maybe look here:
First read:
http://wsus.codeplex.com/discussions
then dll and install/run
http://wsus.codeplex.com/releases/view/18473
first read:
http://wsus.codeplex.com/discussions
Then dl and install/run:
http://wsus.codeplex.com/releases/view/17612
But before you do that, maybe look here:
First read:
http://wsus.codeplex.com/discussions
then dll and install/run
http://wsus.codeplex.com/releases/view/18473
first read:
http://wsus.codeplex.com/discussions
Then dl and install/run:
http://wsus.codeplex.com/releases/view/17612
ASKER
While I recognize this is unsupported, it is still a question with merit and more help along the lines of getting out of the situation would have been beneficial
ASKER