Author |
Message |
jvaldes988
Joined: 01 Mar 2007 Posts: 35 Country: United States |
|
Corrupted job definition |
|
Hello:
We're running the 24x7 Multiplatform Java edition (version 3.4.26) on a Web server (IIS service). We can crete jobs for the first time with no problems. However, if we subsequently edit a previously creted job, the job definition gets corrupted (run as user gets assigend a timestamp, the command line gets erased etc). Is this a known problem on the Web interface? Do we need to apply a patch to fix this issue?
Thanks in advance for the help.
|
|
Mon Apr 16, 2007 7:08 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7969
|
|
|
|
This sounds like you are dealing with some incompatibility issue between the web interface and the scheduler. One of them supports more job properties then the other. What version of the web interface are you using? Are you sure the scheduler version is 3.4.26 and not something like 4.x.x?
|
|
Mon Apr 16, 2007 9:34 pm |
|
 |
jvaldes988
Joined: 01 Mar 2007 Posts: 35 Country: United States |
|
|
|
You are correct. The Web interface version is 3.4.26 BUT the scheduler GUI version is 4.0 Build 215.
Can you show me how to upgrade the Web version? We have a site license.
Thanks for the help.
|
|
Tue Apr 17, 2007 10:22 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7969
|
|
|
|
That's the current version. Version number's for the console and scheduler don't match match. Web console is used with different versions of the scheduler and has its own version number.
Please check in the schedule.log on the scheduler computer if you get any errors or warnings, like "job property ... is not supported in this version." If you do, please let us know which property it refers to.
|
|
Tue Apr 17, 2007 10:30 am |
|
 |
jvaldes988
Joined: 01 Mar 2007 Posts: 35 Country: United States |
|
|
|
Hello:
This is what appears on the 'scheduler.log'. Notice the job ran with no problems the first time, but once I edited it, the job properties got corrupted causing the job to fail the second time:
04/17/2007 10:44:14 AM 2 null null 24x7 Scheduler User petest\administrator connected from 10.111.1.108
04/17/2007 10:47:29 AM 2 7xScmRht5hhVbDPyGb3xspoWOaY= 133 0019-test Job started.
04/17/2007 10:47:29 AM 2 7xScmRht5hhVbDPyGb3xspoWOaY= 133 0019-test Job finished.
04/17/2007 10:53:09 AM 2 7xScmRht5hhVbDPyGb3xspoWOaY= 133 0019-test Job started.
04/17/2007 10:53:09 AM 3 7xScmRht5hhVbDPyGb3xspoWOaY= 133 0019-test Job definition incomplete.
04/17/2007 10:53:09 AM 1 7xScmRht5hhVbDPyGb3xspoWOaY= 133 0019-test Job has been disabled!
Thanks in advance for your help. We can not proceed with the application scheduled Web rollout.
|
|
Tue Apr 17, 2007 11:15 am |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7969
|
|
|
|
If you aren't already running 24x7 in graphical mode, please run it in graphical mode, using web console update some test job and check which properties appear incorrect. You can see all properties on the job details page in the scheduler's graphical interface. Please let us know what you get there.
|
|
Tue Apr 17, 2007 3:00 pm |
|
 |
jvaldes988
Joined: 01 Mar 2007 Posts: 35 Country: United States |
|
|
|
Here's what I did. I created a brand new job in GUI and ran OK. I then used the Web console with the intention of editing this same job. When editing the job properties, I noticed most of them were already corrupted. The command line had '0', the Start in also had a '0', the Run As had a date, etc.
To me, it looks that the Web console is not in sync with the GUI version. It might think we're running an 'old' version and that is why all fields are either shiftted or corrupted.
P.S: Editing this same job in GIU is not a problem. This is just related to the Web Console.
|
|
Tue Apr 17, 2007 4:52 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7969
|
|
|
|
Thanks for the info. We are looking into this.
|
|
Tue Apr 17, 2007 5:44 pm |
|
 |
|