locked
In-Place Upgrade to SCCM 2012 SP1 Fails - Updating Inbox Step RRS feed

  • Question

  • Hi guys,

    After following the KB on how to prepare for the SCCM 2012 SP1 in-place upgrade from SCCM 2012 to SP1 and also watching the TechNet radio video I was confident in performing my upgrade. The installation appeared to go smoothly and all my pre-requisites were clear. I initiated the install, but it failed near the end.

    It failed on the "Upgrading Inbox" step. Here is the error:

    "Setup has encountered fatal errors while performing file operations. Click the View Log button for more information."

    I need some guidance in tracking down what went wrong asap. As it is now, I can NOT login to my SCCM console to view my site and agent statuses in production setting. This is very disappointing.

    Here are the last 4 lines of the log.

    ~Updated inbox def 13, Replication Manager (Incoming)  $$<Configuration Manager Setup><02-16-2013 02:51:07.103+300><thread=872 (0x368)>

    INFO: Enabling monitoring for inbox definition Discovery Data Manager.  $$<Configuration Manager Setup><02-16-2013 02:51:07.119+300><thread=872 (0x368)>

    ~Updated inbox def 14, Discovery Data Manager  $$<Configuration Manager Setup><02-16-2013 02:51:07.134+300><thread=872 (0x368)>

    Saturday, February 16, 2013 12:11 PM

Answers

  • I ended up having to Uninstall the site and re-install the site. Then I had to go back in and configure all the roles, security, client settings, etc. 
    • Marked as answer by Gabriel Beaver Thursday, February 21, 2013 10:21 PM
    Thursday, February 21, 2013 10:21 PM

