Reports Dictionary Mismatch

(0) Share

Report

Posted on by JChen

Hi. I have a freshly installed DynGP '2010 SP1 (same as the server). Default install works fine, and I can access the company data. But when I configure my dynamics.set to point to the server's shared Reports.dic dictionary, I get a version mismatch, and can't login...

I am confused. Shouldn't this be the other way around, where my local dictionary is out-of-sync, and by pointing to the shared dictionary should work OK? Thanks.

*This post is locked for comments

I have the same question (0)

All responses (5)

Answers (0)

Richard Wheeler 75,848 Moderator on at

Like (0)

Report

I would try exporting the reports on the server out to a fresh package file, rename the dictionary on the server and import the package file back in form the workstation.

Are you sure the GP on the server is the same as the workstation. 11.00.xxxx? You see that by clicking the ? and then About MS Dynamics GP.

Was this reply helpful? Yes No
JChen 70 on at

Like (0)

Report

Hi Richard

Thanks for the suggestion; I'll try this. As for the version, I can't swear to it, but I am pretty confident that they are the same.

Was this reply helpful? Yes No
Jonathan Fear on at

Like (0)

Report

Try copying the Dynamics.dic from the working machine. There could be a synch issue with the Dynamics.dic file that is on the problem machine.

Thanks,

Jonathan Fear

Was this reply helpful? Yes No
Aaron Donat on at

Like (0)

Report

Hi There, if you are getting a reports.dic mismatch error, that message indicates that the reports.dic from the Dynamics GP client you just installed IS NOT the same version that you have deployed out on your share. With that said, you need to be careful here as the deployed reports.dic sounds like it needs to be updated?? Also...is the new Dynamics GP client that you jsut installed connecting to the production SQL Server as the rest of your GP clients?

Either way, I would recommend the following:

1. Make sure the deployed versions of the Dynamics GP client match. This is confirmed by pointing to this new client to the new SQL Server and launch DynUtils. If DynUtils wants detects an oldier version STOP and exit from DynUtils as you will be upgrading your databases.

2. If there is no issue with the deployed versions, you may need to try and upgrade the reports.dic or simply synchronize it. Once you get this far and you still hve issue, you need to open a support case or talk to your partner.

Aaron

Was this reply helpful? Yes No
L Vail 65,271 on at

Like (0)

Report

To find the dictionary version you can also hover over the .dic file with your mouse and it will pop up the version and build number.

Was this reply helpful? Yes No