Trouble with Lahnam Eship on NAV 2017

  • Trouble with Lahnam Eship on NAV 2017

    Posted by DSC Communities on November 1, 2019 at 4:08 pm
    • Aaron Fowler

      Member

      November 1, 2019 at 4:08 PM

      I am working on getting our company upgraded to NAV 2017. The current issue that I am having is getting the UPS Link installed for Lahnam Eship. I have worked through the UPS Link Troubleshooting guide and still get errors when trying to print a UPS label. Attached are some of the errors I am getting. Any help is greatly appreciated. Thanks.

      ——————————
      Aaron Fowler
      Information Technology
      CK Power
      St. Louis MO
      ——————————

    • Kevin Fons

      Member

      November 4, 2019 at 8:13 AM

      It looks like you have not installed the external components on the server and client machine and not run the SE install toolbox to setup e-ship UPS.
      The object update is only part of the Lanham upgrade.
      Your partner can get you the installation instructions and files from Lanham if you do not have them.

      ——————————
      Kevin Fons
      Senior Application Consultant
      Innovia Consulting
      waunakee WI
      ——————————
      ——————————————-

    • Wayne Fox

      Member

      November 4, 2019 at 1:11 PM

      I agree with Kevin.Ā  In my experience, the UPSLink external components have to be installed on each PC/client and server that will be used to process UPS manifests, UPSLink mail and add additional workstations.Ā  That’s more than mentioned in the troubleshooting guide.Ā  it’s also a requirement that all users must have full control of the programs and folders outlined there.Ā  You’ll need to get the external components fully installed in order to address the other errors.Ā  The UPSLink routing code error will take care of itself once the components are installed and setup and UPSLink mail is processed.Ā  it’s best that you contact your partner to help get you through that process.

      ——————————
      Wayne Fox
      Senior Consultant
      Team Technology
      greensboro
      ——————————
      ——————————————-

    • Aaron Fowler

      Member

      November 6, 2019 at 9:07 AM

      Wayne,

      Thanks for the advice. I do appreciate it.

      ——————————
      Aaron Fowler
      Information Technology
      CK Power
      St. Louis MO
      ——————————
      ——————————————-

    • Aaron Fowler

      Member

      November 6, 2019 at 9:07 AM

      Kevin,

      Thanks for the advice. I do appreciate it.

      ——————————
      Aaron Fowler
      Information Technology
      CK Power
      St. Louis MO
      ——————————
      ——————————————-

    • Laura Gumbel

      Member

      November 5, 2019 at 9:12 AM

      ?The first issue in your attachment is exactly what it says. Your URC rates are out of date. If you process the UPS Email, the rates should automatically update as part of the process. If you don’t have the rate file, you will need to contact your partner and get the rate file from them and then upload the rates using the xmlport. For the other errors, are you running the 32 bit or 64 bit version of NAV when you run Pack Line scan? We get those errors when we run the 64 bit version. For EShip, you need to run the 32 bit version.

      ——————————
      Laura Gumbel
      Developer
      Group O
      Milan IL
      ——————————
      ——————————————-

    • Aaron Fowler

      Member

      November 6, 2019 at 9:09 AM

      Laura,

      Thanks for the advice. I do appreciate it. I did notice the other day how to switch to 32 bit version. This solved part of my problem but I am still getting an automation server error. Thanks again for your help.

      ——————————
      Aaron Fowler
      Information Technology
      CK Power
      St. Louis MO
      ——————————
      ——————————————-

    • Justin Falconer

      Member

      November 5, 2019 at 9:41 AM

      Sounds like either you are running the 64bit NAV Client or the UPS Link Components are not installed correctly.Ā  LanHam Add-ons only work with the 32bit NAV client.
      You also need to make sure that the system does not have UPS Worldship installed.Ā  If it has then it needs to be uninstalled and registry keys manually cleaned up for UPS Link to work correctly.
      Did you set the correct permissions on Files and Registry Keys for UPS Link?

      Do you have the latest UPSLink Components?Ā  There was an update not too long ago due to UPS switching security requirements.

      ——————————
      Justin Falconer
      IT Manager
      Tender Corporation
      Littleton NH
      ——————————
      ——————————————-

    • Aaron Fowler

      Member

      November 6, 2019 at 9:11 AM

      Justin,

      Thanks for the advice. I do appreciate it. I did notice the other day how to switch to 32 bit version. This solved part of my problem but I am still getting an automation server error. I going to reach out to my partner and see if I can get the update UPS components. I really appreciate the response. Thanks again.

      ——————————
      Aaron Fowler
      Information Technology
      CK Power
      St. Louis MO
      ——————————
      ——————————————-

    DSC Communities replied 5 years, 10 months ago 1 Member · 0 Replies
  • 0 Replies

Sorry, there were no replies found.

The discussion ‘Trouble with Lahnam Eship on NAV 2017’ is closed to new replies.

Start of Discussion
0 of 0 replies June 2018
Now

Welcome to our new site!

Here you will find a wealth of information created for peopleĀ  that are on a mission to redefine business models with cloud techinologies, AI, automation, low code / no code applications, data, security & more to compete in the Acceleration Economy!