This error is received when Micros point of sale is interfaced with another application. Most common application that micros interfaces with would be the Opera Property Management System. This application is used for managing the Hotel side of things.

Below are a list of things that you need to check in order to resolve this issue.

Step 1) Make sure the Micros Interface service is running. This can be in two locations depending on the version of RES 3700 installed.

Version 3700 3.2 and below:
In 3.2 and below the interface service is located in the Micros Control panel. Open the control panel "Start -> Programs -> Micros Applications -> Micros Control Panel" and make sure there is a green tick beside the interface service.

Version 4.0 and above:
In 4.0 and above all micros services except the "SQL Database Service" were moved from the Micros Control Panel to the windows services list. This services list can be accessed by typing Services.msc into the run prompt. Make sure the "Micros Interface Service" is started.

Step 2) Make sure the interface is running. The interface is generally located on another server/pc which is not the Micros server. This program acts as the middle man between Micros and the end product for example Opera PMS.

Step 3) Once you have confirmed that Step 1 and Step 2 are ok the next thing is making sure there is network communication between Micros and the Interface pc. Im not going to get into COM connections and am only going to focus on TCPIP connections.

Open the "Pos Configurator -> Devices -> Interfaces"  and select the interface which you are having trouble with. Select the interface tab on the right and you will see an ip address and port number. Make a note of these.

Open a command prompt and type in "Ping x.x.x.x" where x.x.x.x is the ip address without the quotes and press enter. If you get a reply then the network connection is active.

Next is to test the port number. Open a command prompt and type "telnet x.x.x.x yyyy" where x.x.x.x is the ip address and yyyy is the port number and press enter. If the command prompt goes blank with the blinking cursor in the top left then everything is ok and working, if it does not connect then there is a problem with the port. Consult the supplier of the interface for more info.

Step 4) If step 3 is unsuccessful then the problem is going to be with the end product eg Opera or with the connection between the Interface pc and the Opera server.

The error "Check Detail Read Failed" while trying to open a check/table on the micros 9700 point of sale system. This error is present is all versions of 9700.


This error is an indication that the check has become unreadable in the database. It can occur if the check is being accessed during a power failure or some other interruption to the operation of the micros system.


These checks are unrecoverable and can only be closed in the database.

Due to the nature of the databases used in Micros 9700 SQL 2000,2005,Oracle 9i and 10g; there are many ways to execute the necessary commands. Im going to assume that you know how to execute an SQL statement and just give the command.
Replace XXXX with the micros check number.

update microsdb.checks set checkclose=checkopen where checknumber=XXXX and checkclose is null
This command will close off any checks which are open and have the number you entered.

If you want to be more exact or if there are more than one check open with the same check number then follow the below steps.

Execute command where XXXX is the check number:

Select * from microsdb.checks where checknumber =XXXX and checkclose is null;
Make a note of the CHECKID number and execute the following where XXXXX is the CHECKID:
Update microsdb.checks set checkclose=checkopen where checkid=XXXXX;
And your check is closed.

The error "Check Detail Read Failed" while trying to open a check/table on the micros RES 3700 point of sale system. This error is present is all versions of RES but occurs much less frequently since RES 4.0


This error is an indication that the check has become unreadable in the database. It can occur if the check is being accessed during a power failure or some other interruption to the operation of the micros system.


These checks are unrecoverable and can only be closed in the database.

To proceed you will need to know the check number which is currently causing the error.


Step 1) On the Micros POS server open DBISQL. To do this press Start -> Run -> Type "dbisql" without the quotes.


Step 2) Enter the username and password:

Username: custom
Password: custom
or
Username: installer
Password: installer


Step 3) Type the following command and replace XXXX with your check number and execute:

Select chk_seq, chk_num, chk_open from micros.chk_dtl where chk_num = XXXX;

chk_seq = Check Sequence number is a unique number

chk_num = Four digit check number used to identify a transaction.

chk_open = True or False. True means the check is open, False means its closed.


Step 4)  Make a note of the number in the chk_seq column and type in the following command and replace XXXXXX with the chk_seq number and execute:

call micros.sp_forcechkclose(XXXXXX);

The check should now be closed.

I had a blog a while back running on http://micros-pos.blogspot.com
Its been neglected for quite a while so over the next few days ill be migrating the contents of that blog to here and once that is complete ill be automatically forwarding all visitors from that blog to this one.

Once complete i will try my best to blog about tips and tricks of dealing with the micros pos system.