WSUS 3.0 SP1 on SBS 2003
This post is going to address the Re-installation of WSUS 3.0 SP1 on an SBS 2003 R2 box. However, to set the stage, I need to go back to an earlier post that never actually got posted.
Earlier this month the server in question had some sort of "problem" that resulted in a corrupted file system. Some of you may recognize the following error that is prominently displayed immediately after POST, on boot-up.
This issue was resolved and if you are interested in the resolution (the post that never made it to press), let me know.
A day or two later we developed a problem with WSUS (Update Services) on the same box.
Several attempts to resolve this problem were unsuccessful. Ultimately, WSUS 3.0 SP1 was "ripped and replaced" from the box. That involved stopping services, deleting files, removing registry entries and running the "Windows Install Clean Up" tool. Following all of those tasks, installation of WSUS was a fairly straightforward task. But wait... there's more...
WSUS installed correctly, it just wasn't working properly with the SBS 2003 R2 Server Management Console. We now had the dreaded "Blue Shield", you know, the one that says,
Back to the drawing board... I tried the obvious, ensuring that WSUS was configured in accordance with Software updates are not managed by Microsoft Windows Small Business Server 2003 Update Services. No Joy. The solution lies in a document call, Installing Microsoft Windows Server Update Services 3.0 on Windows Small Business Server 2003 but I still had a problem.
The procedure essentailly call for you to:
1. Uninstall WSUS 3.0.
2. Uninstall Windows SBS 2003 R2 components.
3. Reinstall Windows SBS 2003 R2 components in Maintenance Mode.
4. Upgrade WSUS 2.0 to WSUS 3.0.
1. Uninstall WSUS 3.0. << No Problem - this time. Unistalled from Control Panel\Add or Remove programs. See White Paper for additional instructions.
2. Uninstall Windows SBS 2003 R2 components. << No Problem. Unistalled from Control Panel\Add or Remove programs.
3. Reinstall Windows SBS 2003 R2 components. <<Problem>> First of all, the White Paper tells you to "Reinstall Windows SBS 2003 R2 components in Maintenance Mode." The point you to another URL which is essentially the release notes of the SBS R2 Technologies installation disc. It tells you to run Setup.exe, which is what I did... several times. Each time it would fail and point to a couple of log files that weren't terribly helpful. Eventually, I got to this, "Failed to install PSFSIP (Error 0x80004005: Unspecified error)". Here is where the rubber meets the road.
If you Google that phrase, you will find a number of article with a variety of "suggestions" none of which appeared to be a bona fide solution. I'll cut to the chase and identify the one that worked for me.
It worked and we are back in the "Green Check" business.
Earlier this month the server in question had some sort of "problem" that resulted in a corrupted file system. Some of you may recognize the following error that is prominently displayed immediately after POST, on boot-up.
Windows could not start because the following file is missing or corrupt C:\windows\system32\config\system You can attempt to repair this file by starting windows setup using the original setup CD-Rom. Select "r" at the first screen to start repair.?
This issue was resolved and if you are interested in the resolution (the post that never made it to press), let me know.
A day or two later we developed a problem with WSUS (Update Services) on the same box.
Event ID: 824
SQL Server detected a logical consistency-based I/O error: torn page
(expected signature: 0x0; actual signature: 0x48015c54). It occurred during a read of page (1:80447) in database ID 5 at offset 0x0000002747e000 in file 'H:\WsusDatabase\SUSDB.mdf'. Additional messages in the SQL Server error log or system event log may provide more detail. This is a severe error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.
Several attempts to resolve this problem were unsuccessful. Ultimately, WSUS 3.0 SP1 was "ripped and replaced" from the box. That involved stopping services, deleting files, removing registry entries and running the "Windows Install Clean Up" tool. Following all of those tasks, installation of WSUS was a fairly straightforward task. But wait... there's more...
WSUS installed correctly, it just wasn't working properly with the SBS 2003 R2 Server Management Console. We now had the dreaded "Blue Shield", you know, the one that says,
"Windows Small Business Server (Windows SBS) Update Services is not running because it automatically turns off if you customize Windows Server Update Services (WSUS). For a list of specific settings that cause Windows SBS Update
Services to turn off, see the Microsoft Website. Even if WSUS is managing updates for your network, the accuracy of the status in the Windows SBS monitoring report or on the Update Services home page cannot be guaranteed. To use Windows SBS Update Services, reverse the changes that you have made to WSUS or reinstall Windows SBS 2003 R2."
Back to the drawing board... I tried the obvious, ensuring that WSUS was configured in accordance with Software updates are not managed by Microsoft Windows Small Business Server 2003 Update Services. No Joy. The solution lies in a document call, Installing Microsoft Windows Server Update Services 3.0 on Windows Small Business Server 2003 but I still had a problem.
The procedure essentailly call for you to:
1. Uninstall WSUS 3.0.
2. Uninstall Windows SBS 2003 R2 components.
3. Reinstall Windows SBS 2003 R2 components in Maintenance Mode.
4. Upgrade WSUS 2.0 to WSUS 3.0.
1. Uninstall WSUS 3.0. << No Problem - this time. Unistalled from Control Panel\Add or Remove programs. See White Paper for additional instructions.
2. Uninstall Windows SBS 2003 R2 components. << No Problem. Unistalled from Control Panel\Add or Remove programs.
3. Reinstall Windows SBS 2003 R2 components. <<Problem>> First of all, the White Paper tells you to "Reinstall Windows SBS 2003 R2 components in Maintenance Mode." The point you to another URL which is essentially the release notes of the SBS R2 Technologies installation disc. It tells you to run Setup.exe, which is what I did... several times. Each time it would fail and point to a couple of log files that weren't terribly helpful. Eventually, I got to this, "Failed to install PSFSIP (Error 0x80004005: Unspecified error)". Here is where the rubber meets the road.
If you Google that phrase, you will find a number of article with a variety of "suggestions" none of which appeared to be a bona fide solution. I'll cut to the chase and identify the one that worked for me.
1. regsvr32 /u psfsip.dll
2. rename psfsip.dll in %windir%\system32 to OLD-psfsip.dll
3. try install again
It worked and we are back in the "Green Check" business.
posted by Rick Bahl at
6:01 AM
5 Comments:
I would like to know the answer to: Windows could not start because the following file is missing or corrupt C:\windows\system32\config\system You can attempt to repair this file by starting windows setup using the original setup CD-Rom. Select "r" at the first screen to start repair.?
Serge Shammas, sergenet@yahoo.com
By
Anonymous, At
January 31, 2009 4:29 PM
Serge,
The short story was that there was some actual file system corruption. The recommendation to boot the system CD-Rom did not work. It took a little more than what I am about to say but in simplest terms, I was able to resolve the issue by booting to a “Bart’s Boot Disk” and running CHKDSK from there. If you need more details, drop me a line.
Rick
By
Rick Bahl, At
January 31, 2009 8:50 PM
Thanks for the reply Rick. I have been at this for 17 hours and am not getting anywhere. I cannot go home until I solve this issue. Basically, there are two disks on the system. One is dynamic (used to be mirrored) and the other basic. I installed SBS 2003 on the basic and I can boot from it. I tried to perform a chkdsk from the working os but it won't do it. If you can help me navigate through this it would be great. It is almost 2 am already. Thanks.
Serge
By
Anonymous, At
February 1, 2009 3:42 AM
Serge,
I feel your pain. I have certainly pull the "all nighter" a time or two.
I'll try and keep this simple:
1. Attach an external USP drive to the system.
2. Boot from the CD bootable OS of your choice (Bart's, Ultimate....). If you don't have one, create it.
3. Once you are up on the bootable OS. Copy all of the important data directories to the external drive. This isn't part of the solutioin, but is just good insurance.
4. Run CHKDSK /R from the bootable OS on the affected volume.
5. Copy the contents of the "X:\WINDOWS\repair" folder on the USB drive. Were X is the volume that yo are trying to repair. This folder contains copies of the the Registry files that you need to boot the system, in the event that the CHKDSK still does not solve the problem.
6. Reboot to the affected volume. If the system still does not boot, boot the CD again. Copy the contents of the C:\WINDOWS\system32\config folder to a safe locaton, then delete the contents of the original folder. Copy the files from the "X:\WINDOWS\repair" folder to this location.
7. Reboot to the affected volume. The system SHOULD boot. If it doesn't i'd need some addtional details to figure our what is going on.
Good Luck. Let me know of that works for you.
Rick
By
Rick Bahl, At
February 1, 2009 6:46 AM
This error (c:\windows\system32\config\system) can also be caused if that file has grown above around 13MB.
You can compress it by loading it into another machine's registry editor as a separate hive, then saving it back.
By
RSP, At
August 28, 2009 5:39 AM
Post a Comment
Links to this post:
Create a Link
<< Home