Cannot Schedule Job error in Netconfig

networking · ‎08-31-2005

When trying to run a NetConfig job in RME 3.5 get the following error message:

Cannot Schedule Job. Exception Stack Trace: Java.Lang.NullPointerException.

Any help appreciated,

Mike.

nhabib · ‎08-31-2005

Do you happen to have VMS installed on this server?

networking · ‎09-01-2005

Yes we do have VMS installed.

nhabib · ‎09-01-2005

Did you install fcs-rme3-5-vms2-3-update from the following location?

http://www.cisco.com/cgi-bin/tablebuild.pl/vms-3des

You will be asked if you want to install IDU 9.0, say no if you have a later IDU already installed

networking · ‎09-01-2005

Apparently we only have VMS service pack 2 installed. Do we need to upgrade to SP3 before applying this patch?

nhabib · ‎09-01-2005

No, if you do not have Service Pack 3 for VMS installed, then you do not need the RME 3.5 Update

What does the following command return: pdshow jrm

networking · ‎09-02-2005

The command pdshow jrm gave this output:

C:\Documents and Settings\Administrator>pdshow jrm

Process= jrm

State = Program started - No mgt msgs received

Pid = 2928

RC = 0

Signo = 0

Start = 08/31/2005 02:51:16 PM

Stop = Not applicable

Core = Not applicable

Info = Server started by admin request

nhabib · ‎09-02-2005

This looks fine. Time to contact TAC.

networking · ‎09-04-2005

Will do.

Many thanks for your help!

Data Networking Team

Health Solutions Wales

974312magr · ‎11-09-2005

Hi.

I have exactly the same problem. Besides, in Config Editor, it shows "Cannot schedule job". If you try to launch Job Browser, it shows "JRM display initialization error. Error obtaining data from server. JRM server is down or not accessible".

It was worked some days ago. I changed the hostname of the server. I don´t know if it is the cause of the problem.

I reload the server, but it doesn´t works. The JRM service shows started in Process Status.

Someone knows something about this?

Thank´s.

974312magr · ‎11-09-2005

Hi.

I solved the issue. I changed the hostname in all md.properties files existing in the Server and it worked.

Thank´s.

froekjaer · ‎12-30-2005

Thank you

I had the same issue.

Applying the patch solved my problem problem.