Closest thing I could find says ...
The Xerces parser is trying to access the charset keys within the registry, and the user may not have access to read them. The keys of significance can be located at:
HKEY_CLASSES_ROOT\MIME\DataBase\Charset\
To open the registry and view the keys, launch the Registry Editor by selecting Start -> Run -> and type "regedit".
In the folder view on the left, navigate to \HKEY_CLASSES_ROOT\MIME\DataBase\Charset\
The user must be given read access to those keys.
If the user already has access to the keys, the problem may be that one of the keys is not as it should be.
Every key within the charset directory must contain one (and only one, never both) of the following:
1. AliasForCharset
2. CodePage
- if the key has a CodePage element then it must also have an "InternetCoding" element
If either of the elements are mispelled, they need to be modified.
---
This was for another product but it's worth a shot. Be extremely careful if you edit the registry. And please report back if you get it to work.
