C. Common CLS Error Messages
Backup ledger data files exist (Ledger Startup)
2. Cannot open transaction file (Ledger Startup)
This error will occur if the chart of accounts file (CLA0) has become locked on the server. If so, you will need to reboot the server. If you receive the error message after rebooting the server, re-close the previous generation and answer no to keep existing transactions. Current period transactions will then need to be reentered.
It can also occur if the transaction (CLT0) file for a particular ledger generation is really missing. If this is the case, re-close the previous ledger generation and answer no to keep existing transactions. Current period transactions will need to be reentered.
If you’re not sure what the problem is, please call CLS technical support for help.
3. Ledger is currently in use (Ledger Startup - Network version only)
The network version of CLS places a “lock” on each ledger you log onto. If you don’t exit CLS normally, this lock remains in place, and you will be denied access to the locked ledger when you try to log onto it again.
To solve this problem:
4. The CLS network limit of 15 users has been reached (Ledger Startup - Network version only)
Up to 15 workstations can use the network version of CLS simultaneously.
When you first start the network version CLS, and before you have selected a ledger, CLS assigns an internal user number to you and places a “temporary” lock on it. Normally, a temporary lock is replaced when you log onto a ledger, or is removed when you leave CLS, freeing the user number so another person can use it.
Sometimes a temporary lock isn’t removed when it should be, and this blocks access to one of the internal CLS user numbers (1-15). As the temporary locks accumulate, the number of workstations that can use CLS simultaneously decreases.
Enter LR at the Which program would you like to select? prompt, and press Enter.
5. FICA and FUTA rates for 20xx must be set in PF 4, 2 (EP)
At year-end, payroll rates and limits for the new calendar year must be entered in CLS, even if you do not use the after-the-fact payroll portion of CLS. If you regularly update CLS, the new rates will be set for you. If you don’t, you will need to enter the required information in PF 4 (2) each year.
6. Invalid CLS drive specification
All valid CLS data drives must be specified in SI 1 (4), before they can be used (even for backup or import purposes). If the drive is removable, insert the drive letter before the colon (:); if it is not, add it to the end of the string. There should be only one colon in the drive list; it’s used to separate the floppy (removable) and hard disks.
7. Program not defined in Password Maintenance
Over time, several new programs have been added to CLS. However, they are not automatically added to the CLS menu structure.
In SI 2, Password Maintenance, enter 3 next to each of the programs listed below. This will provide complete access to all of the new CLS menu selections:
Press A at the Accept or Escape? (A,Esc) prompt to accept the changes.
8. Reference numbers overlap (Bank Reconciliation)
The Bank Reconciliation Program has found a conflict between the reference numbers assigned to multiple bank accounts, or to multiple items on a single bank account.
In BR 6, Add/Revise Bank Account, the Source and Batch, Beginning Reference/check number and Ending Reference/check number assignment must all be unique. You can’t use the same setup for two different ‘sets’ of items, or for two different bank accounts. You may use the same source code and/or batch number, as long as the reference numbers do not overlap.
9. You are attempting to load a bound OS/2 application (when starting CLS)
This message can occur in Windows 2000/NT/XP with versions of CLS that use Btrieve 5.15. While annoying, the message doesn’t affect the integrity of CLS. To fix the problem, you will need to access the Windows Command Prompt. To do this, select Start, then Run, enter CMD, and press Enter or click OK.
Change to your CLS directory. If CLS has been installed on the C drive in the newcls directory, type:> cd \newcls and press Enter. You should now be at the c:\newcls> prompt.
Type edit cl.bat and press Enter. You should see the contents of the cl.bat file and two lines that begin with butil. Use the down arrow key to move the cursor to the first butil line. Type rem, and press the space bar once to add a single space. Arrow down to the next butil line, and follow the same procedure. Do not press the Enter key.
Using your mouse, select File and then Exit. Answer Yes to Save all Changes.
When you return to the c:\newcls> prompt, type the word Exit to return to the Windows desktop. When you start CLS, you should no longer see the error message.
Contact Us |
Copyright 2019 - Financial MicroSystems, Inc. All rights reserved.