Can't access Manager Procedures on POS after server update 2

[SvenRizzo]

I've recently started working a management position at a restaurant running a Micros RES 3700D POS system. They recently updated their server from Windows XP to Windows 10 due to a hardware failure and now we are unable to run many of our Manager Screen functions, most importantly Manager Procedures, from the POS terminals.

If you start RES on the server and log in using a manager card number, everything works fine. Clicking the Procedures button properly launches Manager Procedures. When doing this from the POS you receive one of two errors:

General SQL error. (SAP)(ODBC Driver)Connection error: NO IP address found for MICROS1 Alias: Micros​

or

BDE(Open):Unable to authenticate database user​

Our tech supply company doesn't have any techs trained in this system anymore and have been unable to fix the problem. If someone could point me in the right direction to fixing this it would be extremely helpful. We are unable to assign new ID Cards for out managers.

 

[Wildbar]

Was the Micros software re-installed on the server? What version of 3700? Were the workstations re-CAl'ed?

 

[SvenRizzo]

I can only assume they had a fresh install on the server and then migrated the database over. They also had to do some reprogramming for us to (finally) get CC chip readers.

It should be version 5.7 MR5.

Not sure what you mean by reCAL'd. All the workstations are new Series 6 (not sure of exact model). They were installed at the same time as new server.

 

[Wildbar]

For starters the server computer name and IP are the same as the original server was?

 

[SvenRizzo]

Looking at the control panel it would appear that the server name is M-3905, which to the best of my knowledge is different than on the old server. I believe it was Micros or Micros1 (probably where the General SQL error comes from?). I have no idea if the IP changed or not.

 

[Wildbar]

Go into POSCONFIG, DEVICES, NETWORK NODE and locate your server. Its probably number 99 or 100. See what the Computer Name is and the IP.

 

[SvenRizzo]

Server is M-3905 (Number 99) and address is 192.168.137.250.

 

[Wildbar]

What is the servers current IP and is it static?

 

[SvenRizzo]

Server IP is 192.168.137.250 and is static.

Are you thinking the UWS is just pointing to the wrong location? When using the RES from the servers desktop everything works fine, only when you're on a remote UWS does is throw errors.

 

[Wildbar]

Micros 3700 is pretty finicky about computer names and IP's. Does not like changes. If its changed some things may work, some might not work, and some can work but slower. It looks like you have a reference in the database somewhere to the old computer name. Typically you want to match the server name and IP to whats in the database (or what it was on the server your replacing) You can change your server name when not open (going through the correct steps) but that may break something else. No idea how your computer is currently setup. You can look through the Hosts file on the server and see if the old server name and ip is referenced there. Or you can do a full wipe of a workstation and re-CAL it and see what happens. There is an update hosts file in POSCONFIG, DEVICES, NETWORK before doing this.

 

[SvenRizzo]

I've learned very quickly that Micros is quite a powerful program but it seems to have a bit of a learning curve due to its being designed to be adaptable to just about any situation.

You've narrowed my search quite a bit by getting me pointed in the right direction. Hopefully this will be resolved soon. Thank you

 

[SvenRizzo]

To follow up: Basically went through every reference I could find in every file and re-entered the info. Re-CAL'ed the workstations and everything seems to be working fine now.