Starting 10/10/2017, users may experience an error “Unexpected error from external database driver (1)” when importing data into Acctivate. This is caused by a Microsoft security update release that inadvertently affects the JET provider (see this article from Microsoft). The only…
Following a server migration, new installation of Acctivate on a workstation, or a network related change within your system, you may encounter an error along the lines of: Could not Connect to SQL Server If you get this message, there…
If you have received the Microsoft Visual C++ Runtime Error, this is not an Acctivate error. This error could be caused by installation of new software, and has been reported after installing recent Windows Updates. The most likely cause is…
It is important to remember that the when preparing data to be imported it must match exactly what is in Acctivate. This includes any leading zeros for Product ID’s, UPC’s, etc. If you have ever tried to input numbers to…
Occasionally, while working within Acctivate, users may see the following message pop up: Typically, this warning can appear for the following reasons: The network connection to the server is broken or temporarily down The server is rebooting The instance of…
The Acctivate Server (New/Full) Install package includes SQL Server Express Edition. However, there are times when you may need to install SQL Server Express for Acctivate separately. Please follow the instructions below to install and configure SQL Server 2016 Express Edition for…
After updating Acctivate to a new version, users will occasionally run into an error stating: “Acctivate was not able to install required updates: Error: “Registry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\SharedManagementObjects\CurrentVersion\Version is out of date (10.51.2500.0 < 11.0.2100.60). Running msiexec.exe with args /i…
After selecting to download the Acctivate Evaluation RDP file, sent by your Acctivate Sales Representative, you may receive the error, below: This error may be received if the credentials saved on the RDP file are blocked by some Antivirus…
