Announcements
All,
My clients GP is taking long after the user enters the password until he/she sees home page.This takes like 30 minutes .
Its version 11.00.1524 (GP 2010).
After home page its ok.
Any idea on what I should do?.
RomRyan
*This post is locked for comments
I had a similar issue when we moved to a new citrix farm that was running on Server 2012. The login times were extremely slow and we even noticed some modules appearing greyed out.
I made changes to the servers based on this article and login performance is back to normal.
community.dynamics.com/.../tuning-remote-desktop-services-2012-for-microsoft-dynamics-gp
It is possible that security is coming into play here. I have seen IT Staffs lock down workstations so tightly that the computers are essentially useless. Great for them but not so great for the users. Reaching for straws here I would try uninstalling GP 2010 and removing the program directory. I would them install GP 2010 into its own folder outside of C:\Program Files (x86). If you have a D or E drive so much the better, put GP there.
MB Good day - so I was working on a client migration yesterday and ran into a problem that might be similar to your experience. After install in GP2016 on the client workstation as the DOMAIN Admin user and testing as the same - I experienced no issues. However as soon as I logged off as Admin user and connected to same machine as the Regular User I encountered login issues - I did not time the event but I got many SQL Error messages and then finallay got to the User Login Screen and waited there for 45 to 50 seconds ( not timed ) and then was allowed to enter USER / Password.
When GP tried to connect it continued to toss up a number of Errors and when finally displayed the home screen was missing half the application screens.
While not exactly like your issue - I solved this by making sure that the local user had full Read / Write / Create / Delete permissions on the local client installation folder for GP2016 as well as for the shared folder where the Reports.dic folder was mapped.
Once I did this I was able to connect in about 10 sec - no errors and all applications were available.
Now I know this is not a perfect fit, but I leads me to this thought -
Be sure to check the user access permissions / run gp in Admin mode (as noted by Harry) and be sure that any shares have the permissions passed to the local user, not just to the Admin user when created.
Hope this helps.
This one is a tough one. Let's start by agreeing this is aberrant behavior. GP normally shows the "splash screen" for a second or two, then resolves to the SQL Login screen.
Additionally, this is totally different behavior from the symptoms related to the issue covered in this post, which has to do with what happens once users log into Dynamics GP and SQL tables are accessed.
In my original response to your expanded question on this post, I think I glossed over several things in one breath, which is sometimes my way. So here it is in bullet points.
1. User Account Control must be suppressed on the workstation/user profile (for each user) GP is running on, GP does not support interactions with this tool set.
2. On modern work station Operating Systems (since Vista), it is important to go to the compatibility tab and ensure that GP is always run with elevated permissions (effectively running as Administrator). You should be able to cache the credentials for this, so you don't have to make users administrators.
3. The user account used during installation and when elevating permissions must have machine administrator access. This is a very specific thing, and one cannot assume that all domain administrators are members of the machine administrators groups.
Here is a link to an unanswered post from a user who describes the exact symptoms you report, as well as the cause in his environment. Please review it, and include his methods in your troubleshooting methodology.
community.dynamics.com/.../80843
Finally, be not discouraged. I would strongly suggest compiling a list of fixes/proposed resolutions and looking for holes in the approaches taken. Walk front to back through the list on a new/sanitized machine to make sure that in the process of jumping around during troubleshooting a potential fix hasn't been rolled back or omitted. Often times it is a constellation of errors that result in the behavior we're looking to fix.
I completely agree, it appears to be something endemic to your environment. Do you have any computers that have not been sterilized by your IT staff? I ask because I would be tempted to install GP using SQL Express to see how that behaves on these computers. Then after that connect that computer to your network and change the ODBC connection to look at your server. Now have IT come and do their thing and make note of what they do and after they are done see if the sluggishness returns. I think whatever this is has nothing to do with GP. What kind of hard drives do you have (SSD, 5400, 7200 or better rpms). How able RAM and CPU's?
Reaching for straws here, what happens if you go to the server and login from there. Is that GP client slow as well?
Not trying to be difficult because I appreciate the interest in our issue. I am not following however the fact that if a user cannot log their name and password to the initial screen due to it being frozen how any of these possibilities stemming from the configuration tie in. The user has not yet been associated to the session. I mean I can see how all this applies after the login and password are passed on enter.. but not before.
Pretty much all users in the enterprise, regardless of locale without patterns of better or worse based on roles or perms within GP or defined in SQL.
Does this happen on all computers or just this one? Does it follow only certain users.
Already done that for myself and for admin accounts. Re-tested login. Changed Role from one to others between steps and cleared all cells, closed. Reopened. No change. Still freezes on the user/password screen.
#1
Almas Mahfooz
3
User Group Leader
Share
Report
All responses (
Answers (
