This is a reposting of an article Patrick Roth originally wrote on my Developing for Dynamics GP blog.
This summer I was contacted by one of my associates in our LATAM office.
He noted that their office was running into more and more cases as described below.
Dynamics GP freezes during 2-3 minutes just after the login window appears (you cannot even enter the password). This only happens when the Terminal server does not have access to the internet.
So far the only work-around we have consists in downloading the following files:
And manually registering them:
certutil -addstore CA CSC3-2004.crl
certutil -addstore CA pca3.crl
certutil -addstore CA CodeSignPCA2.crl
certutil -addstore CA CSPCA.crl
But in some cases the issue reappears after some time.
I ran this by one of my favorite SEE’s (Support Escalation Engineer), Kelly, and she confirmed that they’ve run into this issue on the system team. Basically the solution to that point was try the above solution and if it wasn’t working for them then either live with it or give the machine access to the internet.
I thought about it and this reminded me of Dave Dusek’s case and blog post about an addin performance issue he ran across. But in this case the solution being offered seemed to be essentially the same.
I considered running a Process Monitor trace to confirm this was the specific issue or something new. But before I suggested doing this, I seemed to recall reading about this at another time.
After my brain failed to pinpoint the specific memory, I did an internet search and came up with the blog post I was thinking of. In it, it detailed the same issue as we were seeing and the solution.
According to the blog post (which references a Microsoft KB as well) if you have one of the .NET 2.0 updates (anything past RTM I believe), you can use the method described in that KB to resolve this issue.
Config File Lines
<?xml version=”1.0″ encoding=”utf-8″?><br />
<generatePublisherEvidence enabled=”false”/><br />
Now because this is Dynamics.exe, that means we’d have to add these lines to the Dynamics.exe.config file and it already has the configuration section. We just need to add the runtime section and the generatePublisherEvidence item.
A modified version of a vanilla Dynamics.exe.config file is attached to this post as a text file to show the addition.
When we made the change to the Dynamics.exe.config file, Dynamics GP no longer had the slow down issue that it had previously experienced thus resolving the issue.
Hope this tip helps.
Dynamics GP Developer Support
This article was originally posted on the Developing for Dynamics GP Blog and has been reposted on http://www.winthropdc.com/blog.