WSUS 3.0 Update fails/Updats services 3.0 wont connect to WSUS ser

Hello,

I have recently attempted to upgrade WSUS 2.0 to WSUS 3.0. When trying
to install the update, an error is produced that directs me to look to the
“WSUSsetup.log” file for more information. Below is a list of the errors
produced from the attempted installation.


2008-06-25 13:11:48 Success MWUSSetup Validating pre-requisites...
2008-06-25 13:11:48 Error MWUSSetup ExecuteQuery: Failed to
execute SQL query USE SUSDB IF EXISTS (select * FROM master..sysdatabases
WHERE name= N'SUSDB' AND suser_sname(sid) is null) EXEC dbo.sp_changedbowner
N'"Domain"\"UserName"' (Error 0x80040E14)
2008-06-25 13:11:48 Error MWUSSetup ExecuteQueryGetNoResults:
Failed to execute query USE %s IF EXISTS (select * FROM master..sysdatabases
WHERE name= N'%s' AND suser_sname(sid) is null) EXEC dbo.sp_changedbowner
N'%s' (Error 0x80040E14)
2008-06-25 13:11:48 Error MWUSSetup
CUpgradeDriver::PerformPreSetupActions: Failed to reset database owner name
for SUSDB to owner "Domain"\"UserName" (Error 0x80040E14)
2008-06-25 13:11:48 Error MWUSSetup CSetupDriver::LaunchSetup:
Failed to perform pre-setup actions (Error 0x80040E14)
2008-06-25 13:11:48 Error MWUSSetup
CProgressManager::EnableCancel: GetDlgItem returning error (Error 0x80070578:
Invalid window handle.)
2008-06-25 13:11:53 Error

Also, now that I have tried to upgrade to WSUS 3.0, I am no longer able
to connect to my WSUS server via Update Services 3.0. When I try to "Connect
To Server" I receive a connection error and am unable to connect. Presently
the WSUS content folder has become congested due to my inability to gain
access to update services 3.0.
Does anyone have any ideas?

80040E14 errors are almost always query related. Since you can't change the
WSUS queries, we have to assume that a SQL component (such as full-text
querying) is corrupt/not registered properly. I'd probably try
re-installing WSUS2 which should keep your database and content directory
while reregistering all of the SQL components. Then rerun WSUS3. But I'll
admit that this is really winging it so hopefully somebody has better
advice...

You might just have to scrap your db and install WSUS3 fresh and re-approve
updates.

-Cliff

"jayredder" <jayredder@discussions.microsoft.com> wrote in message
news:E60CDB19-6A46-4636-8AA0-2B4DC6B9CD6B@microsoft.com...
> Hello,
>
> I have recently attempted to upgrade WSUS 2.0 to WSUS 3.0. When trying
> to install the update, an error is produced that directs me to look to the
> “WSUSsetup.log” file for more information. Below is a list of the errors
> produced from the attempted installation.
>
>
> 2008-06-25 13:11:48 Success MWUSSetup Validating
> pre-requisites...
> 2008-06-25 13:11:48 Error MWUSSetup ExecuteQuery: Failed to
> execute SQL query USE SUSDB IF EXISTS (select * FROM master..sysdatabases
> WHERE name= N'SUSDB' AND suser_sname(sid) is null) EXEC
> dbo.sp_changedbowner
> N'"Domain"\"UserName"' (Error 0x80040E14)
> 2008-06-25 13:11:48 Error MWUSSetup
> ExecuteQueryGetNoResults:
> Failed to execute query USE %s IF EXISTS (select * FROM
> master..sysdatabases
> WHERE name= N'%s' AND suser_sname(sid) is null) EXEC dbo.sp_changedbowner
> N'%s' (Error 0x80040E14)
> 2008-06-25 13:11:48 Error MWUSSetup
> CUpgradeDriver::PerformPreSetupActions: Failed to reset database owner
> name
> for SUSDB to owner "Domain"\"UserName" (Error 0x80040E14)
> 2008-06-25 13:11:48 Error MWUSSetup
> CSetupDriver::LaunchSetup:
> Failed to perform pre-setup actions (Error 0x80040E14)
> 2008-06-25 13:11:48 Error MWUSSetup
> CProgressManager::EnableCancel: GetDlgItem returning error (Error
> 0x80070578:
> Invalid window handle.)
> 2008-06-25 13:11:53 Error
>
> Also, now that I have tried to upgrade to WSUS 3.0, I am no longer
> able
> to connect to my WSUS server via Update Services 3.0. When I try to
> "Connect
> To Server" I receive a connection error and am unable to connect.
> Presently
> the WSUS content folder has become congested due to my inability to gain
> access to update services 3.0.
> Does anyone have any ideas?
>

