Error: "...serial number...already in use by the maximum number of computers"

How to fix the error: "You cannot Use Sage 50 right now because the serial numbers you have...are already in use by the maximum number of computers." This error occurs when launching or logging in to Sage 50 Accounting.

1. Check the number of user licenses

1. Follow these steps if some users can log in, but others can't.
   • If no one can log in, skip to the next section
2. Check the number of user licenses in Sage 50.
3. If you have more users than licenses, purchase more licenses at (877) 495-9904.
   • You'll also get this error if you have a single user license: you need multi-user licensing
4. If you have enough users for all your licenses, consider if you need more for add-on programs. 
   • Add-on programs such as Act! Link, CertPay, ShipGear also use licenses to access Sage 50
5. If you use SmartPosting and don't have Sage 50 Quantum, it'll also use a license.
   • If you have fewer than 10 active users in Sage 50, switch to Real-time posting
   • Consider using Batch posting instead, as it doesn't require a license
6. Once you've purchased enough user licenses, activate them with the new serial number.

If you have enough licenses for all your users and add-ons, but still get the error, continue with the next section.

2. Reboot

If you’re using the program on a stand-alone computer, reboot and try again.

If you're using Sage 50 on a network, skip to the next section.

3. Restart Actian Zen and close open files

1. Restart Actian Zen on the server.
2. If you still get the error, close Sage 50 on all workstations and the server.
3. At the server, press the Windows+R keys.
4. In the Run window, type fsmgmt.msc, and then click OK.
5. In the Shared Folders window, select Open Files.
   •  TIP: Maximize the Shared Folder window to make entries easier to see 
6. Highlight any open Sage files and close them.
7. Open the company in Sage 50, and verify you no longer receive the error.

4. Reinstall Actian Zen

1. On the server or stand-alone computer, uninstall and reinstall Actian Zen.
2. Test to make sure this resolves the error.
   • If you still get the error on the server or stand-alone computer, skip to the next section
3. If you get the error on workstations but not on the server, reinstall Actian on each workstation.

5. Check permissions on the shared folder

On the server, check to make sure you've set up permissions correctly on the shared folder.

6. Check your data path

1. Verify that the data path is correct on your server (or stand-alone computer).
2. Verify that the data path is correct on your workstations.

7. Check for different versions on the server and workstations

If you're on a stand-alone computer, skip to the next section.

1. On the server, see if you have the latest version of Sage 50 installed.
   • If your version is out of date, install the latest update
   • Check the version again after updating
2. Make a note of the Release and Build number on the server.
3. On each workstation, open Sage 50 and go to Help, About Sage 50 Accounting.
4. Check the Release and Build number on each workstation.
   • If these don't match the server, update the workstation
   • Check the version again after updating

8. Removed damaged data path files and reactivate Sage 50

1. If possible, back up your company data before following these steps.
2. Go to the server or stand-alone computer where you keep your company data for Sage 50.
3. Find the data path, and close Sage 50 on all computers.
4. Press the Windows + E keys on your keyboard to open Windows File Explorer.
5. In File Explorer, browse to your data path.
6. Make sure you're able to view file extensions.
7. Delete or rename the following files:
   • ENVSESS.DAT
   • ENVSETNG.DAT
   • ENVUSER.DAT
   • SERIAL.DAT
   • SERIAL.DAT.BAK
   • *.LCK
   • *.PTL
   • ClientInfo.xml
   • Entitlements.xml
   • SoftwareInstallations.xml
8. If you can't delete one of the above files, close open files on the server.
9. Open Sage 50 and activate the program.

9. Remove damaged company files

Follow these steps if the error only occurs in one company.  Otherwise, skip to the next section.

1. Locate your company data folder.
2. Go to the server or stand-alone computer that holds your company data folder.
3. Browse to your company data folder, and open it.
4. Select all the .DDF files, and press the Delete key.
5. Select COSESS.DAT, and then press the Delete key.
6. Open your company, and verify you no longer receive error.
7. If you still get the error, create a clean data folder.

10. Replace the Reports folder

1. Browse to the data path.
2. Delete Reports folder.
3. Repair Sage 50.
4. Verify you no longer receive the error.

11. Check your Firewall and Antivirus

Make sure you're letting the right files through your firewall or antivirus.

12. Correct the IP Address in the hosts file

1. Browse to C:\Windows\System32\Drivers\etc.
2. Double-click Hosts.
3. When prompted to select a program to Open with, select Notepad.
4. Look for an entry for the server, confirm the IP address and hostname.
5. At the server, press Windows+R keys, and then type cmd.
6. Click OK.
7. Type hostname, and then press Enter (this gives the computer name).
8. Type ipconfig, and then press Enter.
9. Edit the server name or IP address in the hosts file if they're incorrect.
10. Select File, and then select Save, and close Notepad.

13. Check for damaged Microsoft .NET Framework

1. Open the Start Menu, and go to Control Panel.
2. Open the Administrator Tools and select Event Viewer.
3. Select Windows Logs from the left-hand pane and then Application.
4. If you see .NET Framework errors, follow the steps below to uninstall and reinstall .NET Framework.
   • If you don't see .NET Framework errors, skip to the next section
5. Go to the Control Panel, and then select Programs & Features.
6. Click Turn Windows Features On & Off.
7. Clear .Net Framework 3.5 and .Net Framework 4.5 boxes, and then click OK.
8. Restart your computer when prompted.
9. Go to the Control Panel, and then select Programs & Features.
10. Click Turn Windows Features On & Off.
11. Select .Net Framework 3.5 and .Net Framework 4.5 boxes, and then click OK.
12. Close Control Panel.
13. Press Windows+R keys, type cmd, and then click OK.
14. Type sfc /scannow, and then press Enter.
15. Restart your computer when the test completes.
16. Verify Sage 50 opens with no error.

14. Change Windows User Account Control (UAC) settings

1. Right-click on the Sage 50 shortcut and select Run as administrator.
2. If this resolves the error, set Sage 50 to run as administrator by default.
3. If you still get the error, disable Windows User Account Control (UAC), and try again.

15. Check the Windows Workgroup Domain settings

If you have Sage 50 on a stand-alone computer, skip to section 17.

1. Make sure that all workstations are using the same Windows Workgroup or Domain as the server.
   •  TIP: Contact your local IT group or network administrator to check or change this 
2. Verify Sage folders have full Owner rights and Full Control rights.
3. If you still get the error, log in as another Windows user or create a new Windows account.

    

16. Force workstations to activate

Use the INI file to force workstations to activate.

If you're using Sage 50 on a stand-alone computer, skip to the next section.

17. Correct the system date and time

1. Close Sage 50.
2. Change the Windows date and time to the correct values.
   • If you're using Sage 50 on a network, do this on the server first
3. Test to make sure this resolves the error.
   • If this fixes the issue on the server, correct the system date and time on workstations, too

18. Uninstall and reinstall Sage 50

1. Uninstall Sage 50.
   • If you're using Sage 50 on a network, uninstall from the workstations first, then the server
2. Install Sage 50 again, on the server first then the workstations.
   • If you have a 64-bit computer, always install to a folder in C:\Program Files (x86)