RTMT on CCM 4.2 Java error

Answered Question
Jan 27th, 2008
User Badges:

Hi,


When I start the RTMT on the servere or on a client connection to the server i get a java.util.missingresourceexeption error.


can anyone help me with this problem how to get i solved ?


Best regards

Soren Knudsen

Correct Answer by Rob Huffman about 9 years 2 months ago

Hi Soren,


You may be hitting this bug;


CSCse78153 Bug Details


RTMT does not work on winos 2000.4.3a or 4.3SR1

Symptom:

RTMT can not work after upgrading to winos 2000.4.3a sr 4.3SR1 with following

error.


java.util.MissingResourceException: Can't find bundle for base

name org.apache.xerces.msg.XMLMessages, locale ja_JP


Conditions:

OS upgraded to 2000.4.3, 2000.4.3a, or 2000.4.3aSR1. This documents the need

for RTMT to function correctly when RemoveServerHeader=1 in urlscan.ini.


Workaround:

Change the value of RemoveServerHeader in urlscan.ini

(C:\Winnt\system32\inetsrv\URLscan\urlscan.ini) from 1 to 0 and reboot the server.

OS 2000.4.3asr2 sets RemoveServerHeader to 1 to workaround this issue until

RTMT can correct behavior.


After upgrade to 4.2(3) 3.3(5)ES49 4.0(2a)ES88 4.1(3)ES72 4.2(1)ES21

RemoveServerHeader can be set back to 1.



1st Found-In

4.1(3)

4.1(3)SR3

4.2(1)


Fixed-In

4.2(2.116)

4.2(3.1)

3.3(5)ES49

4.0(2a)ES88

4.1(3)ES72

4.2(1)ES21


Hope this helps!

Rob

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (1 ratings)
Loading.
Correct Answer
Rob Huffman Sun, 01/27/2008 - 08:11
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Soren,


You may be hitting this bug;


CSCse78153 Bug Details


RTMT does not work on winos 2000.4.3a or 4.3SR1

Symptom:

RTMT can not work after upgrading to winos 2000.4.3a sr 4.3SR1 with following

error.


java.util.MissingResourceException: Can't find bundle for base

name org.apache.xerces.msg.XMLMessages, locale ja_JP


Conditions:

OS upgraded to 2000.4.3, 2000.4.3a, or 2000.4.3aSR1. This documents the need

for RTMT to function correctly when RemoveServerHeader=1 in urlscan.ini.


Workaround:

Change the value of RemoveServerHeader in urlscan.ini

(C:\Winnt\system32\inetsrv\URLscan\urlscan.ini) from 1 to 0 and reboot the server.

OS 2000.4.3asr2 sets RemoveServerHeader to 1 to workaround this issue until

RTMT can correct behavior.


After upgrade to 4.2(3) 3.3(5)ES49 4.0(2a)ES88 4.1(3)ES72 4.2(1)ES21

RemoveServerHeader can be set back to 1.



1st Found-In

4.1(3)

4.1(3)SR3

4.2(1)


Fixed-In

4.2(2.116)

4.2(3.1)

3.3(5)ES49

4.0(2a)ES88

4.1(3)ES72

4.2(1)ES21


Hope this helps!

Rob

Rob Huffman Fri, 02/01/2008 - 05:44
User Badges:
  • Super Blue, 32500 points or more
  • Hall of Fame,

    Founding Member

  • Cisco Designated VIP,

    2017 IP Telephony, Unified Communications

Hi Soren,


You are most welcome! Always some strange errors aren't there?


Take care,

Rob

Actions

This Discussion