Welcome to my Micros Point of sale Help Blog

Welcome to my Micros Point of sale Help Blog

Use the search feature on the left to find what your looking for.

Below are 5 most visited blog posts for March 2011:

Remember drop me an email if you have a question that i have not covered.
**If you find my information has helped you and saved you an expensive call to Micros support please feel free to use the donate button in the top left, Thanks **

E7 - Micros E7 POS Password ID recovery.


Have you lost, forgotten or never had your managers access password ID? Don't worry it can be recovered.

Unfortunately its very difficult compared to Micros 3700 and 9700 and unless you know how to decode binary files using a hex editor im not going to get into it.

If you wish to recover your access I will perform this for a nominal fee of €30 (around 42USD).

For this price you will receive full administrative access to your micros POS system.

If for whatever reason there is no administrative user account in your system ie someone deleted it and then downgraded their own access rights. (Ive seen it done!) I can create an administrative user for you. This will be charged at €100 (around 140USD) because its significantly more work.

I do not need access to your system to perform these tasks but i will need a single file from your database which has the encoded password ID's. Please contact me via email for further information regarding this service. micros.pos.info@gmail.com.


RES 3700 - Cannot delete menu items from Pos Configurator

When you try and delete some menu items from the Pos Configurator menu item list you get the following error:

Key violation.
[Sybase][ODBC Driver][Adaptive Server Anywhere]Integrity constraint violation: Primary key for row in table 'mi_def' is referenced by foreign key 'CFK2MI_DTL'
General SQL error.
in table mi_dtl.

First thing is not to be worried. This is normal behavior.

The reason you are getting this error is because micros keeps records of sales compared to menu items. So basically you cannot delete menu items which have been sold until those historical totals are purged.
See the Pos Configurator -> Reporting -> Historical Totals. This will show you how long each report hold data before they are purged.

If you don't want to use this menu item anymore you have a few options.
1) Reuse the menu item. Just rename it and edit all the options for a new item.
2) Clear all options including the name so its a blank menu item.
3) Renumber the menu item so that it remains in your system but is just out of the way. See the below pictures as an example. Most people don't have millions of menu items in their database so usually the 9000000 number range is blank.
When you double click on the number beside the menu item you can change the number. Change it to something in the 9000000 range or whatever you want and put it in that part of the list.


E7 - Managing and configuring your employees privileges.

E7's employee privilege management is messy but here is how its done.
First you need to enter the Configuration and select Jobs (1).

2 This is the where you can add a new job or a new job category. Select the down arrow and choose the appropriate option.
3  A job category is nothing more than a label. It has no effect on anything.
4  A job is very important. It defines all of the jobs privileges and access rights. See below image.

To make things easily managed i suggest you create a "Job Category" for your different types of staff. Eg Managers, Employees, Temporary staff etc.

Within the "Job Category" you should have the breakdown of each employee class where you plan on making their configuration slightly different. EG. Duty Manager has the rights to perform voids but a Bartender does not.

Each of the "Jobs" ie Bartender has 6 tabs containing different options and access rights. Configure them so they are appropriate for the Job type.

Once completed from the Drop down list at 1 select "Employees".

2 You can add a new "Employee Category" or "Employee".
3 "Employee Category" is nothing more than a label. I suggest you create the same categories as you created for "Jobs". It just makes for easier management of your staff.
4 "Employee" is important. Its a unique identification for each employee you have. You can define their name, address, login id's etc. 
When you create a new employee on the "Job Information" tab you need to select the "Default Job" which you previously created. This links the privileges created to that particular employee. See below Image.

And your done.


RES 3700 - Incorrect server name in MDSHOSTS.XML


If you are seeing this error message in your 3700d.log then either someone has changed the name of your servers hostname or someone changed the name of the server in the pos configurator.

Micros RES relies on the server name remaining unchanged.

Step 1) Find out what your server name should be.
To do this open Services.msc. You will have a service called "sqlSERVERNAME" where servername is the name that your server should be.

Step 2) Next check what your servers name actually is. Open a command prompt and type in "hostname". This will return to you your servers name.

If the servers name is incorrect then change the name back to what you found in step 1. Right click on My Computer -> Properties -> Computer Name tab and click change.


Do you need to change your server name?

There are some reasons why you need to change your servers name whether it be changing your companys name and your server name reflects the old one, moving your server onto a domain etc.

Micros supplies a handy little tool which does all the work for you. This tool is compatible with RES 4.9 and below. Click here to download it.
Email me if the download link stops working.


Within the ZIP file you have the following files:
- setname.exe
- setname.cfg
- mfc70.dll
- msvci70.dll
- msvcr70.dll

Copy all 5 files to D:\Micros\Res\Pos\Etc

Note: This tool changes your computer name as well as any necessary registry settings.

