HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup Regstry Key missing

Printable View

07-05-2007
S Kent

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup Regstry Key missing

Hello everybody,

I want to migrate WSUS2.0SP1 to WSUS3.0, but the installation fails with the following failures:

2007-05-07 16:33:47 Success MWUSSetup Validating pre-requisites...
2007-05-07 16:33:47 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.)
2007-05-07 16:33:47 Error MWUSSetup IsWSUSInstalledOnPort80: Failed to open SOFTWARE\Microsoft\Update Services\Server\Setup registry key (Error 0x80070002: The system cannot find the file specified.)
2007-05-07 16:33:47 Error MWUSSetup CUpgradeDriver::PerformPreSetupActions: Failed to open SOFTWARE\Microsoft\Update Services\Server\Setup registry key (Error
0x80070002: The system cannot find the file specified.)
2007-05-07 16:33:47 Error MWUSSetup CSetupDriver::LaunchSetup: Failed to perform pre-setup actions (Error 0x80070002: The system cannot find the file specified.)
2007-05-07 16:33:47 Error MWUSSetup CProgressManager::EnableCancel: GetDlgItem returning error (Error 0x80070578: Invalid window handle.)
2007-05-07 16:33:49 Error MWUSSetup DoInstall: Wsus setup failed (Error 0x80070002: The system cannot find the file specified.)

My problem is, that the registry Key ..\Setup did not exist!

I have allready reinstalled WSUS2.0SP1, but it doesn't change anything.

Did somebody have any ideas?

Thanks for any help.
08-05-2007
Zachary

You're not running on x64, are you?

The reason that the regkey was missing could be you hit canceled in the middle of upgrade earlier, which results in regkey being deleted but WSUS 2.0 is not uninstalled completed. I believe in that case if you reinstall WSUS 2.0 sp1, then you could see an *uninstallation* process rather than a reinstallation*. If you did a successful installation, then the regkey should be there and an upgrade to 3.0 should be good to go.
08-05-2007
S Kent

Hello,

Thanks for your answer. You're rigth, WSUS is running on a Windows Server 2003 R2 x64. I'm sorry, but this is a clean WSUS2.0SP1 installation on a new Windows Server 2003 R2 x64, not an upgrade.
I also have uninstalled and installed WSUS for two times! There is now key in the registry anymore.
09-05-2007
Zachary

Re: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup Regstry Key missing

In that case you're in an unsupported scenario. WSUS 2.0 or 2.0SP1 is not supported on x64 and as you've noticed the upgrade will not work. You'll need to do a clean install of WSUS 3.0.
10-05-2007
S Kent

Re: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup Regstry Key missing

Ok, but if this scenario is not supported, why can I upgrade from WSUS2.0 SP1 to WSUS3.0 x64???

If I must do a clean WSUS3.0 Installation, how can I convert the WSUS2.0 SP1 SQL-Database???
11-05-2007
ApPy10

Re: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\Setup Regstry Key missing

WSUS 2.0 only installs (is supported on) 32-bit systems.

WSUS 3.0 x64 *cannot* be installed on 64-bit systems.

THUS.. it is *impossible* to upgrade WSUS 2.0 to WSUS 3.0 x64 in any conceivable scenario.

Quote:

If I must do a clean WSUS3.0 Installation, how can I convert the WSUS2.0
SP1 SQL-Database???

The same way you would migrate any other 32-bit database to a 64-bit database server.

[1] Seek out a qualified DBA to help.
[2] Start from scratch.
11-05-2007
ApPy10

Kent.. the WSUS2.0 installation on your R2 x64 environment is an *UNSUPPORTED* installation.

Ergo, upgrading WSUS 2.0 on anything "x64" to WSUS 3.0 x64 is an *UNSUPPORTED* operation.

Your only option is to uninstall WSUS 2.0 and install a fresh WSUS 3.0 x64.

As for migrating the database... as noted in a previous message, that's a function of any 32-bit database migration to a 64-bit database, and I'd recommend seeking out a SQL Server DBA qualified in that particular process.

Alternatively, since that database was running on an unsupported environment, you might want to consider installing a fresh, *supported*, database environment, and synchronizing from scratch. The /content/ can be left in place and reused.

Quote:

This line should have read: WSUS 3.0 x64 *cannot* be installed on 32-bit systems
16-05-2007
Hockson

Re: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Update Services\Server\SetupRegstry Key missing

Your existing installation of WSUS 2.0 service pack 1 is unsupported, because it is running on a 64-bit operating system.

This means not only that you can't depend on the updater working properly (which it didn't) but also that you can't depend on it telling you whether it is going to work or not.

Quote:

If I must do a clean WSUS3.0 Installation, how can I convert the WSUS2.0 SP1 SQL-Database???

I suppose you could run WSUS3 in a 32-bit virtual operating system, though that would mean buying another OS license.