none
Site Repair Wizard on a SCCM Secondary

    שאלה

  • I am replacing our SCCM 2007 SP1 secondary sites with new hardware and Windows 2008 64 bit.
    I  have made a backup of the secondary. Shutdown the old server removed it from AD. 
    Added the new server to AD with the same server name. 
    Installed SCCM with the exact site names/information. 
    I then install the SCCM console on the secondary in order to use ConfigMgr Site Recovery Wizard. 

    This is where the problem is.  The Wizard stops with the following error: "SCCM - Recoverywizard has stopped working"

    It places this in the application event log

    Fault bucket 253032840, type 5
    Event Name: CLR20r3
    Response: None
    Cab Id: 0

    Problem signature:
    P1: repairwizard.exe
    P2: 4.0.6221.1000
    P3: 48339214
    P4: RepairWizard
    P5: 4.0.6000.0
    P6: 48339214
    P7: 47a
    P8: a1
    P9: System.NullReferenceException
    P10:

    Attached files:
    C:\Users\*****\AppData\Local\Temp\2\WERAA72.tmp.version.txt

    These files may be available here:
    C:\Users\*****\AppData\Local\Microsoft\Windows\WER\ReportArchive\Report13ecbb15

    These files have no more information other than it stopped working.

    The process worked perfectly on the Primaries.

    I have many secondaries to replace and a short time to do so.

    Any thoughts on how to get the repairwizard to run on the secondaries?
    יום חמישי 28 מאי 2009 19:30

תשובות

  • As far as I am aware recovery of a secondary has never worked. Please don't queue up to bite me on this one, the few times I've tried it's not worked.

    If you want to confirm this raise a CSS case.

    I'd recommend you do this differently. You've done most of the hard work on rebuilding the secondary, just delete the site from the hierarchy using the hierarchy maintenance tool, then backup the SMSPCK, SMSPKGSIG and SMSSIG$ folders and put them back on the server when it's rebuilt, then setup the shares and preload the packages to get it back to where it was before after reconfiguring the site settings from the parent (if needed). Make sure the account you use when running the preload tool has site rights or you'll get an error.

    I regularly rebuild secondary site servers on new servers with same hostname and sitecode. I just perform the above steps and it's back up and running within a few hours.
    יום רביעי 17 יוני 2009 16:58
    מנחה דיון

כל התגובות

  • My suggestion would be to call PSS.


    http://www.enhansoft.com/
    יום חמישי 28 מאי 2009 21:45
    מנחה דיון
  • As far as I am aware recovery of a secondary has never worked. Please don't queue up to bite me on this one, the few times I've tried it's not worked.

    If you want to confirm this raise a CSS case.

    I'd recommend you do this differently. You've done most of the hard work on rebuilding the secondary, just delete the site from the hierarchy using the hierarchy maintenance tool, then backup the SMSPCK, SMSPKGSIG and SMSSIG$ folders and put them back on the server when it's rebuilt, then setup the shares and preload the packages to get it back to where it was before after reconfiguring the site settings from the parent (if needed). Make sure the account you use when running the preload tool has site rights or you'll get an error.

    I regularly rebuild secondary site servers on new servers with same hostname and sitecode. I just perform the above steps and it's back up and running within a few hours.
    יום רביעי 17 יוני 2009 16:58
    מנחה דיון
  • Hi,

    SMS Marshall
    Can You write step by step procedure to replace the secondary site server with same hostname and sitecode?
    (for better understanding)
    (little more)

    Thanks in advance

    MCSE
    יום שישי 11 ספטמבר 2009 13:07
  • So How did you rebuild/repair or replace your secondary server? I am having a similar problem where my secondary server stopped reporting but it is still "active." I need to repair it ad there is no way to repair the server/software installation. I am getting ready to rebuild the entire system, but if I can repair the existing server that would be great.
    יום שני 01 פברואר 2010 11:49
  • It is not supported to restore secondary sites: http://technet.microsoft.com/en-us/library/bb680393.aspx: "Although there is a task to create a backup of a Configuration Manager 2007 secondary site, you cannot restore this backup by using the Site Repair Wizard. Instead, you must reinstall the secondary site. The primary site will replicate secondary site data to the reinstalled secondary site."
    יום שני 01 פברואר 2010 12:31
    מנחה דיון
  • What about PREINST /UPGRADE <site>

    That seemed to work for me...
    יום רביעי 18 ספטמבר 2013 16:56
  • Could you please share steps to reinstall secondary site on same hostname with same site code. 

    This is the error I am getting even after clearing registry entries:

    INFO: Attempting to load resource DLL...               Configuration Manager Setup     5/23/2018 7:42:06 AM  16700 (0x413C)

    INFO: SQL Server Native Client: SQLNCLI11 version:<11.3.6260.1>              Configuration Manager Setup     5/23/2018 7:42:06 AM        16700 (0x413C)

    Enforce using SQL native client for SQL connection.          Configuration Manager Setup     5/23/2018 7:42:06 AM                16700 (0x413C)

    ERROR: Connection strings not initialized               Configuration Manager Setup     5/23/2018 7:42:06 AM  17216 (0x4340)

    CSql Error: Cannot find data for connection type: , cannot get a connection.          Configuration Manager Setup                5/23/2018 7:42:06 AM  17216 (0x4340)

    ERROR: Failed to connect to SQL Server 'master' db.         Configuration Manager Setup     5/23/2018 7:42:06 AM                17216 (0x4340)

    INFO: Prerequisite rules for secondary site fresh installation are being run.            Configuration Manager Setup                5/23/2018 7:42:06 AM  17216 (0x4340)

    INFO: smstsvc.exe source path is set to S:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\BIN\X64                Configuration Manager Setup     5/23/2018 7:42:06 AM  17216 (0x4340)

    INFO: File \\?\C:\Windows\smstsvc_test_1.exe does not exist. No zapping needed.           Configuration Manager Setup                5/23/2018 7:42:06 AM  17216 (0x4340)

    INFO: test loop count:29.              Configuration Manager Setup     5/23/2018 7:42:35 AM  17216 (0x4340)

    INFO: smstsvc_test_1 Return result <0> Configuration Manager Setup     5/23/2018 7:42:35 AM  17216 (0x4340)

    CurrentVersion = 6.3       Configuration Manager Setup     5/23/2018 7:42:45 AM  17216 (0x4340)

    CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL on Abc.com              Configuration Manager Setup     5/23/2018 7:43:10 AM  17216 (0x4340)

    CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL on Abc.com              Configuration Manager Setup     5/23/2018 7:43:13 AM  17216 (0x4340)

    CWmiRegistry::GetValues: Failed to get values from SOFTWARE\Microsoft\Microsoft SQL Server\Instance Names\SQL                Configuration Manager Setup     5/23/2018 7:43:13 AM  17216 (0x4340)

    CWmiRegistry::GetValues: Failed to connect to registry on machine Abc.com. Error code: 2            Configuration Manager Setup 5/23/2018 7:43:15 AM  17216 (0x4340)

    CurrentVersion = 6.3       Configuration Manager Setup     5/23/2018 7:43:19 AM  17216 (0x4340)

    INFO: Checking Installed SMS componants on:Abc.com. Configuration Manager Setup     5/23/2018 7:43:21 AM                17216 (0x4340)

    CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\SMS\Setup on Abc.com         Configuration Manager Setup 5/23/2018 7:43:23 AM  17216 (0x4340)

    CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\SMS\Operations Management\SMS Server Role on Abc.com        Configuration Manager Setup     5/23/2018 7:43:24 AM  17216 (0x4340)

    CWmiRegistry::WmiOpen: Failed to read key SOFTWARE\Microsoft\SMS\Providers\Sites on Abc.com       Configuration Manager Setup 5/23/2018 7:43:24 AM  17216 (0x4340)

    CSql Error: Cannot find data for connection type: SMS Master, cannot get a connection.  Configuration Manager Setup                5/23/2018 7:43:24 AM  17216 (0x4340)

    INFO: smstsvc.exe source path is set to S:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\BIN\X64                Configuration Manager Setup     5/23/2018 7:43:31 AM  17216 (0x4340)

    INFO: File \\?\UNC\Abc.com\admin$\smstsvc_test_2.exe does not exist. No zapping needed.      Configuration Manager Setup 5/23/2018 7:43:33 AM  17216 (0x4340)

    INFO: test loop count:19.              Configuration Manager Setup     5/23/2018 7:44:21 AM  17216 (0x4340)

    INFO: smstsvc_test_2 Return result <1> Configuration Manager Setup     5/23/2018 7:44:22 AM  17216 (0x4340)

    INFO: smstsvc.exe source path is set to S:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\BIN\X64                Configuration Manager Setup     5/23/2018 7:44:32 AM  17216 (0x4340)

    INFO: File \\?\C:\Windows\smstsvc_test_3.exe does not exist. No zapping needed.           Configuration Manager Setup                5/23/2018 7:44:32 AM  17216 (0x4340)

    INFO: test loop count:8. Configuration Manager Setup     5/23/2018 7:44:40 AM  17216 (0x4340)

    INFO: smstsvc_test_3 Return result <0> Configuration Manager Setup     5/23/2018 7:44:40 AM  17216 (0x4340)

    INFO: This is a local site system. There is no need to check for the Admin$ share. Configuration Manager Setup                5/23/2018 7:44:42 AM  17216 (0x4340)

    CurrentVersion = 6.3       Configuration Manager Setup     5/23/2018 7:44:48 AM  17216 (0x4340)

    INFO: Checking Windows Cluster.             Configuration Manager Setup     5/23/2018 7:44:53 AM  17216 (0x4340)

    CWmi::Connect(): ConnectServer(Namespace) failed. - 0x8004100e           Configuration Manager Setup     5/23/2018 7:44:57 AM        17216 (0x4340)

    INFO: WMI namespace root\MSCluster does not exists on Abc.com.         Configuration Manager Setup     5/23/2018 7:44:57 AM        17216 (0x4340)

    INFO: smstsvc.exe source path is set to S:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\BIN\X64                Configuration Manager Setup     5/23/2018 7:45:01 AM  17216 (0x4340)

    INFO: File \\?\UNC\Abc.com\admin$\smstsvc_test_4.exe does not exist. No zapping needed.      Configuration Manager Setup 5/23/2018 7:45:03 AM  17216 (0x4340)

    INFO: test loop count:22.              Configuration Manager Setup     5/23/2018 7:45:51 AM  17216 (0x4340)

    INFO: smstsvc_test_4 Return result <7> Configuration Manager Setup     5/23/2018 7:45:52 AM  17216 (0x4340)

    INFO: smstsvc.exe source path is set to S:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\BIN\X64                Configuration Manager Setup     5/23/2018 7:46:05 AM  17216 (0x4340)

    INFO: File \\?\UNC\Abc.com\admin$\smstsvc_test_5.exe does not exist. No zapping needed.      Configuration Manager Setup 5/23/2018 7:46:06 AM  17216 (0x4340)

    INFO: test loop count:22.              Configuration Manager Setup     5/23/2018 7:46:59 AM  17216 (0x4340)

    INFO: smstsvc_test_5 Return result <7> Configuration Manager Setup     5/23/2018 7:47:00 AM  17216 (0x4340)

    INFO: smstsvc.exe source path is set to S:\PROGRAM FILES\MICROSOFT CONFIGURATION MANAGER\BIN\X64                Configuration Manager Setup     5/23/2018 7:47:24 AM  17216 (0x4340)

    INFO: File \\?\UNC\Abc.com\admin$\smstsvc_test_6.exe does not exist. No zapping needed.      Configuration Manager Setup 5/23/2018 7:47:26 AM  17216 (0x4340)

    INFO: test loop count:18.              Configuration Manager Setup     5/23/2018 7:48:14 AM  17216 (0x4340)

    INFO: smstsvc_test_6 Return result <0> Configuration Manager Setup     5/23/2018 7:48:15 AM  17216 (0x4340)

    CurrentVersion = 6.3       Configuration Manager Setup     5/23/2018 7:48:32 AM  17216 (0x4340)

    INFO: Abc.com is a 64 bit operating system.         Configuration Manager Setup     5/23/2018 7:48:37 AM  17216 (0x4340)

    יום חמישי 24 מאי 2018 07:57