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

Announcements

No record found.

News and Announcements icon
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Forums / Microsoft Dynamics GP (Archived) / Creating a "Fresh...
Microsoft Dynamics GP (Archived)

Creating a "Fresh" - (Not Test) company in Dynamics GP 2013

(0) ShareShare
ReportReport
Posted on by Community Member

Hello,

I'm new to the community... I've been asked to create a completely new company in our existing environment.  The process using GP utilities is pretty straitforward.  After launching GP though I receive the 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 understand the issue with Company InterID and per some members suggestions ran the script per article https://mbs2.microsoft.com/Knowledgebase/kbdisplay.aspx?wtntzsmnwukntmmyqlytnsukzpxkmunvqpuupouzqqtvtyuz .  I still receive the error though upon login and it seems the article refers to a test company where you are restoring data from an existing company.  I need a fresh company.  I understand there are IDs in table SY00100 and SY01500 and have manually tried to make IDs unique to no avail.  I deleted the company and tried to start over and maybe use Rapidstart Services but it says I need Econnect.  All I want is a fresh slate of a company.  I'm doing something wrong.  Any guidance is appreciated. 

Thank you, 

Tien Jo

*This post is locked for comments

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

    Hi,

    Refer the below link.

     community.dynamics.com/.../how-to-create-a-company-in-microsoft-dynamics-gp-2010.aspx

  • Community Member Profile Picture
    Community Member on at

    Hi Shan,

    Thank you for the response.  I've completed that process.  It's the error I receive after logging into the new company I created that is the issue.  I'll keep looking.  

    Thanks again,

    Tien Jo

  • Community Member Profile Picture
    Community Member on at

    Hi,

    There is another thread related to your issue.

    community.dynamics.com/.../91083.aspx

  • Suggested answer
    Frank Hamelly | MVP, MCP, CSA Profile Picture
    Frank Hamelly | MVP... 46,633 Moderator on at

    You shouldn't need to run the InterID scripts when creating a new company, as I believe you've discovered.  My guess is you may have missed a step somewhere in the creation of the company.  I highly recommend getting a copy of this book if you are new to setting up and configuring GP company databases - www.amazon.com/.../ref=sr_1_1_twi_2;ie=UTF8&qid=1424708413&sr=1-1.   $22 is a bargain for this step-by-step guide to setting up GP.

    Rapid Start would not resolve the issue you encountered.  Get the book and start over with creating a new company.

  • Community Member Profile Picture
    Community Member on at

    Hi,

    Thanks Shan.  I'll take a look.

  • Community Member Profile Picture
    Community Member on at

    Hi Frank,

    We don't do this often but I'll take a look at the book!  

    Thank you,

    Tien Jo

  • Suggested answer
    Mahmoud Saadi Profile Picture
    Mahmoud Saadi 32,738 on at

    The process of creating a new company is definitely straightforward. Ian has a comprehensive article on this, check Dynamics GP 2013 – How To Create A Company

    Let us know if you have any further inquiries,

  • Suggested answer
    Community Member Profile Picture
    Community Member on at

    Hi Everyone,

    Thanks for submitting suggestions.  It really wasn't the creation of a company that I was having issues with.  I did receive one error about Microsoft Dynamics GP Utilities: "Violation of PRIMARY KEY constraint 'PKSY60100'. Cannot insert duplicate key in object 'dbo.SY60100'" but an article suggests that it is because DYNSA is not the DBowner.  The issue was upon login I had to "You must resolve the database configuration to log in to the company".  

    Spoke with Support.  All we ended up doing was manually changing the SY00100 table on the new database to reflect what was in SY01500 in Dynamics.  I know there is a script to change that in GP2013 but it didn't work.  Support said it was the first time they saw that.  I hope that doing that manually won't haunt me down the road!

    Thanks again,

    Tien Jo

  • Suggested answer
    Bill Campbell Profile Picture
    Bill Campbell 12 on at

    We have not seen that happen with the create of a new company so can not comment.

    However, we have done the manual change 100's of times, each time we update the TEST environment with a copy of LIVE it is a requirement that we do this - so, pretty sure it works and does not generate any errors down the road.

    Hope this helps ensure that the solution is correct.

  • Community Member Profile Picture
    Community Member on at

    Bill,

    Thank you for your input!  It helps to know that it is not uncommon to have to do that.

    Tien Jo

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

Introducing the 2026 Season 1 community Super Users

Congratulations to our 2026 Super Stars!

Meet the Microsoft Dynamics 365 Contact Center Champions

We are thrilled to have these Champions in our Community!

Congratulations to the April Top 10 Community Leaders

These are the community rock stars!

Leaderboard > 🔒一 Microsoft Dynamics GP (Archived)

#1
Shravan Attelli Profile Picture

Shravan Attelli 1

Last 30 days Overall leaderboard

Featured topics

Product updates

Dynamics 365 release plans