Before starting turn your database off from the Micros Control panel.

Run setname.exe and you will be shown the same as the below image.

Enter your new server name in the text box provided and press OK. You will be informed when the program has completed. It shouldn't take too long.

Restart the server.

Once the server is restarted open the Pos Configurator -> Devices -> Network nodes.

Select your server from the list and change the computer name to your new name.
Press the green tick to save.
Reload the database from the Micros Control Panel.

And your done!.



LES 9700 - Installing Winstation or SAR OPS on Desktop PC Win32 environment.

This guide is for people who want to install Micros LES 9700 Winstation or SAR OPS on a Windows based PC.

These are instructions on how to install the workstation but not how to configure the workstation in the EMC. I might create instructions on this at a later stage.

NOTE: From this point on i will refer to the computer you want to install micros on as a workstation.

Step 1) On your workstation map a network drive to your micros server. To do this press Start -> Run and type "\\SERVERNAME" where SERVERNAME is the IP address or Hostname of the micros server.

You may be prompted to enter a username and password.

Either way you will be brought to a share drive where you should have a folder called "MicrosClient" or "ClientInstalls".

If you wish to install a Winstation client proceed to step 2. If you wish to install a SAR client proceed to step 3.

Step 2) Double click on the Winstation.exe. The installation will begin. Keep pressing Next until you come to a screen to choose Administrator or Workstation mode. Choose Administrator mode. As the name suggests you must be loggin in as an administrator.

Keep pressing next and finally Finish and then the installation will begin.
Once finished you will need to reboot the workstation.

After reboot you will have a Winstation.exe on you desktop where you will be able to launch the client from.

Step 3) Open the SarClient folder and double click on the setup.exe. When the installer asks you to enter your Primary server name enter the IP address of the micros server. Enter the workstation name and complete the install.

After reboot you will have a SAROPS.exe on the desktop of your workstation.

RES/LES/SIM/E7 - How to configure a WindowsCE based workstation using CAL. WS4/WS4lx/WS5/WS5a

All Micros POS workstations come preloaded with the Micros CAL software.
The CAL instructions are the same regardless of what version of POS you are running whether it be RES 3700, LES 9700, Simphony or E7.

Step 1) This is not a necessary step but i recommend it anyway. We want to wipe any traces of previous installations off the workstation. Skip this step if you have information and files on the workstation you want to retain.

On all WS4, WS4LX, WS5 and WS5a workstations there are two drives called CF and DOC. To access these open the "My Device" or "My Computer" folder which is on the Desktop of your workstation.

The DOC is a storage space on the workstation which is not on the Compact Flash card.
In the DOC drive you will have a folder called Utilities and inside this folder there is an executable called WCF.exe. This executable is basically used to reset the workstation back to factory settings.

Once launched you will be given three options:
- Clear Registry Settings
- Erase Compact Flash
- Format Compact Flash

All options are self explanatory. One note however Format Compact Flash automatically performs option 1&2 as well as formatting the flash.
I recommend selecting option 1&2. Once any of the options are selected you will be asked to confirm and then the workstation shuts down. You will need to press the power button to turn it back on.
When the workstation turns back on it will automatically start searching for your micros server.

 Step 2) If you have performed step 1 skip this step.

Press the Windows Start button -> Programs -> CAL -> Reconfigure CAL.

When you select this you will see a program popup which a blue progression bar. This program is searching for your micros server. See below image.
Step 3) Once the search is complete you will be displayed a list of your available Micros Servers.
See below image.

You will likely be returned only one server but im using a test system which has lots of servers as you can see.
In the "Available Servers" section you will have two columns. Server Name and Pos Type. I have greyed out my server names. From this list select your server and you will see the Server Name, Server IP and Pos Type fields will be automatically populated.

You also have an option called "CAL Enabled". Make sure this box is ticked.

If no server is found make sure your network cable is securely plugged in and that the micros server is running.

Step 4) Select Next. You will be displayed a list of available workstations. See below Image.

I have cleared the fields in the above image.

In the "Available Workstation List" you should have all of your workstations listed.
Select the workstation you wish to configure. When you select the workstation name all of the information fields will automatically populate. Once done select SAVE and the installation will begin.

The workstation will likely reboot multiple times during the install but will eventually complete.

NOTE: If you reach this step and the workstation list is blank you have two options:
1) Go to your micros server and find the workstation detail and enter them manually. Will will likely have to connect a USB keyboard to do this.
2) Save anyway and it will install the software without linking it to any particular workstation. Go to the micros server and restart the "Micros CAL Service" from services.msc and repeat steps 2 and 3.
3) You did not select "CAL Enabled" resulting in no workstations displayed in which case see option 2.

And your done.

