Update failed install due to split cab files?

move question system center configuration manager forums > configuration manager software distribution  here.

my software updates works fine throug sccm deployment except 1 big size update, split 2 parts of cab file, , failed install on client. suspect sccm client agent not support split cab file.

does 1 have suggestion?

i publish package size 481mb throug wsus sdk, saw on c:\wsus\wsuscontent , c:\wsus\updateservicespackages folder there 2 cab files update.

 

i use interface microsoft.updateservices.administration.ipublisher.publishpackage() publish update package, interface automaticlly compress package 2 cab files. not know how change it.

microsoft.updateservices.administration.dll version 3.1.6001.1 update services remotable administration api, not think there configue used set max package size.

on client, downloaded cab files same size server side files under c:\wsus\updateservicespackages

c:\windows\syswow64\ccm\cache\e2c8bfed-4f2b-b3f8-0647-fe66af8ca750.1.system

89e5ca14-5b87-4e7c-8e34-bd557764a286_1.cab size 436 mb

89e5ca14-5b87-4e7c-8e34-bd557764a286_2.cab size 19 mb

another point want mention update package consists of lots of executable files , 1 invoker file, invoker file has responsibility invoke other files. , invoker file packaged second cab file.

i extract these 2 cab files winrar correctly , invoke files run without error manually.

below detail server/client information , logs errors.

sccm server:

os: windows server 2008 sp1 64bit

sccm version: sccm 2007 sp2

wsus version: wsus 3.0 sp1

client:

os: windows server 2008 hpc 64bit

wuahandler.log:

failed download updates wuagent datastore. error = 0x80070570. wuahandler 5/4/2011 4:14:48 pm 3792 (0x0ed0)

updatesdeployment.log:

failed update (site_d9b47bd5-ee30-4d12-b545-8ff7b69aefe0/sum_e2c8bfed-4f2b-b3f8-0647-fe66af8ca750) article id, error = 0x80040215

updateshandler.log:

failed initiate install of wsus updates, error = 0x80070570 updateshandler 5/4/2011 4:14:48 pm 3792 (0x0ed0)

failed start batch install through wsus install handler , error = 0x80070570 updateshandler 5/4/2011 4:14:48 pm 3792 (0x0ed0) installupdatesinbatch failed error 0x80070570 updateshandler 5/4/2011 4:14:48 pm 3792 (0x0ed0)

executing updates job ({5820e09f-b22a-4f1a-810e-cadddb5cc8ec}). updateshandler 5/4/2011 4:14:48 pm 3792 (0x0ed0)

starting or resuming update (e2c8bfed-4f2b-b3f8-0647-fe66af8ca750). updateshandler 5/4/2011 4:14:48 pm 3792 (0x0ed0)

failed initiate install of wsus updates, error = 0x80070570 updateshandler 5/4/2011 4:14:52 pm 3792 (0x0ed0)

failed start wsusupdate, error = 0x80070570 updateshandler 5/4/2011 4:14:52 pm 3792 (0x0ed0)

cdeploymentjob -- failed start procesing of update (e2c8bfed-4f2b-b3f8-0647-fe66af8ca750). error = 0x80070570 updateshandler 5/4/2011 4:14:52 pm 3792 (0x0ed0)

execution completed job ({5820e09f-b22a-4f1a-810e-cadddb5cc8ec}). updateshandler 5/4/2011 4:14:52 pm 3792 (0x0ed0)

raising event:

[sms_codepage(437), sms_localeid(1033)] instance of sms_sumagentupdateerror_internal {

  clientid = "guid:bd7b161f-98d4-4fd6-88fc-988c2d830432";

  datetime = "20110504081452.437000+000";

  machinename = "hh2node";

  modelname = "site_d9b47bd5-ee30-4d12-b545-8ff7b69aefe0/sum_e2c8bfed-4f2b-b3f8-0647-  fe66af8ca750";

  processid = 1320; sdmpackageversion = "1";

  sitecode = "gbb"; threadid = 3792; updateid = "e2c8bfed-4f2b-b3f8-0647-fe66af8ca750";

  win32errorcode = 2147943792;

};

  updateshandler 5/4/2011 4:14:52 pm 3792 (0x0ed0)

sending completion status execution manager updateshandler 5/4/2011 4:14:52 pm 3792 (0x0ed0)

successfully sent job ({5820e09f-b22a-4f1a-810e-cadddb5cc8ec}) success completion sdmagent updateshandler 5/4/2011 4:14:52 pm 3792 (0x0ed0) completejob received sdm. updateshandler 5/4/2011 4:14:52 pm 3948 (0x0f6c)

complete - job ({5820e09f-b22a-4f1a-810e-cadddb5cc8ec}) cleanup. updateshandler 5/4/2011 4:14:52 pm 3948 (0x0f6c)

completejob - job ({5820e09f-b22a-4f1a-810e-cadddb5cc8ec}) removed job manager list. updateshandler 5/4/2011 4:14:52 pm 3948 (0x0f6c)

 

i'm not expert, agree suspect... think splitted cab files can problem windows update. when played big size files created big self-exractor zip archive (that once file extrated runs real setup.exe) multipat archive and for each single file i wrapped again in self-extractor zip archive (that unzip multipart file).. in way had not several splitted cab several .exe files... , works fine....

Windows Server  >  WSUS