Dynamics GP 2013 password resets take long to complete

(1) Share

Report

Posted on by Community Member

We've noticed that user password resets in Dynamics GP 2013 are taking up to 15 minutes to process. Has anyone encountered this and successfully resolved it?

We are running GP 2013 on SQL 2012 R2 in a Citrix plus Terminal Server environment. The issue comes up in both Citrix and RDP connection. All servers are Hyper-V VMs

Thanks

Ken

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (1)

Suggested answer

babubaskaran@outloo... 12 on at

Like (0)

Report

Hi Ken,

Have you tried to reset the password using SA for the user who is having this problem and tell them to login and try to reset the password again on user preference and see whether its still take 15 min to process.

Was this reply helpful? Yes No
Suggested answer

soma 24,410 on at

Like (0)

Report

We have many machine with GP 2013 and Citrix and RDP connected. But, we couldn't face this issue yet now.

I think, this may occurs due to poor network connection to the SQL server. Please check with GP server directly (without citrix/RDP) and check whether this happens again).

What about the other transaction level posting process speed?

Hope this helps!!!

Was this reply helpful? Yes No
Verified answer

soma 24,410 on at

Like (0)

Report

Also please have a look on the below link as well.

support.microsoft.com/.../898982

community.dynamics.com/.../optimizing-and-maintaining-performance-for-microsoft-dynamics-gp.aspx

Hope this helps!!!

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

KenThiongo, Alternatively I would suggest you to use logging mechanisms like Sql server profiler or dexsql.log to get more information about this.

Was this reply helpful? Yes No
Justin Thorp 2,265 on at

Like (0)

Report

Hi,

I recommend first trying to identify where the performance is slow.

1.) Sitting at (or RDP'd directly onto) the SQL server, open SSMS and change the password of a user here (Security - Logins). Note how long this takes and let us know. If it takes a long time, I suggest capturing a network trace from the SQL server and having it analyzed, otherwise proceed to step 2.

2.) Does the problem happen from a non-citrix machine (for example just a standard windows 7 VM)?

3.) Capture a network trace from the slow workstation/Citrix and the SQL server at the same time, and have it analyzed.

Thanks,
Justin

Was this reply helpful? Yes No