Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.
Endpoint Management Community Blog

Using Reserved Characters in Custom Inventories - Good or Bad?

Created: 13 Feb 2008 • Updated: 13 Feb 2008
BRING's picture
0 0 Votes
Login to vote

Naming objects in our Notification Server environment. Seems fairly simple, but the process can be a bit troublesome. Or naming applications, or custom dataclasses. Some times we like to use reserved characters in those names to be descriptive. Characters like($ ; & + , / : = ? @) are reserved characters, specifically to IIS.

These things can cause problems for custom inventories especially. You could see errors like:

Unable to process the file "...\Altiris\Notification Server\NSCap\EvtQFast\Process\INVblah.nse" Moving to "...\Altiris\Notification Server\NSCap\EvtQFast\Bad\AeXException\nseXXX.tmp". Reason: Failed to process NSE System.Xml.XmlException: An error occurred while parsing EntityName.

Certainly, if you can avoid the use of these characters in your naming conventions, that helps.

However, best practices when using these characters, and writing custom inventories is to follow the procedures found in, and specifically make sure that you change the 'write' statements to 'WriteXML'. This will tell the code to properly escape the characters and present your data in proper XML code, keeping the Notification Server cooking with good data!