Dear all you MVP's,
Have I got a stumper. Here is the short version:
WSUS status stopped showing up on the SBS Console (2008 that is). Was
working fine. Don't know why it stopped.
After trying to get it working; making sure WSUS was configured correctly
and all that I went for the uninstall and re-install using these
instructions:
http://www.tech-archive.net/Archive/.../msg00037.html



Got it all gone. Went for the re-install using these instructions:
http://technet.microsoft.com/en-us/l...8WS.10%29.aspx

Never did work.

So I tried to do the same thing but without the 'quite' switch so I could
see where it was failing.

Here is the WSUSSetup.log:
2009-09-24 08:12:25 Success MWUSSetup Validating
pre-requisites...
2009-09-24 08:12:28 Error MWUSSetup Failed to determine if an
higher version of WSUS is installed. Assuming it is not... (Error
0x80070002: The system cannot find the file specified.)
2009-09-24 08:12:38 Success MWUSSetup Initializing installation
details
2009-09-24 08:12:38 Success MWUSSetup Skipping Asp.Net install
since not running on win2k3...
2009-09-24 08:12:38 Success MWUSSetup Installing wYukon using
ocsetup on Windows Server 2008
2009-09-24 08:12:38 Success MWUSSetup Windows Internal database
is already installed on this machine
2009-09-24 08:12:38 Success MWUSSetup Installing WSUS...
2009-09-24 08:12:42 Success CustomActions.Dll Successfully set propery
of WSUS admin groups' full names
2009-09-24 08:12:43 Success CustomActions.Dll .Net framework path:
C:\Windows\Microsoft.NET\Framework64\v2.0.50727
2009-09-24 08:12:47 Success CustomActions.Dll Creating user group: WSUS
Reporters with Description: WSUS Administrators who can only run reports on
the Windows Server Update Services server.
2009-09-24 08:12:47 Success CustomActions.Dll Creating WSUS Reporters
user group
2009-09-24 08:12:47 Success CustomActions.Dll WSUS Reporters user group
already exists
2009-09-24 08:12:47 Success CustomActions.Dll Successfully created WSUS
Reporters user group
2009-09-24 08:12:47 Success CustomActions.Dll Creating user group: WSUS
Administrators with Description: WSUS Administrators can administer the
Windows Server Update Services server.
2009-09-24 08:12:47 Success CustomActions.Dll Creating WSUS
Administrators user group
2009-09-24 08:12:47 Success CustomActions.Dll WSUS Administrators user
group already exists
2009-09-24 08:12:47 Success CustomActions.Dll Successfully created WSUS
Administrators user group
2009-09-24 08:12:47 Success CustomActions.Dll Successfully created WSUS
user groups
2009-09-24 08:14:45 Error MWUSSetup InstallWsus: MWUS
Installation Failed (Error 0x80070643: Fatal error during installation.)
2009-09-24 08:14:45 Error MWUSSetup
CInstallDriver::PerformSetup: WSUS installation failed (Error 0x80070643:
Fatal error during installation.)
2009-09-24 08:14:45 Error MWUSSetup CSetupDriver::LaunchSetup:
Setup failed (Error 0x80070643: Fatal error during installation.)
2009-09-24 08:14:47 Error MWUSSetup DoInstall: Wsus setup
failed (Error 0x80070643: Fatal error during installation.)

I have chased down the 0x80070643 error and have ensured that I have
sysadmin permissions to the SSEE SQL instance. Still didn't fix it.

Here is the weird part. During the install I get an error popup:
Could not open key:
UNKNOWN\Components\7323F9765E4664E4999102DE6CE03322\25B648779C414CF4EB36EF60FA054124.
System error 5. Verify that you have sufficient access to that key, or
contact your support personnel.



The relevant portion of the WSUSSetupmsi_090924.log:
....
MSI (s) (F4:5C) [08:13:06:851]: Executing op:
SetTargetFolder(Folder=C:\Windows\SysWOW64\)
MSI (s) (F4:5C) [08:13:06:851]: Executing op:
SetSourceFolder(Folder=1\StmFldr\|SystemFolder\)
MSI (s) (F4:5C) [08:13:06:851]: Executing op:
RegisterSharedComponentProvider(,,File=f_E3AC5431_1D4B_4518_A7DE_2FDDB3ABBF60,Component={679F3237-64E5-4E46-9919-20EDC60E3322},ComponentVersion=7.1.6001.65,ProductCode={77846B52-14C9-4FC4-BE63-FE06AF501442},ProductVersion=3.1.6001,PatchSize=0,PatchAttributes=0,PatchSequence=0,SharedComponent=0,IsFullFile=0)
MSI (s) (F4:5C) [08:13:06:851]: Note: 1: 1402 2:
UNKNOWN\Components\7323F9765E4664E4999102DE6CE03322\25B648779C414CF4EB36EF60FA054124
3: 5
MSI (s) (F4:5C) [08:14:41:979]: Product: Microsoft Windows Server Update
Services 3.0 SP1 -- Error 1402. Could not open key:
UNKNOWN\Components\7323F9765E4664E4999102DE6CE03322\25B648779C414CF4EB36EF60FA054124.
System error 5. Verify that you have sufficient access to that key, or
contact your support personnel.
....


The only similar reported error that I found was on a Russian web site.
Google translation didn't do so well and I don't think they ever fixed it.
I also found something similar on experts-exchange where someone mentioned
that Mariana Roos fixed it for them by finding some obsure registry key but
they didn't know which one.

Anyone have any ideas?

Thanks!

John V.