All replies

  • I've heard that many problems Microsoft have investigated have turned out to be Anti-virus-related, it's good to disable it during installation. 

    So how does it look now? Can you run the update again?

    More info: http://myitforum.com/myitforumwp/2013/01/11/configmgr-2012-sp1-rollout-tip-disable-antivirus-before-upgrade/

    Exclution list for AV: http://www.systemcenterblog.nl/2012/05/09/anti-virus-scan-exclusions-for-configuration-manager-2012/

    • Edited by Samus-Aran Saturday, February 16, 2013 2:25 PM
    Saturday, February 16, 2013 2:21 PM
  • Thank you for the reply.

    I disabled SCEP on the server, even added the list of exclusions you mentioned to SCEP as well. I still had a failure at the same exact point, being Updated inbox def14, Discovery Data Manager.

    INFO: Enabling monitoring for inbox definition Replication Manager (Incoming).  $$<Configuration Manager Setup><02-17-2013 21:28:36.535+300><thread=6404 (0x1904)>
    ~Updated inbox def 13, Replication Manager (Incoming)  $$<Configuration Manager Setup><02-17-2013 21:28:36.535+300><thread=6404 (0x1904)>
    INFO: Enabling monitoring for inbox definition Discovery Data Manager.  $$<Configuration Manager Setup><02-17-2013 21:28:36.535+300><thread=6404 (0x1904)>
    ~Updated inbox def 14, Discovery Data Manager  $$<Configuration Manager Setup><02-17-2013 21:28:36.535+300><thread=6404 (0x1904)>

    Anyone have any further advice? What am I missing? Any other specific places I should look for clues in rooting this issue out?

    --

    Gabe

    EDIT - Also forgot to mention, I did re-download the SP1 installation as Anoop had suggested. The ISO I had before was from before Jan 25th.
    Monday, February 18, 2013 2:32 AM
  • After some digging I found something that may link this to the product key.

    2/17/2013 9:28:36 PM: ConfigMgrSetupWizard Verbose: 1 : Received setup progress [Installing registry] from native code.

    2/17/2013 9:28:36 PM: ConfigMgrSetupWizard Verbose: 1 : Received setup progress [Upgrading inbox] from native code.

    2/17/2013 9:28:36 PM: ConfigMgrSetupWizard Verbose: 1 : Completed the site installation thread.

    2/17/2013 9:28:36 PM: ConfigMgrSetupWizard Error: 1 : Exception message: [Object reference not set to an instance of an object.], Exception details: [System.NullReferenceException: Object reference not set to an instance of an object.

       at Microsoft.SystemCenter.ConfigMgr.SetupFramework.NativeMethods.UpgradeSiteNative(IntPtr productKey, IntPtr downloadDir, IntPtr scriptPath)

       at Microsoft.SystemCenter.ConfigMgr.SetupFramework.NativeMethods.UpgradeSite(String productKey, String downloadDir, String scriptPath)

       at Microsoft.SystemCenter.ConfigMgr.Setup.FinishPage.DoWorkSetup(Object sender, DoWorkEventArgs e)

       at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)].

    2/17/2013 9:31:24 PM: ConfigMgrSetupWizard Information: 1 : Cancelling asynchronous threads...

    2/17/2013 9:31:24 PM: ConfigMgrSetupWizard Information: 1 : Notified monitoring threads to exit.

    2/17/2013 9:31:24 PM: ConfigMgrSetupWizard Information: 1 : All monitoring threads have completed.

    2/17/2013 9:31:24 PM: ConfigMgrSetupWizard Verbose: 1 : Exiting SetupWPF.exe.

    So I tried another upgrade without specifying the Product Key and opting for Eval only (you can enter key in console afterwards) and I got further, only this time I’ve hit another wall. Researching further...

    I am parsing the logs now.

    Bit of advice for anyone doing the upgrade, just stick to installing with 180 day eval and doing your key later. Should help avoid, in part, any potential issue.

    --

    Gabe

    Monday, February 18, 2013 10:12 PM
  • The other components did eventually install. The only error is now on Installing Boot Image Package, and its a warning not a failure:

    Monday, February 18, 2013 10:19 PM
  • We received an email about malware detected and removed on a few systems, so it looks like my site is functioning, I just cannot get into the admin console.

    Here is the error message that I see in the event log on the MP server, after trying to open the CM console:

    Transport error; failed to connect, message: 'The SMS Provider reported an error.'\r\nMicrosoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryException\r\nThe SMS Provider reported an error.\r\n   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()

       at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlConnectionManager.Connect(String configMgrServerPath)

       at Microsoft.ConfigurationManagement.AdminConsole.SmsSiteConnectionNode.GetConnectionManagerInstance(String connectionManagerInstance)\r\nConfigMgr Error Object:

    instance of __ExtendedStatus

    {

                    Operation = "ExecQuery";

                    ParameterInfo = "SELECT * FROM SMS_Site WHERE SiteCode = 'CLT'";

                    ProviderName = "WinMgmt";

    };

    Error Code:

    ProviderLoadFailure

    \r\nSystem.Management.ManagementException\r\nProvider load failure \r\n   at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)

       at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()

      at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryResultsObject.<GetEnumerator>d__0.MoveNext()\r\nManagementException details:

    instance of __ExtendedStatus

    {

                    Operation = "ExecQuery";

                    ParameterInfo = "SELECT * FROM SMS_Site WHERE SiteCode = 'CLT'";

                    ProviderName = "WinMgmt";

    };

    \r\n

    Ideas?

    Tuesday, February 19, 2013 2:30 PM
  • One thing I just noticed, the SiteCode=CLT. This same server used to run SCCM 2007 and that was the site code.

    This server was running SCCM 2012 with the SiteCode 001. I am looking at this thread, and seeing what I can do to ensure this old site code is gone completely and that 001 is the only SiteCode referenced.

    http://social.technet.microsoft.com/Forums/nl-NL/configmanagergeneral/thread/f1849892-dc1d-4a98-a250-8b2e4e766be3

    Tuesday, February 19, 2013 3:54 PM
  • I ended up having to Uninstall the site and re-install the site. Then I had to go back in and configure all the roles, security, client settings, etc. 
    • Marked as answer by Gabriel Beaver Thursday, February 21, 2013 10:21 PM
    Thursday, February 21, 2013 10:21 PM