November 8, 2017 at 6:36 pm
One method of creating a copy of an on premise CRM database is to use the copy database method.
But it has to be a database name that does not exist in the SQL instance.
Afterward a few scripts are run to set the org ID and then there is a process in the CRM Deployment manager where I can import that new databases into a new instance, and in the process run a utility that allows for the users to be mapped to the new organization.
This supplies new GUIDS for the users in the System User base table in the org database.
I first got the failure in my dev environment, and since the copy database wizard seems to use the account for the SQL Server Agent, Switched it to local security account and restarted the service. Running the copy database wizard then finished and I had a copy of Production in a new database with a new name. I imported it into a new organization and updated the GUIDS for the new users and I was in business. The new site came up in the browser and I had another instance in server.
This worked fine in my lab, but on the client's site, not so much in the clients production environment. The job fails with an Event ID: 208 error but not much else. I configured the errors to generated in a txt file but it never writes to it.
I tried the changes to the Agent account on the client SQL server but it still fails. What's the difference. The SQL server has two instances on it in production, thus it has the agent running twice on the production server.
I have Deployment admin rights and security admin rights in the SQL instance. Wish I could find were the error is. I'm about to start a CRM trace too see if it yields a clue, but if any other Dynamics CRM On prem SQL folks out there have run into this I would appreciate the help. Thanks.
November 9, 2017 at 10:41 am
osgcurt - Wednesday, November 8, 2017 6:36 PMOne method of creating a copy of an on premise CRM database is to use the copy database method.
But it has to be a database name that does not exist in the SQL instance.
Afterward a few scripts are run to set the org ID and then there is a process in the CRM Deployment manager where I can import that new databases into a new instance, and in the process run a utility that allows for the users to be mapped to the new organization.
This supplies new GUIDS for the users in the System User base table in the org database.I first got the failure in my dev environment, and since the copy database wizard seems to use the account for the SQL Server Agent, Switched it to local security account and restarted the service. Running the copy database wizard then finished and I had a copy of Production in a new database with a new name. I imported it into a new organization and updated the GUIDS for the new users and I was in business. The new site came up in the browser and I had another instance in server.
This worked fine in my lab, but on the client's site, not so much in the clients production environment. The job fails with an Event ID: 208 error but not much else. I configured the errors to generated in a txt file but it never writes to it.
I tried the changes to the Agent account on the client SQL server but it still fails. What's the difference. The SQL server has two instances on it in production, thus it has the agent running twice on the production server.I have Deployment admin rights and security admin rights in the SQL instance. Wish I could find were the error is. I'm about to start a CRM trace too see if it yields a clue, but if any other Dynamics CRM On prem SQL folks out there have run into this I would appreciate the help. Thanks.
There should be a job created which would be named something like CDW_SourceServer_DestinationServer_N
You need to check the job history for that job. It will have more details. Right click on the job, select history, click on the plus sign to expand the history details.
Sue
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply