Tuesday, January 12, 2016

Dynamics GP Error: Selected company is not configured as a company of the current system database

By Steve Endow

Today I created a new test company in my development environment and then restored the TWO database into my new TEST database.  I dutifully ran the GP refresh company script and got a few strange errors, but eventually ran the script successfully.

But when I logged into GP and selected my new Test company, I received this error:

The selected company is not configured as a company of the current Microsoft Dynamics GP system database.  You must resolve the database configuration to log in to the company.

I've never seen this error before, so I didn't know where to start.  I Googled the message, and after digging around, I finally found a GP partner post that discussed the issue and mentioned that the problem was with the SY00100 table in the new company database.  The record in that table should reference the Dynamics GP System database, not the Company database.

Sure enough, the SY00100 table in my new Test company had its own INTERID value of TEST, instead of the DYNAMICS system database.  I corrected the value in SY00100 and was able to login.

Turns out that Tim Wappat documented this issue in detail a year ago, but I didn't see it in the Google search results.

Here is Tim's post from January 2015:


And I now see that Jen Kuntz also documented the issue in August 2015:


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.

You can also find him on Google+ and Twitter


Ian Grieve said...

From experience, this is usually caused by running an old version of the Copy Company scripts from Microsoft.

The old one sets all INTERID to the db_name, but the new one handles the SY00100 table differently.

Steve Endow said...

Thanks Ian, I agree, but I'm also wondering if there might be something that the script isn't catching. This is the first time I've had the issue, and it was on GP 2015. I initially used the script I had on hand, which gave me numerous strange errors.

I then tried the latest one from the MS KB article, and it worked, but then caused this error message.

So I'm not sure if using the older script first was the issue, or exactly how the incorrect system db value was set.

In my abundant free time, I may try another test.

Ian Grieve said...

Yes, running the old script first will have changed the entry from your system database to the company db name. The second script won't have changed it back as it has no way of knowing which is the system db.

Pradeep said...

Please check the resolution in the post below.