AX Connector error messages
The following table describes the error messages that may appear in the aclse1.log file and provides troubleshooting suggestions.
| Message | Description | Resolution |
|---|---|---|
|
An unknown error has occurred. |
The application encountered an unexpected error condition. |
Restart the AX Connector service and try the operation again. Contact ACL Support Services if you cannot resolve the issue. |
|
Concurrent user information missing. |
The acl.conf file contains incomplete concurrent user information. |
Contact ACL Support Services. |
|
Control prefix missing for concurrent users. |
The acl.conf file contains incomplete concurrent user information. |
Contact ACL Support Services. |
|
Data buffer size invalid, using default of <value>. |
The “Workspace” buffer size specified is invalid. The valid range is 32760 to 2000000 (2MB). |
Adjust the WORK SPACE ALLOC value in the acl.conf file to fall within the required range. |
|
DB - Database error <error> |
AX Connector detected a database error. <error> is the error message returned by the database engine. An unknown service name, a bad username/password, and configuration issues are some causes of database errors. |
Verify the account information in the database profile, and check your database configuration. Contact ACL Support Services if you cannot resolve the issue. |
|
Expiry Date is invalid. |
The acl.conf file is corrupt. |
Contact ACL Support Services. |
|
Failed to load resource string tables. |
The AX Connector service was unable to open one of the string resource files. By default, these files are located in the analytic_engine\aclse\conf subfolder where AX Server is installed, but the configuration directory location can be customized using the -c command line parameter. |
If the files have been accidently moved, restore them to the specified location. If the files have been deleted you need to reinstall the service. |
|
Failed to validate running session. |
The running session was not found in the c:\aclsessions\sessions file. The file has been corrupted or modified. This error only occurs while concurrent user limits are in effect. |
Log in again and start a new session. |
|
Failure validating concurrent user limit. |
This message indicates that there was a problem in tracking the number of concurrent users. This can be caused by a corrupt or missing c:\aclsessions directory. |
Ensure that the c:\aclsessions directory is writable by all users so that a AX Connector service process running under any user can access the sessions file. |
|
Hash code missing for concurrent users. |
The acl.conf file contains incomplete concurrent user information. |
Contact ACL Support Services. |
|
Incorrect number of entries in custom/config file. |
This message indicates that acl.conf may be corrupt. |
Contact ACL Support Services. |
|
Insufficient memory available to run ACL. |
AX Connector was unable to allocate enough memory to continue. |
Check to see if system resources have been exhausted and whether the memory settings in acl.conf can be increased. If this error occurs regularly, consider upgrading the hardware on the server where the service is installed. |
|
Invalid concurrent user code. |
The acl.conf file contains invalid concurrent user information. |
Contact ACL Support Services. |
|
Invalid username or password. |
In ACL Analytics, verify the username and password in the Server Profile. |
If they are correct, contact your system administrator. |
|
License has expired. |
The expiry date of the software has been reached. |
Contact ACL Support Services. |
|
Machine Id does not match custom/config file entry. |
The licensing information does not match the server the file is located on. |
Contact ACL Support Services. |
|
Maximum ACL Users logged on. |
Concurrent user limits are in effect and there are no more licenses available for the login. |
Try logging in again when a license is available. If this error occurs regularly you may need to purchase additional licenses. |
|
Non-unicode client cannot connect to Unicode server. |
There is a mismatch between the editions of ACL on the client and server. This message only applies to the Unicode release of ACL Analytics Exchange. |
Install the Unicode edition of ACL Analytics on the client. |
|
Serial Number is invalid. |
The serial number in the acl.conf file is incorrect. |
Ensure that the serial number is entered correctly, and contact ACL Support Services if the error message persists. |
|
Sort Memory value is out of range, using <value> MB. |
The sort memory setting in acl.conf is outside the valid range. |
Enter a value between 2000000 and 100000000 bytes (2MB to 100MB). |
|
Unable to change to directory <directory_name>. |
In ACL Analytics, the Prefix in the Server Profile is not valid. Either the folder does not exist or the user does not have the necessary permissions. |
Specify a different folder, or adjust the permissions on the folder to grant the user the necessary rights. |
|
Unable to open custom/config file. |
The config file, acl.conf, either could not be found or could not be opened. The default location for this file is the analytic_engine\aclse\conf folder. If you used the -c parameter to specify a different location for your configuration directory, ensure that the acl.conf file exists in the specified location. |
Ensure that the file exists in the specified location. |
|
Unicode client cannot connect to non-Unicode server. |
There is a mismatch between the editions of ACL on the client and server. This message only applies to the non-Unicode release of ACL Analytics Exchange. |
Install the non-Unicode edition of ACL Analytics on the client. |
|
User is not authorized for ACL access. |
A user that is not in the aclauth file has tried to connect. If the user should have access, verify that the name in the aclauth file matches the user’s login name, and ensure that the aclauth file is in the correct format. |
If the user should have access, verify that the name in the aclauth file matches the user’s login name, and ensure that the aclauth file is in the correct format. |