GP 2015 Web Client posting error

(0) Share

Report

Posted on by Community Member

We seem to get errors when users are logged in as Directory Account and posting transactions or batches. If they log in with SQL account they can post these transactions successfully.

Example error when posting a GL journal transaction:

Audit trail code information is incomplete or missing. A code could not be assigned.

Example error when posting a batch:

The stored procedure glpPostBatch returned the following results:

DBMS 0, Microsoft Dynamics GP: 20062

*This post is locked for comments

I have the same question (0)

All responses (11)

Answers (0)

Community Member on at

Like (0)

Report

We've had exactly the same issue. Active directory accounts don't work, but SQL accounts do.

For now, changed all our users to have SQL accounts until we find a solution.

Was this reply helpful? Yes No
Suggested answer

John Lowther 5,122 on at

Like (0)

Report

The first thing I would do is check the SQL security settings on the account that the web client is using to access the database.

That account probably doesn't have the correct security. Keep in mind that is not the users GP account but the one that is used by the web client itself.

Was this reply helpful? Yes No
Suggested answer

Community Member on at

Like (0)

Report

Exactly. As John mentioned, when web client is installed and configured, you must have created a "Web Client SQL Proxy Account".

Remember that user ID, go to SQL Security logins, spot that user ID, open User Properties, check User Mapping. For each GP database (including DYNAMICS), check if DYNGRP is enabled.

This is mandatory for web client to work without hassles. If by any chance, DYNGRP is not enabled for web client SQL proxy account, enable it on respective databases.

Hope this helps.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Thanks for your replies, but all those things have been checked. It actually turns out that it is a bug with UK install and is currently being looked at by MS.

There is a fix that involves deleting the message table installing a US instance, rebuilding the messages table and uninstalling the US instance.

Was this reply helpful? Yes No
Dan Peltier on at

Like (0)

Report

Correct, this is a known issue we are investigating right now. Currently we've found that this issue comes about if you have a UK code installed Dynamics DB, and a US code installed Company DB. The workaround steps are here:

1. Download the GP install media for the correct version that you're running.

2. Install a US installation of the code, as a separate instance from the UK code install.

3. Delete the MESSAGES table in the DYNAMICS db.

DELETE DYNAMICS..MESSAGES

4. Set Synchronize=TRUE in the US code install, then run the US GP Utilities.

5. Launch the UK Dynamics GP, and log in. You’ll get a message about building messages.

6. Close the UK install, and launch the US install. It will again build the messages.

7. Uninstall the US code instance.

8. As soon as that completes, log into Web Client and post a batch to test.

Dan Peltier

Systems Support Engineer

Microsoft

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi,

I have just installed GP 2015 Web client R2 and this issue seems to have been corrected. Do you know if the fix was released with this version?

Thanks,

Paul

Was this reply helpful? Yes No
Dan Peltier on at

Like (0)

Report

It has not been officially fixed in the recent release. It may have inadvertently been resolved by the code, but it is still being investigated. I will update this thread when I know more!

Dan

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi,

I've encountered the same issue using Web Client v14.00.0661 and had logged a call with the Microsoft Support Team to get an update...

The Problem Report for this issue is #86584. It looks like Development is currently in the testing phase of the process so not yet scheduled for release. The workaround is as previously posted.

Regards,

James

Was this reply helpful? Yes No
ImtiazCif on at

Like (0)

Report

HI Phill,

in your last post you mentioned that you'd update this post. Has there been any movement on this. We are facing a similar problem as described. However GP2015 R2 does not seem to resolve it.

any ideas?

Regards

Imtiaz

Was this reply helpful? Yes No
Dan Peltier on at

Like (0)

Report

Hi Imtiaz,

The workaround I've detailed above has resolved all cases we've seen opened for this issue. You may need to replace the UK installation with whatever other language installation you're using, but the steps will be the same. The error is occurring because you're missing a code, and you have to build both localization's codes using the method I detailed above.

Was this reply helpful? Yes No