If you have updated nShift Ship On-premises Server and experience problems with the update of nShift Ship On-premises client, it can be caused by several things. We have made a list of the most common problems and solutions to try:
User rights
Updating nShift Ship On-premises client requires local administrator rights.
- Right-click on the icon and choose Run as Administrator.
- Contact your system administrator if a username and password are required or if the client is on a terminal or Citrix server.
- If the Client is not able to update or start after an update of the server, try to run the update manually by running the program file called UpdateClient.exe located in \Program Files\Consignor Client\. Remember to have administrator rights when running this file.
Overwriting client files
On the On-premises server:
- Locate and open the file Server.ini placed in C:\Program Files(x86)\
- Find the line LiveUpdateRoot=C:\Consignor\Consignor\LiveUpdate
- Go to the LiveUpdate folder.
- Create a folder on a drive that all clients have access to.
- Copy the content of the Client and Common folders from LiveUpdate to the new folder.
On the On-premises client:
- Right-click on the client icon and choose Properties > Open File Location.
- Copy and overwrite everything from the folder created in step 4 above to the Client folder. This ensures that the version matches.
- Start the On-premises client.
Issues with the hosts file
If the nShift Ship On-premises server cannot be pinged by name from the client.
Note, that it may be necessary on some networks to define the IP address together with the nShift Ship On-premises server name.
- Find and open the hosts file in C:\Windows\System32\drivers\etc
- Enter the IP address and name of the nShift Ship On-premises Server.
- Save the changes and restart your computer.
We also recommend reading this article if you have problems with the server-client connection: Opening Windows Firewall for client connections to server
Please contact nShift Customer Service if your problem persists.