Problems after upgrading from WSUS 2.0 to WSUS 3.0

[SRMW]

Hello,

We are having some strange problems after upgrading our secure WSUS 2.0 SP1
server to WSUS 3.0. Previously we were using SQL server 2000 running on the
same server, during the upgrade we chose to go with the Windows internal
database. The upgrade process went smoothly without any problems at all. The
only down side was that it rest the secure configuration using using SSL &
port 8531 to a unsecured server using port 8530 during the upgrade. No
problem there as I reconfigured it again as before as a secure WSUS server
and used port 8531 for the Admin site. Once this was done everything started
working ok with the clients reporting and being able to deploy updates and
run reports. The securing WSUS 3.0 introduced a new problem. Except for
myself & another coworker all others in the WSUS Administrators group cannot
connect to the WSUS server by using servername.domainname and port 8531 or
any other port or just the server name . They get an error like below.

“Cannot connect to <<WSUS server name>> the server may be using another port
or different secure socket layer”

We all have the same AD group memberships on the server, we are members of
the WSUS Administrators group and also local administrator on the server,
only myself & another coworker can access the server all others in the same
group cannot. The PC’s that the WSUS consoles and MMC are installed are on
the same AD domain as the WSUS server. IF my co worker or myself logs on to
their PCs we can access the WSUS server through the remote console.

My IIS settings for the WSUS admin site are as follows,

Default Website Require SSL Authentication

Client web services no anonymous
Self Update no anonymous

WSUS Administration site
API Removing 30 yes Integrated
Client web services yes anonymous
Content no anonymous
Dss Auth Webservice yes anonymous
Inventory no anonymous
Reporting Webservice no anonymous
Self Update no anonymous + Integrated
Server Sync Webservice yes anonymous
Simple Auth Webservice yes anonymous


I also see the following errors in the application log. These errors seem to
be common among lot of other WSUS 3.0 users who have commented in the WSUS
forums and are supposed to related
the Server Health monitoring subsystem of WSUS. Although these error appear
in the application log the WSUS server works fine except the console access
problem which I mentioned before.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12012
Description:
The API Remoting Web Service is not working.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12032
Description:
The Server Synchronization Web Service is not working.


Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12022
Description:
The Client Web Service is not working.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12042
Description:
The SimpleAuth Web Service is not working.

Event Type: Error
Event Source: Windows Server Update Services
Event Category: Web Services
Event ID: 12052
Description:
The DSS Authentication Web Service is not working.

I have been visiting most of the WSUS forums out there; these errors are
common among lot of other users out there although some are for new
installations of WSUS 3.0. I have tried all of the solutions suggested in the
following forum postings page and have still not had any luck with then issue
on our server.

http://www.wsus.info/forums/lofiversion/index.php?t10007.html

Appreciate if anyone can let me know of any suggestions you might have,

Thanks for your help,

SRMW

 

[TaurArian [MS-MVP]]

Re: Problems after upgrading from WSUS 2.0 to WSUS 3.0



"SRMW" <SRMW@discussions.microsoft.com> wrote in message
news:E510DCEE-6198-4C99-ADB6-81DBB1F12F74@microsoft.com...
| Hello,
|
| We are having some strange problems after upgrading our secure WSUS 2.0 SP1
| server to WSUS 3.0. Previously we were using SQL server 2000 running on the
| same server, during the upgrade we chose to go with the Windows internal
| database. The upgrade process went smoothly without any problems at all. The
| only down side was that it rest the secure configuration using using SSL &
| port 8531 to a unsecured server using port 8530 during the upgrade. No
| problem there as I reconfigured it again as before as a secure WSUS server
| and used port 8531 for the Admin site. Once this was done everything started
| working ok with the clients reporting and being able to deploy updates and
| run reports. The securing WSUS 3.0 introduced a new problem. Except for
| myself & another coworker all others in the WSUS Administrators group cannot
| connect to the WSUS server by using servername.domainname and port 8531 or
| any other port or just the server name . They get an error like below.
|
| "Cannot connect to <<WSUS server name>> the server may be using another port
| or different secure socket layer"
|
| We all have the same AD group memberships on the server, we are members of
| the WSUS Administrators group and also local administrator on the server,
| only myself & another coworker can access the server all others in the same
| group cannot. The PC's that the WSUS consoles and MMC are installed are on
| the same AD domain as the WSUS server. IF my co worker or myself logs on to
| their PCs we can access the WSUS server through the remote console.
|
| My IIS settings for the WSUS admin site are as follows,
|
| Default Website Require SSL Authentication
|
| Client web services no anonymous
| Self Update no anonymous
|
| WSUS Administration site
| API Removing 30 yes Integrated
| Client web services yes anonymous
| Content no anonymous
| Dss Auth Webservice yes anonymous
| Inventory no anonymous
| Reporting Webservice no anonymous
| Self Update no anonymous + Integrated
| Server Sync Webservice yes anonymous
| Simple Auth Webservice yes anonymous
|
|
| I also see the following errors in the application log. These errors seem to
| be common among lot of other WSUS 3.0 users who have commented in the WSUS
| forums and are supposed to related
| the Server Health monitoring subsystem of WSUS. Although these error appear
| in the application log the WSUS server works fine except the console access
| problem which I mentioned before.
|
| Event Type: Error
| Event Source: Windows Server Update Services
| Event Category: Web Services
| Event ID: 12012
| Description:
| The API Remoting Web Service is not working.
|
| Event Type: Error
| Event Source: Windows Server Update Services
| Event Category: Web Services
| Event ID: 12032
| Description:
| The Server Synchronization Web Service is not working.
|
|
| Event Type: Error
| Event Source: Windows Server Update Services
| Event Category: Web Services
| Event ID: 12022
| Description:
| The Client Web Service is not working.
|
| Event Type: Error
| Event Source: Windows Server Update Services
| Event Category: Web Services
| Event ID: 12042
| Description:
| The SimpleAuth Web Service is not working.
|
| Event Type: Error
| Event Source: Windows Server Update Services
| Event Category: Web Services
| Event ID: 12052
| Description:
| The DSS Authentication Web Service is not working.
|
| I have been visiting most of the WSUS forums out there; these errors are
| common among lot of other users out there although some are for new
| installations of WSUS 3.0. I have tried all of the solutions suggested in the
| following forum postings page and have still not had any luck with then issue
| on our server.
|
| http://www.wsus.info/forums/lofiversion/index.php?t10007.html
|
| Appreciate if anyone can let me know of any suggestions you might have,
|
| Thanks for your help,
|
| SRMW
|

Perhaps try the WSUS Newsgroup
http://www.microsoft.com/technet/co...crosoft.public.windows.server.update_services

news://msnews.microsoft.com/microsoft.public.windows.server.update_services
(OE client)

Xposted for convenience
--
====================================
TaurArian [MS-MVP] 2005-2008 - Australia
====================================
How to make a good post: http://www.dts-l.org/goodpost.htm
Defending your machine: http://defendingyourmachine2.blogspot.com/
http://taurarian.mvps.org/index.htm

Emails will not be acknowledged - please post to the newsgroup so all may benefit.

 

[SRMW]

Re: Problems after upgrading from WSUS 2.0 to WSUS 3.0

Thanks for your reply, I believe my post appears in the Update services
newesgroup, please let me know if it is not,

"TaurArian [MS-MVP]" wrote:

