Character reference is an invalid XML character
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-25-2012 08:25 AM
After running a report in ServiceNow, when I click on 'Update All' in List header context menu, I come up with an error message.
Error: Character reference is an invalid XML character.
I have verified my profile with one of my colleague who is able to perform this action and found no difference.
Experts, please provide your input...
- Labels:
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎10-26-2012 04:11 AM
Experts, please provide your input...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-21-2013 06:24 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-25-2013 06:07 AM
In case anyone experiences this, I may have found a solution but I'm not 100% sure what I did was what actually resolved the issue.
Similar to what was described in the original post, I too started experiencing the "Invalid XML character" soon after creating and running a report. I know for a fact there was an issue with the data I ran the report against because I tried exporting the same data to an Excel file and had a similar message bark at me from Excel when I tried to create an XML file from it.
In my attempt to resolve my issue, I deleted the report I created as well as fixed the record entry that had the invalid character but none of these corrections seem to work.
Since this issue was only happening on my account (impersonating other users didn't result in the same behavior) I tried to think of something that would be isolated to only my account. I thought Update Sets. I looked in the "Default" update set and found two entries related to the report I created. I removed the two entries from the "Default" update set and soon after, my issue went away.
The issue wasn't resolve right away so maybe there was a caching issue but it did resolve very soon after so I can only think what was in the update set was what was causing the issue.
-Michael