Troubleshooting
The following tables list the components involved in the TaskAgent, the locations of their configuration files and logging information.
|
Component
|
Type
|
Description
|
|---|---|---|
|
Service Controller
|
Windows Service
|
Controls TransactionListenerProcessor.exe and the JobScheduleProcessor.exe.
Automatically started upon system start.
|
|
TransactionListenerProcessor
|
Executable
|
Notifies the registered TransactionListeners about transaction events.
Started and stopped by CreoServiceController.exe.
|
|
JobScheduleProcessor
|
Executable
|
Regularly checks the JobSchedule (Task) queue and the job queue on the JobSpooler. Sends new jobs to the JobSpooler and processes the results of jobs finished on the JobSpooler.
Started and stopped by CreoServiceController.exe.
|
|
JobSpooler
|
Windows Service
|
Receives jobs from the JobScheduleProcessor and distributes them to available JobServers.
Automatically started upon system start.
|
|
JobServer
|
Windows Service
|
Executes jobs using the selected application (Creo Elements/Direct Modeling or Creo Elements/Direct Drafting).
Automatically started upon system start.
|
|
Component
|
Configuration File
|
|---|---|
|
Service Controller
|
<Creo Elements/Direct Manager Server>\ServiceControllerConfig.xml
or
<Creo Elements/Direct Manager Server>\CustomServiceControllerConfig.xml
|
|
TransactionListenerProcessor
|
<Creo Elements/Direct Manager Server>\ServiceControllerConfig.xml
or
<Creo Elements/Direct Manager Server>\CustomServiceControllerConfig.xml
|
|
JobScheduleProcessor
|
<Creo Elements/Direct Manager Server>\ServiceControllerConfig.xml
or
<Creo Elements/Direct Manager Server>\CustomServiceControllerConfig.xml
|
|
JobSpooler
|
<Creo Elements/Direct Manager Server>\JobSpoolerServer\JobSpoolerConfiguration.<version>.xml
Use the ConfigureJobSpooler.exe tool for reconfiguration.
|
|
JobServer
|
<Job Server installation>\JobServerConfiguration.<version>.xml
Use the ConfigureJobServer.exe tool for reconfiguration.
|
|
Component
|
Logging
|
|---|---|
|
Service Controller
|
<Creo Elements/Direct Manager Server>\logs\ServiceController.log
|
|
TransactionListenerProcessor
|
<Creo Elements/Direct Manager Server>\logs\TransactionListenerProcessor.log
Set the debug level (LogLevel) in CustomServiceControllerConfig.xml.
|
|
JobScheduleProcessor
|
Configuration check results -
<Creo Elements/Direct Manager Server>\logs\JobScheduleProcessorConfig.log
Runtime information -
<Creo Elements/Direct Manager Server>\logs\JobScheduleProcessorService.log
Set the debug level (LogLevel) in CustomServiceControllerConfig.xml.
|
|
JobSpooler
|
>
Set the debug level in JobSpoolerConfiguration.<version>.xml.
|
|
JobServer
|
>
Set the debug level in JobServerConfiguration.<version>.xml.
|
Common Problems
Macro or LISP file customizations don’t seem to work
Issues that occur during processing a Creo Elements/Direct Drafting macro or Creo Elements/Direct Modeling LISP file can be analyzed by using the job’s log file. To access the log file, do the following:
• Edit <Manager Server>\JobSpoolerServer\JobSpoolerConfiguration.<version>.xml.
◦ Set <KeepJobData>true</KeepJobData>.
• Restart the JobSpooler ( > > > > ).
• Run the job again.
• In the JobSpooler’s data directory <Manager Server>\JobSpoolerData\JobSpooler Files you’ll find the log file <job id>\job.log.
 |
The <KeepJobData> tag should not be set to true in production use. The job files will never be deleted and the server’s disc will fill up.
|
New job type not found or not executed
This can be caused by invalid configuration files or missing Java code.
|
Symptom
|
Possible solution
|
|---|---|
|
Is the configuration file a valid XML document?
|
Check the JobScheduleProcessorConfig.log. On startup, the JobScheduleProcessor reads and checks all configuration files in jobconfig. The log file contains information about issues found in the configuration.
|
|
Is the new job type unique?
|
See above.
|
|
Is the new job type a valid subtype?
|
Jobs executed by a Creo Elements/Direct Modeling server must have a type of the form modeling.<conversion type> (drafting.<type> for Creo Elements/Direct Drafting jobs).
Otherwise the JobSpooler cannot assign the job to any server and will not accept the job. It will remain in the "Ready" state.
The simplest way to generate new job types is to derive them from existing ones. For example, to generate a custom set of 3D output formats, you can derive a type modeling.conversion.myformats from the existing type modeling.conversion.
|
|
Did you restart the Service Controller after deploying the new configuration file?
|
Check the JobScheduleProcessorConfig.log.
It should list your new job type.
|
|
Did you deploy your custom Java code appropriately?
|
Check the JobScheduleProcessorConfig.log.
If the new job type contains custom Java components (Exporters, ResultHandlers), the corresponding classes must be available in jar\custom\<your custom code>.jar. If the code is not found, the new job types cannot be instantiated. This will be reported as a "ClassNotFoundException" in the log file.
|