When ops is starting on all versions of micros workstations it loads a number of different modules.
The essential ones are as follows for correct operation of the workstations.
MDSHosts.xml
MDSServices.xml
MDSPrinters.xml
Ops.exe

You may also find KDS Display loading depending on your setup.

You may find that the Application Loader will stall on any one of these, the most common being MDSHosts.xml.

MDSHosts.xml contains IP address and Hostname information for the server and all workstations so its essential for operation.
On WS4, WS4LX, WS5 model workstations its located on the compact flash drive in cf\micros\etc
On Win32 workstations its located in c:\micros\common\etc.
Same applies for all the .xml files above.

Workstations should be kept up to date automatically with these files and should be downloaded upon installing ops using CAL.

If you find the Application Loader stalling there are a few simple steps you need to take.

Quick Fix: Transfer a copy of the MDSHosts.xml to the workstation. It is located on the server under D:\micros\common\etc and needs to be copied to the workstation. See above for the correct directory.

Long Term Fix:

Step 1) Make sure the MDSHosts.xml has a good copy on the server. It should be located in D:\micros\common\etc
Check the last modified date. It should be fairly recent ie. a few days. Reload the database via the Micros Control Panel (reload not restart). If the modified date has not updated and the workstation still not starting then proceed to step 2.

Step 2) Force the database to create a new copy. Open services.msc and restart the following services:

Micros Distributed Services ManagerMicros DB Update Service
Step 3) Reload the database via the Micros Control Panel. ( reload not restart ). The last modified date of the file should have updated to the current date/time.

From time to time it is possible that the micros drives can run out of space. Below i will list the usual suspects.

Database backups:

If your backing up the micros database on the server you should be running database validation. If the validation fails it will create a .bad extension backup in the "%Database Dir%\micros\database\data" directory where %Database Dir%  is the drive the database is stored on.

For reasons i dont know why if a .bad file is created the archived backups will no longer rotate and it will store backups in the "%Database Dir%\micros\database\data\archives" until the hard  drive runs out of space.

Solution: Delete the .bad file and delete any unnecessary backups in the archives directory.

-----------------------------------------------------------------

3700d.log Verbosity:

In the D:\Micros\Res\Pos\Etc directory there are 7 days worth of 3700d.log files.
If the verbosity is turned up high in the logs and left like that it can eat up disk space very quickly.
To change the verbosity open the Micros Control panel via the command line.

cpanel.exe /verbosity

The Micros Control Panel will now open with a verbosity tab where you can change the verbosity for the services and workstations between 0 and 10. Normal use should all be 0.

-------------------------------------------------------------------

Database Log File size:
All RES 3700 databases have a file called micros.log kept in the "%Database Dir%\micros\database\data" directory along with the micros.db which is the database.

The micros.log file is essential for the database to run but on occasion this file has been known to vastly increase in size into the gigabytes. Usually they are less than a few meg if not less than a meg.

Version 3.2 and below:

Step 1) Stop the database.

Step 2) Start -> Run and type in "scview" without the quotes and press ok.

Step 3) Select utilities and select "Change log file information". You may need to add the adaptive server anywhere plugin to get these options.

Step 4) Browse to the micros.db file and press next.

Step 5) Use all the default options here except the step where it asks you to create a mirror log file, here select "no change"

Step 6) Tick the box to delete the old log file information and press finish.

Step 7) Once you press finish you will be given a summary of your settings, just press ok to this.

Step 8) Open a command prompt and change the directory to the micros database directory which contains the micros.db file and execute the following command.

dbsrv6.exe micros.db -f

The SQL adaptive server anywhere program should have opened and now shrank down to the system tray. Double click on the icon and select shutdown.
Now start the database via the Micros Control Panel and shazam you should have a started database and a brand new small micros.log file.

Version 4.0 and above:
Thankfully much easier than 3.2 and much less frequently needed.

Step 1) Stop the database

Step 2) Delete the micros.log file

Step 3) Run the following command from the run prompt where D:\ is the drive of your database. You might notice something flash up for a split second but will most likely go unnoticed. (Capital F is important)

DM.exe -F D:\micros\database\data\micros.db

Step 4) Start the database via Micros Control Panel, you should now have a new micros.log file.

The service Autoseqserv.exe is responsible for managing scheduled autosequences as well as allowing autosequences such as end of shift reports,  to be executed from the pos operations.
If this service is frozen or simply not running you will get an error indicating that there was a failure communicating with the autosequence pc.
A lot of the time if the service is frozen you will simply have the pos operations hang for a few minutes before the error displays, if the service is not running you should get the error almost instantly.

RES 3.2 and below:
The autosequence service is located in the Micros Control Panel and can be turned on or off.

RES 4.0 and above
The autosequence service is located in windows services and is called "Micros Autosequence Service". If it is stopped start it, if it is started then restart it.

If you are unable to restart the service you will need to kill the executable via task manager or 3rd party program  such as pskill.exe which can be downloaded from microsoft.com.

System Closed is an error that you will get on the micros workstations when the system is set to "Back of House".

To resolve this open the Micros Control Panel. Start -> Programs -> Micros Applications -> Micros Control Panel.

Select Restaurant. On the right hand side you should have the option to press "Front of House" and then press ok.

All should be ok now.

Stand Alone Mode - is a status where the tills can operate by themselves without any communication with the micros server. All checks will be stored on the workstation and any checks created on the other workstations will not be accessible from anywhere except the workstation it was created on.

A requirement for this to be successful in closing off checks and giving customer receipts is to have payment types designed for Stand alone mode.  These payment types are usually denoted by "O/L" before the payment type.OL = Off Line.

This is only a requirement if the Micros is integrated with a PMS system as to prevent the offline still attempting to communicate with the PMS system.

Troubleshooting

Step 1) Make sure the Micros server is turned on.

Step 2) Make sure the database is running. Open the Micros Control Panel "Start -> Programs -> Micros Applications -> Micros Control Panel". Select Restaurant and make sure that the system is set to "Front Of House".

Step 3) If the system is set to Front of House next thing to check is if the workstations are showing as green arrows in the control panel. If all the workstations are Red arrows then the problem is with the network communication between the server and the workstations.
If you dont see any workstations green or red then select View -> Show All Clients.
You should now be able to see whether they are Green or Red.

Step 4) Check the free diskspace on the database drive. If the drive has no space the system wont work.

Step 5) If all of the above is ok then your next step is to check the status of the MICROS MDS HTTP SERVICE.
Open services list by typing Services.msc into the run prompt. Scroll down to the Micros mds http service and make sure its started. After it is started reload the database via the control panel. This service is required for communication between the workstations and the database.

Step 6) If all above has failed then restarting the server couldnt hurt.

Step 7) Further investigation into the logs would be needed.

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.