Error 1935
Hello Experts,
While working on an application I am getting error 1935. Pulling my hair to resolve this.
The error says: Error 1935. An error occured during the installation of assembly 'Microsoft.MSXML2,processorArchitecture="x86", publickeyToken="6bd6b9abf345378f", version="4.0.2.0",type="win32". Please refer to Help and Support for more information. HRESULT: 0x800736CC.
Any help would be appreciated.
Thanks
WEk
While working on an application I am getting error 1935. Pulling my hair to resolve this.
The error says: Error 1935. An error occured during the installation of assembly 'Microsoft.MSXML2,processorArchitecture="x86", publickeyToken="6bd6b9abf345378f", version="4.0.2.0",type="win32". Please refer to Help and Support for more information. HRESULT: 0x800736CC.
Any help would be appreciated.
Thanks
WEk
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
VMGupta
14 years ago
Hi,
Found some articles on this:
http://forum.ipsentry.com/tm.aspx?m=239&mpage=1&key=ï
If the application is .Netframework, then resolution is on MS site:
http://support.microsoft.com/kb/308096
http://support.microsoft.com/kb/839547
Found some articles on this:
http://forum.ipsentry.com/tm.aspx?m=239&mpage=1&key=ï
If the application is .Netframework, then resolution is on MS site:
http://support.microsoft.com/kb/308096
http://support.microsoft.com/kb/839547
Posted by:
anonymous_9363
14 years ago
One has to utterly despise vendors who suggest disabling AV/firewall products when installing software. Do they think for even a nansecond before offering that advice? Jeez.......
Moving on, error number 0x800736CC (decimal -2147956428) :
A component's file does not match the verification information present in the component manifest.
You would typically see this message if the source media or drive was faulty or, in rare cases, one of the machine's RAM modules was flaky. At one time, it was a commonly reported fault for XP installs.
EDIT:
Would this be SCCM/ConfigMgr, by any chance? That downloads a CAB file containing an XML file for its manifest. It then extracts that file and begins to parse it. Does the target machine have the MS XML parser installed? I imagine you might see a similar error if it doesn't...
Moving on, error number 0x800736CC (decimal -2147956428) :
A component's file does not match the verification information present in the component manifest.
You would typically see this message if the source media or drive was faulty or, in rare cases, one of the machine's RAM modules was flaky. At one time, it was a commonly reported fault for XP installs.
EDIT:
Would this be SCCM/ConfigMgr, by any chance? That downloads a CAB file containing an XML file for its manifest. It then extracts that file and begins to parse it. Does the target machine have the MS XML parser installed? I imagine you might see a similar error if it doesn't...
Posted by:
WEK76V
14 years ago
Posted by:
Mallikarjun
10 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.