Error Codes and Messages
When any of the following error messages occur, please contact Technical Support.
65 Unable To ROLLBACK Transaction
75 Invalid Field Type Descriptor
78 Invalid Number Of Parameters
79 Unsupported Data Type In File
80 Unsupported File Driver Function
89 Record Changed By Another Station
Posting Errors
0001 File Not Open Can't Log Unable to Post
This error is received when the system cannot open the file it needs. The file is being used by another computer or the system thinks it is being used. The simplest fix is to reboot the affected computer(s) after checking to make sure no one is in the specified file.
This Batch in use by another user
This message will come into view anytime there is someone in the Batch or the accounting system has been shut down improperly. If this message occurs and there is someone in the Batch, press the OK button (on the screen). If this message occurs and there is no one in the Batch, press the letter "O" (on the keyboard) and it will override this message and allow access to the Batch.
This message appears when Special Accounts are not assigned in the General Ledger tab of Setup Accounting Options. All three 'Special Accounts' must be assigned or when posting is attempted, the following error message will occur. Go into Setup Accounting Options and make sure all three of the Special Accounts have accounts assigned. Make sure the accounts they are assigned to are valid General Ledger Accounts.
There are two possible causes:
1. G/L account does not exist for the specified Job and cost code.
A. Check employee timesheets.
B. Check the Job Setup Budget Tab and make sure that the Cost Code has valid G/L account setup.
2. Invalid G/L Fiscal Period
A. Check the validity of the fiscal periods. This is done through Fiscal Periods. Make sure the Fiscal Period is open.
B. Make a backup.
C. Recalculate the GL Balances. This is done through Utilities > Recalculate G/L Balances.
This message appears when a payment, such as an invoice or timesheet, is assigned to a job that does not exist. The problem can be resolved in either of 2 ways:
1. Change the job number to reflect an existing job.
2. Create the job in Job Setup, and then reenter the payment.