web
You’re offline. This is a read only version of the page.
close
Skip to main content

Notifications

Announcements

No record found.

Community site session details

Community site session details

Session Id :
Microsoft Dynamics GP (Archived)

This is not a Microsoft Dexterity Dictionary

(0) ShareShare
ReportReport
Posted on by

Hi all,

One of my users just upgraded her PC to Windows 7 64bit. After installing GP, we are unable to launch it. We get the error "This is not a Microsoft Dexterity Dictionary". I have already tried reinstalling twice. I have also tried copying the GP2010 folder from a working PC to this one. I get the same error message.

Any help would be greatly appreciated.

Thanks in advance.

Regards,

Saras

*This post is locked for comments

I have the same question (0)
  • Suggested answer
    Community Member Profile Picture
    on at

    Hi Saras,

    Did the same error appears in all the work station after upgrading PC?

    Please make sure that the paths to the dictionary files in the Dynamics.set file on the local computer are correct.

    Are you placing any un-matched versions of dynamics.dic?

    If another computer is working correctly, copy the Dynamics.dic file from the working computer to the computer that is experiencing the error message.

    Also make sure you have proper permissions in GP installation folder

  • sueconrod Profile Picture
    337 on at

    Although you setup a 64 bit session of Great Plain, Great Plains runs on a 32-bit DSN.  If you go in and manually set that up you will probably be able to launch Great Plains.

    Creating the ODBC: (32-bit)

    C:\Windows\SysWow64\odbcad32.exe

    Double click “Data Sources ODBC”

    Create: GP201313

    Once this screen pops up, click the System DSN tab. Then click Add.

    Select SQL  Server Native Client  11.0 and click finish.

    Go to add from the System DSN

  • Jonathan Fear Profile Picture
    on at

    First we want to remember that copying code in the old days was okay because we didn't write too much to the registry, but now a days you cannot do that.

    I am guessing that you have a antivirus software on this machine and you haven't setup exclusions for the GP code folder and any shared location you may be storing notex, Reports/Forms.dic file, ETC.

  • Verified answer
    Community Member Profile Picture
    on at

    Hi Nataraj,

    We found that the shared Reports.DIC was corrupted. The Dynamics.set was referring to this dictionary. I could not import the modified reports from the corrupted dic. Luckily I had an old backup of the reports.dic which I used to replace. Then we were able to launch GP.

    Regards,

    Saras

  • Community Member Profile Picture
    on at

    Thank you, that worked exactly for me as well.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Responsible AI policies

As AI tools become more common, we’re introducing a Responsible AI Use…

Neeraj Kumar – Community Spotlight

We are honored to recognize Neeraj Kumar as our Community Spotlight honoree for…

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
mtabor Profile Picture

mtabor 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans