Skip to main content

Notifications

Announcements

No record found.

Microsoft Dynamics SL (Archived)

Setting up test environment, Company Name configuration error 7006

Posted on by Microsoft Employee

Good morning,

We are attempting to create a test environment and have run into some issues.

What we've done:

Cloned the application server (Dynamics SL (2011) and Unanet)

Copied the database(s) and renamed them

Upgraded out Unanet environment

Attempting to log in into SL using our new databases (on same database server)

We did rename the databases

UPDATE COMPANY SET DatabaseName = 'XXXXXX' where DatabaseName = 'YYYYYY'
UPDATE DOMAIN SET DatabaseName = 'XXXXXX' where DatabaseName = 'YYYYYY'

as well as run the database maintenance tool to synchronize

But we are unable to log in due to an error with "Company Name" 

System Message 7006

Company Configuration error: Company XX not properly matched to system Database

Any guidance to what the next step is would be greatly appreciated.

*This post is locked for comments

  • Suggested answer
    notrozer Profile Picture
    notrozer 10 on at
    RE: Setting up test environment, Company Name configuration error 7006

    I ran into this myself...  But what I found out is that the Database name In the System Database goes in 2 tables..

    The 'Domain' and 'Company' tables .. When they dont Match I get that error.,

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Setting up test environment, Company Name configuration error 7006
    I am not exactly sure what fixed it, or why it is working this way but... We are able to connect to the "test" system database, and when SL opens it is reading/connected to the "test" app database. On the live system we connect directly to the app database, hey but it is working and reading the test data.  We did change the company name to test_XX so that must have done it.
    Thanks,

    Mike

  • Suggested answer
    Bill Degnan Profile Picture
    Bill Degnan 650 on at
    RE: Setting up test environment, Company Name configuration error 7006

    did you run the update views process in Database maintenance?

  • Suggested answer
    Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Setting up test environment, Company Name configuration error 7006

    There is one view in the application database that, when incorrect, typically causes this message.  Not sure that is your issue but execute the following against the test application database:

    sp_helptext vs_company

    switch to results to text option before executing the above.

    Look at the text of the view and note the system database name after the from statement.  If that is showing the wrong system database name for the test environment then execute the following:

    drop view vs_company

    go

    create view vs_Company as select * from  xxxxxx..Company

    note: replace the xxxxxx with the test system database name.

    Try launching SL again and see if this takes care of your issue.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Setting up test environment, Company Name configuration error 7006

    Rick,

    Thanks for the suggestion. Yes, I think.  So I was able to run the scripts against the APP database successfully but not the System Database ( Msg 208, Level 16, State 1, Line 1

    Invalid object name 'Company'.). We did Update Views as well as  Execute Master indexes, Views, and Stored Procedures.  We are still unable to connect SL to the database.

    Same Error: 7006

    Company Configuration Error: Company XX not properly matched to system database XXXXXXX

    We did not change the company name (XX) and I expect it is the same as it was in the original database.

    Full Disclosure, I am not a Database expert.

  • Community Member Profile Picture
    Community Member Microsoft Employee on at
    RE: Setting up test environment, Company Name configuration error 7006

    Based on your update queries run I am assuming that you also included a new test system database and ran the queries against that new system database as opposed to adding new companies under the production system database.  If that assumption is correct, did you run the update master views process using the new system database.  There are views that associate the application database with the system database.

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

December Spotlight Star - Muhammad Affan

Congratulations to a top community star!

Top 10 leaders for November!

Congratulations to our November super stars!

Tips for Writing Effective Suggested Answers

Best practices for providing successful forum answers ✍️

Leaderboard

#1
André Arnaud de Calavon Profile Picture

André Arnaud de Cal... 291,253 Super User 2024 Season 2

#2
Martin Dráb Profile Picture

Martin Dráb 230,188 Most Valuable Professional

#3
nmaenpaa Profile Picture

nmaenpaa 101,156

Leaderboard

Featured topics

Product updates

Dynamics 365 release plans