Micros Station not connected to network

Micros Station not connected to network

Issue#1: Term# not connecting to the network and showing inactive.
Issue#2: Can't see the node in file utilities to connect via VNC.

Steps taken to troubleshoot...

  1) Check network cables. If cables are secure it helps sometimes to disconnect and then re-connect to ensure the are seated properly. 
  2) Go to Managers Procedures> WorkStation> Select Term# (That needs to be reconnected) >set inactive, then re-activate. 
       (If no change then next...)
  3) reboot WS. 
       (With MICROS systems some changes take some time. Give about 5 minutes after system is totally back up and are able to log in; then if no change go to next...)
  4) power cycle POS switch. Sometimes this will fix issue completely, and others it will allow the device to be seen on network but still not active on Micros network.
       (i.e. in Managers Procedures>Workstations there are 2 Active/Inactive indicators for each Terminal. One is for the LAN connectivity and the other is with the MICROS system. Also under 
        File utilities>Node selection can now see missing Node#, and in Manager Procedures> WorkStations terminal shows "Network is Active", but  no change in the Terminal connection to the MICROS.)
  5) Check VNC to see if you can login to station having the issue. 
       (If no change then next...) 
  6) Go to "File Utilities" on the top right there is a drop down box for accessing the nodes in the system. Select the node you are needing to access>CF file
       (sometimes it is under a different folder)>and executed the CEVncSvr.exe file.
  7) If when trying to go to Node# you get error, "Can't obtain listing from [node3,MICROSe7].Errorcode:'FRC_COMM_ERROR'
       (Go to next...)
  8) Go to the terminal>login> Manager Procedures>set station Inactive> then back to Active.
       (If no change then next...)
  9) reboot Terminal again
10) Go back to MP, WS, select Term#>set inactive> set it back Active.
      (At this point Station should at least be Active on both settings in MP and also seen as such on other stations.)
11) If when the trouble station finally gets to complete active on LAN and MICROS, but shows all other stations as in active inactive... Go to each station in MP, select the station you are
       remoted into and set as Inactive and then back on again.
       (You should see in the original trouble station the other stations going active as this is completed for each one.)
12) check that all stations have the same open and closed checks. If there is a discrepancy need to 
13) From the station that was causing the issue go to MP>WS>select a Terminal that was not an issue and has the correct Check listing> Select the retrieve or update checks function. 
    • Related Articles

    • Station Freezes when employee clocks out

      ISSUE: Station freezes after employee clock out 1) Go to Setup in Focus and check the Job unique number. Then test if there is an issue with that job # i.e. 10020 by creating another user with the same job #. do a check out and see if issue repeats. ...
    • Switching Location ISP- Focus

      1- It may help to have site contact to send pics so that you can verify connections and clarify steps for the switch over to new device. 2- If available having contact label the cables with a sharpie often helps particularly where multiple cables ...
    • MICROS error "USER LOCKED - CALL CSR"

      1) error when running cc "User Locked- Call CSR" 2) multipass system may need to be reset. Before calling for reset attempt the following... 3) Get access and login to online web portal [https://merchantcenter.transit-pass.com]. 4) Create new ...
    • CAP station lost connection with Server

      Issue: CAP POS throwing "cannot connect to the server" error. Solution: 1) Open task manager and close software. 2) open CMD and run ping command to server. If good ping signal return time. 3) Check if reconnecting the shared drive will restore. ...
    • Internet down. Meraki not taking over network. For SpotOn systems

      ISSUE: site lost network connection and Meraki failover is not taking over to provide service. Troubleshooting: #1 Solution- remove network feed from port one. If site modem is still sending enough signal to the Meraki even if it creates a system ...