In-Place Upgrade fails

I am trying to upgrade my Windows 8.1 Enterprise x64 to the Windows 10 Tech Preview for Enterprise. I have a USB with setup. I run setup, it says everything's fine, it starts setup. After reboot, it gets to Setting up...it gets to 79% and then just sits
there for a long time.
Eventually, it restarts, reverts me back to my Windows 8.1 and gives the attached error image.  Can anyone let me know how I can troubleshoot this?  Thanks!
Michael R.
Michael Reinders, MCITP:Enterprise Administrator Tushaus Computer Services

Hi Michael R.
Sometimes, a few devices and services would stop the installation, so we suggest to disable or remove unnecessary items.
Glad you have installed successfully. Enjoy it.
Alex Zhao
TechNet Community Support

Similar Messages

  • In place upgrade to 2012 R2 fails, Setup can't continue. Your computer will now restart, and your previous version of windows will be restored.

    
    I have multiple Windows Server 2008 R2 machines in which I am attempting to do an in place upgrade to 2012 R2, and it is repeatedly failing.
    Setup gets all the way through, and it says Getting ready, followed immediately by an error saying: Setup can't continue.  Your computer will now restart, and your previous version of Windows will be restored.
    I am attempting to install:
    Windows Server 2012 R2 Datacenter (Server with GUI)
    x64 Date modified 3/18/2014
    I have found several posts, many discussing how disk space can be an issue, I have increased disk space so it shouldn't be an issue.  I have also made sure the only only partition on disk 0 is C: and system reserved.
    I have disabled all unessential services and went through and removed all unessential applications, and extras.  Still getting the error.
    Here is the update log
    2014-11-24 08:20:20:715
    888 ed8
    AU AU initiates service shutdown
    2014-11-24 08:20:20:715
    888 ed8
    AU ###########  AU: Uninitializing Automatic Updates  ###########
    2014-11-24 08:20:20:840
    888 ed8
    Report CWERReporter finishing event handling. (00000000)
    2014-11-24 08:20:20:840
    888 ed8
    Service *********
    2014-11-24 08:20:20:840
    888 ed8
    Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2014-11-24 08:20:20:840
    888 ed8
    Service *************
    2014-11-24 08:23:27:265
    892 9a0
    Misc ===========  Logging initialized (build: 7.6.7600.320, tz: -0500)  ===========
    2014-11-24 08:23:27:281
    892 9a0
    Misc  = Process: C:\Windows\system32\svchost.exe
    2014-11-24 08:23:27:281
    892 9a0
    Misc  = Module: c:\windows\system32\wuaueng.dll
    2014-11-24 08:23:27:265
    892 9a0
    Service *************
    2014-11-24 08:23:27:281
    892 9a0
    Service ** START **  Service: Service startup
    2014-11-24 08:23:27:281
    892 9a0
    Service *********
    2014-11-24 08:23:27:635
    892 9a0
    Agent  * WU client version 7.6.7600.320
    2014-11-24 08:23:27:635
    892 9a0
    Agent  * Base directory: C:\Windows\SoftwareDistribution
    2014-11-24 08:23:27:635
    892 9a0
    Agent  * Access type: No proxy
    2014-11-24 08:23:27:635
    892 9a0
    Agent  * Network state: Connected
    2014-11-24 08:24:14:827
    892 9a0
    Report CWERReporter::Init succeeded
    2014-11-24 08:24:14:827
    892 9a0
    Agent ***********  Agent: Initializing Windows Update Agent  ***********
    2014-11-24 08:24:14:827
    892 9a0
    Agent  * Prerequisite roots succeeded.
    2014-11-24 08:24:14:827
    892 9a0
    Agent ***********  Agent: Initializing global settings cache  ***********
    2014-11-24 08:24:14:827
    892 9a0
    Agent  * WSUS server: <NULL>
    2014-11-24 08:24:14:827
    892 9a0
    Agent  * WSUS status server: <NULL>
    2014-11-24 08:24:14:827
    892 9a0
    Agent  * Target group: (Unassigned Computers)
    2014-11-24 08:24:14:827
    892 9a0
    Agent  * Windows Update access disabled: No
    2014-11-24 08:24:14:951
    892 9a0
    DnldMgr Download manager restoring 0 downloads
    2014-11-24 08:24:14:981
    892 9a0
    AU ###########  AU: Initializing Automatic Updates  ###########
    2014-11-24 08:24:14:997
    892 9a0
    AU  # AU disabled through Policy
    2014-11-24 08:24:14:997
    892 9a0
    AU  # Will interact with non-admins (Non-admins are elevated (User preference))
    2014-11-24 08:24:15:043
    892 9a0
    AU Initializing featured updates
    2014-11-24 08:24:15:043
    892 9a0
    AU Found 0 cached featured updates
    2014-11-24 08:24:15:397
    892 9a0
    Report ***********  Report: Initializing static reporting data  ***********
    2014-11-24 08:24:15:397
    892 9a0
    Report  * OS Version = 6.1.7601.1.0.196880
    2014-11-24 08:24:15:397
    892 9a0
    Report  * OS Product Type = 0x00000007
    2014-11-24 08:24:15:428
    892 9a0
    Report  * Computer Brand = VMware, Inc.
    2014-11-24 08:24:15:428
    892 9a0
    Report  * Computer Model = VMware Virtual Platform
    2014-11-24 08:24:15:428
    892 9a0
    Report  * Bios Revision = 6.00
    2014-11-24 08:24:15:428
    892 9a0
    Report  * Bios Name = PhoenixBIOS 4.0 Release 6.0     
    2014-11-24 08:24:15:428
    892 9a0
    Report  * Bios Release Date = 2013-07-30T00:00:00
    2014-11-24 08:24:15:428
    892 9a0
    Report  * Locale ID = 1033
    2014-11-24 08:24:15:582
    892 9a0
    AU Successfully wrote event for AU health state:0
    2014-11-24 08:24:15:582
    892 9a0
    AU Successfully wrote event for AU health state:0
    2014-11-24 08:24:15:582
    892 9a0
    AU AU finished delayed initialization
    2014-11-24 08:24:20:865
    892 6a0
    Report CWERReporter finishing event handling. (00000000)
    2014-11-24 08:55:38:187
    892 9a0
    AU AU initiates service shutdown
    2014-11-24 08:55:38:187
    892 9a0
    AU ###########  AU: Uninitializing Automatic Updates  ###########
    2014-11-24 08:55:38:250
    892 9a0
    Report CWERReporter finishing event handling. (00000000)
    2014-11-24 08:55:38:297
    892 9a0
    Service *********
    2014-11-24 08:55:38:297
    892 9a0
    Service **  END  **  Service: Service exit [Exit code = 0x240001]
    2014-11-24 08:55:38:297
    892 9a0
    Service *************
    Any ideas on how I can resolve this, or further troubleshoot?

    I also had this error: "Setup cannot continue. Your computer will now restart, and your previous version of Windows will be restored."
    trying to do a in-place upgrade of a Domain Controller Windows 2008 R2 to Windows 2012 R2.
    The problem was the separated System Reserved Partition. After I removed using this instructions:
    http://jacobackerman.blogspot.com/2012/12/how-to-remove-system-reserved-partition.html
    The upgrade ran ok, and now have my DC as Windows 2012 R2.
    Hope that helps!.

  • "Windows 8.1 installation has failed" - in-place upgrade to Windows 8.1 U1

    I am unable to upgrade my toshiba laptop that has Windows 8 to Windows 8.1 U1. I am getting an error message at 37% or 39% through the upgrade process and am met with an error message similar to this:
     Ignore the 96%, but this is the same exact error message I am getting each time I try to do an in-place upgrade of Windows 8.1 U1 Pro.
    I am currently running Windows 8 Pro on my laptop. I have the .cbs log file contents here:
    http://pastebin.com/52QpQzZA
    I really would like to do an in-place upgrade and not have to re-configure all the apps and their settings again. What could be causing this failure?

    I have seem to have figured out the problem after some trial and error.
    First, I followed another user's solution about turning off Windows Update service before I performed the Windows 8.1 Upgrade via USB flash drive.
    Second, my mistake here was I was upgrading Windows 8 to Windows 8.1 U1. When I tried upgrading Windows 8 to
    Windows 8.1, it finally worked without issue.
    Either I was upgrading two versions ahead that made the Windows Upgrade process fail each time or it had something to do with Windows Update service being on during the upgrade process.
    It has completed without failure!
    Thank you for your replies!

  • In-place upgrade of Windows Server 2012 RDS to R2 fails

    Hi All
    I have a Server 2012 Standard RDS virtual machine (vmware) on which I have tried doing an in-place upgrade to 2012 R2 but it constantly fails.
    It sits at the "Collecting files, settings and applications" process for quite a while - always on 0% and then says: Installing Windows was Canceled "Setup can't continue. Restart the computer and restart Setup. When prompted, try getting
    the latest updates."
    I have tried combinations of all the settings during setup to look for updates, not look for updates, etc., rebooted several times, even disabled the RDS services and still the same result.
    As a test, I tried doing an in-place upgrade on the base OS installation that was used to create this VM and it works perfectly. The only difference between the servers is that the live has RDS role installed.
    Is there any Microsoft documentation on the 2012 RDS in-place upgrade process to R2?
    Can anyone offer any suggestion as to why the in-place upgrade might be failing with the RDS role installed?
    Thanks heaps

    As I stated I have already tried an in-place upgrade on the base 2012 vm that I used to create the production RDP server and it worked.
    It seems that the RDS role may be preventing the upgrade?
    Ideally I want to go down the in-place upgrade on the production server as we have alot of users using this machine. I would rather not have to build an R2 RDS server from scratch.
    if you really think the RDS is preventing the upgrade, how about stopping the RDS service then do an in place upgrade.
    check how it goes.. :)
    Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.

  • In-Place Upgrade using SCCM Fails (W7 to W10)

    I'm trying to troubleshoot attempting to perform an in-place upgrade using SCCM (following the blog posted by the SCCM Team).
    I started with a fresh build of an HP z620 using our standard corporate Windows 7 64bit Enterprise (SP1) build.
    My first attempt just hung after rebooting into WinPE.  It was able to complete the "Getting Ready" step but then would go no further.  In fact it sat at that boot screen for most of the weekend.
    I found a forum post that suggested running SCF/SCANNOW to make sure that all the system files were intact.  I did this and attempted it again.  This time a Windows 10 "Your PC ran into a problem" flashed briefly and then it rebooted
    and rolled back to Windows 7.
    Any suggestions on where I should look?  I've been testing this task sequence on a Hyper-V VM using the same corporate image and it works fine.  My gut keeps telling me it's driver related, but I don't know if I'm just jumping to conclusions.

    On Mon, 1 Dec 2014 17:42:41 +0000, mmarable wrote:
    I'm trying to troubleshoot attempting to perform an in-place upgrade using SCCM (following the blog posted by the SCCM Team).
    You should post a comment on the blog about this and ask them where to post
    for support on this issue.
    The only officially supported methods are using the ISO or Windows Update.
    Paul Adare - FIM CM MVP
    I'm not a luser laser, I'm a luser laser's mate, and I'm only lasing
    lusers 'cause the luser laser's late.. or something.. -- Gid Holyoake

  • Rule "SQL Server 2012 feature Upgrade" Failed

    I am doing an in-place upgrade of SQL Server 2008 R2 SP2 > SQL Server 2012 SP1, both 64-bit, installed on Windows Server 2008 R2.
    I ran the SQL Server Upgrade Advisor tool prior to upgrade which reported no issues.
    The error I am getting is:
    In the detailed.txt log I can see the following:
    (11) 2013-12-29 12:28:10 Slp: Initializing rule      : SQL Server 2012 Feature Upgrade
    (11) 2013-12-29 12:28:10 Slp: Rule is will be executed  : True
    (11) 2013-12-29 12:28:10 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.SkuUpgradeRule
    (11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' looking for previous version upgrade data for feature package 'sql_as_Cpu64'.
    (11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Found feature package  'sql_as_ctp6_Cpu64' with SkuValue=ENTERPRISE (Enterprise) ProductVersion=10.52.4000.0
    (11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' found sourceVersion 10.0 and edition ENTERPRISE for feature package 'sql_as_Cpu64'.
    (11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix checking sku matrix for sourceVersion=10.0 sourceEdition=ENTERPRISE (Enterprise) sourceArchitecture=X64 targetEdition=STANDARD (Standard) targetArchitecture=X64
    (11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix source and target architecture match.
    (11) 2013-12-29 12:28:10 Slp: -- SkuPublicConfigObject : ValidateSkuMatrix did not find a match in sku matrix .
    (11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' feature package 'sql_as_Cpu64' is blocking upgrade.
    (11) 2013-12-29 12:28:10 Slp: -- SkuUpgradeRule : Rule 'FeatureUpgradeMatrixCheck' detection result: IsValidFeatureUpgrade=False
    (11) 2013-12-29 12:28:10 Slp: Evaluating rule        : FeatureUpgradeMatrixCheck
    (11) 2013-12-29 12:28:10 Slp: Rule running on machine: TAUPE-SERVER
    (11) 2013-12-29 12:28:10 Slp: Rule evaluation done   : Failed
    (11) 2013-12-29 12:28:10 Slp: Rule evaluation message: The specified edition upgrade is not supported. For information about supported upgrade paths, see the SQL Server 2012 version and edition upgrade in Books Online.
    (11) 2013-12-29 12:28:10 Slp: Send result to channel : RulesEngineNotificationChannel
    Prior to upgrade:
    From Summary.txt file:
    Overall summary:
      Final result:                  Passed
      Exit code (Decimal):           0
      Start time:                    2013-12-29 12:04:28
      End time:                      2013-12-29 12:08:02
      Requested action:              RunRules
    Machine Properties:
      Machine name:                  TAUPE-SERVER
      Machine processor count:       1
      OS version:                    Windows Server 2008 R2
      OS service pack:               Service Pack 1
      OS region:                     United States
      OS language:                   English (United States)
      OS architecture:               x64
      Process architecture:          64 Bit
      OS clustered:                  No
    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services                
    1033                 Enterprise Edition   10.52.4000.0    No       
      SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text and Semantic Extractions for Search 1033                
    Enterprise Edition   10.52.4000.0    No       
      SQL Server 2008 R2   MSSQLSERVER          MSAS10_50.MSSQLSERVER          Analysis Services                       
    1033                 Enterprise Edition   10.52.4000.0    No       
      SQL Server 2008 R2   MSSQLSERVER          MSRS10_50.MSSQLSERVER          Reporting Services - Native             
    1033                 Enterprise Edition   10.52.4000.0    No       
      SQL Server 2008 R2                                                      
    Management Tools - Basic                 1033                 Enterprise Edition   10.52.4000.0   
    No       
      SQL Server 2008 R2                                                      
    Management Tools - Complete              1033                 Enterprise Edition   10.52.4000.0   
    No       
      SQL Server 2008 R2                                                      
    Client Tools Connectivity                1033                 Enterprise Edition   10.52.4000.0   
    No       
    Package properties:
      Description:                   Microsoft SQL Server 2012
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      Installation location:        
    \\dovekie\drop\TFS2013\SQLServer2012SP1\x64\setup\
      Installation edition:          Standard
      Slipstream:                    True
    User Input Settings:
      ACTION:                        RunRules
      CONFIGURATIONFILE:            
      ENU:                           true
      FEATURES:                     
      HELP:                          false
      IACCEPTSQLSERVERLICENSETERMS:  false
      INDICATEPROGRESS:              false
      INSTANCENAME:                  <empty>
      PID:                           *****
      QUIET:                         false
      QUIETSIMPLE:                   false
      RULES:                         GlobalRules
      UIMODE:                        Normal
      X86:                           false
      Configuration file:            C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131229_120425\ConfigurationFile.ini
    Rules with failures:
    Global rules:
    There are no scenario-specific rules.
    Rules report file:               C:\Program Files\Microsoft SQL Server\110\Setup Bootstrap\Log\20131229_120425\SystemConfigurationCheck_Report.htm
    As far as I'm aware, the upgrade path I am following is a supported one, any suggestions will be much appreciated!
    Thank you.

    Product features discovered:
      Product              Instance             Instance ID                   
    Feature                                  Language            
    Edition              Version         Clustered
      SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Database Engine Services                
    1033                 Enterprise Edition   10.52.4000.0    No       
      SQL Server 2008 R2   MSSQLSERVER          MSSQL10_50.MSSQLSERVER         Full-Text and Semantic Extractions for Search 1033                
    Enterprise Edition   10.52.4000.0    No       
      SQL Server 2008 R2   MSSQLSERVER          MSAS10_50.MSSQLSERVER          Analysis Services                       
    1033                 Enterprise Edition   10.52.4000.0    No       
      SQL Server 2008 R2   MSSQLSERVER          MSRS10_50.MSSQLSERVER          Reporting Services - Native             
    1033                 Enterprise Edition   10.52.4000.0    No       
      SQL Server 2008 R2                                                      
    Management Tools - Basic                 1033                 Enterprise Edition   10.52.4000.0   
    No       
      SQL Server 2008 R2                                                      
    Management Tools - Complete              1033                 Enterprise Edition   10.52.4000.0   
    No       
      SQL Server 2008 R2                                                      
    Client Tools Connectivity                1033                 Enterprise Edition   10.52.4000.0   
    No       
    Package properties:
      Description:                   Microsoft SQL Server 2012
      ProductName:                   SQL Server 2012
      Type:                          RTM
      Version:                       11
      Installation location:        
    \\dovekie\drop\TFS2013\SQLServer2012SP1\x64\setup\
      Installation edition:          Standard
      Slipstream:                    True
    User Input
    Hello ,
    You are trying to upgrade to SQL 2012 standard edition which is not supported .you can only upgrade from SQL server 2008 R2 Sp2 Enterprise edition to SQL 2012 Enterprise or business intellgience. see below link for supported upgrade paths
    http://technet.microsoft.com/en-us/library/ms143393.aspx
    If you want to move ahead you should try Side by side approach.Create new SQL server 2012 box and restore backup.
    Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

  • How can I perform an "in-place upgrade" on an unbootable Windows 7 machine or at least rebuild Safe Mode?

    Some strange glitch has erased every single unlocked & unprotected file on my C: drive. It wasn't a virus because I checked autorun records and running processes using the respective Sysinternals utilities and didn't find anything suspicious.
    I restored all data except for some system files and files that had "too long" of a path using shadow copies, which luckily for me were just a few hours old. Then, I decided to reboot into Recovery Environment and run System Restore from there. For even
    more strange reason, the available restore points in RE were dated November 2010 (it's May 2012 right now) and the recent save dates are nowhere to be found.
    To make matters worse, SFC doesn't work and Safe Mode shows BSOD after loading CLASSPNP.SYS.
    Error messages so far:
    RE's startup repair tool: System files integrity check and repair error code 0x2
    SFC: Windows Resource Protection could not perform the requested operation
    BSOD: 0x7B (0xFFFFF880009A9928, 0XFFFFFFFFC0000034, 0x0, 0x0), but the HDD is perfectly fine - it's a dual-boot machine
    CBS.log: Failed to get CSI store. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
    What I need is a way to perform either an in-place upgrade without booting into Windows, or a way to fix the SXS Component Store, or rebuild the Safe Mode so that I could initiate upgrade install from there. A clean install isn't an option because I don't
    have the luxury of time to run through the reboot cycles when re-installing and updating other software (I'm using Windows 8 CP for now as my work tools are mostly in the cloud).

    "Den B" wrote in message news:9528356a-7e8f-45bf-9eee-30b40b5df4aa...
    Some strange glitch has erased every single unlocked & unprotected file on my C: drive. It wasn't a virus because I checked autorun records and running processes using the respective Sysinternals utilities and didn't find anything suspicious.
    I restored all data except for some system files and files that had "too long" of a path using shadow copies, which luckily for me were just a few hours old. Then, I decided to reboot into Recovery Environment and run System Restore from there. For even
    more strange reason, the available restore points in RE were dated November 2010 (it's May 2012 right now) and the recent save dates are nowhere to be found.
    To make matters worse, SFC doesn't work and Safe Mode shows BSOD after loading CLASSPNP.SYS.
    Error messages so far:
    RE's startup repair tool: System files integrity check and repair error code 0x2
    SFC: Windows Resource Protection could not perform the requested operation
    BSOD: 0x7B (0xFFFFF880009A9928, 0XFFFFFFFFC0000034, 0x0, 0x0), but the HDD is perfectly fine - it's a dual-boot machine
    CBS.log: Failed to get CSI store. [HRESULT = 0x80073712 - ERROR_SXS_COMPONENT_STORE_CORRUPT]
    What I need is a way to perform either an in-place upgrade without booting into Windows, or a way to fix the SXS Component Store, or rebuild the Safe Mode so that I could initiate upgrade install from there. A clean install isn't an option because I don't
    have the luxury of time to run through the reboot cycles when re-installing and updating other software (I'm using Windows 8 CP for now as my work tools are mostly in the cloud).
    It is not possible to do a repair install of a system unless you can boot to the system.
    Have you checked the hard drive for problems? - download the manufacturer's test utility, create the disk, and run the extended checks.
    Noel Paton | Nil Carborundum Illegitemi |
    CrashFixPC | The Three-toed Sloth

  • SCOM 2012 R2 agent upgrade fails crippling agents

    Running into a large amount of SCOM agents that are failing the upgrade from 2012 SP1 to R2 and would appreciate any feedback from my SCOM community colleagues.  Warning this issue is not for the faint of heart. 
    Plan:
    I am in the process of upgrading 1900 manually installed SCOM 2012 SP1 agents to R2.  I am using SCCM to deliver the upgrade using the standard sanctioned upgrade parameters. 
    Momagent.msi /qn /l*v %SystemDrive%\SCOM2012AgentUpgrade.log AcceptEndUserLicenseAgreement=1
    Problem:
    I have run into a problem where on a larger group of systems, 165 servers, where the upgrade fails and leaves the agent in a crippled state.  At this point the agent cannot be removed cleanly via add remove, nor can a straight install of the agent
    be done.  What is required is a manual removal of registry keys and then a clean install of the agent can be performed to remediate.  This is no problem and I am able to do this.  (Note: all other methods of agent removal did not work ie:
    Cleanmom.exe utility or add remove)
    Task:
    Seeing that we need to do agent upgrades in the future it would be great to know why this happened so we can plan for this in the future.
    Notes:
    Seems like a random sample of servers (2003/2008) with different applications running on them so that doesn't help in narrowing things down. 
    Looking at the MSI log, I see a common issue among systems that had this problem.
    ******* Product: {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
               ******* Action:
               ******* CommandLine: **********
    MSI (s) (7C:7C) [08:08:43:668]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (7C:7C) [08:08:43:668]: User policy value 'DisableMedia' is 0
    MSI (s) (7C:7C) [08:08:43:668]: Machine policy value 'AllowLockdownMedia' is 0
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media enabled only if package is safe.
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Looking for sourcelist for product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Adding {387306D9-78CE-4E0E-B952-28A50CC8B3EE}; to potential sourcelist list (pcode;disk;relpath).
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Now checking product {387306D9-78CE-4E0E-B952-28A50CC8B3EE}
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Media is enabled for product.
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Trying source C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\.
    MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 2203 2: C:\WINDOWS\SysWOW64\CCM\Cache\LFG00446.1.System\i386\MOMAgent.msi 3: -2147287037
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
    MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing net source list.
    MSI (s) (7C:7C) [08:08:43:668]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
    MSI (s) (7C:7C) [08:08:43:668]: SOURCEMGMT: Processing media source list.
    MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 2203 2:  3: -2147287037
    MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
    MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
    MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Processing URL source list.
    MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1402 2: UNKNOWN\URL 3: 2
    MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2: -2147483647 3: MOMAgent.msi
    MSI (s) (7C:7C) [08:08:44:744]: Note: 1: 1706 2:  3: MOMAgent.msi
    MSI (s) (7C:7C) [08:08:44:744]: SOURCEMGMT: Failed to resolve source
    MSI (s) (7C:8C) [08:08:44:744]: Note: 1: 1714 2: Microsoft Monitoring Agent 3: 1612
    CustomAction  returned actual error code 1612 (note this may not be 100% accurate if translation happened inside sandbox)
    MSI (s) (7C:8C) [08:08:44:744]: Product: Microsoft Monitoring Agent -- Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
    Error 1714.The older version of Microsoft Monitoring Agent cannot be removed. Contact your technical support group. System Error 1612.
    Action ended 8:08:44: RemoveExistingProducts. Return value 3.
    Action ended 8:08:44: INSTALL. Return value 3.
    Ok so the obvious is that the installer is looking for original source installation files and not able to find them. What is surprising to me however is that the product references a 32 bit scom agent guid
    387306D9-78CE-4E0E-B952-28A50CC8B3EE, however this is a 64 bit machine.  Our build process dictates that a 64 bit machine only receive a 64 bit SCOM agent. 
    Doing a search on this product guid I realized I skipped some other references at the top of the MSI log that might offer some more explanation...
    MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_OM12_SP1_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
    MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Modifying OM_OM12_SP1_AGENT_FOUND property. Its current value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'. Its new value: '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
    MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
    MSI (s) (7C:8C) [08:08:11:896]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
    MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_OM_AGENT_FOUND
    Action ended 8:08:11: FindRelatedProducts. Return value 1.
    MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding OM_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
    Action start 8:08:11: _Set_OM_AGENT_FOUND.
    MSI (s) (7C:8C) [08:08:11:896]: Doing action: _Set_MOMV3_AGENT_FOUND
    Action ended 8:08:11: _Set_OM_AGENT_FOUND. Return value 1.
    MSI (s) (7C:8C) [08:08:11:896]: PROPERTY CHANGE: Adding MOMV3_AGENT_FOUND property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330};{387306D9-78CE-4E0E-B952-28A50CC8B3EE}'.
    Action start 8:08:11: _Set_MOMV3_AGENT_FOUND.
    Well that is interesting, seems to me that in the first line the MSI installer reads the OM_OM12_SP1_AGENT_FOUND property and identifies this with a  64 bit agent guid (8B21425D-02F3-4B80-88CE-8F79B320D330), but then appends
    the 32 bit guid at the end (387306D9-78CE-4E0E-B952-28A50CC8B3EE).  This is the point of my confusion and my suspicion as the cause of the problem I am having. 
    Concluding thoughts:
    Why does the installer seems to first recognizes a 64 bit agent, but then later changes it's property to include a 32 bit agent guid.  Could a 32 bit agent have got on this 64 bit server based on the details of this log?  Would this
    cause my agents to fail the upgrade?  I think so, but looking to bounce this over to another fellow SCOM colleague who may have wrestled with this before.
    Thanks in advance if you took the time to read this and think about it.  Extra points if you have any extra thoughts!
    Keith

    Hi,
    Have you used Requirement to limit the platform when you deploy application with SCCM.
    We
    are trying to better understand customer views on social support experience, so your participation in this
    interview project would be greatly appreciated if you have time.
    Thanks for helping make community forums a great place.

  • I receive message the CC desktop needs to upgrade and the upgrade fails to complete

    I have tried many times and the upgrade fails at the same place, almost to the far right end of the progress bar. I have downloaded to my PC and tried from there as well as the automatic upgrade the happens when I try to acces CC desktop. I'm running Win 8.1

    Did anything download or are you getting this when trying to install?
    Try booting into the Safe Mode and do the installation there.
    Safe Mode
    Safe Mode - About
    There are various suggestions in this discussion. You might start with the last post first.
    https://discussions.apple.com/thread/4136660?start=30&tstart=0

  • PI 2.0 to 2.1 Upgrade Fail

    Upgrade failed. Output states:
    ERROR: The last upgrade operation was unsuccessful. See dbadmin_StdOut.log for details. To recover, reinstall the server and restore the saved backup data.
    % Pre-install step failed. Please check the logs for more details.
    I cannot find this log anywhere. I cannot reinstall as it gives me the same error. No documents reference this file or log directory on the PI VM. Any help? Anyone seen this before?

    Hi ,
    was HA configured before on PI 2.0 ?
    If yes remove the HA config from Both primary and secondary (ncs ha remove )  then try the upgrade.
    I also suspect that something wrong can happen  during file transfer from ftp server .
    place the upgrade file locally on the NCS server and then try the upgrade .
    You can place the file under /localdisk/defaultRepo/ .
    You need to login as root first then you will be able place the file into this directory below .
    PI20-1/admin#
    PI20-1/admin# root
    Enter root password :
    Starting root bash shell ...
    ade #
    ade #
    ade # cd /
    ade # cd /localdisk/defaultRepo/
    ade #
    After that , you can transfer the file from your ftp server to your NCS server.
    Now,  you can perform the upgrade locally using console
    application upgrade PI-Upgrade-2.x.x.x.x.x.x.gz defaultRepo
    and lastly , the file it is pointing to ,it bydeafault location is :/opt/CSCOlumos/logs/
    Thanks-
    Afroz
    ***Ratings Encourages Contributors ****

  • SCSM 2012 R2 - In-Place Upgrade to Windows Server 2012 R2

    Hello,
    is an in-place upgrade of the underlying OS from Windows Server 2012 to Windows Server 2012 R2 supported by SCSM 2012R2. I know of some products where it is supported, some where it isn't (e.g. Exchange) but I haven't found any information on SCSM (Management,
    DW, SQL, DWSQL).
    Thank you in advance.
    Regards
    Sascha

    i would never recommend upgrading the OS on any production environment, especially you have any virtualization and can stand up the new OS on the same hardware. 
    that being said, i don't see any obvious reason this would fail, but i don't thing it would be obviously supported either. 

  • Upgrade Windows Server 2012 to Windows Server 2012 R2 in-place upgrade

    I have tried to do an in place upgrade for Windows Server 2012 Standard to Windows Server 2012 R2 using the in-place upgrade at least a dozen times. Always with the same unhelpful failure message. 
    I have tried downloading the latest (setup) update and not downloading it - makes no difference - same error.
    I would really rather upgrade this server than re-install. I have scoured the internet looking for answers and I can't find anything useful. 
    I have downloaded the latest 2012 R2 Standard iso. The version of 2012 installed is a stock retail Standard version it was never an eval version.
    Any help much appreciated.
    Andy

    I did check the article. I did the ADPREP as described and adprep worked fine. Unfortunately it did not make any difference. Log entries below:
    setupact
    2014-05-28 07:56:56, Info                  MIG    End of hive list
    2014-05-28 07:56:56, Warning    [0x0803db] MIG    IndirectKeyMapper: RegLoadKey(HKEY_USERS,S-1-5-21-902023783-652776199-2643897273-500 (1),C:\Users\Administrator\NTUSER.DAT) failed; giving up (32)
    2014-05-28 07:56:56, Error      [0x08039d] MIG    Cannot add mapping for user profile C:\Users\Administrator. Error: 32: Win32Exception: The process cannot access the file because it is being used by another process. [0x00000020] __cdecl
    Mig::CIndirectKeyMapper::CIndirectKeyMapper(class UnBCL::String *,struct HKEY__ *,class UnBCL::String *,class UnBCL::String *,int,int,const Mig::HiveLoadRetryOptions *)[gle=0x000000cb]
    2014-05-28 07:56:56, Error      [0x080801] MIG    User profile loading error. Aborting due to external request.[gle=0x000000cb]
    2014-05-28 07:56:56, Warning    [0x0803de] MIG    Failed to unload hive at HKEY_LOCAL_MACHINE\$ONLINE_RW$ELAM (error 1314)
    2014-05-28 07:56:56, Warning    [0x0809d4] MIG    Failed to close keymapper 'ELAM': error 1314
    2014-05-28 07:56:56, Warning    [0x0803de] MIG    Failed to unload hive at HKEY_LOCAL_MACHINE\$ONLINE_RW$ELAM (error 1314)
    2014-05-28 07:56:56, Error                        MigStartupOnline caught exception: Win32Exception: User profile loading error. Aborting due to external request.: The specified user does not have
    a valid profile. [0x000004E5] void __cdecl Mig::COnlineWinNTPlatform::ProcessUser(class Mig::CRegistryDataStore *,class Mig::CRegistryDataUnit *,class UnBCL::String *,class UnBCL::String *,int,int)
    2014-05-28 07:56:56, Info                         Leaving MigStartupOnline method
    2014-05-28 07:56:56, Error                 MIG    pDoOnlineGather: Engine initialization failed with error: 0x00000004
    2014-05-28 07:56:56, Error      [0x0800ad] MIG    Callback_GatherOldSys: Migration phase failed.
    2014-05-28 07:56:56, Info                  MIG    PublishCriticalError: Setup can't continue. Restart the computer and restart Setup. When prompted, try getting the latest updates.
    2014-05-28 07:56:56, Info       [0x0a013d] UI     Accepting Cancel. Exiting Page Progress.
    2014-05-28 07:56:56, Info                  UI     Entering Page Cancel.
    2014-05-28 07:56:56, Info       [0x0a0035] UI     Allowing Page 'App Compat' to be shown
    2014-05-28 07:56:56, Info       [0x0a0035] UI     Allowing Page 'App Compat' to be shown
    2014-05-28 07:56:56, Info       [0x0a011c] UI     WizardDialogPost::SetActive
    2014-05-28 09:17:28, Info       [0x070042] DIAG   CallBack_DiagnosticDataSend: Called with notification for Error published by ErrorHandler
    2014-05-28 09:17:28, Info       [0x0a0023] UI     progress task ProgressInfo\SendDiagnostics : StartProgress
    2014-05-28 09:17:28, Info                  DIAG   DiagnosticDataSendWorker: Phase=1 Start time was 0X309961825, End time was 0X309962C98, total time was 0X1473
    2014-05-28 09:17:28, Info       [0x070044] DIAG   DiagnosticDataSendWorker: startSetupTimeInSecs = 0X309962634
    2014-05-28 09:17:28, Info       [0x070045] DIAG   Processing Diagnostic data at 2014-05-28 09:17:28
    2014-05-28 09:17:28, Info       [0x070046] DIAG   DiagnosticDataSendWorker: endSetupTimeInSecs = 0X309963AA8
    2014-05-28 09:17:28, Info                  DIAG   DiagnosticDataSendWorker: setupInstallTime = 0X1474
    2014-05-28 09:17:28, Info                  DIAG   DiagnosticDataSendWorker: User is NOT OPTED-IN for SQM and Watson.
    2014-05-28 09:17:28, Info       [0x0a0024] UI     progress task ProgressInfo\SendDiagnostics : EndProgress
    2014-05-28 09:17:28, Info       [0x090095] PANTHR WdsExitImmediate called!  Execution will stop, and the queue won't be saved.
    2014-05-28 09:17:28, Info                  DIAG   Module path is [C:\$WINDOWS.~BT\Sources\setup.exe]
    2014-05-28 09:17:28, Info                  DIAG   Module version is [6.3.9600.16384 (winblue_rtm.130821-1623)]
    2014-05-28 09:17:28, Info                  DIAG   Module path is [C:\$WINDOWS.~BT\Sources\setup.exe]
    2014-05-28 09:17:28, Info                  DIAG   Failed install count for build [6.3.9600.16384 (winblue_rtm.130821-1623)] is [12]
    2014-05-28 09:17:28, Info                  IBS    Successfully incremented the failed install count on this machine
    2014-05-28 09:17:28, Info       [0x0800af] MIG    Leaving Callback_GatherOldSys (failure)
    2014-05-28 09:17:28, Info       [0x09008c] PANTHR SeqExecute -- stopping, since WdsExitImmediate() was called
    2014-05-28 09:17:28, Info       [0x090086] PANTHR pWorkerThreadFunc -- Stopping
    2014-05-28 09:17:28, Info       [0x090086] PANTHR pWorkerThreadFunc -- Stopping
    2014-05-28 09:17:28, Info       [0x090086] PANTHR pWorkerThreadFunc -- Stopping
    2014-05-28 09:17:28, Info                  PANTHR DeleteCriticalSection for pExecQueue->csLock;
    2014-05-28 09:17:28, Info       [0x0500bd] DU     Module_Term_DU called
    2014-05-28 09:17:28, Info       [0x050081] DU     Done with DU. DUMgr is cleaning up...
    2014-05-28 09:17:28, Info       [0x050082] DU     Cleanup completed
    2014-05-28 09:17:28, Info       [0x0605a6] IBS    Requested UI to hide the language and locale selection pages.
    2014-05-28 09:17:28, Info       [0x06010d] IBS    Module_Term_Productkey: Valid product key in blackboard, show property set to hide.
    2014-05-28 09:17:28, Info                  UI     CallbackWin32UITerminate: Deleted WizardUI
    2014-05-28 09:17:28, Info       [0x090081] PANTHR Destroying any unreferenced modules! (SEQ6)
    2014-05-28 09:17:28, Info       [0x0601d7] IBS    InstallWindows:Error Type = 3211266
    2014-05-28 09:17:28, Info       [0x090009] PANTHR CBlackboard::Close: c:\$windows.~bt\sources\panther\setupinfo.
    setuperr
    2014-05-28 07:56:56, Error      [0x08039d] MIG    Cannot add mapping for user profile C:\Users\Administrator. Error: 32: Win32Exception: The process cannot access the file because it is being used by another process. [0x00000020] __cdecl
    Mig::CIndirectKeyMapper::CIndirectKeyMapper(class UnBCL::String *,struct HKEY__ *,class UnBCL::String *,class UnBCL::String *,int,int,const Mig::HiveLoadRetryOptions *)[gle=0x000000cb]
    2014-05-28 07:56:56, Error      [0x080801] MIG    User profile loading error. Aborting due to external request.[gle=0x000000cb]
    2014-05-28 07:56:56, Error                        MigStartupOnline caught exception: Win32Exception: User profile loading error. Aborting due to external request.: The specified user does not have
    a valid profile. [0x000004E5] void __cdecl Mig::COnlineWinNTPlatform::ProcessUser(class Mig::CRegistryDataStore *,class Mig::CRegistryDataUnit *,class UnBCL::String *,class UnBCL::String *,int,int)
    2014-05-28 07:56:56, Error                 MIG    pDoOnlineGather: Engine initialization failed with error: 0x00000004
    2014-05-28 07:56:56, Error      [0x0800ad] MIG    Callback_GatherOldSys: Migration phase failed.
    Kind regards, Andy CISSP, GCIA, GCIH, GPEN, GWAPT, CSTA, CSTP Blog.InfoSecMatters.net

  • How to Perform In-Place Upgrade of Windows Vista Home Professional amd64

    I'm trying to perform an in-place upgrade of Windows Vista Home Professional amd64 but the setup process fails stating that I need to remove Windows PowerShell prior to the upgrade. 
    I didn't have http://support.microsoft.com/kb/928439 installed so I couldn't uninstall it.
    I checked Windows features and PowerShell and the ISE were listed.
    I tried removing it (via optionalfeatures.exe) but it fails with 'An error has occurred. Not all of the features were successfully changed.'
    I tried installing http://support.microsoft.com/kb/928439 then removing the Windows feature - same error as above.
    I tried installing http://support.microsoft.com/kb/947821 then removing the Windows feature - same error as above.
    I tried uninstalling http://support.microsoft.com/kb/928439 then removing the Windows feature - same error as above.
    I tried performing an in-placce upgrade again and it continues to say that Windows PowerShell needs to be removed.
    I cannot remove PowerShell (or the ISE) via ocsetup.exe as no such option exists according to http://technet.microsoft.com/en-us/library/ff716463.aspx
    I tried removing it with DISM via /online /Remove-Package /Disable-Feature, but "DISM does not support servicing Windows Vista with the /Online option."
    I tried sfc /scannow again - same 'Windows
    Resource Protection' error.
    I tried the in-place upgrade again and it still needs PowerShell to be removed.
    There have been chkdsks and reboots peppered throughout this process.
    I don't know what else to try & I  feel like I'm stuck in a possibly crazy catch 22 situation.
    Note: This is a Windows Vista Home Premium SP2 64-bit machine.
    For those that need more history on how I got here, I'm going to refer you to my 'Windows
    Resource Protection could not perform the requested operation' post in the, incorrectly categorized, Windows 7 forums.  In short:
    Whenever I run Windows updates, all the updates fail.  It doesn't matter if I do one, all or something in between - they all fail.
    I ran sfc /scannow but that fails with 'Windows
    Resource Protection could not perform the requested operation' 
    I tried performing an offline scan as well but that failed with the same 'Windows
    Resource Protection' error.
    Not sure what to do at this point and I don't know what logs would be helpful for you to review at this stage (cbs.log, windowsupdate.log, other?)

    Please try below and check if we can boot normally now.
    1.
    Boot to Recovery console2. Use the backup
    System registry hiv to replace the current hiv
    In the Recovery Console.
    In CMD, go to:
         %systemroot%\System32\Config\
    Run: ren system system.old
    Go to:
         %systemroot%\System32\Config\regback
    Run: copy
         %systemroot%\system32\config\regback\system %systemroot%\system32\config
    Restart your computer.
    After that, please try to test if the server can boot to normal mode now.
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Any updates,
    JuliusPIV?
    JuliusPIV
    Northwind Traders
    475 Points               
    10               
    2               
    0                       
    Recent Achievements           
    Forums Replies III                                           
    Forums Answerer II                                           
    Code Answerer II                                                           
    JuliusPIV's threads                               
    View Profile           
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    Apologies for the delay.  I will first try your suggestion above followed by system restore if that fails.
    I'll do this over the weekend (if not this evening) and update this post.
    Thanks!

  • Error during in place upgrade of IPAM (W2k12 to W2k12 R2) - any solution yet

    After an in-place upgrade of an IPAM server from W2k12 to W2k12 R2 and during the IPAM upgrade from ver 6.2.0.1 to ver 6.3.0.1 I receive an error:
    Failed to convert Schema
    The given key was not present in the dictionary
    Please restart the wizard to update the IPAM server
    The error.log at %windir%\WID\log has an entry of:
    Login failed for user 'NT AUTHORITY\NETWORK SERVICE' Reason: Could not find a login matching the name provided
    I've installed sql express mgmt studio on another lab IPAM server and don't see any db server logins for Network Service so it's not a surprise that the login would fail.
    I have seen other mentions of others getting this error with the reply that this is a known issue and a hotfix is on the way. Is this a known issue and is there a hotfix - or some other fix - available.
    In a related note, is there any official technical documentation re: the IPAM upgrade process such as an Operational Guide or something similar? All I have been able to locate are marketing type of documents that extol the new features in IPAM ver 6.3.0.1
    but I haven't located any technical documentation.
    Thanks

    That's sadly funny. The hotfix leads to a different error. Thankfully I'm not an end user of IPAM - which seems to me not ready for prime time and not worth the trouble. The overlapping scopes was one of the issues for me that was preventing
    a successful upgrade in my dev environment, which is nonsensical since an overlapping scope is a failover scope which is one of the selling points of wk212 r2 dhcp which IPAM is supposed to work with. As I recall you can't have reservations either.
    My prod environment, I didn't have any overlapping scopes and got rid of all reservations and the upgrade still failed so I ended up removing the IPAM feature and doing a fresh install using the WID db and then migrating to SQL using move-IpamDatabase
    (I couldn't get using a remote sql db to be seen during a fresh install thus the WID then migrate).
    Hopefully, the end users will tire of the limited functionality of IPAM and it'll fade away here and I won't have to deal with it much longer. 

  • OES2sp1 to OES2sp2 in place upgrade

    Was working with site today trying to upgrade their OES2sp1 server to OES2sp2. We where also doing a SuSE10sp2 to sp3 in place upgrade at same time. Got to the OES update portion and got the following error:
    Checking if server is ready to service requests...Name resolution failed:Error = -634
    The instance at /etc/opt/novell/eDirectory/conf/nds.conf is upgraded successfully
    ERROR: /opt/novell/eDirectory/bin/ndsconfig return value = 56
    This server is one of 8 OES2 servers in the tree, but runs his DNS/DHCP and iprint environment. He was able to abort the update and bring the server back online using a mirror disk he had prepared before the upgrade, so server is back to where it was before the we tried the upgrade. He really wants to either migrate these services off this server, or get the OES2 to latest version but can't migrate due to prerequisites require for the OES11 migration tool. Edirectory was checked before upgrade and time was in synch. We did get time synch error before we got this error in the process as well.

    Can someone close this thread out. I posted it in wrong area, should have gone under OES-Linux. I reposted it to the OES-Linux/Install section.

Maybe you are looking for