Newest KB Articles in Error Messages

Exceed the number of licensed users after power outage

Mon, 26 Jul 2021 21:05:20 GMT

A power outage, or improper shutdown of a computer, can result in damage to files used to facilitate record locking within Atrex. If this occurs, it can result in the message "Starting this copy of Atrex will exceed the number of licensed users".

You can attempt to resolve this issue using the following steps:

Close Atrex on all workstations.
Restart the server computer. If you are running a client/server configuration and cannot restart the server for any reason, restart the Atrex database server engine via the Atrex Database Server Administrator.
Before opening Atrex on any system, locate the data folder in Windows File Explorer, and delete ua_data.* from that folder.
Again in Windows File Explorer, locate In the central folder, and delete ua_atrex.* .

(Applies to Atrex 13+)

Error: "Out of System Resources" when printing to screen

Tue, 27 Aug 2019 14:24:23 GMT

Error: "Out of System Resources" is displayed when printing to screen.

This error is most frequently displayed when printing to screen when using a remote desktop connection and the screen resolution is changed while a report is printed to the screen. This can cause one of the print preview settings to be set to a incorrect value.

The following instructions will allow you to reset this value:

Select "Options - Company Setup / Customization - Edit Local Settings" from the main Atrex menu.
Read and then click OK on the warning message.
Locate and right click on the "Preview AccessoryToolbar" configuration section.
Select "Delete Section" from the popup menu.
Close the configuration editor.
Restart Atrex.

(Applies to Atrex 16 and newer)

ElevateDB Error 1100

Wed, 15 Nov 2017 17:14:19 GMT

This error is displayed when Atrex cannot connect to the database server engine.

The error message is displayed in the format of "A connection to the server at <ServerAddress> cannot be established (<ErrorMessage>)", where <ServerAddress> is replaced with the host name or IP address of the server that Atrex was attempting to connect to, and <ErrorMessage> is replaced with the actual socket error that was encountered.

This is a common error that occurs after the server installs a large Windows update. If your server rebooted after receiving Windows Updates, rebooting it again will usually restart the database server engine the properly.

Resolving error 1100 mainly involves determining what is causing the connection failure. The things to check and verify are:

Verify that the server engine is actually running on the server computer at the <ServerAddress> indicated in the message. Open up the Administrative Tools from the Windows Control Panel and then open the Services manager. Look for a service named "ElevateDB Server".

If it is present, make sure that the status is "Running". If it is not, right click on the entry and select Start.

If it is NOT present, then the server engine has either been uninstalled OR this isn't the same computer as indicated by the <ServerAddress>

If the server engine is installed and frequently fails to start after the server computer is restarted, you may want to consider changing the startup option for the ElevateDB Server service to a delayed start. This prevents delays with other services starting, or Windows updates, from preventing the ElevateDB Server service from starting.
Verify that you actually have the correct server name. If the server name is correct, use the windows command line to "Ping" the server using the address followed by -4. On the window command line, to ping a server named "DBServer" it would be entered like Ping DBServer -4

Verify that the IP address returned from the ping is the same IP address that the server is using. If it is not, then you have a DNS lookup error and you will need to use the IP address of the server rather than the name of the server to make the connection.
Verify that the firewall is not blocking the connection. To do this, turn the firewall off temporarily and then try to make a connection with Atrex. If the connection is successfull, you will need to add an exception to your firewall to allow the connection to the database server engine on port 12010 before you can enable the firewall again. You will need to consult the documentation for your firewall for instructions on how to add the exception. For version 16 and above of Atrex, reinstalling the server engine for your version of Atrex will automatically add the exception to the standard Windows firewall.

Different versions of Windows and different firewalls behave differently, so the socket error number MAY or MAY NOT be helpful in directing you towards the solution. The most likely causes of the connection errors for various socket errors are:

Error 10049: Incorrect name or IP address for the host. Make sure that it is correct and resolves to the correct IP address.
Error 10060: Server engine not running, wrong server name or address, or the firewall is blocking the connection silently.
Error 10061: Server engine not running, or the firewall is actively rejecting the connection.

(Applies to Atrex 13 and newer)

ElevateDB Error 100

Tue, 12 Jul 2016 15:27:24 GMT

This is a general error that indicates indicates that there is an error in a table or object definition within the database catalog, or an inconsistency between the database catalog and the actual tables. The error message displayed will provide additional detail about the specific instance of the error.

This error can be caused by numerous events such as a power outage while data is being written, a failing hard drive, anti-virus software, or even automatic backup software such as Carbonite (http://support.1000years.com/kb/a22/carbonite-online-backups.aspx).

If the error is minor, it can be repaired using the Repair Tables option of the "Options - Batch Processing" function with the "Repair Tables" option selected.

If the error is not resolved by running the "Repair Tables" option of the batch processing, the database is damaged beyond repair and you will need to restore from a backup taken prior to the onset of the issue.

(Applies to Atrex 13 and newer)

Error "Could not compile program"

Mon, 02 Mar 2015 15:49:01 GMT

The "Could not compile program" error within ReportBuilder indicates that there is a problem with one of the events of the report. If you have deleted or renamed any objects on a standard report, there is most likely code in one of the event handlers that are still pointing to the old or deleted object name.

To track these types of errors down, you will need to do the following:

Open up the report in the designer.
Preview the report to get the name of the event or object that is causing the error.
Click on the "Calc" tab of the report designer.
Click on the "View" menu and and select the "Module" view. This will display all of the event handlers for the currently selected report or sub-report in the right hand box.
Look for any event handlers that have a red icon to the left of the event handler name. This indicates that there is an error in that event.
Click on the first event that has a red icon to display the event code in the lower portion of the calc tab.
At this point, you need to correct the code in this event to get it to the point where it will compile. Right click on the code for the event handler, and select "Compile" from the popup menu. Just below the code window, the results of the compile will be displayed to show you where the problem is.
It will most likely tell you that there is an undeclared identifier. This means that the code is trying to access an object or property that does not exist. If you have deleted an object from the report, you need to find the code that references that object and remove it as well.
Repeat steps 5 through 8 until you no longer see any event handlers with a red icon.
If there are still problems with the report after cleaning up all of the event handlers, you will need to select each of the sub-reports (if there are any) for event handlers that have errors by selecting the sub-reports one at a time from the tabs at the bottom of the calc page. When you select a new sub-report, all of the event handlers for that sub-report will visible, and the events that have errors will be highlighted with the red icon.

ElevateDB Error 601

Mon, 23 Feb 2015 20:04:17 GMT

This error is displayed if there is an error reading, writing, or validating a table.

If this error occurs consistently, every time the same table is accessed, the table is damaged. If the damage is minor, it can be repaired using the Repair Tables option of the "Options - Batch Processing" function. If the damage cannot be repaired, you will need to restore from a recent backup taken before the onset of the issue.

If the error is intermittent, this is an indication that something is blocking proper access to the table. One known common cause of this error is "Live" backup software programs such as Carbonite. Please refer to the following article on how to properly configure your live backup solution for use with Atrex: http://support.1000years.com/kb/a22/carbonite-online-backups.aspx .

(Applies to Atrex 13 and newer)

ElevateDB Error 407

Wed, 18 Feb 2015 16:22:00 GMT

This error message is displayed when a table exceeds the maximum default file size.

In Atrex 17 and older, the database engine defaults allow for a maximum file size of 4GB for any one single file within the database. Most Atrex installations will never hit this limit, but for installations with a large number of inventory items, a large number of product images, or high transaction volume, additional space within the tables may be required.

To allow for larger tables, the ElevateDB database engine can be configured in the Atrex Database Server Administrator to allow for large file support. With large file support enabled, the maximum file size for any single file in the database is increased to 128GB. Please note that Large File Support is only available with a client/server configuration of Atrex.

Enabling Large File Support:

Close Atrex on all workstations.
Open the Atrex Database Server Administrator and log into the application..
Select "Tasks - Modify Server Settings" from the main menu.
Click on the "Configuration" tab.
Check (enable) the check box that says "Enable Large File Support".
Click the OK button.
Click Yes when prompted to confirm the restart of the database server.

In Atrex 18 and newer, the database engine defaults to Large File Support being enabled. If you are experiencing this error in Atrex 18, you will need to determine which table is full and reduce the amount of data in that table. In most cases, this will be the code images table being full because the images are high resolution. Using the image resize function inside of Atrex and setting a default maximum image size can resolve this issue.

Class Not Registered error displayed during credit card processing

Wed, 20 Nov 2013 15:32:15 GMT

The "Class Not Registered" error message displayed during credit card processing indicates that a required component of the Worldpay / Vantiv plug-in has been uninstalled.

To resolve this issue, re-install the Worldpay / Vantiv plug-in.

The WorldPay / Vantiv plug-in can be downloaded from the Millennium Software Client Center.

ElevateDB Error 401

Sat, 12 Oct 2013 22:23:18 GMT

This error indicates that an attempt has been made to access a object (table, stored procedure, index, etc) in the database that does not exist.

There are 4 possibilities that can cause this error to occur.

1. Atrex is no longer pointed to the correct data location. To correct this, use the "Options - Locations - Data Location" function to redirect Atrex to the correct location.

2. The Atrex data location has been pointed to an empty directory, or a previous batch processing has failed. To correct this, run the "Options - Batch Processing" function to recreate the missing objects.

3. You are attempting to run a SQL query that references a table that does not exist. Check the query to ensure that the table names entered in the query are correct.

4. You are running mixed versions of Atrex. If you have recently upgraded Atrex to the current version and converted the data, opening an older version of Atrex on a system pointed to the converted data may damage the database and cause this error. To correct this, make note of which version of Atrex is installed on each system and then close Atrex on all systems. Install the current version of Atrex on all systems. Reopen Atrex on just one system. Make a backup (Options - Backup/Restore - Backup). After the backup completes, run Batch Processing (Options - Batch Processing - click OK).

(Applies to Atrex 13 and newer)

ElevateDB Error 300

Sat, 12 Oct 2013 22:22:47 GMT

This error indicates that a required lock could not be obtained. The most common causes of this are:

1. Attempting to use both direct and client/server connections to the same Atrex database.

2. Attempting to access a Atrex database using the direct connection method, but using different data paths.

One-at-a-time, start Atrex on all systems, then go to Help - System Information. Locate the "Paths" section of information and then both the "Data" and "Central" sub-sections.

Ensure that all the systems are using the same connection method and that the path listed is identical. For example, while the following paths may point to the same location, because the path specified is different between the systems, you will receive the 300 error.

System-1:
     Data Path: C:\Program Files\Atrex\Shared\Data
     Central Path: C:\Program Files\Atrex\Shared\Central
System-2:
     Data Path: \\System-1\Atrex\Data
     Central Path: \\System-1\Atrex\Central

Client/server provides several advantages over the direct connection method including the ability to schedule data backups.

(Applies to Atrex 13 and newer)