Skip to content
  • Home
  • About Me
    • Disclaimer
    • Privacy Policy
    • Terms of Use
    • Consultant’s Toolbox
  • Solutions
    • Dynamics 365
    • Dynamics GP
      • GP 2018 Toolbox
    • Dexterity
    • Royalty Management System
    • Franchisee Portal
  • Contact Me

Dynamics Insight – Modern ERP Perspectives

Driving Innovation with Microsoft Dynamics 365, Power Platform & Data-Driven Strategy
Menu
Facebook Twitter Google+ LinkedIn
  • Home
  • About Me
    • Disclaimer
    • Privacy Policy
    • Terms of Use
    • Consultant’s Toolbox
  • Solutions
    • Dynamics 365
    • Dynamics GP
      • GP 2018 Toolbox
    • Dexterity
    • Royalty Management System
    • Franchisee Portal
  • Contact Me
Home  /  Dynamics GP • General  /  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”
PostedinDynamics GP, General Posted on April 10, 2018

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”

Posted By Samuel Mathew

Problem:

Recently while I was working on merging two different GP instance as part of a company acquisition. Initially, I had to bring one company to match the other company GP installation such as GP release and service pack. Then I was able to create a shell company in “GP instance 1” and restored the backup from “GP Instance 2”. Then ran the GP Utilities to synchronize the account framework. But while launching GP application, I received the following error message:

“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”

Cause:

This is due to the fact that when I created a shell company in “GP Instance 1”, GP system assigned a “CMPANYID” in SY01500 table in the system database. But when I restored the backup of the company database from “GP Instance 2”, the company ID in the company database was not matching to the system database.

Solution:

Use the following SQL Queries

Select

--Repleace DYNAMCIS with correct System database name
USE <'Database ID of the COMPANY created'>
GO

--Script 1
select INTERID, CMPANYID, * from DYNAMICS..SY01500 where INTERID='Database ID of the COMPANY you created'
--Script 2
select * from SY00100

Compare the CMPANYID values from both results. CMPANYID in SY001000 (Script 2) table must match with the CMPANYID value in SY01500 (Script 1).

UPDATE SY00100
set CMPANYID = (select CMPANYID from DYNAMICS..SY01500 where INTERID='Database ID of company you created')

I hope this will be useful.

Tags: GP SQL Script
Share on Facebook Share on Twitter Share on Google+ Share on LinkedIn Share on Pinterest
Previous Article
Microsoft Dynamics 365 Business Central – Pricing Announced
Next Article
Simplifying Data Analytics with Export to Data Lake for Dynamics 365 F&O and Synapse Analytics

About Author

Samuel Mathew

Software developer acknowledged for talents conceptualizing and directing the development and continuous refinement of advanced technology solutions to meet clients’ needs. Sophisticated programming knowledge combines with well-honed problem-solving strengths to meet the challenges of business economics, client needs, and technical innovation.

Facebook Twitter LinkedIn

Related Posts

  • Understand Dynamics GP Lifecycle Policies

    December 2, 2024
  • Complete List of Versions information of Dynamics GP 2018

    February 12, 2018
  • Microsoft Product Lifecycle Policy

    February 2, 2018

1 Comment

  1. Pingback: 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” - DynamicAccounting.net

About Me

Samuel Mathew

Software developer acknowledged for talents conceptualizing and directing the development and continuous refinement of advanced technology solutions to meet clients’ needs. Sophisticated programming knowledge combines with well-honed problem-solving strengths to meet the challenges of business economics, client needs, and technical innovation.

Social Media

  • LinkedIn
  • Google
  • Facebook
  • Twitter
  • Pinterest

Subscribe

Archives

  • March 2025
  • February 2025
  • January 2025
  • December 2024
  • January 2023
  • April 2018
  • March 2018
  • February 2018
  • December 2017
  • November 2017
  • April 2017
  • January 2017
  • September 2016
  • June 2016
  • May 2016
  • April 2016
  • October 2015
  • February 2015
  • November 2014
  • February 2014
  • March 2013

Categories

  • Dexterity
  • Dynamics 365
  • Dynamics GP
  • Featured
  • Franchisee Portal
  • General
  • GP 2018 Toolbox
  • Royalty Management System

Tags

Azure Data Lake Business Central D365F&O Security Development Dexterity Dynamics 365 Dynamics 365 F&O Dynamics GP Environment ERP System Featured GP GP 2013 GP 2016 GP 2018 GP Web Client Installation Microsoft Dynamics Microsoft Dynamics 365 BC Microsoft SQL Server Migration from GP to Business Central Multi-tenant Product LifeCycle Royalty & Rights SmartList SmartList Designer SQL Reporting Services SQL Script Synapse Analytics Telemetry

inDynamics 365 March 14, 2018

Announcing Microsoft Dynamics 365 Business Central

BySamuel Mathew
inDynamics GP February 10, 2015

Who actually uses the Dynamics GP Multi-Tenant feature?

BySamuel Mathew

Meta

  • Log in
  • Entries feed
  • Comments feed
  • WordPress.org

Azure Data Lake Business Central D365F&O Security Development Dexterity Dynamics 365 Dynamics 365 F&O Dynamics GP Environment ERP System Featured GP GP 2013 GP 2016 GP 2018 GP Web Client Installation Microsoft Dynamics Microsoft Dynamics 365 BC Microsoft SQL Server Migration from GP to Business Central Multi-tenant Product LifeCycle Royalty & Rights SmartList SmartList Designer SQL Reporting Services SQL Script Synapse Analytics Telemetry

© Copyright 2020 Samuel Mathew.  All rights reserved.