Home
.. About WSUS Wiki

WSUS
.. WSUS FAQ
.. WSUS on SBS
.. WSUS Troubleshooting
.. WSUS News Groups
.. Known WSUS Issues
.. WSUS Links
.. WSUS Wish List

WSUS Documents
.. WSUS Deployment Guide
.. WSUS Installation Guide
.. WSUS Release Notes
.. WSUS Best Practice

SUS
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues
.. SUS FAQ
.. What Is SUS
.. SUS Troubleshooting
.. SUS Links
.. SUS Known Issues

Wiki Community

 .. Wiki Contributors
.. I Love WSUS
.. WSUS Wiki Diary
.. Wiki Statistics
.. To Do Page

Miscellaneous Stuff
.. Other Resources
.. Do You Know?

SOAP Fault0x00012c

You see this error in WindowsUpdate.log while the AU Client is trying to communicate with WSUS RC.

Error:

SOAP Fault: 0x00012c
2005-04-09 02:34:20-0400  860 370     faultstring:Fault occurred
2005-04-09 02:34:20-0400  860 370     ErrorCode:RegistrationRequired(3)
2005-04-09 02:34:20-0400  860 370     Message:need to call RegisterComputer.
2005-04-09 02:34:20-0400  860 370
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2005-04-09 02:34:20-0400  860 370
ID:f59bb389-f830-49a0-b1ae-990169f5f7eb
2005-04-09 02:34:20-0400  860 370     URL returning Fault:
http://wsus/ClientWebService/client.asmx
2005-04-09 02:34:20-0400  860 370 PT: Attempting to recover, action=0
2005-04-09 02:34:20-0400  860 370 PT: Calling GetConfig on server
2005-04-09 02:34:20-0400  860 370 Add header for accept-encoding: xpress
succeeded
2005-04-09 02:34:20-0400  860 370 DetectCompressionType returning type 1,
hr=0x0
2005-04-09 02:34:20-0400  860 370 PT: Using server URL
http://wsus/SimpleAuthWebService/SimpleAuth.asmx
2005-04-09 02:34:20-0400  860 370 DetectCompressionType returning type 0,
hr=0x1
2005-04-09 02:34:20-0400  860 370 Add header for accept-encoding: xpress
succeeded
2005-04-09 02:34:20-0400  860 370 DetectCompressionType returning type 1,
hr=0x0
2005-04-09 02:34:20-0400  860 370 Add header for accept-encoding: xpress
succeeded
2005-04-09 02:34:20-0400  860 370 StatusCode for transaction returned from
WinHttpQueryHeaders is 500.
2005-04-09 02:34:20-0400  860 370 Extended Winhttp Message: Internal Server
Error..
2005-04-09 02:34:20-0400  860 370 DetectCompressionType returning type 0,
hr=0x1
2005-04-09 02:34:20-0400  860 370 SyncUpdates: 0x8024400d
2005-04-09 02:34:20-0400  860 370 SOAP Fault: 0x00012c
2005-04-09 02:34:20-0400  860 370     faultstring:Fault occurred
2005-04-09 02:34:20-0400  860 370     ErrorCode:RegistrationRequired(3)
2005-04-09 02:34:20-0400  860 370     Message:need to call RegisterComputer.
2005-04-09 02:34:20-0400  860 370
Method:"http://www.microsoft.com/SoftwareDistribution/Server/ClientWebService/SyncUpdates"
2005-04-09 02:34:20-0400  860 370
ID:60937dea-e6dd-4aea-9469-e93775db1823
2005-04-09 02:34:20-0400  860 370     URL returning Fault:
http://wsus/ClientWebService/client.asmx
2005-04-09 02:34:20-0400  860 370 Sync of Updates: 0x8024400d
2005-04-09 02:34:20-0400  860 370 WU client failed Searching for update with
error 0x8024400d
2005-04-09 02:34:20-0400  860 370 Search Callback Failed, hr is 0x8024400d
2005-04-09 02:34:20-0400  860 370 Setting next AU detection timeout to
2005-04-09 11:34:20
2005-04-09 02:34:20-0400  860 370 Setting AU scheduled install time to
2005-04-10 06:00:00
2005-04-09 02:34:20-0400  860 370 WU client calls back to search call
{3AC982DB-B7F0-4F4B-9953-05E721BBA509} with code Call failed and error
0x8024400d
2005-04-09 02:34:20-0400  860 370 WU client completed and deleted call
{3AC982DB-B7F0-4F4B-9953-05E721BBA509}
2005-04-09 02:34:25-0400  860 66c CEventCacheFile::Init failed = 80070002.

Description:

Currently, if WMI is having issues on a client machine, the client will be unable to sync.  It will fail to get OS information to send to the WSUS server and will simply bail out.

Workaround:

One thing to check is, if WMI is working properly on this client machine?

To do so, go to the command prompt and run wbemtest and try to connect with default settings. If you run WBEMTEST on the machine and unable to connect to the root means an issue with WMI on the workstation.

Stop the "Windows Management Instrumentation" Service

Go to "system32\wbem"  folder

Delete the "repository" folder

Start the "Windows Management Instrumentation" Service

run "wuauclt /detectnow" to force check.

After this it should start working..

After RTM, if WMI is having issues on the machine, the client will be unable to send up certain OS-related information but will still be able to sync. So, you still might see "Unknown" for OS (or you might see some OS information but not all OS information, it depends on the state of WMI) but those issues will no longer block sync (and your client will still be able to receive updates).

Status: This is a known issue and will be fixed at RTM.

Note: If you (Microsoft) fix this problem, please let us know here. Rajiv thanks for adding the comment here.

Track ID is: 187309821.