When trying to get new configuration on the Altiris Agent, the following error message appears in the logs: RequestPolicies failed: Invalid XML response from URL http://Servername/Altiris/NS/Agent/GetClientPolicies.aspx (-2147467259)
Last Updated March 04, 2013
In this case, after the customer did an upgrade on the Notification Server and Solutions, he started to noticed that his client machines were not able to obtain new configurations. The communication between his client machines and the NS were fine.
The Agent logs showed the following error message every time that he tried to update configuration on the Altiris Agent:
Unknown. For some reason during the upgrade there was a chance that one of the policies got corrupted. In this case the corruption was related to missing the closing tag on one of the policies contained in the Client Policy XML.
As the error message in the logs refer, there is a invalid XML response when the Altiris Agent is requesting a policy. In this case you will need to identify what is wrong in the XML that is been generated by the Notification Server.
1. Please review KB Article ID: HOWTO10484 "How to manually retrieve the Client Policy for a computer using a browser in NS7". In this case try to manually obtain the Client Policy XML that is generated. 2. If there is something wrong in the XML generated, you may see an error message at the bottom of your browser like this:
3. Check that all the tags are formatted properly. Meaning, if you have an opening tag, you should also have a closing one. You can do this manually (reviewing the XML by hand until you find a missing tag), or you could use "XML Notepad" (free tool) or any other XML parser. If you save the XML and try to open it on "XML Notepad", if there is something wrong, you may see an error message like this:
In this case the opening tag without a closing one was on line 110. 4. Identify the policy that belonged to that missing tag. In this example the policy was called "Install Compatibility Pack for Office 2007" 5. Go to the Console and find the offending policy. Clone it, rename the cloned one, enable the cloned one and disable the original one. This should force the NS to create a new entry for the client policy with the proper tag format. 6. Now you should be able to obtain the proper XML response for the client configuration requests.
Symantec Management Platform 7.0 SP4
Imported Document ID: TECH127307
Subscribing will provide email updates when this Article is updated. Login is required to Subscribe