If you wish to learn how to install LES 9700 Winstation or SAR Client on a Desktop PC click here.
If you wish to learn how to install RES on a Desktop PC click here.

RES 3700 - How to clear system financial totals from the database.

So for whatever reason you want to clear all of the financial totals from the database. Here is how its done.

Open the Micros Control Panel and bring the system to database level.

Open the Micros Pos Configurator -> Totals -> Clear All Totals or you can clear each set of totals individually.

Depending on how many totals you have in the database this can take a few seconds to about 15 minutes.

After it is successfull you will get a popup advising you of this.You will be unable to use the pos configurator untill this has been completed.

After completion you will need to reboot the micros database.

RES 3700 - How to configure an Autosequence.


An autosequence is basically some group of tasks that can be set to run automatically or manually. They are similar to a macro.

Login to the Pos Configurator -> Reporting

Select Autosequences. Scroll down to the bottom and press the blue + button to create a new Autosequence and enter a name.

Here you can set the autosequence to run as part of a schedule. From the drop down list select a schedule or press the yellow folder symbol to create a new schedule.
If you want the Autosequence to appear on the run screen of "Autosequences and Reports" make sure the "Hide on run screen" is not selected.

Save and now select "Autosequence Steps" from the Pos Configurator. From the drop down list select the autosequence you created.

Press the blue + to create a new step and double click on the Type field to select what sort of step you want to create.

From here on its fairly self explanatory.

Call Autosequence - Calls a previously created autosequence.
Report - Allows you to print a report as part of the autosequence (you can also print to a file from here)
Stored Procedure - Allows you to call stored procedures eg Set Business Date.
External Program - Allows you call an external program configured in the Pos Configurator -> System -> External Programs.

RES 3700 - Recover Micros login ID from database

Due to the nature of the restaurant business there is generally a large amount of staff turnover. This can sometimes lead to senior level access to the Micros POS system being lost of just not passed from one person to another.

Thankfully its easy to get back through some SQL commands.

NOTE: If you are uncomfortable with performing any of these tasks contact someone who will be able to follow these instructions or I may be able to perform these tasks remotely for a fee. See my email address at the top of this page if you need to contact me.

Classic Security:

For this we need access to DBISQL. If you don't know what this is read my quick overview of it here.

After logging in run the following statement:
Select first_name, last_name, pc_appl_id, id, effective_to from micros.emp_def

This will return to you all of the employees in the database with their login information. Select the appropriate information for the previous person with full system access.

PC_APPL_ID = Login ID for the micros applications on the server eg Pos Configurator
ID = Login ID for the till system. Usually their employee card number.
EFFECTIVE_TO = If the employee was setup to expire at a particular date then this is the date. If it is before today then you will not be able to login using this ID.

Enhanced Security:

If you have enhanced security which requires a username and password to login to the micros applications follow the below steps.

First you will need to perform the above steps for Classic Security and get a valid PC_APPL_ID.

Next you want to disable the Enhanced Security so that you can login using just the PC_APPL_ID number.

Execute the following update in DBISQL to disable the enhanced security.

update micros.rest_def set ob_classic_security = 'T'

Now open the Pos Configurator and it will allow you to login with just the pc_appl_id number.
As soon as you login execute the following statement to re-enable the enhanced security.

update micros.rest_def set ob_classic_security = 'F'
Now open the employee list and you can now set yourself a new Username and Password.

Hope this helps you out.

Erasing contents of a Micros WS4, WS4LX, WS5(a)

Sometimes you want to wipe the contents of a workstation for whatever reason. These instructions are identical regardless of workstation and POS type. This is how its done:

On all WS4, WS4LX, WS5 and WS5a workstations there are two drives called CF and DOC.

The DOC is a storage space on the workstation which is not on the Compact Flash card.
In the DOC drive you will have a folder called Utilities and inside this folder there is an executable called WCF.exe. This executable is basically used to reset the workstation back to factory settings.

Once launched you will be given three options:
- Clear Registry Settings
- Erase Compact Flash
- Format Compact Flash

All options are self explanatory. One note however Format Compact Flash automatically performs option 1&2. Once any of the options are selected the workstation shuts down. You will need to press the power button to turn it back on. Once it turns back on you will be requested to install micros again using CAL.

RES 3700 - Log files for Micros RES 3700

3700d.log - Located in D:\Micros\Res\Pos\Etc

The 3700d.log contains the general day to day logs of the micros pos system.

The logs are rotated every day as part of the end of day or whenever the executable "rotatelog.exe" is executed.
Each rotation appends a number to the end of the file name eg. 3700d.log.0
A maximum of 7 days logs is kept at any one time.

The verbosity level of the log file defines how much detail is logged. By default it is at level 0.
To change the verbosity open the micros control panel via the run prompt "cpanel.exe /verbosity" and in the control panel you will have a new verbosity tab where you can set the logging level. See the below screenshot.

