What this means is that we could not execute the convertxml.exe command on the windows helper server to decode hfnetchk6b.xml file (this is a part of the windows catalog update job). The error of interest here would be "DTD is prohibited" coming from msxml.
I don't think we've seen this MSXML error message before. Web search reveals some hits towards enhanced security, so we need to figure out how to disable this security level.
Technically this does not seem to be bladeissue and seems to be MSXML related, so can be researched outside of bladelogic. If I get more info, I'll update the thread. If you find the solution please do so as well.
Seems like this is enabled by default with msxml6, though I've never encountered such issue before. Also various courses tell to modify the code to disable it, which may imply that this is something we should do in the code:
Finally, I got the solution...I think the patch catalogue hfnetchk6b.xml got currupt.
But one strange thing was, when one role updates the catalogue it removes BLAdmins permissions on few of the bulletins and hot fixes... Any idea what could be cause?
So just to be clear, the "DTD is prohibited" turned out nothing but a corrupt shavlik xml file?
About the Role that removed permissions on some of the bulletins and hotfix objects... it could be due to issues or maybe even defects with ACL Policies or Templates... probably best to file a ticket for this item
Yes, DTD caused due to currupt shavlik file and after deleting the file, and CUJ, evrything went fine.
I faced the same issue: DTD is prohibited. I did not delete the HfNetChk.xml file but downloaded from Shavlik via Patch Global Config.
After it downloaded, I ran the Cataloag update job and it successfully completed. Thanks for this post. its really helpful.
did you experience this as a one-time issue? We seem to have this situation occur at least once per XML release. Looking for a resolution that doesn't require manual intervention, as we need to get our catalogs updated before business hours.
I get a similar issue sporadically, which occurred this month:
Error Feb 13, 2013 7:11:45 AM Error occur: Level: F
Message: ConvertXML.exe returned error (Exit code: 1): Error 80004005 from Unknown: Could not load MSXML DOM document due to: The character '>' was expected.
[msxml4.dll] The character '>' was expected.
Re-running the update job a few minutes later worked fine.