Hi all,
We've got a GP Dynamics 2018 server setup, and clients access it from a Remote Desktop Web Access (RemoteApp) farm, rather than us installing the GP client on all their machines.
This has been working fine for years (back to GP2010).
Our Remoteapp farm was just 2 hosts, plus a gateway/connection broker. With the increased load of people using Remoteapp due to working at home during Covid19, we decided to expand our farm to 3 session hosts.
We're running on vSphere 6.7.
I cloned one of the two hosts, did the customization/sysprep, and added it into the RemoteDesktop server group.
This new server is working fine, other than a couple glitches with GP.
1-At first, when users tried to Launch GP, they got an error about an invalid SET file. We have the commandline to start GP like c:\progfiles\microsoft dynamics\gp2018\dynamics.exe c:\progfiles\microsoft dynamics\gp2018\mysetfile.set
I ran process monitor on an existing session host, and the new one. On the existing ones, I see GP trying to open up that SET file at the path specified. On the new one, it tries to open that file at a DFS path rather than from the specified C: path. That dfs path is listed in that SET file to point to some dictionary files, but nothing should be telling GP to look for the SET file there.
The really weird thing, is on the affected session host, if I launch file explorer, and then paste in the same commandline used from the icon in RemoteApp, GP opens properly, using the c: path.
If I copy the SET file to that DFS path, GP now opens properly, but I don't know why it's even looking there.
2-Probably related, but on the affected server, if I try to open SmartView from within GP, instead of it launching, it opens a small window, that has a launch smartview button, but that button doesn't do anything.
Any thoughts?
Hi Lee,
Glad you found a solution..
By reading thru your OP, I was wondering if that wasn't some sort of permission issues when the user would log into the new farm server (3) and maybe some profiles wouldn't be ready to work yet..
When cloning a system, it might be safer to redo some of the settings, especially when it comes to RDP apps publishing.. you may never know what was carried over from the cloned system settings.
I may have found the fix for this. In the RD App collection, I edited the GP published app, just changed one thing, changed it back, and hit apply.
now it's reading from C: and Smartview works.
I'm guessing maybe that did some sort of registration on the host in question.
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,469 Most Valuable Professional
nmaenpaa 101,148