You’re offline. This is a read only version of the page.
Hi,
We're currently moving over to Microsoft Dynamics GP 2010, and it is installed on Windows 2003 Server Standard (x64) w/ SP2
When I start GP, logged in as a user with admin rights, the splash screen stays on for barely a second or two, disappears, and I get the logon screen.
If I do this as a standard user (in our case, they are connecting in via RDP), it sticks for anywhere between 30-90 seconds before eventually showing the login screen.
My first instinct is to check permissions, so I ran Process Explorer to see what was going on and the admin user get's no ACCESS DENIED process messages, whereas the normal user gets plenty, revolving largely around access to registry keys, so I'm presuming these are the issues (screenshow below shows a sample)
Short of putting users in the admin group, I'd like to try and isolate exactly what is going on. Has anybody come across this before? I can't imagine for a second that it's just me
*This post is locked for comments
I would recommend you setup a account to log into CustomerSource. From a techincal support side we do not assist with performance issues as the white paper link goes through a large percentage of the issues.
Hi Jonathan, apologies for the late response.
I am unable to get into that link due to not having a login to hand, but my main query is that when the roaming profile is created for the first time, and I try to open GP, the login screen loads really quickly, around 10 seconds, so do you know if the app itself is putting something in, profile specific, that causes the load time to slow considerably from that point?
I would review the white paper we have on performance as we don't really troubleshoot performance cases in techincal support. Here is a link:
mbs.microsoft.com/.../mdgp2010_whitepaper_performance.htm
Again if GP is only taking 30-90 seconds to load the login screen that is normal.
Hi Jonathan, thanks for the response.
Yes, it appeared that a regular old user took longer to get to it.
However, i've since discovered further....
Firstly, we use roaming profiles, and so I rebooted the server and removed the locally cached copy.
I then renamed the stored roaming profile on the file server, and then logged in as the user again.
Obviously a new profile is then created, at which point the login page loads up as expected in 5-10 seconds or so, give or take.
I then started the process of copying everything over from the old profile to the new one, logging out, back in and so on, up to the point the profile was identical other than the ntuser.dat file from the old profile.
At this stage, it still logs on quickly, so it must be something to do with the ntuser.dat file, which I know stores a load of preferences etc....
Does that help shed any light?
So a normal user can gets to the login screen just takes a minute? This is very common with GP 2010 as there is more calls to the registry. If you want to try to speed this up you need to grant windows permissions to the access denied records showing in the proc mon.
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,240
Super User 2024 Season 2
#2
Martin Dráb
230,149
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (