Microsoft XML - system does not support the specified encoding

Author

system does not support the specified encoding

klaus triendl

2005-02-15, 4:21 am

hi,

i'm scanning already some hours through the archives for this error, but
there is no posting describing my problem or there is no real solution to
it.

we are using msxml4 (sp1) extensively for storing configuration files and
for communication in our application (4 years already) and just recently
the following error has occurred on some machines:

xml-error 0xc00ce56e
line 1, char 42
the system does not support the specified encoding
source: "<?xml version="1.0" encoding="UTF-16LE"?>"

source is an xml-file loaded with the load() method of a
MSXML2::DOMDocument40 in c++.
the file is saved in UTF-16LE including the BOM. we can open it
successfully on our machines here in the company, but 2 customers get the
above error.
encoding changed to "UTF-16" works fine.

we are sure that the right version of msxml4 is loaded; customers'
machines are set up with win2000 (server and professional, sp too), ie5 is
installed on those machines. ie reports the same error when loading the
xml-file.

--
klaus triendl

klaus triendl

2005-02-15, 6:43 pm

On Tue, 15 Feb 2005 09:21:16 +0100, klaus triendl <triendl.kj@m-box.at>
wrote:

> we are sure that the right version of msxml4 is loaded; customers'
> machines are set up with win2000 (server and professional, sp too), ie5
> is installed on those machines. ie reports the same error when loading
> the xml-file.

i've set up a machine with w2k professional and i got the same error as
our 2 customers;
next i installed all important service packs and fixes except ie6 - still
the same error.

as soon as ie6 was installed no error occurs.
this tells me that msxml4 works with some components related to encoding
which ie updates. does somebody know how msxml4 works? or is this a former
bug?

--
klaus triendl

Martin Honnen

2005-02-15, 6:43 pm

klaus triendl wrote:

> we are using msxml4 (sp1) extensively for storing configuration files
> and for communication in our application (4 years already) and just
> recently the following error has occurred on some machines:
>
> xml-error 0xc00ce56e
> line 1, char 42
> the system does not support the specified encoding
> source: "<?xml version="1.0" encoding="UTF-16LE"?>"
>
> source is an xml-file loaded with the load() method of a
> MSXML2::DOMDocument40 in c++.
> the file is saved in UTF-16LE including the BOM. we can open it
> successfully on our machines here in the company, but 2 customers get
> the above error.
> encoding changed to "UTF-16" works fine.
>
> we are sure that the right version of msxml4 is loaded; customers'
> machines are set up with win2000 (server and professional, sp too), ie5
> is installed on those machines. ie reports the same error when loading
> the xml-file.

Are the machines in your company also Windows 2000, or are those a later
Windows version that perhaps has support for UTF-16LE while the customer
machines don't?

--

Martin Honnen
http://JavaScript.FAQTs.com/

klaus triendl

2005-02-15, 6:43 pm

On Tue, 15 Feb 2005 12:53:16 +0100, Martin Honnen <mahotrash@yahoo.de>
wrote:

> Are the machines in your company also Windows 2000, or are those a later
> Windows version that perhaps has support for UTF-16LE while the customer
> machines don't?

we have both, w2k and winxp but everywhere ie6.

--
klaus triendl

klaus triendl

2005-02-16, 4:30 am

On Tue, 15 Feb 2005 12:49:12 +0100, klaus triendl <triendl.kj@m-box.at>
wrote:

> as soon as ie6 was installed no error occurs.
> this tells me that msxml4 works with some components related to encoding
> which ie updates. does somebody know how msxml4 works? or is this a
> former bug?

ok, i've found the cause.
msxml depends on mlang.dll which is (still) shipped only with ie as far as
i got to know. mlang handles charset and encoding issues; it has the same
version number as ie itself.
mlang5 has obviously problems with encoding UTF-16LE and UTF-16BE,
understands only UTF-16. installing a newer version of ie solves the
problem.

not nice, but a solution at least.

--
klaus triendl