Hello,
Over the summer we migrated file servers which affected the shared paths used in our 2018 R2 packages and installed dex.ini and dynamics.set files. We ran a PS script to change the paths in the dex.ini and dynamics.set files and all users were able to keep running without issue. Now when we go to apply an update or change installed modules on existing installations, it appears that cached install files are still referencing the old file paths and it breaks the installation. The only work around I've found is complete uninstall and reinstall with the new packages and correct paths. Any ideas on what cached files we should be looking for to change without reinstalling all clients? trying to roll out the year end update.
Thanks if advance.
Cecil,
When you migrated the file servers, I am assuming you just copied over the GP file folders and all.
I would just try to run the GP installers from the Installation disc (once) and just install the default components; Dexterity Shared Components, Visual C++, etc on the destination machine and that should update the paths. In most cases anyway, these components are needed when running minor modules like Integration Manager, etc.
Hope this helps. SHould you have additional questions, I suggest you send us a case so we can dig in further. Please see (+) Important changes coming to technical support workflow and how you create a support case - Microsoft Dynamics GP Community
Happy to help.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
André Arnaud de Cal... 290,524 Super User 2024 Season 2
Martin Dráb 228,493 Most Valuable Professional
nmaenpaa 101,148