>
>
> "SRMW" <SRMW@discussions.microsoft.com> wrote in message
> news:E510DCEE-6198-4C99-ADB6-81DBB1F12F74@microsoft.com...
> | Hello,
> |
> | We are having some strange problems after upgrading our secure WSUS 2.0 SP1
> | server to WSUS 3.0. Previously we were using SQL server 2000 running on the
> | same server, during the upgrade we chose to go with the Windows internal
> | database. The upgrade process went smoothly without any problems at all. The
> | only down side was that it rest the secure configuration using using SSL &
> | port 8531 to a unsecured server using port 8530 during the upgrade. No
> | problem there as I reconfigured it again as before as a secure WSUS server
> | and used port 8531 for the Admin site. Once this was done everything started
> | working ok with the clients reporting and being able to deploy updates and
> | run reports. The securing WSUS 3.0 introduced a new problem. Except for
> | myself & another coworker all others in the WSUS Administrators group cannot
> | connect to the WSUS server by using servername.domainname and port 8531 or
> | any other port or just the server name . They get an error like below.
> |
> | "Cannot connect to <<WSUS server name>> the server may be using another port
> | or different secure socket layer"
> |
> | We all have the same AD group memberships on the server, we are members of
> | the WSUS Administrators group and also local administrator on the server,
> | only myself & another coworker can access the server all others in the same
> | group cannot. The PC's that the WSUS consoles and MMC are installed are on
> | the same AD domain as the WSUS server. IF my co worker or myself logs on to
> | their PCs we can access the WSUS server through the remote console.
> |
> | My IIS settings for the WSUS admin site are as follows,
> |
> | Default Website Require SSL Authentication
> |
> | Client web services no anonymous
> | Self Update no anonymous
> |
> | WSUS Administration site
> | API Removing 30 yes Integrated
> | Client web services yes anonymous
> | Content no anonymous
> | Dss Auth Webservice yes anonymous
> | Inventory no anonymous
> | Reporting Webservice no anonymous
> | Self Update no anonymous + Integrated
> | Server Sync Webservice yes anonymous
> | Simple Auth Webservice yes anonymous
> |
> |
> | I also see the following errors in the application log. These errors seem to
> | be common among lot of other WSUS 3.0 users who have commented in the WSUS
> | forums and are supposed to related
> | the Server Health monitoring subsystem of WSUS. Although these error appear
> | in the application log the WSUS server works fine except the console access
> | problem which I mentioned before.
> |
> | Event Type: Error
> | Event Source: Windows Server Update Services
> | Event Category: Web Services
> | Event ID: 12012
> | Description:
> | The API Remoting Web Service is not working.
> |
> | Event Type: Error
> | Event Source: Windows Server Update Services
> | Event Category: Web Services
> | Event ID: 12032
> | Description:
> | The Server Synchronization Web Service is not working.
> |
> |
> | Event Type: Error
> | Event Source: Windows Server Update Services
> | Event Category: Web Services
> | Event ID: 12022
> | Description:
> | The Client Web Service is not working.
> |
> | Event Type: Error
> | Event Source: Windows Server Update Services
> | Event Category: Web Services
> | Event ID: 12042
> | Description:
> | The SimpleAuth Web Service is not working.
> |
> | Event Type: Error
> | Event Source: Windows Server Update Services
> | Event Category: Web Services
> | Event ID: 12052
> | Description:
> | The DSS Authentication Web Service is not working.
> |
> | I have been visiting most of the WSUS forums out there; these errors are
> | common among lot of other users out there although some are for new
> | installations of WSUS 3.0. I have tried all of the solutions suggested in the
> | following forum postings page and have still not had any luck with then issue
> | on our server.
> |
> | http://www.wsus.info/forums/lofiversion/index.php?t10007.html
> |
> | Appreciate if anyone can let me know of any suggestions you might have,
> |
> | Thanks for your help,
> |
> | SRMW
> |
>
> Perhaps try the WSUS Newsgroup
> http://www.microsoft.com/technet/co...crosoft.public.windows.server.update_services
>
> news://msnews.microsoft.com/microsoft.public.windows.server.update_services
> (OE client)
>
> Xposted for convenience
> --
> ====================================
> TaurArian [MS-MVP] 2005-2008 - Australia
> ====================================
> How to make a good post: http://www.dts-l.org/goodpost.htm
> Defending your machine: http://defendingyourmachine2.blogspot.com/
> http://taurarian.mvps.org/index.htm
>
> Emails will not be acknowledged - please post to the newsgroup so all may benefit.
>
>
>

 

[SRMW]

Re: Problems after upgrading from WSUS 2.0 to WSUS 3.0

Appriciate if someone can help, thanks

"SRMW" wrote:

> Thanks for your reply, I believe my post appears in the Update services
> newesgroup, please let me know if it is not,
>
> "TaurArian [MS-MVP]" wrote:
>
> >
> >
> > "SRMW" <SRMW@discussions.microsoft.com> wrote in message
> > news:E510DCEE-6198-4C99-ADB6-81DBB1F12F74@microsoft.com...
> > | Hello,
> > |
> > | We are having some strange problems after upgrading our secure WSUS 2.0 SP1
> > | server to WSUS 3.0. Previously we were using SQL server 2000 running on the
> > | same server, during the upgrade we chose to go with the Windows internal
> > | database. The upgrade process went smoothly without any problems at all. The
> > | only down side was that it rest the secure configuration using using SSL &
> > | port 8531 to a unsecured server using port 8530 during the upgrade. No
> > | problem there as I reconfigured it again as before as a secure WSUS server
> > | and used port 8531 for the Admin site. Once this was done everything started
> > | working ok with the clients reporting and being able to deploy updates and
> > | run reports. The securing WSUS 3.0 introduced a new problem. Except for
> > | myself & another coworker all others in the WSUS Administrators group cannot
> > | connect to the WSUS server by using servername.domainname and port 8531 or
> > | any other port or just the server name . They get an error like below.
> > |
> > | "Cannot connect to <<WSUS server name>> the server may be using another port
> > | or different secure socket layer"
> > |
> > | We all have the same AD group memberships on the server, we are members of
> > | the WSUS Administrators group and also local administrator on the server,
> > | only myself & another coworker can access the server all others in the same
> > | group cannot. The PC's that the WSUS consoles and MMC are installed are on
> > | the same AD domain as the WSUS server. IF my co worker or myself logs on to
> > | their PCs we can access the WSUS server through the remote console.
> > |
> > | My IIS settings for the WSUS admin site are as follows,
> > |
> > | Default Website Require SSL Authentication
> > |
> > | Client web services no anonymous
> > | Self Update no anonymous
> > |
> > | WSUS Administration site
> > | API Removing 30 yes Integrated
> > | Client web services yes anonymous
> > | Content no anonymous
> > | Dss Auth Webservice yes anonymous
> > | Inventory no anonymous
> > | Reporting Webservice no anonymous
> > | Self Update no anonymous + Integrated
> > | Server Sync Webservice yes anonymous
> > | Simple Auth Webservice yes anonymous
> > |
> > |
> > | I also see the following errors in the application log. These errors seem to
> > | be common among lot of other WSUS 3.0 users who have commented in the WSUS
> > | forums and are supposed to related
> > | the Server Health monitoring subsystem of WSUS. Although these error appear
> > | in the application log the WSUS server works fine except the console access
> > | problem which I mentioned before.
> > |
> > | Event Type: Error
> > | Event Source: Windows Server Update Services
> > | Event Category: Web Services
> > | Event ID: 12012
> > | Description:
> > | The API Remoting Web Service is not working.
> > |
> > | Event Type: Error
> > | Event Source: Windows Server Update Services
> > | Event Category: Web Services
> > | Event ID: 12032
> > | Description:
> > | The Server Synchronization Web Service is not working.
> > |
> > |
> > | Event Type: Error
> > | Event Source: Windows Server Update Services
> > | Event Category: Web Services
> > | Event ID: 12022
> > | Description:
> > | The Client Web Service is not working.
> > |
> > | Event Type: Error
> > | Event Source: Windows Server Update Services
> > | Event Category: Web Services
> > | Event ID: 12042
> > | Description:
> > | The SimpleAuth Web Service is not working.
> > |
> > | Event Type: Error
> > | Event Source: Windows Server Update Services
> > | Event Category: Web Services
> > | Event ID: 12052
> > | Description:
> > | The DSS Authentication Web Service is not working.
> > |
> > | I have been visiting most of the WSUS forums out there; these errors are
> > | common among lot of other users out there although some are for new
> > | installations of WSUS 3.0. I have tried all of the solutions suggested in the
> > | following forum postings page and have still not had any luck with then issue
> > | on our server.
> > |
> > | http://www.wsus.info/forums/lofiversion/index.php?t10007.html
> > |
> > | Appreciate if anyone can let me know of any suggestions you might have,
> > |
> > | Thanks for your help,
> > |
> > | SRMW
> > |
> >
> > Perhaps try the WSUS Newsgroup
> > http://www.microsoft.com/technet/co...crosoft.public.windows.server.update_services
> >
> > news://msnews.microsoft.com/microsoft.public.windows.server.update_services
> > (OE client)
> >
> > Xposted for convenience
> > --
> > ====================================
> > TaurArian [MS-MVP] 2005-2008 - Australia
> > ====================================
> > How to make a good post: http://www.dts-l.org/goodpost.htm
> > Defending your machine: http://defendingyourmachine2.blogspot.com/
> > http://taurarian.mvps.org/index.htm
> >
> > Emails will not be acknowledged - please post to the newsgroup so all may benefit.
> >
> >
> >

 

[tic1745@hotmail.co]

Re: Problems after upgrading from WSUS 2.0 to WSUS 3.0

Hi,

Sorry, I won't be able to help you. I just want to ask you before I will
upgrade my WSUS server.

I have WSUS 2 with sql 2000 on the same box and I don't use ssl.
I am thinking to upgrade to WSUS 3 in the same box but I don't want to
install full version of SQL since my other application won't work on SQL
2005. Will it work? Will the upgade keeps all the approved and non approved
setting?

your reply will be appreciated.

"SRMW" wrote:

> Appriciate if someone can help, thanks
>
> "SRMW" wrote:
>
> > Thanks for your reply, I believe my post appears in the Update services
> > newesgroup, please let me know if it is not,
> >
> > "TaurArian [MS-MVP]" wrote:
> >
> > >
> > >
> > > "SRMW" <SRMW@discussions.microsoft.com> wrote in message
> > > news:E510DCEE-6198-4C99-ADB6-81DBB1F12F74@microsoft.com...
> > > | Hello,
> > > |
> > > | We are having some strange problems after upgrading our secure WSUS 2.0 SP1
> > > | server to WSUS 3.0. Previously we were using SQL server 2000 running on the
> > > | same server, during the upgrade we chose to go with the Windows internal
> > > | database. The upgrade process went smoothly without any problems at all. The
> > > | only down side was that it rest the secure configuration using using SSL &
> > > | port 8531 to a unsecured server using port 8530 during the upgrade. No
> > > | problem there as I reconfigured it again as before as a secure WSUS server
> > > | and used port 8531 for the Admin site. Once this was done everything started
> > > | working ok with the clients reporting and being able to deploy updates and
> > > | run reports. The securing WSUS 3.0 introduced a new problem. Except for
> > > | myself & another coworker all others in the WSUS Administrators group cannot
> > > | connect to the WSUS server by using servername.domainname and port 8531 or
> > > | any other port or just the server name . They get an error like below.
> > > |
> > > | "Cannot connect to <<WSUS server name>> the server may be using another port
> > > | or different secure socket layer"
> > > |
> > > | We all have the same AD group memberships on the server, we are members of
> > > | the WSUS Administrators group and also local administrator on the server,
> > > | only myself & another coworker can access the server all others in the same
> > > | group cannot. The PC's that the WSUS consoles and MMC are installed are on
> > > | the same AD domain as the WSUS server. IF my co worker or myself logs on to
> > > | their PCs we can access the WSUS server through the remote console.
> > > |
> > > | My IIS settings for the WSUS admin site are as follows,
> > > |
> > > | Default Website Require SSL Authentication
> > > |
> > > | Client web services no anonymous
> > > | Self Update no anonymous
> > > |
> > > | WSUS Administration site
> > > | API Removing 30 yes Integrated
> > > | Client web services yes anonymous
> > > | Content no anonymous
> > > | Dss Auth Webservice yes anonymous
> > > | Inventory no anonymous
> > > | Reporting Webservice no anonymous
> > > | Self Update no anonymous + Integrated
> > > | Server Sync Webservice yes anonymous
> > > | Simple Auth Webservice yes anonymous
> > > |
> > > |
> > > | I also see the following errors in the application log. These errors seem to
> > > | be common among lot of other WSUS 3.0 users who have commented in the WSUS
> > > | forums and are supposed to related
> > > | the Server Health monitoring subsystem of WSUS. Although these error appear
> > > | in the application log the WSUS server works fine except the console access
> > > | problem which I mentioned before.
> > > |
> > > | Event Type: Error
> > > | Event Source: Windows Server Update Services
> > > | Event Category: Web Services
> > > | Event ID: 12012
> > > | Description:
> > > | The API Remoting Web Service is not working.
> > > |
> > > | Event Type: Error
> > > | Event Source: Windows Server Update Services
> > > | Event Category: Web Services
> > > | Event ID: 12032
> > > | Description:
> > > | The Server Synchronization Web Service is not working.
> > > |
> > > |
> > > | Event Type: Error
> > > | Event Source: Windows Server Update Services
> > > | Event Category: Web Services
> > > | Event ID: 12022
> > > | Description:
> > > | The Client Web Service is not working.
> > > |
> > > | Event Type: Error
> > > | Event Source: Windows Server Update Services
> > > | Event Category: Web Services
> > > | Event ID: 12042
> > > | Description:
> > > | The SimpleAuth Web Service is not working.
> > > |
> > > | Event Type: Error
> > > | Event Source: Windows Server Update Services
> > > | Event Category: Web Services
> > > | Event ID: 12052
> > > | Description:
> > > | The DSS Authentication Web Service is not working.
> > > |
> > > | I have been visiting most of the WSUS forums out there; these errors are
> > > | common among lot of other users out there although some are for new
> > > | installations of WSUS 3.0. I have tried all of the solutions suggested in the
> > > | following forum postings page and have still not had any luck with then issue
> > > | on our server.
> > > |
> > > | http://www.wsus.info/forums/lofiversion/index.php?t10007.html
> > > |
> > > | Appreciate if anyone can let me know of any suggestions you might have,
> > > |
> > > | Thanks for your help,
> > > |
> > > | SRMW
> > > |
> > >
> > > Perhaps try the WSUS Newsgroup
> > > http://www.microsoft.com/technet/co...crosoft.public.windows.server.update_services
> > >
> > > news://msnews.microsoft.com/microsoft.public.windows.server.update_services
> > > (OE client)
> > >
> > > Xposted for convenience
> > > --
> > > ====================================
> > > TaurArian [MS-MVP] 2005-2008 - Australia
> > > ====================================
> > > How to make a good post: http://www.dts-l.org/goodpost.htm
> > > Defending your machine: http://defendingyourmachine2.blogspot.com/
> > > http://taurarian.mvps.org/index.htm
> > >
> > > Emails will not be acknowledged - please post to the newsgroup so all may benefit.
> > >
> > >
> > >

 

