Event Log Messages
Expected response file is missing. | File = '<name>'.
Error Type:
Error
Possible Cause:
1. The device did not provide the response file or provided it with an unexpected name.
2. The file did not move successfully from the session directory to the working directory.
3. The configured Request Timeout is too short.
4. Another device in the project is configured with the same session directory and a session range that overlaps the range on this device.
Possible Solution:
1. Verify the device follows EUROMAP 63 specification.
2. Verify the user has access to both the session and working directory paths.
3. Verify the machine cycle time and adjust the configured Request Timeout accordingly.
4. Change the minimum and/or maximum session numbers for the device.
Failed to parse response file. | File = '<name>',
Error Type:
Error
Possible Cause:
1. The configured Request Timeout is too short.
2. The file is empty.
3. The file contains data that is not in the expected EUROMAP 63 format.
4. Missing end of command character.
5. Missing or invalid command identifier.
6. Missing or invalid keyword.
7. Malformed response information.
8. Missing or invalid error class.
9. Missing or invalid error code.
10. Malformed error description.
11. Missing or invalid date of occurrence. Should be in yyyymmdd format.
12. Missing or invalid time of occurrence. Should be in hh:mm:ss format.
13. Missing or invalid CSV header.
14. Missing or invalid line of CSV data.
15. Number of fields in CSV header do not match number of fields in CSV data.
Possible Solution:
1. Verify the machine cycle time and adjust the configured Request Timeout accordingly.
2. Verify the device follows EUROMAP 63 specification.
3. If the vendor software controlling the press generates a log file, refer to that file for more details on the problem.
Error opening file. | File = '<name>', OS Error = '<OS supplied message>'.
Error Type:
Error
Possible Cause:
1. The file is locked for access.
2. The path no longer exists.
3. The configured Request Timeout is too short.
4. The user configured the session directory path name with a file name instead of a directory name.
Possible Solution:
1. Verify the device has closed the file before deleting the session request file.
2. Review the OS supplied message to diagnose the problem.
3. Verify the machine cycle time and adjust the configured Request Timeout accordingly.
4. Verify the path name is a valid directory name.
Unable to read tag. | Address = '<address>',
Error Type:
Error
Possible Cause:
1. The device did not provide the data for the tag in the CSV file.
2. Converting the provided data to the tag data type failed.
Possible Solution:
1. Verify tag address matches a token name in the device.
2. Verify the tag data type matches the expected data type of the token in the device.
An error was returned from the device. | Command = '<command>', Class = '<class>', Code = '<code>', Description = '<description>'.
Error Type:
Error
Possible Cause:
1. Message was corrupted.
2. Device does not support the request type.
3. Unexpected EUROMAP 63 implementation.
4. Unable to create/open file.
5. Device does not support one or more parameters in the request.
Possible Solution:
1. No corrective actions may be needed if subsequent requests succeed.
2. Note the details in the error message and refer to the hardware vendor manual to diagnose the problem.
Unable to communicate with the device. Session directory does not exist. | Path = '<path>'.
Error Type:
Error
Possible Cause:
1. The user supplied an invalid session directory path.
2. The user does not have access to the path.
Possible Solution:
1. Verify the path is valid for the target device.
2. Verify the user has access to the path
Unable to communicate with the device. Exceeded the allowed range of session numbers for the device. | Minimum Session Number = '<min session number>', Maximum Session Number = '<max session number>'.
Error Type:
Error
Possible Cause:
1. Unexpected session request and session response files exist in the session directory.
2. Another application is creating session request files in the same session directory.
3. Configured range of session numbers for the device is too small.
Possible Solution:
1. Remove unexpected session request and session response files from the session directory.
2. Only allow one application to create session request files in the session directory.
3. Verify the minimum session number and maximum session number allowed for the device.
Failed to complete transaction due to internal driver error.
Error Type:
Error
Possible Cause:
An unknown error occurred.
Possible Solution:
Attempt the operation again or contact technical support.
Unable to read tag. Unknown parameter. Tag deactivated. | Address = '<address>'
Error Type:
Error
Possible Cause:
1. The Prevalidate Tags device property is enabled.
2. The parameter is not available in the device.
Possible Solution:
Verify tag address matches a token name in the device.
Response file byte count is too large. | File = '<name>', Size (KB) = '<size>'.
Error Type:
Error
Possible Cause:
1. The device has returned a response file that has an unreasonable number of bytes.
2. The Max File Size device property is too small.
Possible Solution:
1. Verify the device is returning the correct amount of data. Reduce the expected amount of data returned in the file.
2. Verify the expected maximum file size.
Unable to write tag. Unknown parameter. Tag deactivated. | Address = '<address>'
Error Type:
Error
Possible Cause:
1. The Prevalidate Tags device property is enabled.
2. The parameter is not available in the device.
Possible Solution:
Verify tag address matches a token name in the device.
Unable to write tag. An error was returned from the device. | Address = '<address>', Class = '<class>', Code = '<code>', Description = '<description>'.
Error Type:
Error
Possible Cause:
1. Message was corrupted.
2. Device does not support the request type.
3. Value out of range for the parameter.
4. Permission denied.
5. Device does not recognize the parameter.
Possible Solution:
1. No corrective actions may be needed if subsequent requests succeed.
2. Note the details in the error message and refer to the hardware vendor manual to diagnose the problem.
Unable to communicate with the device. Access to session directory is denied. | Path = '<path>'.
Error Type:
Error
Possible Cause:
The user does not have access to the session directory path.
Possible Solution:
Verify the user has access to the session directory path.
Unable to write tag. Value contains UTF-8 characters but device Character Encoding is ANSI. | Address = '<address>', Value = '<value>'.
Error Type:
Error
Possible Cause:
Value contains a UTF-8 character, but the device Character Encoding property is set to ANSI mode.
Possible Solution:
Configure the device Character Encoding property to UTF-8.
The transaction has been aborted.
Error Type:
Warning
Possible Cause:
1. The device has been deleted from the server while the transaction was in progress.
2. The server runtime shut down while a transaction was in progress.
Another device with the same session file directory path has a session range that overlaps with this device. | Device = '<device>', Overlapping Range = '<min> - <max>'
Error Type:
Warning
Possible Cause:
Another device in the project is configured with the same session directory and a session range that overlaps the range on this device.
Possible Solution:
Change the minimum and/or maximum session numbers for the device.
Deleted remaining EUROMAP 63 files from the session directory on startup.
Error Type:
Informational
Possible Cause:
1. EUROMAP 63 specific files exist in the Session directory from a previous transaction that terminated abnormally.
2. EUROMAP 63 specific files exist in the Session directory that could not previously be deleted due to access rights.
Possible Solution:
1. Ensure proper shut down.
2. Ensure proper access rights.
Completed retrieval of parameters from device. | Count = '<count>'.
Error Type:
Informational
Possible Cause:
1. The Prevalidate Tags device property is enabled.
2. The parameter list is obtained when first communicate with the device to allow tag address validation.
3. Tag addresses that are not supported in the device will not be included in read requests.
Deleted remaining EUROMAP 63 files from the session directory on transaction reset.
Error Type:
Informational
Possible Cause:
1. The driver reached its maximum transaction number, reset it to 0, and deleted the stranded EUROMAP 63 specific files from the Session directory of this device.
2. The configured Request Timeout is too short. Response files from machine arrived after the driver completed a transaction.
3. EUROMAP 63 specific files exist in the Session directory from a previous transaction that terminated abnormally.
4. EUROMAP 63 specific files exist in the Session directory that could not previously be deleted due to access rights.
Possible Solution:
1. Verify the machine cycle time and adjust the configured Request Timeout accordingly.
2. Ensure proper shut down.
3. Ensure proper access rights.