 |
SoftTree Technologies
Technical Support Forums
|
|
Author |
Message |
jemattson
Joined: 29 Apr 2010 Posts: 7 Country: United States |
|
GetTemplate error when creating a job from template |
|
When attempting to create a new job from a template - we receive a white screen with "GetTemplate error". Ideas?
|
|
Wed Jul 28, 2010 12:10 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7952
|
|
|
|
Is that one of the pre-installed templates or a custom template? Is that in the GUI version or web console?
Which scheduler version are you running?
|
|
Wed Jul 28, 2010 1:15 pm |
|
 |
sasichak
Joined: 02 Aug 2010 Posts: 5 Country: United States |
|
|
|
We are using pre-installed templates and the error is in web console.
24x7 Scheduler Windows Edition
Version: 3.6.9
System: Windows 2003 (Service Pack 2)
|
|
Mon Aug 02, 2010 2:42 pm |
|
 |
SysOp
Site Admin
Joined: 26 Nov 2006 Posts: 7952
|
|
|
|
Please check scheduler.log and debug.log files on the scheduler system for related errors or warnings. You can check for events having times around the time you clicked on the template link. Please let us know what you get there.
I assume you get the same blank screen for all templates. Is that correct?
|
|
Mon Aug 02, 2010 4:23 pm |
|
 |
sasichak
Joined: 02 Aug 2010 Posts: 5 Country: United States |
|
|
|
where do we find these logs. We are getting same blank screen for all templates.
|
|
Tue Aug 03, 2010 4:22 pm |
|
 |
sasichak
Joined: 02 Aug 2010 Posts: 5 Country: United States |
|
|
|
..also when we try to use templates from "Job properties Wizard" in the GUI, we get "template xxx not found" error!
|
|
Tue Aug 03, 2010 4:46 pm |
|
 |
SysOpJ
Joined: 20 Aug 2010 Posts: 95
|
|
|
|
The log files are located in the 24x7 Scheduler installation directory.
It is possible that you'll only see the schedule.log file. If that's the case, you'll need to turn on debugging. To do this, start up 24x7 Scheduler, select Tools from the menu, then Options. In the Options dialog, select the Log tab page, and check the option in the Debug options group. The application will prompt you to restart. After you've done so, you should see both log files. Produce the error again, and let's see what the logs show.
|
|
Mon Aug 30, 2010 8:52 am |
|
 |
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|
|