I got it working. Within the run folder was a registry key for a backup software that is on the computer. That gave me the idea that maybe that was causing the issue. I uninstalled the backup software and the update went through fine.
I got it working. Within the run folder was a registry key for a backup software that is on the computer. That gave me the idea that maybe that was causing the issue. I uninstalled the backup software and the update went through fine.
Hi,Nick Sutkay
Thank you for your reply, I'm glad to hear that your issue has been resolved, it's great to see that you are a passionate researcher.
Also, if it's convenient for you, please feel free to rate my service, feel free to click yes or no, it will help the rest of the community to quickly locate the relevant threads for some advice and inspiration. Thank you for your understanding and cooperation!
Best regards
Bobhe | Microsoft Community Support Specialist
WorldShip 2023 Database Exception Error - How to Fix
** FIXED ** UPS WORLDSHIP ON WIN-10 1809 or 1903 DOES NOT WORK : UPSICC ERROR
UPS Worldship...
Worldship issues.
Posting this for the next poor soul who has to get UPS WorldShip 2023 working in an Administrative/Remote workstation configuration. I would comment here, but the post has been archived...
After installing WorldShip on the remote workstation, it would throw a Database Exception error stating it could not communicate with the Administrative workstation (server). However, we were confident our firewalls were not blocking this.
After several phone calls, and the final phone call taking 1 hr 11 mins, I figure I should post this information somewhere. We went through all of the basic troubleshooting (ping, tracert, DNS, Windows firewall, etc.) but none of it worked. I haven't been able to find everything below elsewhere online.
-
On the Administrative workstation, open SQL Server 2019 Configuration Manager
-
Go to SQL Server Network Configuration > Protocols for UPSWS2019SERVER
-
Right click on "Named Pipes" and choose "Enable" (was disabled for us)
-
Right click on "TCP/IP" and choose "Properties"
-
Go to "IP Addresses" then find "IPAll"
-
Remove the value for "TCP Dynamic Ports"
-
Set the "TCP Port" value to 1434
-
Go to Task Manager > Services
-
Restart MSSQL$UPSWS2019SERVER
-
Edit wstdShipmain.ini (in Notepad, stored in C:\<shareddir>\UPS\WSTD)
-
Under [LANConfiguration] set "DatabaseServerPort" to 1434
-
You may also need to set these:
-
DoNotOverwriteDBName from N to Y
-
DatabaseServerName to use an IP address instead of hostname depending on your environment (leave the \UPSWS2019SERVER at end)
-
Re-run WorldShip on the Remote workstation
Administrative workstation OS: Windows Server 2019
Remote workstation OS: Windows 11
WorldShip version: 26.0.30.0
It sounds very similar to what I had to do a few months ago with 1809. This time I reach out to the UPS level 2/3 contact I was working with last time and asked her about what I had read and she confirmed that MS is working with UPS on this and she assured me she would get back to me when they find a fix. Last time I gave them (UPS level 3 several VMs to work on for about 3 weeks), the eventual fix they came up with didn't work so I ended up redoing the installs on about 10 machines in 3 different locations. Being that they never actually came up with a solution last time, I can tell you if it acts the same it had something to do with permissions as when we ran-as admin they used to work but this time I understand the MS installer actually blocks you from installing if it detects UPS Worldship?
Do we know why?