By Steve Endow
Because I work a lot with Post Master Enterprise, which occasionally requires manual adjustments to the Dynamics GP Dynamics.SET file, I pretty consistently get a question about this error message.
![]()
It is totally understandable when customers ask me what this means. I don't expect them to be familiar with the arcane details of a proprietary configuration file that they normally wouldn't edit.
But I am surprised when a Dynamics GP partner asks me what this error means and how to fix it.
When I started as an employee at a Dynamics GP partner many years ago, the first day that I was introduced to GP, one of the first things the manager showed me was the Dynamics.SET file. It's pretty fundamental to GP, so it's good to understand what it is and how it works.
For that reason, there are many, many blog posts and articles that discuss the SET file, so I'm not going to write another one. Here is one that I found quickly that covers the basics.
http://www.interdynbmi.com/blog/microsoft-dynamics-gp-dictionary-set-file
If you are a GP consultant and you don't know how to edit a SET file and diagnose SET file issues in your sleep, you really need to spend a few minutes to get up to speed.
The Data dictionary memory allocation error shown above is very easy to fix. It indicates that the module count listed on the first line of the SET file does not match the number of modules listed in the SET file. So if you have to manually edit the SET file to remove one module, you need to decrease that module count by one. If you get this error message, it's a 10 second fix.
Learn it. Live it. Love it.
![]()
![]()
Because I work a lot with Post Master Enterprise, which occasionally requires manual adjustments to the Dynamics GP Dynamics.SET file, I pretty consistently get a question about this error message.
It is totally understandable when customers ask me what this means. I don't expect them to be familiar with the arcane details of a proprietary configuration file that they normally wouldn't edit.
But I am surprised when a Dynamics GP partner asks me what this error means and how to fix it.
When I started as an employee at a Dynamics GP partner many years ago, the first day that I was introduced to GP, one of the first things the manager showed me was the Dynamics.SET file. It's pretty fundamental to GP, so it's good to understand what it is and how it works.
For that reason, there are many, many blog posts and articles that discuss the SET file, so I'm not going to write another one. Here is one that I found quickly that covers the basics.
http://www.interdynbmi.com/blog/microsoft-dynamics-gp-dictionary-set-file
If you are a GP consultant and you don't know how to edit a SET file and diagnose SET file issues in your sleep, you really need to spend a few minutes to get up to speed.
The Data dictionary memory allocation error shown above is very easy to fix. It indicates that the module count listed on the first line of the SET file does not match the number of modules listed in the SET file. So if you have to manually edit the SET file to remove one module, you need to decrease that module count by one. If you get this error message, it's a 10 second fix.
Learn it. Live it. Love it.
Steve Endow is a Microsoft MVP for Dynamics GP and a Dynamics GP Certified IT Professional in Los Angeles. He is the owner of Precipio Services, which provides Dynamics GP integrations, customizations, and automation solutions.
