nav-left cat-right
cat-right

Microsoft Dynamics GP Error- Unable to open customizations dictionary

Error Message:

While importing the modified reports or forms using the Customization Maintenance window, you get the following error message

“Unable to open customizations dictionary”

This error message is displayed when there are users logged in GP using the shared Reports or Forms dictionary. This error can also occur in case of local Reports or Forms on a terminal server.

Solution:

Option 1: The simplest solution in this case can be getting all users out of GP and importing the package file. However, this may not always be as simple as it sounds. Or you not want to wait for users to log out.

Option 2 : Doug Pitcher has posted  about using the import option the report writer  to import the package

Unable to open customizations dictionary

However, this technique is only applicable for reports dictionaries. You cannot import Package file containing the modified forms using this method.

Option 3: You can import package in a copy of the modified dictionary and replace the shared modified dictionary with the copy.

1.       Create copy of the Reports or Forms dictionary into which you want to import package and paste it another folder. Let us say dictionary’s shared location is \\server\form.dic and we pasted the dictionary on the desktop.

2.       Change the path of the dictionary file in the using the Edit Launch File window (Microsoft Dynamics GP>> Tools >> System>> Edit launch File)   to point to the copy of the dictionary created in step 1 (Desktop in our example). You can also update the dynamics.set to make this change

3.       Restart GP

4.       Open Customization Maintenance Window  (Tools>>Customize>>Customization Maintenance) and import the package file. This will import the package in the copied dictionary on the desktop in our case

5.       Now, copy the dictionary file from the desktop and paste it over the shared dictionary. You will get window dialog message about do you want to overwrite the file. Choose option to overwrite the shared dictionary with the copy you created in step 1. In our example, you will need to copy the dictionary file from desktop and paste it to location \\server\ and it will replace the file \\server\form.dic

6.       Change the dictionary path back to the shared dictionary using the Edit Launch File window or Dynamics.set file. In our example, change it back to \\server\form.dic

7.       Restart GP

While you are at it – also check out the following articles by David Musgrave on how you can avoid this error completely

Automating Distribution of Customizations Part 1

Automating Distribution of Customizations Part 2

Other References: Here are links to some knowledge base articles related to this error

Error message when you try to import a package file by using the Customization Maintenance window in Microsoft Dynamics GP 9.0: “Unable to open customizations dictionary”  Article ID: 919440

https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?WTNTZSMNWUKNTMMYYUSKWOTVUNVLMRYSTNSVUXSLPPXWYMTZOTSLRQRWYOPOKNLL&wa=wsignin1.0

Error message when you try to import a customized report in Microsoft Dynamics GP: “Unable to open customizations dictionary” Article ID: 869323

https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?WTNTZSMNWUKNTMMYVTQUUXNNZOUKYPPPKXVTVUWSOXPLOMPWZRXOKKVTLPWVZRYX&wa=wsignin1.0

Error message when you try to import a customized report in Microsoft Dynamics GP: “Unable to open customizations dictionary” Article ID: 869323

https://mbs2.microsoft.com/Knowledgebase/KBDisplay.aspx?WTNTZSMNWUKNTMMYVTQUUXNNZOUKYPPPKXVTVUWSOXPLOMPWORVZOVYQKWNXSUMY

 

One Response to “Microsoft Dynamics GP Error- Unable to open customizations dictionary”

  1. [...] Microsoft Dynamics GP Error- Unable to open customizations dictionary | Dynamics GP Help – (Rubal) – digs into all the possible options to resolve this issue. [...]

  2. Doug Pitcher says:

    I was browsing around and saw my name in lights. Thanks for the reference.

    I usually import into a seperate reports.dic then from that reports.dic import it into the live reports file. This works when you don’t want to kick everyone out of the system to bring in mods.

Leave a Reply