The list below shows the event log messages that can be produced if the Syncsort™ Capacity Management Core Service is being used to run the Data Management Schedules and there is a problem running a schedule, for all these errors, contact Precisely Support with the details of the event log message and a copy of the Data Management Schedules directory.
|
Program
|
Message
|
Information
|
|
VBRuntime
|
Precisely’s Syncsort™ Capacity Management Core Error <error number>: [Data Management.BuildScheduleFileList] <error details>
|
Failed to read the list of schedules from the Data Management Schedules directory, does the directory exist and does the user running the scheduler service have permissions to read and write the schedule files.
|
|
VBRuntime
|
Metron’s Syncsort™ Capacity Management Core Error <error number>: [AtheneDataManagementEvent.IAtheneEvent_Execute ' + <schedule path> @ <schedule time>' ] <error details>
|
Failed to run a Data Management Schedule correctly; read the error details and schedule log for further details of the issue.
|
|
VBRuntime
|
Metron’s Syncsort™ Capacity Management Core Error <error number>: [AtheneScheduler.Class_Initialise] Failed to create named mutex 'Metron_Axm631_AtheneScheduler_Exclusion
|
Note
|
|
VBRuntime
|
Metron’s Syncsort™ Capacity Management Core Error <error number>: [AtheneScheduler.Class_Initialise] Named mutex 'Metron_Axm631_AtheneScheduler_Exclusion' already exists
|
Note
|
|
VBRuntime
|
Metron’s Syncsort™ Capacity Management Core Error <error number>: [AtheneScheduler.Class_Initialise] <error details>
|
The scheduler service failed to start cleanly, Athene® may not be installed correctly.
|
|
Note: The use of a Mutex stops more than once copy of the Syncsort™ Capacity Management Core service from running. If these errors occur then Windows thinks a second copy of the application is being started. This is a very rare issue, but can occur if the Syncsort™ Capacity Management Core Service has got into an unclean state. Check the service is stopped and then terminate any AXM630 and AXM631 processes from the Task Manager. If the problem continues, restart the machine.