Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

RES 3700 WS6 Unable to connect to the Server

Status
Not open for further replies.

mvelazquez

Technical User
Mar 14, 2015
118
MX
I have been working with several stores with RES 3700 V5.5 without this type of problems and 2 new units that I decided to install in V5.7 it constantly happens to me that the UWS loses apparent connectivity with the server indicating this:

mstsc_DAG6Bf8Wap_jaixze.jpg


The UWS is inside the network, it is a WS6 610. If I ping the server I can see it and vice versa. The DB ports are open. I have turned off Firewalls. I checked both RES 3700 MDSHOSTs files and Windows HOSTS files, I have checked the 3700.log and increased the Verbosity and it does not indicate anything that gives me an idea of ​​the problem.

It is so strange that once I could not solve it and I left it like that all afternoon, the next day when I returned it was already working normal. On another occasion with a server restart it was solved.

In more extreme cases and tried to reinstall the CAL but when trying I always get this:

mstsc_OoX7OYbKVy_rdxblu.jpg


So I have to choose to reset the factory equipment, reconfigure Windows and reinstall the CAL and the first times it did work for me but in other times I end up in the same place as at the beginning.

Sometimes it happens in UWS 1, then 3, then 4 so I think it is not a problem with the UWS but the server.


This only happens to me with this version 5.7

I have asked ORACLE support but their answers are very long and not concrete.
 
I failed to indicate that according to me it is not an issue of the Client Trust Utility since I am active in the DM Activate Discovery Mode.
 
I was left with the question of the CTU, and I executed it individually from the BIN folder, to see if it would let me update it manually but I get this:

ApplicationFrameHost_caaeENE18I_bqlwdn.jpg


and after a while this other:

mstsc_OpLsFMR5Kc_arcxqa.jpg


So I already wondered if it is the CTU, someone knows how to force the UWS to ask me for the key and enter it manually?
 
Version 5.7.x.x ???? because there are some changes in 5.7.6.0

Installing the Patch
This patch can only be installed on RES 5.7.x
The Activation of the Discovery Mode will activate the PORT on the Server to run the CAL.
It will be "HARD" stopped and blocked after the minutes expire. It does not check if a CAL on the Workstation is still running.



Instructions:

1. Copy the patch to a temp folder on your RES Server.

2. Close ALL running MICROS applications, except MICROS Control Panel.

3. In the MICROS Control Panel, set the Restaurant to OFF.

4. Close the MICROS Control Panel

5. Double-click the patch file in the temp folder to execute the patch.

6. The RES Server will reboot, and then CAL will update and reboot all clients.

7. Once the workstations are at “Wait for MDSHosts File”, put the server in Discovery Mode:

a. A privileged user can log in to Database Manager| Encryption Keys |Activate Discovery Mode

b. Command line option: dm.exe –UID x –PWD y –DS z
x = userid, y = password, z = duration of Discovery Mode, in minutes, up to 60, 0 means turn it off

8. All clients will perform a one-time registration with the server, and then proceed past “Wait for MDSHosts File”.

9. Once all clients have registered with the server, an additional reboot of all clients is needed to ensure that each client has up-to-date trust information for all other clients (this is needed for printing and other peer-to-peer communication).

This patch creates a log file located here: .\Windows\MicrosHotfixPatch.log

This patch creates the following registry entry:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\MICROS\NovaFix\RES_57_MR6
Within this key, a value named ‘Installed Date’ is created. The data for this value will be the date the patch was installed.

After upgrading to RES 5.7.6:

1. RDC devices running CE 5.0 will no longer respond to a remote reboot request

2. When adding a new/replacement client, steps 7 & 9 must be repeated

3. If you need to replace your RES Server, you will need to:

a. At each Windows (Win32) client, delete the folder: .\MICROS\common\Cert

b. At all other clients (except RDC CE 5.0): delete the folder: .\MICROS\Cert

c. Repeat steps 6-9 from above
 
Thanks for your answer POSKitchen, I had not seen your answer, for some reason the system did not notify me.

The version is 5.7 MR6, in fact I just saw in another post that you mentioned 5.7.7, I didn't know it was already available, I'm going to try updating a version of that.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top