[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 16614
  • Last Modified:

WSUS 3.0 Error 12012. The API Remoting Web Service is not working.

Hi Guys,

I have installed WSUS 3.0 on a Windows Server 2003 SBS but I am unable to connect to the administration MSC*.

I have the follow error in System Logs > Application.

Event Type:      Error
Event Source:      Windows Server Update Services
Event Category:      Web Services
Event ID:      12012
Date:            04/10/2007
Time:            14:02:30
User:            N/A
Computer:      ASYNTSERVER
Description:
The API Remoting Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I have used wsusutil checkhealth to make sure there are no other problems and this appears to be the only error I have.

I have uninstalled and reinstalled both version of the ASP .Net frame work (1.1 & 2.0) with no fix.

I started to follow the Microsoft Help & Support document regarding this error message, but when I was asked to compare 3 vbs files, Microsoft only listed partial parts of these files, making it impossible for me to tell if the vbs files are correct.

I have, however, checked the cacls on the <WSUSInstallDir>\WebServices\ApiRemoting30 and can confirm these ACEs are correct.

I have reinstalled WSUS 3.0, but still no luck!

Any ideas?
0
WizPrang
Asked:
WizPrang
  • 10
  • 5
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Did you follow the SBS version of installing WSUS 3.0 documentation?  http://sbsurl.com/wsus

Jeff
TechSoEasy
0
 
WizPrangAuthor Commented:
Hi Jeff,

Thanks for the response.

I didn't follow this particular guide, but I have successfully installed WSSU 3.0 on another Windows Server 2003 SBS.

However, I have checked through the stages of the guide, and it is the same as the procedure I used.

Regards,
0
 
WizPrangAuthor Commented:
Also, just to confirm, I can access the http://SBS-Server:8530 website, only there is no read permissions, which from experience, has a default setting.
0
Nothing ever in the clear!

This technical paper will help you implement VMware’s VM encryption as well as implement Veeam encryption which together will achieve the nothing ever in the clear goal. If a bad guy steals VMs, backups or traffic they get nothing.

 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Is that the ONLY error message you're getting?
0
 
WizPrangAuthor Commented:
Yep
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Hmmm...  I really can't think of anything else for you.  Sorry.

Jeff
TechSoEasy
0
 
WizPrangAuthor Commented:
Hi Jeff,

I have restarted the server (couldn't before as the customer was involved in a project).

Now I have multiple errors...!

Event Type:      Error
Event Source:      Windows Server Update Services
Event Category:      Web Services
Event ID:      12002
Date:            09/10/2007
Time:            09:46:16
User:            N/A
Computer:      ASYNTSERVER
Description:
The Reporting Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error
Event Source:      Windows Server Update Services
Event Category:      Clients
Event ID:      13042
Date:            09/10/2007
Time:            09:46:16
User:            N/A
Computer:      ASYNTSERVER
Description:
Self-update is not working.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error
Event Source:      Windows Server Update Services
Event Category:      Web Services
Event ID:      12032
Date:            09/10/2007
Time:            09:46:16
User:            N/A
Computer:      ASYNTSERVER
Description:
The Server Synchronization Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error
Event Source:      Windows Server Update Services
Event Category:      Web Services
Event ID:      12022
Date:            09/10/2007
Time:            09:46:16
User:            N/A
Computer:      ASYNTSERVER
Description:
The Client Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error
Event Source:      Windows Server Update Services
Event Category:      Web Services
Event ID:      12042
Date:            09/10/2007
Time:            09:46:16
User:            N/A
Computer:      ASYNTSERVER
Description:
The SimpleAuth Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error
Event Source:      Windows Server Update Services
Event Category:      Web Services
Event ID:      12052
Date:            09/10/2007
Time:            09:46:16
User:            N/A
Computer:      ASYNTSERVER
Description:
The DSS Authentication Web Service is not working.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Event Type:      Error
Event Source:      SmallBusinessServer
Event Category:      SBS Monitoring
Event ID:      4104
Date:            09/10/2007
Time:            09:46:53
User:            N/A
Computer:      ASYNTSERVER
Description:
Could not connect to the monitoring database. This can occur when there are multiple connections to the database. Wait a short period of time, and then try again. If this error persists, run the Monitoring Configuration Wizard, and select Reinstall monitoring features.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 05 40 00 80               .@.€    
0
 
WizPrangAuthor Commented:
I'm going to uninstall WSUS 3.0 and use the guide you suggested to rule out the installation procedure as the problem.
0
 
WizPrangAuthor Commented:
I've reinstalled IIS and I have the same errors...

When I go to the http://go.microsoft.com/fwlink/events.asp links Microsoft are suggestion I do the following.

Check the IIS configuration of the reporting Web service using the IIS script adsutil.vbs (or use the IIS Administration UI Tool).
Open a command window.
Locate the adsutil.vbs tool, which is typically in <InetpubDir>\AdminScripts.
Locate WSUS virtual directories on the IIS server: type <InetpubDir>\AdminScripts\adsutil.vbs find path
Find the path of the DssAUthWebService (it will look like W3SVC/<WebSiteID>/ROOT/DssAuthWebService).
Get the properties of the web service: type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC/<WebSiteID>/ROOT/DssAuthWebService
Compare the output with typical values below (this is a partial list): KeyType:"IIsWebVirtualDir" AppRoot:"/LM/W3SVC/<WebSiteID>/ROOT/DssAuthWebService" AppFriendlyName:"DssAuthWebService" AppIsolated:2 Path: "<WSUSInstallDir>\WebServices\DssAuthWebService" AccessFlags:513 AccessExecute:False AccessSource:False AccessRead:True AccessWrite:False AccessScript:True AccessNoRemoteExecute:False AccessNoRemoteRead:False AccessNoRemoteWrite:False AccessNoRemoteScript:False AccessNoPhysicalDir:False AspScriptErrorSentToBrowser:False AspEnableParentPaths:False AuthFlags:1 AuthBasic:False AuthAnonymous:True AuthNTLM:False AuthMD5:False AuthPassport:False AppPoolId:WsusPool"
Type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC/1
Compare the output with typical values below  (this is a partial list).KeyType:"IIsWebServer" ServerState2 ServerComment:"Default Website" ServerSize:1 ServerBindings:":80:" SecureBindings:":443:" ConnectionTimeout:180 DefaultDoc:"Default.htm,Default.asp,index.htm,iisstart.htm" AspBufferingOn:False LogPluginClsid:"{FF160663-DE82-11CF-BC0A-00AA006111E0}" Win32Error:0 AppPoolId:"DefaultAppPool"
Type <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC
Compare output with typical values below. This is a partial listing. For more information, see "Appendix C: IIS Settings for Web Services" in the WSUS 3.0 Operations Guide at http://go.microsoft.com/fwlink/?LinkId=81072  KeyType:"IIsWebService" MaxConnections:4294967295 AnonymousUserName:"IUSR_<machinename>" AuthFlags:1 AuthBasic:False AuthAnonymous:True AuthNTLM:False AuthMD5:False AuthPassport:False AppPoolId:"DefaultAppPool" IIs5IsolationModeEnabled:False

Any ideas if these steps are relevent?
0
 
WizPrangAuthor Commented:
followed the steps, but Microsoft suggested no changes if I found any difference...

I found a slight difference in the <InetpubDir>\AdminScripts\adsutil.vbs enum W3SVC/<WebSiteID>/ROOT/DssAuthWebService

AspScriptErrorSentToBrowser:False AspEnableParentPaths:False AuthFlags:1 AuthBasic:False AuthAnonymous:True AuthNTLM:False AuthMD5:False AuthPassport:False AppPoolId:WsusPool

Were all missing.. does this matter? - If so, how can I amend this?
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Perhaps I missed something... you said you were reinstalling WSUS 3.0, not IIS... how did that happen?

Jeff
TechSoEasy
0
 
WizPrangAuthor Commented:
Sorry, long day yesterday. I meant to type WSUS 3.0...!
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Well, since Monitoring & Reporting doesn't seem to be running have you resolved that issue?

See:  http://groups.google.com/group/microsoft.public.windows.server.sbs/browse_thread/thread/11b4540c2347edd1/0000e4a5bfca060c?lnk=st&rnum=1#0000e4a5bfca060c

Jeff
TechSoEasy
0
 
WizPrangAuthor Commented:
Hi Jeff,

I have checked the services and can only assume that the Error log and yourself are refering to MSSQL$SBSMONITORING, yet the service has started and there are no other errors to indicate there being a problem with this service..

Any other suggestions? - Do you think that the VB scripts could be the problem?
0
 
WizPrangAuthor Commented:
Tried everything, my last resort was getting in contact with Microsoft Support (thankfully we are a partner so support was free !)

After 3 - 4 hours of them remotely trying to resolve the problem, it was a little tick box in IIS that eventually gave us the results.

I/You need to ensure that HTTP Keep Alive is ticked within IIS.

To do this...

Open IIS > right click WSUS Administration > click properties > on the Web Site tab under Connections tick Enable HTTP Keep-Alives.

Fixed the problem!!

Thanks for your help Jeff!
0
 
actavisCommented:
I'm having the same problem, the seven errors of death. However my WSUS seems to be working as intended and has deployed numerous updates..

I have WSUS running on IIS 7 and have tried using appcmd.exe to check if it's possible to enable HTTP Keep-Alives but no luck. Probably enabled by default?

Anyway if anyone has any further insight in to this problem it would be welcome :)
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 10
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now