Error during upgrade of WSUS on Server 2003 SP2

Hello,
We have been running WSUS 2.0 successfully for quite some time. We recently
downloaded and installed WSUS 3.0 We installed all pre-reqs and then
installed the WSUS 3.0 Installer.
During the installation process we recieved a message stating that the
upgrade failed.
The following message was logged in the Application Log:

Event Type: Error
Event Source: MsiInstaller
Event Category: None
Event ID: 11722
Date: 7/30/2007
Time: 11:41:32 AM
User: MI\administrator
Computer: SERVER
Description:
Product: Microsoft Windows Server Update Services 3.0 -- Error 1722. There
is a problem with this Windows Installer package. A program run as part of
the setup did not finish as expected. Contact your support personnel or
package vendor. Action ExAttachDbForUpgrade, location:
C:\WINDOWS\Installer\MSI50D.tmp, command: -S SERVER\MICROSOFT##SSEE -Q
"CREATE DATABASE SUSDB ON (FILENAME = N'e:\WsusDatabase\SUSDB.mdf'),
(FILENAME = N'e:\WsusDatabase\SUSDB_log.ldf') FOR ATTACH" -l
"C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WSUSCa_070730_ 1055.log"

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 32 43 30 44 37 45 33 {2C0D7E3
0008: 35 2d 45 45 36 45 2d 34 5-EE6E-4
0010: 44 43 37 2d 42 41 31 33 DC7-BA13
0018: 2d 32 43 36 38 41 45 44 -2C68AED
0020: 45 42 35 39 44 7d EB59D}



Event Type: Information
Event Source: MsiInstaller
Event Category: None
Event ID: 11708
Date: 7/30/2007
Time: 11:41:36 AM
User: MI\administrator
Computer: SERVER
Description:
Product: Microsoft Windows Server Update Services 3.0 -- Installation failed.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 7b 32 43 30 44 37 45 33 {2C0D7E3
0008: 35 2d 45 45 36 45 2d 34 5-EE6E-4
0010: 44 43 37 2d 42 41 31 33 DC7-BA13
0018: 2d 32 43 36 38 41 45 44 -2C68AED
0020: 45 42 35 39 44 7d EB59D}


We decided to try the installer again and when we ran it, it seemed that it
was running as a fresh install mode, instead of an upgrade. When it
completed, we were left with a successful install, but had no data from 2.0
(computers, approvals and updates missing).

We would like to get our database back but do not know what steps to take.
Please help.

Thank you in advance,
-Scott
Syscom Digital Technologies, LLC.

"SyscomCEO" <> wrote in message
news:C1B88434-E54B-4BE3-93AF-...
> Hello,
> We have been running WSUS 2.0 successfully for quite some time. We
> recently
> downloaded and installed WSUS 3.0 We installed all pre-reqs and then
> installed the WSUS 3.0 Installer.
> During the installation process we recieved a message stating that the
> upgrade failed.
> The following message was logged in the Application Log:
>
> Event Type: Error
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 11722
> Date: 7/30/2007
> Time: 11:41:32 AM
> User: MI\administrator
> Computer: SERVER
> Description:
> Product: Microsoft Windows Server Update Services 3.0 -- Error 1722. There
> is a problem with this Windows Installer package. A program run as part of
> the setup did not finish as expected. Contact your support personnel or
> package vendor. Action ExAttachDbForUpgrade, location:
> C:\WINDOWS\Installer\MSI50D.tmp, command: -S SERVER\MICROSOFT##SSEE -Q
> "CREATE DATABASE SUSDB ON (FILENAME = N'e:\WsusDatabase\SUSDB.mdf'),
> (FILENAME = N'e:\WsusDatabase\SUSDB_log.ldf') FOR ATTACH" -l
> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WSUSCa_070730_ 1055.log"
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 7b 32 43 30 44 37 45 33 {2C0D7E3
> 0008: 35 2d 45 45 36 45 2d 34 5-EE6E-4
> 0010: 44 43 37 2d 42 41 31 33 DC7-BA13
> 0018: 2d 32 43 36 38 41 45 44 -2C68AED
> 0020: 45 42 35 39 44 7d EB59D}
>
>
>
> Event Type: Information
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 11708
> Date: 7/30/2007
> Time: 11:41:36 AM
> User: MI\administrator
> Computer: SERVER
> Description:
> Product: Microsoft Windows Server Update Services 3.0 -- Installation
> failed.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 7b 32 43 30 44 37 45 33 {2C0D7E3
> 0008: 35 2d 45 45 36 45 2d 34 5-EE6E-4
> 0010: 44 43 37 2d 42 41 31 33 DC7-BA13
> 0018: 2d 32 43 36 38 41 45 44 -2C68AED
> 0020: 45 42 35 39 44 7d EB59D}
>
>
> We decided to try the installer again and when we ran it, it seemed that
> it
> was running as a fresh install mode, instead of an upgrade. When it
> completed, we were left with a successful install, but had no data from
> 2.0
> (computers, approvals and updates missing).
>
> We would like to get our database back but do not know what steps to take.
> Please help.
>
> Thank you in advance,
> -Scott
> Syscom Digital Technologies, LLC.


I also have this same issue and would appreciate any feedback on how to
solve this issue, or work on importing C:\WSUS\SUSDB.bak (a file the
installer created after the upgrade to WSUS3 failed).

Again all updates are intact, but the database and all is .. bombed out..

TIA

I had the same issue with installing WSUS3, it was a missing WebSvcExtRestictionList Entry from IIS.

What I did to fix is:

1) Launch IIS
2) Expand the local server
3) Click on the Web Service Extensions
4) Click "Add a new Web service extension."
5) Type "test" into the Extension name field.
6) Click "Add."
7) Enter any path (example: "c:\test").
8) Click "OK" then "OK"
9) Delete the entry for "test", marked as Prohibited, in the right hand pane.
12) Close the IIS

After this, the WSUS3 install went through with no problems. Hope that helps.


EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

Hello,

Can you share out the log in the:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WSUSCa_070730_1 055.log

--
Fei Cao
Microsoft, WSUS

This posting is provided "As Is" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

"SyscomCEO" <> wrote in message
news:C1B88434-E54B-4BE3-93AF-...
> Hello,
> We have been running WSUS 2.0 successfully for quite some time. We
> recently
> downloaded and installed WSUS 3.0 We installed all pre-reqs and then
> installed the WSUS 3.0 Installer.
> During the installation process we recieved a message stating that the
> upgrade failed.
> The following message was logged in the Application Log:
>
> Event Type: Error
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 11722
> Date: 7/30/2007
> Time: 11:41:32 AM
> User: MI\administrator
> Computer: SERVER
> Description:
> Product: Microsoft Windows Server Update Services 3.0 -- Error 1722. There
> is a problem with this Windows Installer package. A program run as part of
> the setup did not finish as expected. Contact your support personnel or
> package vendor. Action ExAttachDbForUpgrade, location:
> C:\WINDOWS\Installer\MSI50D.tmp, command: -S SERVER\MICROSOFT##SSEE -Q
> "CREATE DATABASE SUSDB ON (FILENAME = N'e:\WsusDatabase\SUSDB.mdf'),
> (FILENAME = N'e:\WsusDatabase\SUSDB_log.ldf') FOR ATTACH" -l
> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WSUSCa_070730_ 1055.log"
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 7b 32 43 30 44 37 45 33 {2C0D7E3
> 0008: 35 2d 45 45 36 45 2d 34 5-EE6E-4
> 0010: 44 43 37 2d 42 41 31 33 DC7-BA13
> 0018: 2d 32 43 36 38 41 45 44 -2C68AED
> 0020: 45 42 35 39 44 7d EB59D}
>
>
>
> Event Type: Information
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 11708
> Date: 7/30/2007
> Time: 11:41:36 AM
> User: MI\administrator
> Computer: SERVER
> Description:
> Product: Microsoft Windows Server Update Services 3.0 -- Installation
> failed.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 7b 32 43 30 44 37 45 33 {2C0D7E3
> 0008: 35 2d 45 45 36 45 2d 34 5-EE6E-4
> 0010: 44 43 37 2d 42 41 31 33 DC7-BA13
> 0018: 2d 32 43 36 38 41 45 44 -2C68AED
> 0020: 45 42 35 39 44 7d EB59D}
>
>
> We decided to try the installer again and when we ran it, it seemed that
> it
> was running as a fresh install mode, instead of an upgrade. When it
> completed, we were left with a successful install, but had no data from
> 2.0
> (computers, approvals and updates missing).
>
> We would like to get our database back but do not know what steps to take.
> Please help.
>
> Thank you in advance,
> -Scott
> Syscom Digital Technologies, LLC.

roduct: Windows Server Update Services 3.0 SP2 -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action PERF_COUNTER_INST, location: C:\Program Files\Update Services\Setup\HideConsoleApp.exe, command: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\Inst allUtil.exe /LogFile="C:\DOCUME~1\JAYAPR~1.ADM\LOCALS~1\Temp\WS USCa_101118_1401.log" /ShowCallStack /WsusInstall /CategoryMessageFile="C:\Program Files\Update Services\Common\EventCategories.dll " "C:\Program Files\Update Services\Setup\bin\Microsoft.UpdateServices.Setup. CustomActions.dll "


> On Tuesday, July 31, 2007 5:24 PM SyscomCE wrote:

> Hello,
> We have been running WSUS 2.0 successfully for quite some time. We recently
> downloaded and installed WSUS 3.0 We installed all pre-reqs and then
> installed the WSUS 3.0 Installer.
> During the installation process we recieved a message stating that the
> upgrade failed.
> The following message was logged in the Application Log:
>
> Event Type: Error
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 11722
> Date: 7/30/2007
> Time: 11:41:32 AM
> User: MI\administrator
> Computer: SERVER
> Description:
> Product: Microsoft Windows Server Update Services 3.0 -- Error 1722. There
> is a problem with this Windows Installer package. A program run as part of
> the setup did not finish as expected. Contact your support personnel or
> package vendor. Action ExAttachDbForUpgrade, location:
> C:\WINDOWS\Installer\MSI50D.tmp, command: -S SERVER\MICROSOFT##SSEE -Q
> "CREATE DATABASE SUSDB ON (FILENAME = N'e:\WsusDatabase\SUSDB.mdf'),
> (FILENAME = N'e:\WsusDatabase\SUSDB_log.ldf') FOR ATTACH" -l
> "C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WSUSCa_070730_ 1055.log"
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 7b 32 43 30 44 37 45 33 {2C0D7E3
> 0008: 35 2d 45 45 36 45 2d 34 5-EE6E-4
> 0010: 44 43 37 2d 42 41 31 33 DC7-BA13
> 0018: 2d 32 43 36 38 41 45 44 -2C68AED
> 0020: 45 42 35 39 44 7d EB59D}
>
>
>
> Event Type: Information
> Event Source: MsiInstaller
> Event Category: None
> Event ID: 11708
> Date: 7/30/2007
> Time: 11:41:36 AM
> User: MI\administrator
> Computer: SERVER
> Description:
> Product: Microsoft Windows Server Update Services 3.0 -- Installation failed.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
> Data:
> 0000: 7b 32 43 30 44 37 45 33 {2C0D7E3
> 0008: 35 2d 45 45 36 45 2d 34 5-EE6E-4
> 0010: 44 43 37 2d 42 41 31 33 DC7-BA13
> 0018: 2d 32 43 36 38 41 45 44 -2C68AED
> 0020: 45 42 35 39 44 7d EB59D}
>
>
> We decided to try the installer again and when we ran it, it seemed that it
> was running as a fresh install mode, instead of an upgrade. When it
> completed, we were left with a successful install, but had no data from 2.0
> (computers, approvals and updates missing).
>
> We would like to get our database back but do not know what steps to take.
> Please help.
>
> Thank you in advance,
> -Scott
> Syscom Digital Technologies, LLC.


>> On Thursday, August 02, 2007 12:46 AM The Criminal wrote:

>> "SyscomCEO" <> wrote in message
>> news:C1B88434-E54B-4BE3-93AF-...
>>
>>
>> I also have this same issue and would appreciate any feedback on how to
>> solve this issue, or work on importing C:\WSUS\SUSDB.bak (a file the
>> installer created after the upgrade to WSUS3 failed).
>>
>> Again all updates are intact, but the database and all is .. bombed out..
>>
>> TIA


>>> On Wednesday, August 08, 2007 5:47 AM ace axc wrote:

>>> I had the same issue with installing WSUS3, it was a missing WebSvcExtRestictionList Entry from IIS.
>>>
>>>
>>>
>>> What I did to fix is:
>>>
>>>
>>>
>>> 1) Launch IIS
>>>
>>> 2) Expand the local server
>>>
>>> 3) Click on the Web Service Extensions
>>>
>>> 4) Click "Add a new Web service extension."
>>>
>>> 5) Type "test" into the Extension name field.
>>>
>>> 6) Click "Add."
>>>
>>> 7) Enter any path (example: "c:\test").
>>>
>>> 8) Click "OK" then "OK"
>>>
>>> 9) Delete the entry for "test", marked as Prohibited, in the right hand pane.
>>>
>>> 12) Close the IIS
>>>
>>>
>>>
>>> After this, the WSUS3 install went through with no problems. Hope that helps.


>>>> On Monday, August 13, 2007 1:22 PM Fei Cao \(MSFT\) wrote:

>>>> Hello,
>>>>
>>>> Can you share out the log in the:
>>>> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\WSUSCa_070730_1 055.log
>>>>
>>>> --
>>>> Fei Cao
>>>> Microsoft, WSUS
>>>>
>>>> This posting is provided "As Is" with no warranties, and confers no rights.
>>>> Use of included script samples are subject to the terms specified at
>>>> http://www.microsoft.com/info/cpyright.htm
>>>>
>>>> "SyscomCEO" <> wrote in message
>>>> news:C1B88434-E54B-4BE3-93AF-...


>>>> Submitted via EggHeadCafe
>>>> Client-server autodiscovery in C# and UDP Sockets
>>>> http://www.eggheadcafe.com/tutorials...p-sockets.aspx