[Lawrence Garvin [MVP]]

Re: Problems after upgrading from WSUS 2.0 to WSUS 3.0

"tic1745@hotmail.co" <tic1745@hotmail.co@discussions.microsoft.com> wrote in
message news:99378DB4-8222-4A1E-A2AD-BCFDDF77BF84@microsoft.com...

> I have WSUS 2 with sql 2000 on the same box and I don't use ssl.
> I am thinking to upgrade to WSUS 3 in the same box but I don't want to
> install full version of SQL since my other application won't work on SQL
> 2005. Will it work?

YES.

The WSUS 3.0 installer will migrate your SQL 2000 WSUS 2.0 databases to the
WSUS 3.0 Windows Internal Database environment, and all of your
configuration and approval settings will be retained.


--
Lawrence Garvin, M.S., MCTS, MCP
MVP - Software Distribution (2005-2007)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin

 

[tic1745@hotmail.co]

Re: Problems after upgrading from WSUS 2.0 to WSUS 3.0

thanks

"Lawrence Garvin [MVP]" wrote:

> "tic1745@hotmail.co" <tic1745@hotmail.co@discussions.microsoft.com> wrote in
> message news:99378DB4-8222-4A1E-A2AD-BCFDDF77BF84@microsoft.com...
>
> > I have WSUS 2 with sql 2000 on the same box and I don't use ssl.
> > I am thinking to upgrade to WSUS 3 in the same box but I don't want to
> > install full version of SQL since my other application won't work on SQL
> > 2005. Will it work?
>
> YES.
>
> The WSUS 3.0 installer will migrate your SQL 2000 WSUS 2.0 databases to the
> WSUS 3.0 Windows Internal Database environment, and all of your
> configuration and approval settings will be retained.
>
>
> --
> Lawrence Garvin, M.S., MCTS, MCP
> MVP - Software Distribution (2005-2007)
> MS WSUS Website: http://www.microsoft.com/wsus
> My Websites: http://www.onsitechsolutions.com;
> http://wsusinfo.onsitechsolutions.com
> My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin
>
>

 

