Dynamics GP Web Client Failure

(0) Share

Report

Posted on by IceMan

1,115

We ran into an interesting problem with one of our larger GP Web Client implementations today. The client has about 250 users running the GP 2015 web client. At about 11am we started to get reports that new users could not access GP through the web client but existing GP web client users were unaffected. As part of the troubleshooting process we found that when you logged into the GP Web client, AD authentication completed successfully, company selection and initial screen load all completed without a problem but when it got to the point where it populates the Home Page or body of the GP interface it hung. The Home Page section would stay grey, and the GP client would hang and not allow the user to click on any of the navigation links within the GP interface on the left.

Additional testing of the GP thick client was successful and did not experience the same problems.

Ultimately we found a deadlocking in the database with the following stored procedure:

DYNAMICS.dbo.zDP_ADH00100SS_1;1

Anyone have any idea why this happened? Basically any new GP Web Client sessions where getting blocked by the above request.

*This post is locked for comments

All responses (3)

Answers (0)

Derek Albaugh on at

Like (0)

Report

RE: Dynamics GP Web Client Failure

Sounds good, thanks for the update.
IceMan 1,115 on at

Like (0)

Report

RE: Dynamics GP Web Client Failure

We haven't seen the problem since and it has only been the one time. At this point I will chalk it off to some anomaly. Since the user base is so large we can't control how many people might be attempting to log into the web client at one time. Fingers crossed we don't see it again but if so we will open a ticket. Thanks
Derek Albaugh on at

Like (0)

Report

RE: Dynamics GP Web Client Failure

Hello,

I can't say we've seen this type of issue with Web Client occur, nor could I find anything in our case history regarding this zDP_ADH00100SS_1 procedure and Web Client.

Dynamics GP is designed to avoid deadlocks, so its interesting that you're seeing deadlocking on the zDP_ADH00100SS_1 procedure when new users attempt to login to Web Client.

The only question I can think of, is when this error occurs, are multiple users trying to access Web Client and login at the same time, or does it happen even if it is only one new user logging into Web Client without any others?

If you're still experiencing this issue, I'd recommend creating a support case so we can actually look at it with you and try to determine why its doing what its doing.

Thanks,