OSD application install failing. XML Errors?!

[durwin]

I've got a problem with applications not installing as part of a task sequence. Worked fine up until a week ago and then "something" happened. I've recreated the applications, uninstalled/reinstalled the dp rebuilt the boot images, reinstalled branch cache and BITS and don't know what to do from here.. SCCM 2012 R2

 

The error from the smsts.log is :

 

::DecompressBuffer(65536)
Decompression (zlib) succeeded: original size 15396198, uncompressed size 132024172.

XML parsing error at line 473983 char 36: Operation aborted: MaxXMLSize constraint violated. <property name="Reserved" type="19"><value>1</value></property>PM 2552 (0x09F8)
bSuccess == ((VARIANT_BOOL)-1), HRESULT=80004005 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,1131)
spDoc.loadFromXML(sPolicy), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,3507)

Failed to load policy from XML.Unspecified error (Error: 80004005; Source: Windows)

CompileVersionInfoPolicies(sAppVIPolicyID), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,3459)
TS::Utility::CompileAppVersionInfoPolicies(m_sAppPolicyModelName), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,1016)
Step 2 out of 2 complete
Install application action failed: 'Java test'. Error Code 0x80004005

If i install the applications via the software center after the machine has been built there are no issues, everything works correctly. This is happening with all my task sequences and any of the applications. Packages also fail, strangely enough however the SCCM client install works.

 

I've also added a reboot between the client install and the application install. Anyone experience this or have any hints on how to fix it?

 

revelant section of the smsts.log is attached below..

 

 

 

!--------------------------------------------------------------------------------------------! TSManager 14-Nov-14 4:24:32 PM 1304 (0x0518)
Expand a string: FullOS TSManager 14-Nov-14 4:24:32 PM 1304 (0x0518)
Executing command line: smsappinstall.exe /app:ScopeId_EC06BDBE-B073-4D2C-865D-917B839D1C8A/Application_871c243f-7652-45d4-99c4-f6dbd1ad16b8 /basevar: /continueOnError:True TSManager 14-Nov-14 4:24:32 PM 1304 (0x0518)
[ smsinstallapp.exe ] InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Application Names: InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
'ScopeId_EC06BDBE-B073-4D2C-865D-917B839D1C8A/Application_871c243f-7652-45d4-99c4-f6dbd1ad16b8' InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
BaseVar = '', ContinueOnError='True' InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
SwdAction = '0001' InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Setting progress step for initialization InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Setting total steps to 1 InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Succeeded loading resource DLL 'C:\WINDOWS\CCM\1033\TSRES.DLL' InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Adding 1 installs to steps InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Setting total steps to 2 InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Step 1 out of 2 complete InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Installing application 'Java test' InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
GetAppMgmtSDKInterface successful InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Retrieving value from TSEnv for '_SMSTSPolicy_ScopeId_EC06BDBE-B073-4D2C-865D-917B839D1C8A/Application_871c243f-7652-45d4-99c4-f6dbd1ad16b8' InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
::DecompressBuffer(65536) InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Decompression (zlib) succeeded: original size 1227, uncompressed size 10572. InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Found App policy modelname:ScopeId_EC06BDBE-B073-4D2C-865D-917B839D1C8A/RequiredApplication_871c243f-7652-45d4-99c4-f6dbd1ad16b8 and CIversion:4 InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Start to compile TS policy InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Policy complied successfully in WMI 'root\ccm\policy\defaultmachine\requestedconfig' namespace InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
End TS policy compilation InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
Retrieving value from TSEnv for '_SMSTSCIVersionInfoPolicy' InstallApplication 14-Nov-14 4:24:32 PM 2552 (0x09F8)
::DecompressBuffer(65536) InstallApplication 14-Nov-14 4:24:33 PM 2552 (0x09F8)
Decompression (zlib) succeeded: original size 15396198, uncompressed size 132024172. InstallApplication 14-Nov-14 4:25:19 PM 2552 (0x09F8)
XML parsing error at line 473983 char 36: Operation aborted: MaxXMLSize constraint violated.
<property name="Reserved" type="19"><value>1</value></property> InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
bSuccess == ((VARIANT_BOOL)-1), HRESULT=80004005 (e:\NTS_SCCM_RELEASE\sms\common\inc\ccmxml.h,1131) InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
spDoc.loadFromXML(sPolicy), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,3507) InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Failed to load policy from XML.
Unspecified error (Error: 80004005; Source: Windows) InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
CompileVersionInfoPolicies(sAppVIPolicyID), HRESULT=80004005 (e:\nts_sccm_release\sms\framework\tscore\utils.cpp,3459) InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
TS::Utility::CompileAppVersionInfoPolicies(m_sAppPolicyModelName), HRESULT=80004005 (e:\nts_sccm_release\sms\client\osdeployment\installapplication\installapplication.cpp,1016) InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Step 2 out of 2 complete InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Install application action failed: 'Java test'. Error Code 0x80004005 InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Sending error status message InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Setting URL = http://XXXXXXXXXXXX, Ports = 80,443, CRL = false InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Setting Server Certificates. InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Setting Authenticator. InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Set authenticator in transport InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Setting Media Certificate. InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Sending StatusMessage InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Setting message signatures. InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Setting the authenticator. InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
CLibSMSMessageWinHttpTransport::Send: URL: XXXXXXXXXXXXXXX:80 CCM_POST /ccm_system/request InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Request was successful. InstallApplication 14-Nov-14 4:25:25 PM 2552 (0x09F8)
Process completed with exit code 0 TSManager 14-Nov-14 4:25:25 PM 1304 (0x0518)
!--------------------------------------------------------------------------------------------! TSManager 14-Nov-14 4:25:25 PM 1304 (0x0518)

 

[durwin]

I've managed to solve the issue.. Still don't know what was wrong, but applied CU3 to all the servers and now everything works. I suspect somehow my sccm client installer became corrupted somehow, but everything works now, applications and packages install without fault.

 

 

[Jamin]

I recently ran into this issue but the solution posted here (upgrading to CU3) did not fix it for me. However, as this was the first (and only) site I came across with this error message, and as I have now resolved the issue, I thought I'd post the fix here for others to find.

 

The problem in my case was Windows Updates. Specifically FEP updates. I'd created a nice little automated deployment rule to approve FEP updates, add them to a software update group, and then assign that update group to All Systems. Unfortunately on the automatic deployment rule I'd set the setting to "Create a new Software Update Group" each time the task runs.

 

Over the past 7 months this rule had created in excess of 700 FEP update groups that were all assigned to every PC that was being built. Although I'm not 100% sure of the inner workings of SCCM 2012, my guess is that after the client is installed in the OSD it goes back to the server to find out what deployments it needs to run. This information is then returned in the form of an XML document that the client interprets. The 700+ deployments must have created an XML file that was too big for the client to handle and this caused the build to fail.

 

To resolve the problem I went in to the Software Update Groups section and deleted all but the most recent update group. I then changed my automated deployment rule to "Add to an existing Software Update Group".

 

This resolved the maxXMLsize size constraint violated error.

 

So if you do get this error, check the number of mandatory deployments on All Systems, or any other collection that your computer is a member of.