I had a customer that could not open her company. Her error message was a bit different but none of that particular Article from the knowledgebase fixed the problem. I discovered she had the Crypto virus, that had damaged all the Help Files and the Version.txt file. In your companies data files search for Version.txt. Open using Notepad. You should see a number like this 26.011 ( 26 is version 2016.011 is installed service release. If it is unreadable then this file is damaged. If it is damaged you can rename it to version.bad and then copy a version.txt from a sample company or another company that you can open under that version. However in my customers case all of her companies version.txt were garbage, so we had to restore from a backup into a new company and copy that version.txt to her current company. This may not be the only file that has been damaged. With respect to your error, the following article is from the Sage Knowledgebase. Hope this helps you. Error: "You Cannot Use Sage 50 right now because the serial number(s) you have...are already in use by the maximum number of computers" Article Products Sage 50—U.S. Edition Description Error: "You Cannot Use Sage 50 right now because the serial number(s) you have [serial number] are already in use by the maximum number of computers." Unable to open company Unable to open program Program says my serial number is being used by too many computers User may lose control of cursor or not see cursor for a while before the error displays Cause No unused licenses left (number of currently logged-in users matches license count) Damaged files in data path or company directory Incorrectly set sharing permissions and/or security settings on shared data folder Improper firewall or anti-virus settings Incorrect data path Incorrect IP address reference in the Windows hosts file Program closed abnormally Damaged Pervasive PSQL Workgroup Engine Upgraded the server to the latest version of Sage 50—U.S. Edition but have not on the workstation(s) The workstation is using Windows Workgroup or not the same Domain as the server. Damaged Microsoft .NET Framework The Domain user profile does not have sufficient privileges to the server data path or the Domain user profile is damaged Pervasive licensing issues Damaged PEPusage.dat Damaged DDF file when the error is occurring with only one company. Incorrect system date/time Server data path located in the Users folder Resolution Note: It is possible that the program has not yet closed out the company files from the previous session. If you receive this error please wait approximately 1-2 minutes and try to open the company again. If you continue to receive the error, proceed with the steps below. Section I: Reboot If you are using the program on a stand-alone computer, reboot and try again. Section II: Abnormal close or open file stuck in memory Close Sage 50 on all workstations and the server At the server, select Start, Control Panel Select System and Security, then Administrative Tools. Note: Depending on your current view, you may see may not see System and Security. If that is the case, you will see Administrative Tools instead. Double-click on Computer Management Click System Tools, Share Folders and Open Files Highlight any file open Sage 50 related file and close them Open the company in Sage 50 and verify the error is resolved. Section III: License count met If you have a single-user version of Sage 50, and more than one PC tries to run the program simultaneously, this message will occur. If the number of users currently logged into the program matches the license limit (for example, 3 users logged in with a 3-user license), this message will occur when an additional user tries to log in. Some add-on programs, such as Act! Link, Certpay, Shipgear, etc., utilize a Sage 50 license; you must have enough licenses for all human users plus a license for each add-on program. When the license limit has been met, a user must close the program before another will be able to open it. Section IV: Restart Pervasive Note: If using Sage 50 on a network, perform these steps at the server first, then at each workstation. Press WINDOWS KEY + R. Type services.msc. Click OK. Right-click Pervasive PSQL Workgroup Engine. Click Start or Restart. Once it restarts, close Services. Open Sage 50; if the error continues, proceed to the next section. Section V: Permissions/Security on Shared Folder See Article 10211: Verify my data file permissions are correctly set in Related Resources. Section VI: Firewall/Anti-Virus Settings See Article ID 10903: Files to allow in firewall and anti-virus in Related Resources. Section VII: Damaged data path files Open Computer. Browse to the Sage 50 data path. See Article ID 10165: How to find data path and program path, in Related Resources. Search for and delete or rename the following files: ENV*.DAT OPTIONS.DAT SERIAL.DAT SERIAL.DAT.BAK *.LCK *.PTL Note: If you cannot delete all of the above files, follow Article ID 45627: "How to close open files on Microsoft Windows Server 2008 R2 and 2011" or Article ID 46620: "How to close open files on Server 2012" in the Related Resources section. Verify you can access the program. Section VIII : Damaged company files Browse to the individual company folder that you are unable to open. Delete or rename the following files: COSESS.DAT *.DDF *.DATtemp *.DATptl *.LCK *.MKD *.PTL *.PTR *.RPT Note: If you cannot delete all of the above files, follow Article ID 45627: "How to close open files on Microsoft Windows Server 2008 R2 and 2011" or Article ID 46620: "How to close open files on Server 2012" in the Related Resources section. Close the window. Open Sage 50. Note: If the error still occurs, or if the company starts opening but the program closes, proceed to the next step. Create a New folder for the company, move all of the .DAT files to the new folder, along with version.txt and KMSkeys.xml. Copy the letters, KeysBackup, and BUSINT folders to the new company folder. Close the window Open Sage 50 Note: If the error still occurs, or if the company starts opening but the program closes, proceed to the next section Section IV: Damaged Reports If the files responsible for recreating .DDF files are damaged, the error may still occur, or the program will close when the company tries to open. Open Computer. Browse to the data path. Delete the Reports folder. Close Computer. Repair the installation. See Article ID 10602 How to run Repair, in Related Resources. Section X: Incorrect data path See Article ID 13165: How can I tell if I am mapping my workstation to the correct data location?, in Related Resources. Section XI: Server upgraded but workstation(s) weren't See Article ID 10262: Installation Instructions, in Related Resources. Section XII: Incorrect IP Address in the Hosts file If the computer's Hosts file has entries for the server, and the server or router has been rebooted, it is possible a new IP address has been assigned for the server, thus causing the error. Open Computer. Browse to C:\Windows\System32\Drivers\etc. Double-click Hosts. When prompted to select a program to open it with, select Notepad. Look for an entry for the server; if one exists, confirm the IP address and hostname: At the server, press WINDOWS KEY + R. Type cmd. Click OK. Type hostname and press ENTER; this gives the computer name. Type ipconfig and press ENTER; this gives the IP address. Note: If both an IPv4 and an IPv6 address are given, disregard the IPv6 address. If the server name and/or IP address in the Hosts file are incorrect, edit them to the correct values. If changes were made, click File, Save; if no changes were made, just close Notepad. Section XIII: Damaged Pervasive PSQL Workgroup Engine Note: If the error occurs at the server, perform these steps at the server first; if the error continues on the workstation after this, but not the server, repeat these steps at each affected workstation. Uninstall Pervasive PSQL Workgroup Engine, then Repair Sage 50 See Article ID 10297: How do I manually uninstall Pervasive? in Related Resources. See Article ID 10602: How to run Repair in Related Resources. Section XIV: Damaged Microsoft .NET Framework Note: For assistance with the steps in this section, contact an I.T. person or Microsoft support. Check the Windows Event Viewer; if there are .NET Framework errors, you will need to uninstall and reinstall all versions of .NET Framework. See Article 10777: How to completely uninstall Microsoft .NET Framework in Related Resources. After reinstalling .Net, you may need to reinstall Sage 50. Section XV: Incorrect system date/time Change the Windows date and time to the correct value. Follow Microsoft KB 307938. Reopen Sage 50 and verify you can access the company. Section XVI: Workstation Licensing Note: Perform these steps at each workstation See Article 46520 How to modify the ini file to force activation on a workstation, in Related Resources. Verify Sage 50 can be opened without error. Section XVII: Server Data Path in Users Folder Due to the security settings that Windows forces on the Users folder, the Sage 50 data folder should not be placed here. At the server, use the Database Repair Utility to create a new local data path; see Article 10901 How to create a new data path with the Database Repair Utility, in Related Resources. After doing so, move all the companies into the new data path; see Article 10839 How do I move my company data folder?, in Related Resources. Share the new data folder; see Article 33112 How do I share my data path folder?, in Related Resources. Map a network drive at each workstation to the new shared folder; see Article 10213 How to map a network drive, in Related Resources. Change the configuration file at each workstation to use the new data path; see Article 13517 How to change the data path, in Related Resources. Section XVIII: Windows 8 UAC settings User Account Control (UAC) may be blocking SageMgr.exe. Refer to Related Resources: "User Account Control (UAC) is asking if Sagemgr.exe can make changes to this computer" Related resources Files to allow through firewall and antivirus How can I tell if I am mapping my workstation to the correct data location? How do I manually uninstall Pervasive? How do I move my company data folder? How do I share my Data path folder? How to change the data path How to close open files on Microsoft Windows Server 2008 R2 and 2011 How to close open files on Server 2012? How to completely uninstall Microsoft .NET Framework How to create a new data path with the Database Repair Utility How to find data path and program path How to find the Windows hosts file How to locate company directories How to map a network drive How to modify the ini file to force activation on a workstation How to run Repair Installation instructions User Account Control (UAC) is asking if Sagemgr.exe can make changes to this computer Verify my data file permissions are correctly set Category Performance Product Entitlement Open Last Modified Date: 6-5-2015ID: 10897
↧