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:http://csc3-2004-crl.verisign.com/CSC3-2004.crlhttp://crl.verisign.com/pca3.crlhttp://crl.microsoft.com/pki/crl/products/CodeSignPCA2.crlhttp://crl.microsoft.com/pki/crl/products/CSPCA.crl
And manually registering them:certutil -addstore CA CSC3-2004.crlcertutil -addstore CA pca3.crlcertutil -addstore CA CodeSignPCA2.crlcertutil -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"?>
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.
Best Regards,Patrick RothDynamics GP Developer Support
This is awesome! I have ran into this issue at a couple clients and could not explain what it was either. I will try this out immediately!
Mariano Gomez, MVP
This also affects the execution speed of the GP addins. We had a customer who had all of of their user accounts proxied to an old, non functioning proxy. Our test accounts didn't have the same proxy, so whenever we ran the code, it was super-fast...when they ran the .NET addin - 10 times slower performance.
Thanks for the fix, Patrick!
Posting from Mark Polino at DynamicAccounting.net
Thank you,thank you a million times.
I just resolved this issue on site based on this article.I have logged a call on Partnersource and the guys are still troubleshooting.
The client was getting weary.
I have observed from last 3-4 month Great Plains works very slow. When we launch on Dynamics.exe it takes almost 5 min to come up log in screen.
All modifiled reports and form DIC file on same server. Infact on same location.
I have tried to debug the issue in many ways like checking dex.ini, keeping eye on sql profiler.
We are running Great Plains 10 (SP4) - 10.00.1301 on SQL 2005 on platform window Server 2003.
If you this some issue please let me share the work around.
Regards and thanks
One issue you might not have looked at is were your users' home folder and profiles are stored. Make sure they are local to the terminal server and not going over a wide area network.
If you need more help, ask on the forums or log a support case.
Excellent Solution. Just tried and now it’s working very fine. Come its only a login screen. and why Microsoft is generating this "Publisher Evidences" ? do they have any logical explanation for this ?
Is our data is secured ? I doubt that.... any ways nice solution.
"Come its only a login screen"
Yes - but it is at this point the application is loading and .NET is initializing.
"and why Microsoft is generating this "Publisher Evidences""
This is automatic by .NET and used for authentication. The application is signed -it is possible that the authentication certificate has been revoked and so .NET tries to connect to the internet to verify this.
In this case, it takes a bit to time out which causes the delay.
"Is our data is secured ? I doubt that.... any ways nice solution."
Your data is secured by SQL - this happens on .NET initialization and wouldn't be a factor.
Glad this resolved your issue.
PLEASE READ BEFORE POSTING
Please only post comments relating to the topic of this page.
If you wish to ask a technical question, please use the links in the links section (scroll down, on right hand side) to ask on the Newsgroups or Forums. If you ask on the Newsgroups or Forums, others in the community can respond and the answers are available for everyone in the future.