If you select your Server name and select the verbosity tab you will see a list of modules where you can increase the verbosity level using the slider along the bottom for a particular module.

This becomes very useful if you notice a problem with a certain part of micros and to help diagnose this you increase the verbosity.

NOTE: If the verbosity level is left too high the log files can become very large very fast.

DM.log Located in D:\Micros\Common\Etc

This log contains information from the usage of the Database Manager. ie. backups, backup validation etc.

CLCONTROL_SERVERNAME.log Located in D:\Micros\Res\Pos\Etc

This log contains the logs when the CLCONTROL command line database control program us used.

RES 3700 - Remote reboot of workstations in Micros RES 3700 POS command line

As you may have already noticed in RES 4.x they introduced a reboot feature in the Micros Control Panel which lets you reboot an individual workstation or all of the workstations at once.

What you probably didn't know was that this functionality has always been available since the first Micros 3700 Pos system. It is a command line program called REMOTEREBOOT.exe and is located in D:\Micros\Common\Bin

If you type REMOTEREBOOT /? into the command prompt you get the below user information but simply if you type "remotereboot WS01"  it reboots the workstation called WS01. Simple and useful.

MICROS RES RemoteReboot version 4.1
usage:  RemoteReboot [/?] [-h] [/allclients] [<nodenames>]+

   /? or -h prints this help message.

   /allclients reboots all configured clients. Will not reboot the server.

   Specifying one or more computer nodenames on the command line will cause
      a message to be sent to reboot only those client workstations

RES 3700 - Command line database control for Micros RES 3700 POS.

A little known fact is that Micros RES 3700 POS comes with a nifty little command line tool which lets you replicate the functionality of the Micros Control Panel.

The tool is called CLCONTROL and is located in D:\Micros\Res\Pos\Bin

open the command prompt and type CLCONTROL /? and it will display the below help on how to use it.
It is fairly straight forward and if you don't understand it then you should'nt be using it.

There is also a log file for the tool kept in D:\Micros\Res\Pos\Etc called CLCONTROL_SERVERNAME.log

0000000 02/26/2011 16:15:43 Sat Feb 26 16:15:43 2011
  CLControl /SYSTEM FOH    ( Front Of House )
  CLControl /SYSTEM BOH    ( Back  Of House )
  CLControl /SYSTEM DB     ( Database )
  CLControl /SYSTEM IDLE   ( System Shutdown )
  CLControl /SYSTEM STATUS ( System Status )
          Possible System Status Return Code
          0    ( FAULT )
          1    ( IDLE  )
          2    ( DB    )
          3    ( BOH   )
          4    ( FOH   )
          5    ( BUSY  )

  CLControl /NODE <NNN> /PROCESS <PPP> ON     ( Start  process <PPP> on node <NN
N> )
  CLControl /NODE <NNN> /PROCESS <PPP> OFF    ( Stop   process <PPP> on node <NN
N> )
  CLControl /NODE <NNN> /PROCESS <PPP> RELOAD ( Reload process <PPP> on node <NN
N> )
  CLControl /NODE <NNN> /PROCESS <PPP> STATUS ( STATUS of process <PPP> on node
<NNN> )
          Possible Process Status Return Code
          0    ( FAULT     )
          1    ( OFF       )
          2    ( ON        )
          3    ( RELOADING )
          4    ( BUSY      )

  CLControl /M <text>                        ( Insert <text> in 3700d log file )

  CLControl /CLEAR                           ( Clear the 3700d log file )
  CLControl /LIST <path> NODES               ( List nodes in file <path> )
  CLControl /LIST <path> /NODE <NNN> PROCESS ( List node <NNN> processes in <pat
h> )

  Note that the /SYSTEM commands can have SYNC appended to indicate
       that the request should be issued to all nodes at once.

RES 3700 - Understanding DBISQL for Micros POS.

DBISQL is a program which is used to query the Micros 3700 POS database.
It can be launched on the micros server by typing DBISQL into the run prompt and pressing OK. See below screenshots.

Micros POS installs usually have then following passwords by default. You may also have been given a DBA password by your micros installer.

Username: custom
Password: custom


Username: installer
Password: installer

You may also need to select the ODBC data source name which will be called "Micros" but 99% of the time you wont need to do this. See the image above.


An example of what you expect to be able to see after logging in is shown in the image below.

An example what what an actual query in dbisql looks like is shown in the image below. This query returns the data for all checks in the database.

To search how select, update, inserts and everything to do with SQL works I suggest you google some tutorials so you can get the most out of your micros database.


All information on this web site is correct to the best of my knowledge at the time of writing.
I will not be held responsible for any damage caused through information on this website.