Unsolved
This post is more than 5 years old
30 Posts
0
3713
NMC -- An invalid XML character (Unicode: 0x18) was found in the element content of the document.
The NMC still works, but when switching between windows (e.g. from monitoring to configuration) the following message pops up:
An invalid XML character (Unicode: 0x18) was found in the element content of the document.
It is related to Java but as we don't use Java only for the NMC and don't have any Java expertise.
Also, as far as we know, we didn't changed anything concerning Java options or such.
Someone knows how to fix this?
Polska1422
128 Posts
0
November 29th, 2010 06:00
Hi Phil,
Which NW and Java versions are you using at this server?
Regards
Claudio
phil28
30 Posts
0
November 29th, 2010 07:00
Ah, excuse me.
- NW 7.5 sp 3
- JRE on a Windows machine (version 6 update 22 ( = build 1.6 u22-b04 ) ) It is the latest at the moment.
Polska1422
128 Posts
0
November 29th, 2010 08:00
Have you tried to reinstall Java and/or NMC? Otherwise, try to execute NMC from another remote machine and see the results.
Regards.
Claudio
DavidHampson-rY
294 Posts
0
November 29th, 2010 09:00
First thing I would try would be to go into Java through the control panel, clear out the cache and verify that the correct version of Java is being used.
phil28
30 Posts
0
November 30th, 2010 01:00
Thank you for all the advice.
The NMC spawns the same message on all desktops we used to see if it was a Java problem of the host. As we got on every host the same problem, I think it is a problem with the server (the java jre was not updated/touched on this separate machine) . Thus, the error came out of 'nowhere' . Well you hear it nearly everyday "didn't touch anything and now it is broke" .
We did a "javaws -uninstall" on the host to clear its cache.
Release notes 7.5:
The JRE version 1.6 or 1.5 is required to access the NetWorker Management Console.
We didn't reinstall the NMC yet for the reason that it is a sloppy solution and when I was 'investigating' the problem, it was Friday afternoon.
As this is not critical, just anoying, we decided not reinstall the NMC. Before I will reinstall the NMC, I will reinstall the jre to see if it solves anything.
I will update this thread after we reinstalled the jre.
ble1
2 Intern
2 Intern
•
14.3K Posts
0
December 3rd, 2010 12:00
I'm running NMC on Linux server and connecting from Windows box using java 1.6 (not latest build) and haven't see that error yet.
Probably restarting NMC and clearing JRE cache might address it.
phil28
30 Posts
0
December 7th, 2010 05:00
Hello,
Thank you for your advice. It doesn't solve the problem.
I updated the jre to 1.6 on the NMC server (separate machine) but no luck.
These are the gstd.raw messages:
ble1
2 Intern
2 Intern
•
14.3K Posts
1
December 7th, 2010 16:00
I think the error itself (last one) suggests some issue with database. Unless you are using data in db for reporting (or should I say retain data in database for report and queries), you could nuke database and start from scratch new database and see if this happens again.
phil28
30 Posts
0
December 8th, 2010 01:00
Thank you for the advise.
The first thing I wanted to do when the problem was reported, was checking the NMC database but there are no db consistancy checking tools for it so I was stuck (as there are db tools for the NW databases) .
Alright, I will (copy and) remove the database and update the thread afterwards.