Share
Report
256I'm running into an odd issue with setting up a second organization in our Test environment. Here's our current layout:
Prod Server
- Organization 1 - DBName - MAIN_MSCRM // Org Name - MAIN
Test Server
- Organization 1 - DBName - MAIN_MSCRM // Org Name - MAIN
I need to create a second copy of Prod on the Test server for UAT, so I backed-up Prod, restored to Test with the DB Name UAT_MSCRM, and I started the Org Import process. UAT_MSCRM was the only database that showed up, I named the Org 'UAT', and it ran without issue. So now I have this on the Test Server:
- Organization 2 - DBName - UAT_MSCRM // Org Name - UAT
But when I browse to the new UAT test organization instead of showing the copy of Prod it's presenting the organization that was already on Test (MAIN Org on Test server). In checking MSCRM_CONFIG.dbo.Organization I'm finding the new ORG UAT is now there, but it's using DB Name MAIN_MSCRM instead of UAT_MSCRM. When I setup the Org Import I did select UAT_MSCRM which was the only option available, so can someone give any input on why this is happenign? This is CRM v8 On Prem. On the Test server I can browse to both MAIN and UAT organizations and see the same data - updating something in one shows on the other so I know they're the same -- plus we changed the theme in Test so we know it's not Prod -- and the theme is showing up on both Test organizations now.
So what happened ??? Are GUID's getting crossed since on Test both organizations would have been restored from the same original Organization on the Prod server? Since we depend heavily on the MAIN or in Test for testing our processes I removed the UAT organization from Test, and now the MAIN organization that was there no longer loads.
Thanks for any insight on what happened and how to get the MAIN org on Test back up. I'm about to drop and re-add MAIN to see if that reconnects everything, if not I'll restore the databases from backup.
All responses (
Answers (