[R.liderman]

Re: Problems after upgrading from WSUS 2.0 to WSUS 3.0

I am having the same issue as you,
I have upgraded from Ver 2 to 3 I can see the Computers but my sys log is
loaded with :The SimpleAuth Web Service is not working. error 12042:"
If you have the found the solution please forward
Thanks
Ran

"TaurArian [MS-MVP]" wrote:

>
>
> "SRMW" <SRMW@discussions.microsoft.com> wrote in message
> news:E510DCEE-6198-4C99-ADB6-81DBB1F12F74@microsoft.com...
> | Hello,
> |
> | We are having some strange problems after upgrading our secure WSUS 2.0 SP1
> | server to WSUS 3.0. Previously we were using SQL server 2000 running on the
> | same server, during the upgrade we chose to go with the Windows internal
> | database. The upgrade process went smoothly without any problems at all. The
> | only down side was that it rest the secure configuration using using SSL &
> | port 8531 to a unsecured server using port 8530 during the upgrade. No
> | problem there as I reconfigured it again as before as a secure WSUS server
> | and used port 8531 for the Admin site. Once this was done everything started
> | working ok with the clients reporting and being able to deploy updates and
> | run reports. The securing WSUS 3.0 introduced a new problem. Except for
> | myself & another coworker all others in the WSUS Administrators group cannot
> | connect to the WSUS server by using servername.domainname and port 8531 or
> | any other port or just the server name . They get an error like below.
> |
> | "Cannot connect to <<WSUS server name>> the server may be using another port
> | or different secure socket layer"
> |
> | We all have the same AD group memberships on the server, we are members of
> | the WSUS Administrators group and also local administrator on the server,
> | only myself & another coworker can access the server all others in the same
> | group cannot. The PC's that the WSUS consoles and MMC are installed are on
> | the same AD domain as the WSUS server. IF my co worker or myself logs on to
> | their PCs we can access the WSUS server through the remote console.
> |
> | My IIS settings for the WSUS admin site are as follows,
> |
> | Default Website Require SSL Authentication
> |
> | Client web services no anonymous
> | Self Update no anonymous
> |
> | WSUS Administration site
> | API Removing 30 yes Integrated
> | Client web services yes anonymous
> | Content no anonymous
> | Dss Auth Webservice yes anonymous
> | Inventory no anonymous
> | Reporting Webservice no anonymous
> | Self Update no anonymous + Integrated
> | Server Sync Webservice yes anonymous
> | Simple Auth Webservice yes anonymous
> |
> |
> | I also see the following errors in the application log. These errors seem to
> | be common among lot of other WSUS 3.0 users who have commented in the WSUS
> | forums and are supposed to related
> | the Server Health monitoring subsystem of WSUS. Although these error appear
> | in the application log the WSUS server works fine except the console access
> | problem which I mentioned before.
> |
> | Event Type: Error
> | Event Source: Windows Server Update Services
> | Event Category: Web Services
> | Event ID: 12012
> | Description:
> | The API Remoting Web Service is not working.
> |
> | Event Type: Error
> | Event Source: Windows Server Update Services
> | Event Category: Web Services
> | Event ID: 12032
> | Description:
> | The Server Synchronization Web Service is not working.
> |
> |
> | Event Type: Error
> | Event Source: Windows Server Update Services
> | Event Category: Web Services
> | Event ID: 12022
> | Description:
> | The Client Web Service is not working.
> |
> | Event Type: Error
> | Event Source: Windows Server Update Services
> | Event Category: Web Services
> | Event ID: 12042
> | Description:
> | The SimpleAuth Web Service is not working.
> |
> | Event Type: Error
> | Event Source: Windows Server Update Services
> | Event Category: Web Services
> | Event ID: 12052
> | Description:
> | The DSS Authentication Web Service is not working.
> |
> | I have been visiting most of the WSUS forums out there; these errors are
> | common among lot of other users out there although some are for new
> | installations of WSUS 3.0. I have tried all of the solutions suggested in the
> | following forum postings page and have still not had any luck with then issue
> | on our server.
> |
> | http://www.wsus.info/forums/lofiversion/index.php?t10007.html
> |
> | Appreciate if anyone can let me know of any suggestions you might have,
> |
> | Thanks for your help,
> |
> | SRMW
> |
>
> Perhaps try the WSUS Newsgroup
> http://www.microsoft.com/technet/co...crosoft.public.windows.server.update_services
>
> news://msnews.microsoft.com/microsoft.public.windows.server.update_services
> (OE client)
>
> Xposted for convenience
> --
> ====================================
> TaurArian [MS-MVP] 2005-2008 - Australia
> ====================================
> How to make a good post: http://www.dts-l.org/goodpost.htm
> Defending your machine: http://defendingyourmachine2.blogspot.com/
> http://taurarian.mvps.org/index.htm
>
> Emails will not be acknowledged - please post to the newsgroup so all may benefit.
>
>
>

 

