Errors

Errors can be generated for any number of reasons. Usually the errors are due to a user not entering required information or trying to perform a task that can't be performed at that current point in time. Other errors can occur due to program faults.

Serious errors are logged to the audit table. These can be seen with the View Audit function. An important part of this error information is displayed on the right side of the screen. It lists specific details of the error message and where it occurred in the program. This can help track down the exact problem and let it be fixed quickly.

The service programs and some end of day jobs often keep log files of their activity. This can provide important information in tracking down problems. These log files can be found in the directory specified by the log files directory entry in DYNAMIC.INI.

Some error messages will display an error number. You can use this code to get more information on the error and possible resolutions. Go to TorexConnect (http://torexconnect.com) and select BE Software, Search Error Messages and enter the error number.

Error#

Error Msg

Error Description

User Solution

100

An access violation has occurred. This is caused by a problem within the program. Any changes you have made have been discarded. The program will now shut down.

An access violation is a bug in the program where the program tries to access some information it thinks should exist but it actually does not.

There is not a lot you can do about this error. It generally indicates a bug in the program that will need to be fixed by the programmers. The program will shutdown. You can try to do the task again. If it fails again, you will have to leave the task, or do a manual workaround, until the problem can be fixed.

101

You are running low on memory. This program will not be able to start. You should closing down some other programs before restarting this one. If you still have problems, reboot your computer.

A program uses memory as it does things. It should release the memory as it is no longer required. Sometimes though, a program bug will mean the program keeps taking memory but never releases it. Eventually the memory will be used up and this error message will start occurring.

A restart of the computer will generally fix the problem for the short term. A longer term fix will require a change to the program. Error information provided by the system will help identify the problem. However, it can be helpful if you can record what it was you were doing, especially if you doing a task you don't usually do.

102

The connection to the server has been lost. Wait a moment and try again.

The computer needs to connect to the head office server to do something but is unable to.

Your computer is not able to connect to the head office server. This can be caused by a number of different things but is generally a network issue. If you are using POS, there is a network symbol at the top right of the screen. If this has a red circle with a line through it, this indicates the POS is not able to connect to the server.

You can wait for a period of time to see if the problem resolves itself. If you continue to have problems there are a number of things that can be done:

- If its a non-critical function you were using, continue to use POS until a less busy time of the day.

- Check the network cable (generally a blue one!) is plugged in properly. Sometimes the cable can be accidentally dislodged.

- Restart the POS computer.

103

Cannot connect to the server. This can be caused by the server shutting down unexpectedly or by a bad network connection.

The computer needs to connect to the head office server to do something but is unable to.

Your computer is not able to connect to the head office server. This can be caused by a number of different things but is generally a network issue. If you are using POS, there is a network symbol at the top right of the screen. If this has a red circle with a line through it, this indicates the POS is not able to connect to the server.

You can wait for a period of time to see if the problem resolves itself. If you continue to have problems there are a number of things that can be done:

- If its a non-critical function you were using, continue to use POS until a less busy time of the day.

-Check the network cable (generally a blue one!) is plugged in properly. Sometimes the cable can be accidentally dislodged.

- Restart the POS computer.

104

An error occurred on the server:

Your computer has asked the head office server to do something but there was an error.

The text following this error message will provide details about the actual error that occurred on the server.

105

This code has already been entered

You are trying to enter new data for a specific code but it already exists. For example, you enter a new tender code against a location but the tender code is already set up for that location.

You can't enter the same data twice. You need to change the code you are trying to use to one that doesn't exist, or simply cancel the record you are trying to enter and use the existing one.

106

Could not get a connection to the database

The program needs to talk directly to the database but is unable to.

There is not a lot you can do about this error. Either the database server computer is not running, or possibly something has been configured incorrectly. In either case, this is an issue for technical support to resolve. Technical support will most likely know if the database computer is not running and will be attempting to turn it back on. Leave the computer for a few minutes and try again. If the problem persists it might be a configuration issue and you will need to contact technical support.

108

Cannot save your changes. Another user has already changed this transaction.

In various transactions it is dangerous to have two users changing the same data. This is especially true for inventory transactions. If two users try to change the same data, the second user will get this error.

If you are the unlucky second person who gets this error, you need to cancel the changes you have made, find the transaction and enter your changes again.

109

Cannot find Local Server to use for table transactions. Try to find again? If you answer No, POS will start up but you won''t be able to use tables

The POS has been told it must use the Merchant Local Server but it cannot find it.

The Merchant Local Server program must be running on one computer within the store. If it is not running you will get this error. Check to make sure the program is running on the nominated computer.

If you answer Yes to this question, the POS will check for the server again. So if it wasn't running and you have now started it, POS will find it and continue normal operations.

If you believe Merchant Local Server is running and you can't work out the problem, you can answer No to the question. POS will start in sale mode but you will not be able to access table functionality or put transactions on hold or recall them.

When Merchant Local Server is up and running properly, you will need to restart POS in order to get full functionality again.

110

Local Server not available. Cannot perform this action

The POS is expected to work with the Merchant Local Server but it was not found on start up and you chose to continue working anyway. Any time you try to access a function which requires the use of the Merchant Local Server, you will get this message.

You must get Merchant Local Server running and then restart the POS. When POS is restarted, it will find the server and you will get full functionality back.

111

Server is expecting encrypted data. The program will now shutdown. When you restart it, it will use encrypted data

The server is expecting the data being sent to it to be encrypted and its not.

Press the button to let the program shutdown then restart the application. The program should then just work. If the problem persists, contact support.

112

Cannot download the required version. POS will use old version until the new version can be downloaded.

POS determined that it needed to use a new version of itself. It has attempted to download the new version but there was a problem. The POS will continue using the current version until it is told to restart itself, when it will try to download the new version again.

Support will be able to tell that your POS has not loaded the new version. They will attempt to reload the POS centrally. If they any further questions they will contact you.

113

Cannot connect to the back office server to get table details

The POS needed to connect to the back office server but was not able to. The text following the error message is the reason why it could not connect.

Make sure Merchant Local Server is running on the back office computer.

114

Cannot connect to back office to get details. You can try to continue working although some functions may not work correctly.

The POS needed to connect to the back office server but was not able to. The text following the error message is the reason why it could not connect.

Make sure Merchant Local Server is running on the back office computer.

115

Could not execute the SQL query with current version of Microsoft SQL Server. You need SQL 2005 or above.

The function you are attempting to use (DATAENTRYINVENTORY POTEMPLATE) requires SQL Server 2005 or later. Note that this function is available from version 5.22 onwards of BE.

Upgrade the version of SQL Server on your system or do not make use of this function.

116

No cost record has been set-up or zero carton size

Usually seen while trying to adjust stock levels. The item that is being processed either doesn't have a cost record for the trade unit, or the carton size for the item is zero. Note that this function is available from version 5.22 onwards of BE.

Within item maintenance, correct the item cost details.

Converted from CHM to HTML with chm2web Pro 2.85 (unicode)