I ran it. This is the log message, "Linking to [SAMSYS] SQLEXPRESS..SAMSYS.. Database driver = A4WSQLS.DLL == GetFileVersionInfoSize returned a length of 1892 == Database driver returned error code 99" This is the only message, nothing else.
↧
Forum Post: RE: Unable to connect to the database (error=99)
↧
Forum Post: RE: Unable to connect to the database (error=99)
Something basic is wrong with your SQL configuration. I refuse to use Windows 8, maybe you need to turn off UAC, or you didn't install Accpac in it's own folder, i.e., not the default Program Files folder.
↧
↧
Forum Post: RE: Unable to connect to the database (error=99)
I turned off UAC. And yes, I have modified the default folder path while installing. By default it took "C:\Program Files (x86)\Sage\Sage 300 ERP". I modified it to "C:\Sage 300 ERP". Is this creating problem? What should I do now?
↧
Forum Post: RE: Unable to connect to the database (error=99)
If your database is in a non-default instance, then you might need to manually create the ODBC DSN as {yourcomputername}_SQLEXPRESS32 using c:\Windows\Syswow64\Odbcad32.
↧
Blog Post: The Sage 300 System Manager Core DLLs
Introduction We hold a developer’s exchange (DevEx) every couple of weeks where one of our developers volunteers to present to all the other developers in our office. This past week I presented at the DevEx on what all the core DLLs in our Sage 300 runtime folder do. I thought this might be of interest for a wider audience so here are the gory details. Architecture Our marketing supplied architecture diagram is the following which highlights our three tiers and hide a lot of the details of how the object repository, APIs and supporting services are implemented. I’ve blogged previously on our Business Logic Views . In this article I’m going to go into more detail on all the DLLs that provide the framework to support all of this. Lower Level DLLs If you are an ISV developing Sage 300 SDK applications or have worked for Sage on the 300 product then you will have had to encounter a number of these DLLs. I’m only looking at a subset of current DLLs, and I’m not looking at all the DLLs that support older technologies that are still present to maintain compatibility with add-ons. I didn’t add arrows to this diagram since everything pretty well calls everything else below it. But segregated the DLLs a bit by how low or high level they are. So here is a quick synopsis of each one: A4wcompat.dll: We created this DLL back when we did a native port of the Sage 300 Views for Linux. This DLL isolates operating system differences that need more than some clever #defines. A big part of this is the thread and process synchronization and locking support. Even though we never released the native Linux version, this isolation of operating system dependent parts had made adding multi-threading support, 64 bit support and Unicode support easier. A4wmem32.dll: In 16 bit Windows, the built in memory management was really slow, so everyone used their own. Now this DLL uses the Windows and C default memory management, but is still important for global memory that needs to be shared across processes. Originally this was done through the data segment of a fixed DLL, but now is done through memory mapped files. A4wlleng.dll: This is just a language DLL that holds some lower level error messages used by System manager. A4wsqls.dll: This is the SQL Server database driver (there is also a4worcl.dll for Oracle and a4wbtrv.dll for Pervasive.SQL). This is dynamically loaded based on the type of database you are connecting to. For more on our database support see this article . Cato3msk.dll, cato3dat.dll : The cato3 DLLs are the old CA common controls. We don’t use these in our UIs anymore, but cato3msk.dll provides our mask processing that is used by the Views. Similarly we don’t use this date control, but do use a routine here to format dates in error messages correctly. A4wroto.dll: This handles the loading of the various View DLLs as well as the various UIs we’ve used in the past. It loads the roto.dat files and handles loading the right DLLs when View subclassing is going on or stub Views need to be used. A4wsem.dll: This handles the locking of the semaphor.bin file. It allows processes to lock the company database, an application or the whole site. It also handles application specific cross workstation locking needs. A4wrv.dll: This is the main DLL API entry point for the Views. It manages all the calling of the Views and handles other tasks like sending the calls for macro recording. For more on our View interfaces see this article . A4wapi.dll: This is quite a hodge-podge of services for the Views like revision lists, error reporting and such. It also has support routines for the older CA-Realizer UIs. This is quite a big DLL and has most of our C level API in it. A4wrpt.dll: This is our interface to Crystal Reports, it started as our interface to CA-RET then was converted to Crystal using their CRPE DLL interface, then converted to Crystal’s COM interface and now uses Crystal’s .Net Interface. A4wprgt.dll: This DLL handles replicating the system database tables into the various company databases when needed. A4wmtr.dll: This is our meter DLL for long running processes. It can either put up a meter dialog or just report back to the caller, the current status and percent complete. It also provides the API for cancelling long running processes. Higher Level APIs The next level are some of the DLLs that make up our Java, COM and .Net interfaces. There is a bit of complexity here due to how our previous web deployed system worked. Here we could communicate back to the server originally using DCOM and then later with .Net Remoting. The .Net Remoting layer provides both the communications layer for this web deployed mode and also acts as our .Net API. Depending on how you create your original session will configure which actual DLLs are used and which are calling conventions are used. A4wapiShim.dll: This is the C side of our Java JNI layer. It talks to all the lower level DLLs to get its work done. Sajava.jar: This is the Java side of our Java JNI interface. This allows Java programs to easily call Java classes to interface to our Business Logic Views. For more on this interface see this article . A4wcomsv.dll: This is the main workhorse for the COM and .Net APIs. It does all the heavy lifting and interfacing to the core DLLs. Accpac.Advantage.COMSVR.Interop.dll : This just performs the .Net to COM transition which is created by the MS tools. Accpac.Advantage.Server.dll : Server side of the .Net API, handles the .Net Remoting requests if remotely called or just passes through otherwise. Accpac.Advantage.Types.dll : Defines all the various types we use in our .Net API. Accpac.Advantage.dll: This is the main external interface for our .Net API. For more on our .Net API see the series of articles starting with this one . A4wcomexps.dll : Used when the VB UIs are going to talk .Net Remoting, this DLL is inside a4wcomex.cab. A4wcomex.dll: The main entry point for the COM API. Many More DLLs There are many more DLLs in the Sage 300 runtime, but most of the others are for obsolete APIs like the xapi, the older a4wcom COM API, the cmd API, the icmd API, etc. There are other important ones like to do with Database Setup, but these are the main ones used when you talk to the Business Logic through one of the main popular APIs. Summary For anyone interested this should give you a good idea of what the main DLLs in the runtime folder do. And give you an idea of how the various services in Sage 300 ERP are layered.
↧
↧
Forum Post: Day end processing error
Erp 2012 sp2 when running dayend Internal Error cstp xifo iloc mismatch error (2559 ICCSTPI.C.) Have deleted restart rebooted server thanks
↧
Forum Post: Timeclocks supported for Sage 300 PR
A PRO customer migrating to Sage300 this year has 10 year old time clocks by Timebank (?Timebanc). They are thinking about getting new timeclocks to go with their new software. We have no experience with any time capture systems for Sage 300 - where can I find information about officially supported systems? Any others (not endorsed) solutions you'd recommend? Thanks. Mary
↧
Forum Post: 6.0 US Payroll and Sage 2014
Does anyone know of compatibility issues with using Payroll 6.0 (pre-Aatrix) and either Sage 2012 or 2014? I don't think there are any issues but wanted to double-check. Thanks.
↧
Forum Post: Module not installed message?
I have had to install/uninstall/re-install Sage 300 ERP several times in a test environment to test upgrading from AccPac 5.6 to Sage ERP 300 Standard. Since we have some legacy optional fields, to activate the data the first time, I was able to use a temporary license for the Transaction Analysis and Optional Field Creator. Now, however, after uninstalling and re-installing AccPac 300 ERP today, I am faced with this module not appearing to be installed - when I try to activate my data to go from AccPac 5.6 to Sage ERP 300 I get this error: Yet it seems to have installed correctly with a temporary license. The License Manager, shows all 0's in the Serial #, Type: Temporary and Status: Expires on 03-05-2014. But clicking on License Info for that module does show an earlier Expire Date of 01-04-2014 - perhaps that is the issue? Any ideas on what might be causing this and how to resolve it? We're still in Test mode so I will have to do this at least one more time when we are ready to go to production. Thanks for any help. . . Jeff
↧
↧
Blog Post: Outlook Integration: Troubleshooting Common Installation Issues Part 2
In our last blog , we took a look at troubleshooting some common issues with the Outlook Integration Plugin. Some of the issues that we covered include how to troubleshoot an unresponsive toolbar or when the login fails to load. In part 2, we continue to take a look at more common installation issues and how to troubleshoot them. Sage CRM logon When logging on to Sage CRM from Outlook using the Outlook integration plug-in, you may see the following message: There has been an error with the plug-in. Please contact your system administrator. This error is due to too many shortcuts in Outlook that you will need to clean up. Here are some steps to follow: Open Outlook, Tools, Macro, Macros . Type DelShortcuts in the Macro Name: field . Click Create . This action will open the Microsoft Visual Basic window. In the Code window, replace its contents with the following: Sub DelShortcuts() Dim BG As OutlookBarGroups Dim Count As Integer Set BG = ActiveExplorer.Panes.Item("OutlookBar").Contents.Groups Count = BG.Count While Count 1 BG.Remove (Count) Count = Count - 1 Wend End Sub Click File, Save VbaProject.OTM. Click Close and Return to Microsoft Office Outlook . Re-open the Macros screen as per step 1. Other installation issues When installing the Outlook plugin, all the required information should automatically be filled in such as the Server Name, Install Name and Port. But sometimes, you may find that this information screen is blank. If this screen is blank, it probably means that the information did not come over properly when downloading the installer. When installing the plugin from MyCRM Preferences, you need to ensure that ActiveX Controls are enabled on the web browser. If it is enabled, then a security setting may be preventing the information from passing through. The workaround is to add the CRM website to the list of trusted sites in your web browser like IE. If you are using IE, make sure you are running it as an administrator. Alternatively, you can manually enter the missing data into the installer. If you do that, you need to be make sure that the information inputted is 100% accurate or you won’t be able to connect to CRM. We recommend that this should be done by the System Administrator as the SQL database password may be required. Related to ActiveX, you may see the following message when installing the Outlook integration plug-in: The CRM Outlook integration plugin failed to load If you see this, check to make sure the ActiveX controls are enabled, that you answer yes to any security questions, that you are an administrator on your computer and that you have Outlook 2000 or greater installed. Then go through the following steps to resolve the issue: Open IE, click on Tools , Internet Options , Security . Select the Internet zone that Sage CRM belongs to. The zone is indicated in the lower right corner of the IE status bar. Click Custom Level, select Yes from the Reset to list . The settings can also be customized; however, the following options must be enabled: Automatic prompting for ActiveX controls Download signed ActiveX controls Run ActiveX controls and plug-ins Click OK to close windows and save changes Next time we will take a look at how to troubleshoot synchronization issues you may encounter with the Outlook Integration Plugin. For the latest support news and updates, follow us on...
↧
Forum Post: Refund from a vendor/supplier
Hi Just wondering how to enter a refund from a Supplier? We entered an invoice twice, paid it twice and now they have refunded the overpayment. I have entered a credit note (so the expense account is correct), but need to record the refund so the AP balance is also correct (and it shows for reconciling our bank account). Cheers Anna
↧
Forum Post: Updating custom crystal reports has never been easier
Here is the list of field names that have been added in Sage 300 2014 ICILOC: added fields LEADTIME, QTYMINREQ ICITEM: added fields PREVENDTY, DEFBOMNO ICITMV: added field QTYMINORD ICOPT: added field DUPSERIALS POOPT: added field RCPNEGIN ARCUS: added field CATEGORY Updating your custom reports has never been easier! Donal de Paor Senior Product Manager Sage Mid-Market & CRM Solutions T. +1 604 207 9480| D. +1 604 207 3430 donal.depaor@sage.com | http://www.sage.com �
↧
Forum Post: Status Update Week 4
Hi, As promised I will touch base weekly with everyone to provide a status update on our progress. Last week I shared with you how confident I was that quality is ROCK SOLID in Sage 300 ERP 2014. So, what's the latest........ Customers live 18 (+3) Defects reported 2 (nc) Defects resolved 2 (nc) Partners 11 (+2) Open support issues 0 (nc) We had 1 issue reported to customer support on a windows 8 workstation. We believe the issue pertained to Windows 8.1 last week. Sharon Paul of Gross Mendelsohn Technology Solutions Group simply deleted the existing ODBCs that were there. She logged completely out of the PC, logged back in, ran Accpac and it opened but got a Visual C++ library error. Then she ran regacc and everything was fine! We have documented the error and the solution in our KB in case anyone else experiences the issue. As you know one of Sage 300's great strengths is the fact that we are truly a global product. Partners in South Africa, Asia & Australia have expressed an interest in joining the program. I will share more details as these partners sign up over the next few weeks. More announcements imminently from partners in North America signing up also. Thanks for your interest, Donal de Paor Senior Product Manager Sage Mid-Market & CRM Solutions T. +1 604 207 9480| D. +1 604 207 3430 donal.depaor@sage.com | http://www.sage.com
↧
↧
Blog Post: We have a fix for that Part 1
In a new blog feature, we bring you the latest Sage Knowledgebase articles of note that may address some issues that you’ve encountered while using Sage 300 ERP and a resolution for it. Migrating Sage Pro ERP data to Sage 300 ERP As Sage Pro ERP nears its end of life, we offer some information on how to migrate you Sage Pro ERP data to Sage 300 ERP. This information can be found in KB 29371 . Error: “UFL u25total that implements this function is missing" error when printing a report” You may encounter this error while printing reports: UFL u25total that implements this function is missing. This error may occur if there is an issue with the U25total.dll and U25store.dll files in the Crystal runtime folder. KB article 19650 offers a workaround that will resolve this error. Error: There are No Installed Organizations” may occur when opening a Sage 300 ERP database on a workstation We have noticed the following error appear when opening a Sage 300 ERP database on a workstation: "There are no installed organizations Unable to Open Orgs Table in SITE directory, error = 1 Cannot open the dbprofilestable" A resolution for this error can be found in KB article 19546 . Error: “Cannot access database (error=40960)” After you login, you may see the following error message: “Cannot access database (error=40960). See Help for more information.” This may happen when the DSN used in the database setup is pointing to an incorrect server. KB article 24480 has a workaround that will correct this error. Blank page or spinning icon is displayed when opening Sage 300 ERP Portal For Sage 300 ERP 2012 and Sage ERP Accpac 6.0 , you might encounter a blank page or spinning icon when opening Sage 300 ERP Portal. The cause of this error could be a permissions issue or a Tomcat issue . KB article 23561 has more information as well as some steps to resolve the issue . Error: "HTTP Error 401.3 - Unauthorized" appears when launching Portal If you are on Sage ERP Accpac 6.0 , the following error occurs when launching the portal: HTTP Error 401.3 - Unauthorized. You do not have permission to view this directory or page because of the access control list (ACL) configuration or encryption settings for this resource on the Web server. KB article 20149 offers steps to resolve this issue . Error: "Warning. Unregistered Applications" occurs when opening a company database When you are trying to open a company database, you may see the following error: WARNING - Unregistered Applications You have applications that are not registered! KB article 19332 has two procedures that you can perform that may resolve this issue. Batch status is set to Posting in Progress When posting a batch from the batch list window, you may find that it does not post and the status is displayed as “Post in Progress”. This is caused if the posting process is interrupted or is incomplete. KB 19982 has the steps to resolve the issue. We also have a list of all the HotFixes for all the currently support versions of Sage 300 ERP. This list can be found over at Sage 300 ERP’s Support Community in Sage City. If you have any questions, please let us know. We would like to hear from you! Sound off in the comments. For the latest support news and updates... Follow us on...
↧
Forum Post: RE: Status Update Week 4
Hi, Is there a 1/31/2014 Payroll Tax Update for V2014 of US Payroll V7.1? We have a client going live this weekend and they use Payroll. Thank you!
↧
Forum Post: RE: Status Update Week 4
Hi there, Yes there is. Please contact me directly and I will send you the link to download the file. Thanks, Donal de Paor Senior Product Manager Sage Mid-Market & CRM Solutions T. +1 604 207 9480| D. +1 604 207 3430 donal.depaor@sage.com | http://www.sage.com
↧
Forum Post: Integration to Pitney Bowes Ascent product for Sage 300
A company on Sage PRO (migrating to Sage300) has a Pitney Bowes installation and are asking if there is an existing integration to Sage 300 for Ascent. Pitney Bowes says this is something they don't do, so I'm asking our community to see if someone has done this. We'd much rather they go to SmartLinc and they are prepared to do so, but want to know if they have an option to keep their existing Pitney Bowes system.
↧
↧
Forum Post: Accpac 5.5A and Win 8.1
Hi, Is Accpac 5.5 running with Windows 8? Thanks.
↧
Forum Post: RE: Accpac 5.5A and Win 8.1
If Pervasive, then XP mode only. MSSQL maybe.
↧
Forum Post: Database Changes Document for Sage 300 5.6
Can anyone point me to a database changes document for Sage 300 ERP 5.6? The 6.0 and 2012 documents are easy to locate but not so for 5.6. I need to put together a delta change document for all database changes from 5.5 through to 2012 for a client.
↧