Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

ITMU v3 incompatible with newest wsusscn2.cab?

27 views
Skip to first unread message

Stephan Kaufmann

unread,
Jun 24, 2009, 1:57:03 PM6/24/09
to

Hi

Our SMS 2003 ITMU v3 Sync-Host downloaded the newest wsusscn2.cab file this
morning (24.06.09). Now the scan tool on all clients (x64 and x86 for Vista,
W2K3 and W2K8) failed. SMS reports:

Error Software Updates Scan Tool 11412 Scan component failed(type =
Microsoft Update): Error while trying to execute SmsWusHandler.exe.

In the SmsWusHandler.log I found:

$$<SmsWusHandler><Wed Jun 24 05:45:32.055 2009 W. Europe Daylight
Time><thread=5536 (0x15A0)>
ERROR: UpdateSearcher::Search() failed. $$<SmsWusHandler><Wed Jun 24
05:45:52.258 2009 W. Europe Daylight Time><thread=5536 (0x15A0)>
An error occurred when searching with the existing scan package service.
Removing the service...
$$<SmsWusHandler><Wed Jun 24 05:45:52.258 2009 W. Europe Daylight
Time><thread=5536 (0x15A0)>
ERROR: Search() failed with hRes=0x80070057 $$<SmsWusHandler><Wed Jun 24
05:45:52.696 2009 W. Europe Daylight Time><thread=5536 (0x15A0)>
0x80070057 is the hresult value for the operation. Returning 87 as the exit
code.

In the WindowsUpdate.log I found:

2009-06-24 17:34:25 980 424 EEHndlr FATAL: EE Serializer: Encountered
unknown expression b.LicenseDword
2009-06-24 17:34:25 980 424 EEHndlr FATAL: Parse failed: error 0x80070057
2009-06-24 17:34:25 980 424 EEHndlr FATAL: Parse failed with 0x80070057
2009-06-24 17:34:25 980 424 PT WARNING: Sync of Updates: 0x80070057
2009-06-24 17:34:25 980 424 Agent * WARNING: Failed to synchronize, error
= 0x80070057
2009-06-24 17:34:25 980 424 Agent * WARNING: Exit code = 0x80070057
2009-06-24 17:34:25 980 424 Agent *********
2009-06-24 17:34:25 980 424 Agent ** END ** Agent: Finding updates
[CallerId = SMS_WUSHandler]
2009-06-24 17:34:25 980 424 Agent *************
2009-06-24 17:34:25 980 424 Agent WARNING: WU client failed Searching for
update with error 0x80070057


With ProcessExplorer and the timestamps in WindowsUpdate.log I found the
problem must be in wsusscn2.cab in the file package7.cab and in there in the
2 files

c\688427
c\878231

Only these two files contain the expression b.LicenseDword.

Is there a bug in the current version of wsusscn2.cab or is ITMU no longer
usable to deploy all Microsoft updates?

Nick

unread,
Jun 25, 2009, 7:32:22 AM6/25/09
to
On Jun 24, 6:57 pm, Stephan Kaufmann

I am having the same problem too...

Microsoft?? have you broken it?

Yman

unread,
Jun 25, 2009, 3:06:02 PM6/25/09
to

Hi

I've got the same issues as you. All my windows XP, W2k3, W2K8 failed to
scan this morning. I'm using ITMU scan tool SP2; howerver I went download the
Catalog again manual, update distribution point and force Scan on my SMS Test
collection which contains 29 machines. 8 machines failed. Please see the
error below:

" ERROR: Failed while processing the executable.
Cmdline=["C:\WINDOWS\system32\VPCache\W0100139\SmsWusHandler.exe"
/Catalog:C:\WINDOWS\system32\VPCache\W0100139\wsusscn2.cab
/OutputXml:C:\WINDOWS\system32\VPCache\W0100139\Results.xml],
CurrentDir=[C:\WINDOWS\system32\VPCache\W0100139], ExitCode=[87]".

I'm thinking it is more a cluster F catalog which happen in the past, let's
wait and see what Microsoft is going to come up with.

What kind of Virsu Scan you are using, we are using Mcafee and I'm
suspecting Mcafee is causing this because in the same date Mcafee released
new dat file.

Thanks

Nick

unread,
Jun 26, 2009, 3:54:22 AM6/26/09
to
> > usable to deploy all Microsoft updates?- Hide quoted text -
>
> - Show quoted text -

hi,
using symantec antivirus.

anyone know if microsoft are aware of the problem?

Yman

unread,
Jun 26, 2009, 9:30:01 AM6/26/09
to

I want to add the scanwrapper parameter is wrong "Scan process started with
cmdline = /extended /cahe /kick"

The cache is misspelled.

Stephan Kaufmann

unread,
Jun 29, 2009, 10:46:01 AM6/29/09
to

I found a soloution. You need to update the Windows Update Agent to the
newest Version. You can download ist from:

http://support.microsoft.com/kb/932494/en-us

I downloaded them and added the tools to the existing packages as a new
program. Then I changed the dependency in all Update-Tool Programs to this
new version.

Hope this helps!

Yman

unread,
Jun 29, 2009, 11:25:01 AM6/29/09
to

Thanks Stephan,

I ment to reply to you I found the fix on Thursday by updating the Windows
Update agent. I have a lot of machine that has the windows update agent 5.8...

THanks

NJM

unread,
Jul 13, 2009, 9:33:01 AM7/13/09
to

Hi All,

Does anyone know if this is an MSU catalog file issue? And will it be
corrected in the 7/14/2009 release? We also started experiencing about 20%
failures shortly after ITMUv3 downloaded the last cab file. I will probably
push the latest update agent too but would like to know the source of the
problem.

Thanks!

"Nick" wrote:

> > > An error occurred when searching with the existing scan package service..

Tom Watson

unread,
Jul 23, 2009, 4:14:00 AM7/23/09
to
F.Y.I. This was a fairly common issue, that even caused the Microsoft
ConfigMgr Team to blog about it:-

http://blogs.technet.com/configurationmgr/archive/2009/06/25/sms-2003-sp3-itmu-scan-fails-with-wsusscn2-cab-released-on-june-23rd.aspx

Regards,
Tom Watson

0 new messages