Version Mismatch on Terminal Services server to SQL server

Epicor ERP 10
1

We have our Epicor application sitting on it’s own SQL server. In addition we have a terminal services server for our handheld shipping devices to connect through. We had upgraded E10 to E10.1 and have done some patch upgrades as well (I think currently at 10.1.400.19). How are these updates pushed to the terminal server?

When we try to log into Epicor on the terminal services server - we get a version mismatch error between client (10.1.400.8) and server (10.1.400.19). I don’t recall ever having to do anything to it before.

2

Right-click on your Epicor shortcut on your terminal server and select properties. On the target line, you do see a -skip or /skip? If so, remove that, apply your changes, and try to launch your shortcut again. Does an autoupdate trigger?

Pasted image374×531 12 KB

3

The -skip is not there . That’s why I don’t understand why it’s not updating…

4

In your terminal server open the sysconfig file and change the version number to 0.0.0.0 then launch Epicor, this should trigger a Re-Update of the Client. If like @aidacra says you don’t have /skip on your shortcut.

Pasted image864×225 8.77 KB

5

I changed there to 0.0.0.0 but got same result…I noticed there is another spot further down…does this need to be changed as well?

6

When you changed it to 0.0.0.0 and ran the client it didn’t do an update?

7

It did not - came up with same error…but further down in the config sys file there is a section that has the following:

Would this need to be changed as well?

8

The screen shot didn’t come through…

10

Screenshot didn’t make it through, but you could try this:

  1. On your RDS server, right-click on your Epicor shortcut and select Open File Location.
  2. Open your Config Folder.
  3. Open the appserver .sysconfig file in a text editor.
  4. Search for deploymentserver.
    Pasted image905×150 9.95 KB
  5. Close the .sysconfig file.
  6. In another Windows Explorer, navigate to the [deploymentserver]\client\config.
  7. Copy the .sysconfig file with the same name as step 3 and overwrite the one in the RDS server’s client folder
    Pasted image802×415 58.6 KB
  8. Open the newly copied .sysconfig file that is on your RDS server with a text editor.
  9. Search for customization name and remove the reference to the latest patch.

BEFORE:

Pasted image1054×88 3.11 KB

AFTER:

10. Save your changes.
11. Launch your client shortcut on the RDS server and hopefully the autoupdate triggers successfully.

1 Like
11

If that latest recommendation doesn’t work, I would recommend calling into Epicor Support and we’ll be able to get to the bottom of this in short order.

2 Likes
12

I think this may have been the problem…I copied the entire folder from a working client to the TermSrvr folder.

Then when connecting handhelds - after configuring and saving to a renamed config.sys (ie E10TEST-HH01.sysconfig) - copied this sysconifg to the appserver deployment config folder…(it didn’t need to be an exact copy but did need one with the same name it appears.