Accpac Error Messages
Contents |
Sage Accpac ERP system. Everything was working fine yesterday, and today you can’t access your program. What
Accpac Error 49153
does this mean? First of all, let’s clarify some basic information that accpac error 98 is going to help us troubleshoot this problem. 1) Your license files are (or should be) located sage accpac error 49153 in the Accpac Shared Data location. This is where accpac stores common files for all application files to use. If you don’t know where your shared data directory is
Sage Accpac Error 40962
located, you will have to check the registry. The full path to the registry settings is: HKEY_LOCAL_MACHINE\SOFTWARE\ACCPAC International, Inc.\ACCPAC\Configuration. The SharedData key tells you the exact location of your license files. 2) Your license files will start with the two character module abbreviation, then the version and either a .lic, .pls or a .sbe extension (depending on
Sage 300 Erp Invalid Database Specification
the Edition of Accpac that you are using). For example, SM56A0.lic is a license file for System Manager Version 5.6 Edition 500. GL55A0.pls is a license file for General Ledger Version 5.5 Edition 200. Now that we know what a license file looks like, and where they are supposed to be, we can start checking for the source of this error. 1) Browse to your shared data location and check that your license files are there. Has someone unknowingly moved them, or have they been deleted by mistake? You will need to restore them from backup, or re-install System Manager and then re-license all the individual modules. You will need all your activation codes for this process. 2) Was your accpac installed with a temporary license that has now expired? System Manager will need to be re-installed with an activation code to fix this. 3) When browsing to your shared data location, you may have received an error, and cannot open this location. Are your network drives mapped? Has t
developers and resellers. Greytrix has accumulated hundreds of man years of experience in Sage 300 ERP. sage accpac In this blog, Greytrix will endeavour to share its knowledge with regards to implementation, training, customisation, components and technology and help users to understand in depth techno - functional aspects of Sage Accpac ERP! Contact accpac (at) greytrix (dot) com Currently viewing the tag: "error" Database Error 49153 in Sage 300 ERP By greytrix On January http://www.baass.com/plusblog/bid/48051/Accpac-Error-You-Do-Not-Have-a-License-to-Use-This-Product 6, 2016 While accessing any Sage 300 Company, at times user may encounter error such as -”Cannot access database (error=49153). See Help for More information.” New Stuff : Significance of using Default Posting Date option of I/C Options in Sage 300 ERP When the user reports error […] Continue Reading → Database Error 98 in Sage 300 http://www.greytrix.com/blogs/sageaccpacerp/tag/error/ ERP By greytrix On August 26, 2015 While accessing any Sage 300 Company, at times user may encounter error such as - ”Cannot access database (error=98). See Help for More information.” New Stuff: Options for maintaining Sales History in Sage 300 When the user reports error to System Administrator, the system admin team checks is the Database […] Continue Reading → Configuration tips for Greytrix Extended Report Pack in sage 300 ERP By greytrix On March 24, 2015 As we have learnt in our last blogs about Greytrix Extended Report Pack which comprises of vital registers and vouchers, and are specifically designed and configured to meet Indian Business working style. Many times, due to some wrong or incomplete configuration, consultants ask for the solution on the errors or printing issue that they are […] Continue Reading → Error: Sage 300 ERP UI Container has stopped working message occurs when printing reports By greytrix On February 27, 2015 Sometimes users face an error message “Sage 300 ERP UI Conta
developers and resellers. Greytrix has accumulated hundreds of man years of experience in Sage 300 ERP. In this blog, Greytrix will endeavour to share its knowledge with regards to implementation, training, customisation, components and technology and help users http://www.greytrix.com/blogs/sageaccpacerp/2014/09/23/invalid-database-specification-error-sage-300-erp-formerly-sage-accpac/ to understand in depth techno - functional aspects of Sage Accpac ERP! Contact accpac (at) greytrix https://smist08.wordpress.com/2010/04/17/diagnosing-problems-running-accpac-part-2/ (dot) com Default Create OE Invoice in Sage 300 ERP CHECK DUPLICATE CUSTOMER PURCHASE ORDER NUMBER IN SAGE 300 ERP Invalid Database Specification error Sage 300 ERP (formerly Sage Accpac) By greytrix On September 23, 2014 Invalid Database Specification is a common error message that can occur when opening Sage 300 ERP (formerly Sage Accpac). This error message generally appears while opening accpac error Sage 300 ERP (Accpac). On opening the application, it tries to connect to the database. If there is a connection problem, user may face this error. New Stuff: Commit All in OE ORDER ENTRY There are a number of reasons that can cause this message to appear. In a client server system where Sage 300 ERP is installed and the database server is on a separate system and if the database server is unavailable/not reachable due to some reason, accpac error 49153 this message could occur while attempting to open Sage 300 ERP and login to a company. If it is a new installation, or just a single user, you need to examine why the workstation is not able to connect to the database server. The workstation will connect to the database server using ODBC connection to data. Some good troubleshooting steps: 1. Check to make sure that the proper ODBC entries have been made - Depending on your configuration in Sage 300 ERP Database Setup, you may need to make a single ODBC entry called databaseservername32 or an individual ODBC entry for each database (e.g. SAMSYS, SAMINC) - If the workstation is a 64-bit workstation, your entries must be made with the 32-bit ODBC client (C:\Windows\SysWow64\ODBCAD32.exe) 2. Disable UAC (User Account Controls) - This can often interfere with Sage 300 ERP while making a connection with the ODBC drivers 3. Check that the right versions of Sage 300 ERP and SQL Clients are set in the ODBC Entry. Starting with version 5.6, the SQL Native Client is required. 4. Disable any firewall that might be blocking outbound traffic. 5. Login as a user that has local admin rights on the machine and then test as that user. - If this fixes it, run RegAcc as the Admin user. This will create all of the required registry entries that the non-admin user will need. Hop
time we will look at what happens when you click ok on the sign-on dialog through to when the desktop is displayed and ready to go. When Accpac loaded the sign-on dialog with the company list, it kept track of whether security is turned on for that company/system database. This information is stored in orgs.ism. Accpac will then validate the user name against accpacshareddata\site\users.ism. If security is enabled it will also validate the password. If you are having trouble signing on, first run DBSpy. If nothing appears in DBSpy then the problem is before opening the database links and will be to do with something in the accpacshareddata\site directory. Run ScanIsam to ensure the various ism files are ok. Sometimes ScanIsam can even fix them. Also remember that every user must have full control security access to all the files in the site directory. Next Accpac will try to reserve a lanpak slot for this workstation/company/userid combination. If there is a free slot then you will be allowed to proceed, if not you will get an error message that all the lanpaks are in use. You can use the Desktop menus to see how many lanpaks are available and how many are used and which userid/company combinations are using them. If you think they should be available make sure the lanpaks aren’t expired 30 day licenses. If everyone is out of the system, it is safe to delete the site\lanpak.bin file. It will be re-created the next time you run Accpac. To do all this the desktop runs the a4wLPMgr.exe program which then tracks the lanpak usage for this workstation. Accac will now run the Accpac Signon Manager (a4wSignonMgr.exe). This isn’t required by the Desktop, but is run so if anyone starts a UI program from outside the desktop, it can connect to this to share the signon info. You see this running in the icon tray in the bottom right of your screen. If the signon manager doesn’t run as part of the desktop startup process, you may have a problem with the Accpac COM components. The best bet is to re-register these by running accpac\runtime\regacc.exe. This program will register all the Accpac COM components, normally this is run by the Accpac installation program, but sometimes parts of this can fail. Accpac then ne