Micros 3700 KDS screens down, I'm at a loss

[sarajayne]

Hey friends,

At my work (restaurant) we use Micros 3700 (the exact version I am unsure of--it's 5.x something). Anyway, we upgraded our main computer/server in October, and shortly thereafter two of our KDS screens have been down ever since. All of the workstations are fine (although a bit buggy, I had to do a work around in the touchscreen designer to link them up weirdly--but they do work).

The cooks have been complaining about the two screens being down and we thought that maybe if we connected them to a working rdc via usb it may solve the problem. It didn't.

Next, I tried update the .dtr files by transferring them via usb (I had a previous thread that asked for that file). The error screens disappeared, but CAL was unable to detect any servers.

My next step was to try to connect them to server manually by putting in the addresses from the main server from this tutorial

http://micros-pos.blogspot.com/2011/03/reslessime7-how-to-configure-windowsce.html.

Last night when I opened MICROS Control Panel, all of the network nodes were set to READY except for the two screens that were down, and I couldn't figure out how to connect them to the server. I rebooted the server, hoping that the updated files would work--in addition to rebooting all RDCs and KDS screens.

Everything was working last night, and then I came to find out this afternoon that now all four KDS screens (hot, cold, broil, and expo) were all down--even though they were working when I left. One had been down since open, and the main screen went down in the afternoon out of nowhere.

Any ideas? I'm at a loss. And now that Micros has been taken over by Oracle they are a huge pain in the butt to get a work order fulfilled in a timely manner (we used have a local Micros office, located in Pittsburgh--but now you have to go pretty much exclusively through email, getting a live person is like find a unicorn.)

Any suggestions--or even someone who knows a place where I can get POS tech support for a reasonable rate would be appreciated, even over the phone or remote access. I'm located in the greater Pittsburgh area. I'm considered the resident computer wizard, but I don't want to mess things up further.

 

[Wildbar]

What errors do you get?
Is your kds controller service running on the server? Are you getting errors on the server?
Ensure your kds services are setup to start automatically.
Have you looked at the hosts file?
Are you using a firewall or antivirus?

 

[sarajayne]

Hey thanks for the reply!

- I got the screens that worked previously up and running again (I have a feeling that someone was messing with the default settings, so I changed them back and all is well.)

- My HOTKDS and EXPOKDS screens are still down, before I updated with the .dtr file I was getting a \FS2 error and CAL wouldn't run.
Now CAL will startup (although not automatically on the screens that are down) but it does not detect any servers. I will check KDS services on the main computer and see what comes up.

- I have been afraid to mess with the MDSHosts file, worried that it will mess up everything.

- No firewall/antivirus--strictly forbidden because it messes with the server. I'm confident that that's not the issue because the other screens are working again.

edit-- Apologies--was unable to find a KDS services program on the main computer. I will look into how to check the MDSHosts file.

Some errors I wrote down last night (running on WinCE):

'This application (KDSDisplay.exe) requires a newer version of the Microsoft®.NET Compact Framework than the version installed on this device'

Programs -> CE Client -> connection status -> running - disconnected (I can't figure out why it's disconnected)

'Exception in Log constructor. Can't find PInvoke.DLL'

'Can't find MDSSysUtilsProxy.dll'

edit2--I "deleted" the MDSHosts file (I just moved/saved it to a flash drive just in case) because I have read on here that a new file will be automatically created. However, when I restarted Micros Control Panel, everything was the same but none of the screens were working. So I restored the original MDSHosts file, rebooted everything, and it works again.

Here is my MDSHosts file:

<!-- MDS Utility Configuration File -->

<!-- Generated Wed Oct 19 10:16:17 2016 on RES Server RESSERVER -->

<!-- CRUMMDS.dll Version 5.4.0100.2276 - Built Sep 10 2014 21:16:57-->

<!-- This file will be overwritten when changes are made -->

　

　

<NODES>

　

<NODE>

<MachineName>RESSERVER</MachineName>

<IPAddress>192.168.100.250</IPAddress>

<NetMask>255.255.255.0</NetMask>

<LanNodeSeq>2</LanNodeSeq>

<LanNodeObjNum>99</LanNodeObjNum>

<WorkstationType>P</WorkstationType>

<UwsSeq>24</UwsSeq>

<MBSeq>NULL</MBSeq>

<KDSSeq>NULL</KDSSeq>

<OCBSeq>NULL</OCBSeq>

<KPISeq>NULL</KPISeq>

<IsServer>T</IsServer>

<IsBackupServer>F</IsBackupServer>

<IsKDSServer>T</IsKDSServer>

</NODE>

　

<NODE>

<MachineName>BroilerKDS</MachineName>

<IPAddress>192.168.100.13</IPAddress>

<NetMask>255.255.255.0</NetMask>

<LanNodeSeq>12</LanNodeSeq>

<LanNodeObjNum>13</LanNodeObjNum>

<WorkstationType>D</WorkstationType>

<UwsSeq>NULL</UwsSeq>

<MBSeq>NULL</MBSeq>

<KDSSeq>106</KDSSeq>

<OCBSeq>NULL</OCBSeq>

<KPISeq>NULL</KPISeq>

<IsServer>F</IsServer>

<IsBackupServer>F</IsBackupServer>

<IsKDSServer>F</IsKDSServer>

</NODE>

　

<NODE>

<MachineName>ColdKDS</MachineName>

<IPAddress>192.168.100.11</IPAddress>

<NetMask>255.255.255.0</NetMask>

<LanNodeSeq>10</LanNodeSeq>

<LanNodeObjNum>11</LanNodeObjNum>

<WorkstationType>D</WorkstationType>

<UwsSeq>NULL</UwsSeq>

<MBSeq>NULL</MBSeq>

<KDSSeq>107</KDSSeq>

<OCBSeq>NULL</OCBSeq>

<KPISeq>NULL</KPISeq>

<IsServer>F</IsServer>

<IsBackupServer>F</IsBackupServer>

<IsKDSServer>F</IsKDSServer>

</NODE>

　

<NODE>

<MachineName>ExpoKDS</MachineName>

<IPAddress>192.168.100.12</IPAddress>

<NetMask>255.255.255.0</NetMask>

<LanNodeSeq>11</LanNodeSeq>

<LanNodeObjNum>12</LanNodeObjNum>

<WorkstationType>D</WorkstationType>

<UwsSeq>NULL</UwsSeq>

<MBSeq>NULL</MBSeq>

<KDSSeq>108</KDSSeq>

<OCBSeq>NULL</OCBSeq>

<KPISeq>NULL</KPISeq>

<IsServer>F</IsServer>

<IsBackupServer>F</IsBackupServer>

<IsKDSServer>F</IsKDSServer>

</NODE>

　

<NODE>

<MachineName>HOTKDS</MachineName>

<IPAddress>192.168.100.10</IPAddress>

<NetMask>255.255.255.0</NetMask>

<LanNodeSeq>9</LanNodeSeq>

<LanNodeObjNum>10</LanNodeObjNum>

<WorkstationType>D</WorkstationType>

<UwsSeq>NULL</UwsSeq>

<MBSeq>NULL</MBSeq>

<KDSSeq>105</KDSSeq>

<OCBSeq>NULL</OCBSeq>

<KPISeq>NULL</KPISeq>

<IsServer>F</IsServer>

<IsBackupServer>F</IsBackupServer>

<IsKDSServer>F</IsKDSServer>

</NODE>

　

<NODE>

<MachineName>PCWS01</MachineName>

<IPAddress>192.168.100.1</IPAddress>

<NetMask>255.255.255.0</NetMask>

<LanNodeSeq>4</LanNodeSeq>

<LanNodeObjNum>1</LanNodeObjNum>

<WorkstationType>4</WorkstationType>

<UwsSeq>26</UwsSeq>

<MBSeq>NULL</MBSeq>

<KDSSeq>NULL</KDSSeq>

<OCBSeq>NULL</OCBSeq>

<KPISeq>NULL</KPISeq>

<IsServer>F</IsServer>

<IsBackupServer>F</IsBackupServer>

<IsKDSServer>F</IsKDSServer>

</NODE>

　

<NODE>

<MachineName>PCWS02</MachineName>

<IPAddress>192.168.100.2</IPAddress>

<NetMask>255.255.255.0</NetMask>

<LanNodeSeq>5</LanNodeSeq>

<LanNodeObjNum>2</LanNodeObjNum>

<WorkstationType>4</WorkstationType>

<UwsSeq>27</UwsSeq>

<MBSeq>NULL</MBSeq>

<KDSSeq>NULL</KDSSeq>

<OCBSeq>NULL</OCBSeq>

<KPISeq>NULL</KPISeq>

<IsServer>F</IsServer>

<IsBackupServer>F</IsBackupServer>

<IsKDSServer>F</IsKDSServer>

</NODE>

　

<NODE>

<MachineName>PCWS03</MachineName>

<IPAddress>192.168.100.3</IPAddress>

<NetMask>255.255.255.0</NetMask>

<LanNodeSeq>6</LanNodeSeq>

<LanNodeObjNum>3</LanNodeObjNum>

<WorkstationType>4</WorkstationType>

<UwsSeq>28</UwsSeq>

<MBSeq>NULL</MBSeq>

<KDSSeq>NULL</KDSSeq>

<OCBSeq>NULL</OCBSeq>

<KPISeq>NULL</KPISeq>

<IsServer>F</IsServer>

<IsBackupServer>F</IsBackupServer>

<IsKDSServer>F</IsKDSServer>

</NODE>

　

<NODE>

<MachineName>PCWS04</MachineName>

<IPAddress>192.168.100.4</IPAddress>

<NetMask>255.255.255.0</NetMask>

<LanNodeSeq>7</LanNodeSeq>

<LanNodeObjNum>4</LanNodeObjNum>

<WorkstationType>4</WorkstationType>

<UwsSeq>29</UwsSeq>

<MBSeq>NULL</MBSeq>

<KDSSeq>NULL</KDSSeq>

<OCBSeq>NULL</OCBSeq>

<KPISeq>NULL</KPISeq>

<IsServer>F</IsServer>

<IsBackupServer>F</IsBackupServer>

<IsKDSServer>F</IsKDSServer>

</NODE>

　

<NODE>

<MachineName>PCWS05</MachineName>

<IPAddress>192.168.100.5</IPAddress>

<NetMask>255.255.255.0</NetMask>

<LanNodeSeq>8</LanNodeSeq>

<LanNodeObjNum>5</LanNodeObjNum>

<WorkstationType>4</WorkstationType>

<UwsSeq>30</UwsSeq>

<MBSeq>NULL</MBSeq>

<KDSSeq>NULL</KDSSeq>

<OCBSeq>NULL</OCBSeq>

<KPISeq>NULL</KPISeq>

<IsServer>F</IsServer>

<IsBackupServer>F</IsBackupServer>

<IsKDSServer>F</IsKDSServer>

</NODE>

　

</NODES>

 

[Wildbar]

You need the correct version of Microsoft®.NET Compact Framework on the KDS. Sounds like maybe the operating system was reinstalled? Or somehow the wrong version got put on.
Search these threads for a link to the correct net framework download. Good chance that will clear up all your issues. (See what version of Net Framework is on the screens that work and install on those that dont

 

[sarajayne]

You're my hero.

The main server is running Windows 10, and the KDS runs on Windows CE--so I'm guessing that I'll need to find the correct version of Microsoft.NET Compact Framework for Windows CE? Perhaps it's possible I can copy it from one the working KDS RDCs?

The OS was reinstalled--our previous server was ridiculously old and ran on WinXP; it died a slow death. When we upgraded, Oracle reinstalled the OS and copied everything via remote access.

It makes total sense. If the net framework is not compatible, how can it possibly find the server? Hopefully I can get it connected.

I will check the threads here though and see what comes up. Fingers crossed, and many thanks.

 

[Wildbar]

Just an FYI you dont want to do anything with the server. Its just the KDS clients you need to update the net framework. I have never used the RDC's so not sure how its done. We use Win 32.

 

[sarajayne]

Good to know, I was actually going to go straight to the RDCs that are down and install it via USB. I couldn't find anything on the forum that wasn't dead links, but I found this on the microsoft site

https://www.microsoft.com/en-us/download/details.aspx?id=65,

seems to be the newest version (even though it's like 10 years old).

Even if it doesn't work, I can't thank you enough for all of your help. Tech support through Micros/Oracle is pretty useless--not to mention expensive. My boss doesn't want to pay a ton of money for something after he just spent thousands on upgrading the server--and he has a point. My employees have adjusted and call the tickets, but the point of having screens is to make everything easier and making their lives easier is part of my job. Sorry to go off on a tangent, just wanted to say you have my gratitude.

 

[jimmymcp02]

You will need to upgrade the .net framework version for the RDC or it will not work correctly. use the update utility on the RDC it looks like an army Swiss knife and upload either one of these files depending on the RDC model you have. Then you should be able to re-run cal.

 

[jimmymcp02]

And here is the other file if that one doesnt work. Also there is a setting on the RDC box that for some reason gets re-enabled after upgrading to 5.4 is on the RDC box to enable power savings when idle which will put the RDC to sleep or the monitor will turn off.