SOLVED how to move SCCM Database to another SQL server

[Gregg Cooper]

Ok so this is a biggy.

We have a client who has contacted us that their SCCM box (Virtual Hyper-V 2012 r2) will not boot.

It is reporting inaccessable boot device.

We have tried various things to get this back up and running, reparing all of the EFI boot file etc, but its refusing to start.

I am coming to the conclusion that this server is never going to boot again.

Now, there are ZERO backups of this server. Their backups have been failing for ages, and the internal database backup is non-existent. (We do no manage this network, but did setup SCCM initially.

Thankfully, we can open up the VHDX files and can see the full structure of both the C and D drive.

How would be go about recovering SCCM from this state?

I wish it would be as simple as creating a new VM (which boots) and then copying the structure of C over the top... But I know that wouldnt work.

I do believe everything about this server is ok, minus the booting ability.

A bit of background, the HDDs were full, so we merged a snapshot that was taken and expanded the dynamic vhdx files. The server wanted to reboot for updates. It is when this happened the issue occured.

Any advice would be appreciated.

Thanks

 

[Gregg Cooper]

FYI, I have made some progress with this, but still need help.

I have built a new server with the same name and installed all the required resources for sccm. SQL, MDT, WSUS, WDS, ADK.

I have copied the sccm database files from broken server and attached to new one. I am running through site recovery in the SCCM install and I get to the point where the sql has been setup and it is attempting to copy files.

But it errors out at this point. The log says this on the last few lines:

INFO: Found the file enrollweb_enu.msi on install.map. Updating this file.... $$<Configuration Manager Setup><02-28-2016 01:30:18.488+00><thread=5804 (0x16AC)>
WARNING: Failed to get file size for enrollweb.msi. $$<Configuration Manager Setup><02-28-2016 01:30:18.488+00><thread=5804 (0x16AC)>
INFO: Updating install Items from updated install.map. $$<Configuration Manager Setup><02-28-2016 01:30:18.769+00><thread=5804 (0x16AC)>
INFO: Installing resources for default language $$<Configuration Manager Setup><02-28-2016 01:30:18.769+00><thread=5804 (0x16AC)>
ERROR: Could not find resource file for Migration, locale 1033 $$<Configuration Manager Setup><02-28-2016 01:30:18.769+00><thread=5804 (0x16AC)>
ERROR: Failed to install resource for language ENU (1033) $$<Configuration Manager Setup><02-28-2016 01:30:18.769+00><thread=5804 (0x16AC)>
~~===================== Completed Configuration Manager 2012 Server Setup ===================== $$<Configuration Manager Setup><02-28-2016 01:30:18.769+00><thread=5804 (0x16AC)>

Unable to get past this point and get SCCM reinstalled. Any ideas on what this means?

 

[Prajwal Desai]

Check the following links -

https://blogs.technet.microsoft.com...igmgr-2012-site-database-to-a-new-sql-server/

https://social.technet.microsoft.co...another-sql-server?forum=configmanagergeneral

 

[Gregg Cooper]

I know this is an old thread, but thought I would update what happened. Apologies I have been on extended sick leave due to being in hospital for a while.

I did finally fix this, in March, but did it a fairly dodgy way. I would say pretty much unsupported, but its all working again now.

I decided to forget about a site recovery. So installed a clean SCCM and got it to create a new blank Database. I then did a sneaky switch of the old DB and the new DB and restarted all of the services.

This worked unbelievably. SCCM ran and all my content was there.

I did, after this point have to do multiple repairs:

I had to reinstall WDS and WSUS (and respective SCCM roles) and also renew WDS certificate. This was due to all software updates and PXE booting being completely broken.

I had to revalidate all content on DP. Some I had to remove and redistribute.

I had to recreate task sequences.

_

To be fair, this took less time than it would have to start again. Like I said, completely unsupported way of doing it, but it worked and now everything is green and working perfectly. I even managed to fix things that were not working before the server died which was nice!

 

[SCCMAD1]

FYI, I have made some progress with this, but still need help.

I have built a new server with the same name and installed all the required resources for sccm. SQL, MDT, WSUS, WDS, ADK.

I have copied the sccm database files from broken server and attached to new one. I am running through site recovery in the SCCM install and I get to the point where the sql has been setup and it is attempting to copy files.

But it errors out at this point. The log says this on the last few lines:

INFO: Found the file enrollweb_enu.msi on install.map. Updating this file.... $$<Configuration Manager Setup><02-28-2016 01:30:18.488+00><thread=5804 (0x16AC)>
WARNING: Failed to get file size for enrollweb.msi. $$<Configuration Manager Setup><02-28-2016 01:30:18.488+00><thread=5804 (0x16AC)>
INFO: Updating install Items from updated install.map. $$<Configuration Manager Setup><02-28-2016 01:30:18.769+00><thread=5804 (0x16AC)>
INFO: Installing resources for default language $$<Configuration Manager Setup><02-28-2016 01:30:18.769+00><thread=5804 (0x16AC)>
ERROR: Could not find resource file for Migration, locale 1033 $$<Configuration Manager Setup><02-28-2016 01:30:18.769+00><thread=5804 (0x16AC)>
ERROR: Failed to install resource for language ENU (1033) $$<Configuration Manager Setup><02-28-2016 01:30:18.769+00><thread=5804 (0x16AC)>
~~===================== Completed Configuration Manager 2012 Server Setup ===================== $$<Configuration Manager Setup><02-28-2016 01:30:18.769+00><thread=5804 (0x16AC)>

Unable to get past this point and get SCCM reinstalled. Any ideas on what this means?

Hello,

I know this is a really old thread, but I recently ran into this exact issue while recovering a site.

After fighting with this for some time, I realized that I was selecting recover a CAS as opposed to recover a Primary Site. As soon as I selected recover a primary site, the recovery was successful.

I just wanted to post this in case someone else finds this article looking for a resolution.