Hello,

Thank you for your post. My name is Robbin Meng, and it is my pleasure to
work with you on this issue!

Please allow me to confirm that my understandings are correct. As I
understand it, the issue is:

When you attempted to upgrade WSUS 2.0 to WSUS 3.0, the installation failed
with error messages. Now, you cannot connect to WSUS server via Update
Services 3.0 with the console.

If I have misunderstood your concerns please feel free to let me know.

This issue may occur if you have not uninstalled the old WSUS 2.0 before
installing WSUS 3.0. We many need to uninstall WSUS 2.0 first from add
/remove program and install WSUS 3.0 sp1.To do this, let's try the
following steps:

Step 1: If you can find WSUS 2.0 on the SBS server from Add/Remove
programs, please uninstall it first.


Step 2: Step by step to Migrate from WSUS 2.0 to WSUS 3.0.

The WSUS 3.0 installation program will migrate all WSUS 2.0 settings to
WSUS 3.0. Furthermore, if the installation program finds any SQL Server
database other than SQL Server 2005 Service Pack 1 (or SQL Server 2005
Service Pack 2 for Windows Server 2008), it will back up the existing
database, install Windows? Internal Database, and migrate the database to
it.

First of all before you install WSUS 3.0, please check and add
"Authenticated users" and "Local Network" account with Full Control
permission to the WSUS package directory and sub-directory. By default, it
is the C:\WSUS folder, if your SBS is installed in C drive.

To install the WSUS 3.0 SP1 product on Windows Small Business Server 2003,
follow the instructions at:

Installing Windows Server Update Services 3.0 on Windows Small Business
Server 2003(WSUS 3.0 SP1 Server Installation on Windows Small Business
Server 2003)
http://technet2.microsoft.com/Window...brary/de2e9436
-f23f-47f0-b840-e8b3e72182751033.mspx?mfr=true

If you can install WSUS 3.0 successfully this time, please configure it
with step 3.
Step 3: About configuring WSUS3.0 setup wizard, please see link��

Using the WSUS 3.0 Configuration Wizard
http://technet2.microsoft.com/window...7-6d6d-4122-9d
02-e2227efd65571033.mspx

About how to Migrate from WSUS 2.0 to WSUS 3.0��please see link��
http://technet2.microsoft.com/window...4-17ee-4769-aa
f4-da09524cb8221033.mspx


More Information:

Backing up Windows Server Update Services
http://technet2.microsoft.com/window...1-eb48-4156-81
a2-267d846f844f1033.mspx?mfr=true

If we cannot resolve the issue after we perform the above steps, please
help me collect some information for further investigation:

Information Need
==============
1. If possible, please capture some screenshot when the error messages
regarding cannot connect to WSUS console appear and send them to me :
v-robmen@microsoft.com

2. Please gather an MPS setup report:

1) Please download the MPSRPT_SETUPPerf.EXE from the following link and
then run this tool to gather some information from the problematic computer:
http://download.microsoft.com/downlo...5-a579-30b0bd9
15706/MPSRPT_SETUPPerf.EXE

2) Double-click on the MPSRPT_SETUPPerf.EXE file.

[Note] This process may take some time; however, it will not have a
negative effect on the performance.

3) A CAB file will be generated in the
%systemroot%\MPSReports\Setup\Reports\Cab directory called
%COMPUTERNAME%_MPSReports.CAB. The CAB file will contain the reports
generated by the MPS Reporting Tool.

Send the .cab file directly to me at v-robmen@microsoft.com .


I look forward to your reply. If you have any questions or concerns, please
do not hesitate to let me know.

Thank you for your time and cooperation!

Best regards,
Robbin Meng(MSFT)

Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities...s/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.

Hello,

This is Robbin again. Sorry, I just found there is a little omit in the
Step 1 in my last email.

Please note we unable to find WSUS 2.0 on the SBS server from Add/Remove
programs. It is called "Windows Small Business Server 2003 R2" instead of "
WSUS 2.0 ". So please select the "Windows Small Business Server 2003 R2" to
remove it.

Thanks!

Best regards,
Robbin Meng(MSFT)

Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security

Hello,

Thank You for your reply. I will begin to implement the steps that you
have suggested.

Jay Redder

""Robbin Meng [MSFT]"" wrote:

> Hello,
>
> This is Robbin again. Sorry, I just found there is a little omit in the
> Step 1 in my last email.
>
> Please note we unable to find WSUS 2.0 on the SBS server from Add/Remove
> programs. It is called "Windows Small Business Server 2003 R2" instead of "
> WSUS 2.0 ". So please select the "Windows Small Business Server 2003 R2" to
> remove it.
>
> Thanks!
>
> Best regards,
> Robbin Meng(MSFT)
>
> Microsoft CSS Online Newsgroup Support
> Get Secure! - www.microsoft.com/security
>
>

Hello again,

I have begun to follow the steps that have been suggested by Robbin
Meng. I would like to make the following clarifications. I am not running
WSUS on Windows small business server. I am running it on Windows server 2003
Standard edition.

I started today by first backing up my Database. After successfully
backing the Database up, I navigated to “Add/Remove Programs” so I could
uninstall any pervious versions of WSUS before making the upgrade to WSUS
3.0. “WSUS 2.0” was not listed under the “currently installed programs:”
list. Instead, I choose to uninstall Windows Server Update Services 3.0.
When the uninstallation wizard started, I choose to keep my Database in
tact while performing the uninstall operation. Immediately after starting the
Uninstall, An error occurs and I am prompted that the uninstallation was
unsuccessful. The error prompt did not offer any additional information.

I am not sure where to go from here.

Jay Redder


""Robbin Meng [MSFT]"" wrote:

> Hello,
>
> This is Robbin again. Sorry, I just found there is a little omit in the
> Step 1 in my last email.
>
> Please note we unable to find WSUS 2.0 on the SBS server from Add/Remove
> programs. It is called "Windows Small Business Server 2003 R2" instead of "
> WSUS 2.0 ". So please select the "Windows Small Business Server 2003 R2" to
> remove it.
>
> Thanks!
>
> Best regards,
> Robbin Meng(MSFT)
>
> Microsoft CSS Online Newsgroup Support
> Get Secure! - www.microsoft.com/security
>
>

Hello Jay,

Thanks for writing back to me to clarify the current situation.

However, since this is a pure Windows Server 2003 WSUS issue and NOT a SBS
2003 issue, as the current news group is mainly focus on issues with SBS
2003 product, I suggest you submit this issue to our special WSUS news
group:

Discussions in Software Update Services
http://www.microsoft.com/communities...aspx?dg=micros
oft.public.softwareupdatesvcs

Personally meanwhile, I'd like to share some information about how to
manually delete the WSUS and the Windows Internal Database, then try to
install again. The following steps are just for your additional reference
if you want to have a try:

1. Download the SDK to obtain MSIZAP

To obtain the Windows Server 2003 SP1 Platform SDK, visit the following
Microsoft Web site:
http://www.microsoft.com/downloads/d...B43-E24F-4EA3-
A93E-40C0EC4F68E5

2. From a command prompt, type:

For WSUS 2.0: MSIZAP T {A0D46DC6-8950-451A-8990-53C86E17666E}
For WSUS 3.0: MSIZAP T {2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}

3. From a command prompt, type: sc delete wsusservice

4. Again, From a command prompt, type: MSIZAP T
{2C0D7E35-EE6E-4DC7-BA13-2C68AEDEB59D}

5. Run following command to ensure the Windows internal database is
removed.

On 32-bit platforms: msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB}
callerid=ocsetup.exe
On 64-bit platforms: msiexec /x {BDD79957-5801-4A2D-B09E-852E7FA64D01}
callerid=ocsetup.exe

6. Reboot the server.

7. From a command prompt, type: aspnet_regiis -i

8. From a command prompt, type: iisreset

9. Install WSUS 3.0 with SP1 again.

More information about WSUS:
http://technet.microsoft.com/en-us/wsus/default.aspx

Hope this helps.

Again, thank you for posting in the SBS newsgroups. Please feel free to
contact us again in the future.


Best regards,
Robbin Meng(MSFT)

Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security

=====================================================
This newsgroup only focuses on SBS technical issues. If you have issues
regarding other Microsoft products, you'd better post in the corresponding
newsgroups so that they can be resolved in an efficient and timely manner.
You can locate the newsgroup here:
http://www.microsoft.com/communities...s/default.aspx

When opening a new thread via the web interface, we recommend you check the
"Notify me of replies" box to receive e-mail notifications when there are
any updates in your thread. When responding to posts via your newsreader,
please "Reply to Group" so that others may learn and benefit from your
issue.

Microsoft engineers can only focus on one issue per thread. Although we
provide other information for your reference, we recommend you post
different incidents in different threads to keep the thread clean. In doing
so, it will ensure your issues are resolved in a timely manner.

For urgent issues, you may want to contact Microsoft CSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

Any input or comments in this thread are highly appreciated.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.