[Lawrence Garvin [MVP]]

Re: Problems after upgrading from WSUS 2.0 to WSUS 3.0


"R.liderman" <Rliderman@discussions.microsoft.com> wrote in message
news:24E62D3B-A950-4ED1-ACCA-40C643186AF8@microsoft.com...

>> "SRMW" <SRMW@discussions.microsoft.com> wrote in message
>> news:E510DCEE-6198-4C99-ADB6-81DBB1F12F74@microsoft.com...
>> | Hello,
>> |
>> | We are having some strange problems after upgrading our secure WSUS 2.0
>> SP1
>> | server to WSUS 3.0.

> I am having the same issue as you,
> I have upgraded from Ver 2 to 3

This particular upgrade issue is well documented in the release notes.

Upgrading from WSUS 2.0 to WSUS 3.0 requires the re-entry of the
authentication credentials on the proxy configuration page of the WSUS
Administration Console after completing the upgrade.

--
Lawrence Garvin, M.S., MCTS, MCP
MVP - Software Distribution (2005-2007)
MS WSUS Website: http://www.microsoft.com/wsus
My Websites: http://www.onsitechsolutions.com;
http://wsusinfo.onsitechsolutions.com
My MVP Profile: http://mvp.support.microsoft.com/profile/Lawrence.Garvin