SQL 2012 SP1 not recognized by CM 2012 CU2+

Hi there,
I am currently attempting to install and configure the System Center 2012 R2 Configuration Manager onto a Windows 2012 (6.3.9600) server using SQL 2012 SP1, however when I attempt to link it to the database in the CM Install panel, it informs me that I must
link it to one of several versions of SQL that is compatible.  It directly lists SQL 2012 SP1 as an acceptable version.
My current SQL version is 11.0.3349.0 (11.0.3---.- being SP1).  The instance, FQDN, and database name are correct but this error presents every time.  
So breakdown is below:
-With Instance it presents with a connection error
-Without Instance it presents with a SQL Version error
-Account has SQL admin access
-Server is not using dynamic ports
-Firewall is disabled for testing purposes
Is there something I am missing?

Define "Account has SQL admin access"?
That statement is ambiguous at best. The exact requirement is that the account you are using to run setup must both be a local admin on the system hosting the SQL Instance and must be a sysadm in that SQL Instance. The two requirements are very different
things.
Are you trying to use a non-default instance? If so, I'm assuming it's also not listening on port 1433. In this case, you must enable the SQL Browser service so that the non-default SQL Instance can be found.
Is there a specific reason you are using a non-default, remote instance of SQL Server?
Jason | http://blog.configmgrftw.com

Similar Messages

  • Trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.

    I am trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
    It verifies the connection and then throws the error:
    The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
    WSUS Server : Windows Server 2012 R2
    Remote SQL Server: 2012 SP1 CU7 hosted on Windows Server 2012 R2
    Please let me know if anyone has experienced this issue.

    We were trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
    It verifies the connection and then throws the error:
    The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
    Same error even after rebooting the server multiple times.
    WSUS Server : Windows Server Standard2012 R2
    Remote SQL Server: Windows Server 2012 SP1 CU7 hosted on Windows Server 2012 R2
    Event ID 7000:
    The Windows Internal Database service failed to start due to the following error:
    The service did not start due to a logon failure.
    Event ID 7041
    The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
    Logon failure: the user has not been granted the requested logon type at this computer.
    Service: MSSQL$MICROSOFT##WID
    Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID
    This service account does not have the required user right "Log on as a service."
    User Action
    Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user
    right is assigned to the Cluster service account on all nodes in the cluster.
    If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated
    with this node might be removing the right.
    I found following article:
    "MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID" error when you install WID in Windows Server 2012
    http://support.microsoft.com/kb/2832204/en-us
    To work around the issue, use one of the following methods:
    Assign the Log on as a service user right to NT SERVICE\ALL SERVICES in the GPO that defines the user right.
    Exclude the computer from the GPO that defines the user right.
    We moved the SCCM server to OU where no policies were getting applied and then applied the new GPO to that OU. Restarted the server and we were able to install WSUS role.
    Regards
    PR

  • Install SQL Server 2012 SP1 on a Windows Server 2012 R2 Failover Cluster - hangs at "Running discovery on remote machine" on VMWare VSphere 5.5 Update 1

    <p>Hi,</p><p>I'm trying to install SQL Server 2012 SP1 on the first node of a Windows Server 2012 R2 failover cluster.</p><p>The install hangs whilst displaying the "Please wait while Microsoft SQL Server 2012 Servce
    Pack 1 Setup processes the current operation." message.</p><p>The detail.txt log file shows as follows:</p><p>(01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : Use cached PID<br />(01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider
    : NormalizePid is normalizing input pid<br />(01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid<br />(01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : Use cached
    PID<br />(01) 2014-07-17 15:36:35 Slp: Completed Action: FinalCalculateSettings, returned True<br />(01) 2014-07-17 15:36:35 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True<br />(01) 2014-07-17 15:36:35 Slp: ----------------------------------------------------------------------<br
    />(01) 2014-07-17 15:36:35 Slp: Running Action: RunRemoteDiscoveryAction<br />(01) 2014-07-17 15:36:36 Slp: Running discovery on local machine<br />(01) 2014-07-17 15:36:36 Slp: Discovery on local machine is complete<br />(01) 2014-07-17
    15:36:36 Slp: Running discovery on remote machine: XXX-XXX-01</p><p>After about 4 hours and 10 minutes, the step seems to time out and move on, however it doesn't seem to have discovered what it needs to and the setup subsuently fails</p><p></p>

    Hi,
    Sorry Information you provided did not helped can you post content of both summary file and details,txt file on shared location for analysis.
    Can you download Service pack again and try once more
    Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
    My TechNet Wiki Articles

  • Server 2012 R2 and DPM 2012 (ocsetup not recognized)

    I am trying to install DPM 2012 on Server 2012 R2 and unalbe to get past prerequisties check.  When I try the command "OCSetup.exe SIS-Limited"  it comes up that OCSetup is not recognized.  How do I install (SIS) on Server 2012 R2?

    Hi.
    DPM 2012 SP1 is not supported running on Windows 2012 R2.  Please decide on one of the following.
    A) Install DPM 2012 R2 on the Windows Server 2012 R2 or other
    supported operating systems.
    B) Install DPM 2012 SP1 on Windows Server 2012 or other
    supported operating systems.
    FYI for Windows server 2012 R2 the new command is:
    dism /online /enable-feature:SIS-Limited
    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. Regards, Mike J. [MSFT] This
    posting is provided "AS IS" with no warranties, and confers no rights.

  • SharePoint 2010 SP2 hosted on Windows 2012 R2 NOT discovered by SCOM 2012 R2 + 2 SP MP's

    What is the process to get SharePoint 2010 Management Packs loaded in System Center 2012 R2 to discover/monitor SharePoint 2010 SP2 (14.0.7121.5000) loaded on Windows 2012 R2?
    View of installed system:
     System Center 2012 R2 loaded on Windows 2012 R2 (supported separately by SQL 2012 SP1 loaded on Windows 2012 R2)
    -Microsoft SharePoint 2010 Products Management Pack for System Center Operations Manager 2007
    -System Center 2012 Monitoring Pack for SharePoint 2010
     SharePoint 2010 SP2 (14.0.7121.5000) loaded on Windows 2012 R2 (supported separately by SQL 2012 SP1 loaded on Windows 2012 R2)
    The SharePoint 2010 Management Shell works fine!
    Result
    Event 0, Operations Manager - Cannot identify which SharePoint farm server is associated with. Check the management pack guide for troubleshooting information.
    Looked at these already:
    KB2690744, Configuring the SharePoint 2010 Management Pack for System Center Operations Manager. 
    http://om2012.wordpress.com/2013/05/24/sharepoint-2010-mp-on-scom-2012/
    Further, if the xml push does have the command get-farm instead of get-spfarm, that could be the issue. i.e.
    http://www.scom2k7.com/advanced-troubleshooting-of-the-sharepoint-2010-mp/
    Thanks,
    +Tony
    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

    Peter,
     I recommend to remove the Windows 2012 R2 server out of the farm and redeploy on W2008 R2.
    This issue does not have an easy fix.
    Summarizing, this appears to be the issue:
    1. Windows Management Framework 3.0 is integrated with Windows 2012 R2, which installs .NET 4 and Powershell 4.0. Not uninstallable.
    2. The Add-PSSnapin Microsoft.SharePoint.PowerShell is not supported with Powershell 4.0.
    3. The SCOM SP2010 MP puts a package on the defined farm server and when the agent launches the package, it calls Powershell (v4 in theis case) and errors out. The target W2012 server will have an Error 0 in the Operations Manager Event log. See below.
    Options:
    1. Work around maybe - Develop method for manual discovery (I'm working on that now).
    2. Rebuild SP2010 farm on Windows 2008 R2
    3. System Center Team - Write a new MP to down version Powershell (Powershell.exe -Version 2)
    4. Powershell Team - Write a SharePoint Snapin for Powershell 4
    Please click "Propose As Answer" if a post solves your problem or "Vote As Helpful" if a post has been useful to you.

  • SCCM 2012 SP1 SUP on Windows Server 2012

    Hi sccm guys,
    I'm having Troubles to get the SUP role working on my Windows Server 2012. I'm using SCCM 2012 SP1. I installed (and did not configure) the WSUS role from the Server Manager. I Chose to install the DB on the local SQL instance (no WID instance).
    Then I added the SUP role to the Server and configured it with the seperate wsus Administration site (Ports 8530 and 8531).
    WSUS gets configured partially (Proxy Settings and "Products and Classification" Options only for Office and Windows)
    The folowing error pops up in the wcm.log
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
    Any clues?
    Cheers
    Sebastian Bammer

    Also did not fix my issue. A round of my logs:
    Checking for supported version of WSUS (min WSUS 3.0 SP2 + KB2720211 + KB2734608)
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Checking runtime v2.0.50727... SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
    Did not find supported version of assembly Microsoft.UpdateServices.Administration.
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Checking runtime v4.0.30319... SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
    Found supported assembly Microsoft.UpdateServices.Administration version 4.0.0.0, file version 6.2.9200.16384
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Found supported assembly Microsoft.UpdateServices.BaseApi version 4.0.0.0, file version 6.2.9200.16384
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Supported WSUS version found SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
    Using DOMAIN\Administrator credentials for network connections
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Verify Upstream Server settings on the Active WSUS Server
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    No changes - WSUS Server settings are correctly configured and Upstream Server is set to Microsoft Update
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Done using DOMAIN\Administrator credentials
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:28:59 a.m. 3556 (0x0DE4)
    Using DOMAIN\Administrator credentials for network connections
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:28:59 a.m.
    3556 (0x0DE4)
    Done using DOMAIN\Administrator credentials
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:14 a.m.
    3556 (0x0DE4)
    Successfully refreshed categories from WSUS server
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:16 a.m.
    3556 (0x0DE4)
    Using DOMAIN\Administrator credentials for network connections
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
    3556 (0x0DE4)
    Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
    3556 (0x0DE4)
    Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
    3556 (0x0DE4)
    Category Product:587f7961-187a-4419-8972-318be1c318af (Microsoft Dynamics CRM 2011 SHS) not found on WSUS
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
    3556 (0x0DE4)
    Starting WSUS category sync from upstream...
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:21 a.m.
    3556 (0x0DE4)
    Refreshing categories from WSUS server SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:29:26 a.m. 3556 (0x0DE4)
    Using DOMAIN\Administrator credentials for network connections
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:26 a.m.
    3556 (0x0DE4)
    Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:26 a.m.
    3556 (0x0DE4)
    Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:26 a.m.
    3556 (0x0DE4)
    Done using DOMAIN\Administrator credentials
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:41 a.m.
    3556 (0x0DE4)
    Successfully refreshed categories from WSUS server
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Done using DOMAIN\Administrator credentials
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Using DOMAIN\Administrator credentials for network connections
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Attempting connection to WSUS server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Successfully connected to server: SCCM01.domain, port: 8530, useSSL: False
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Category Product:587f7961-187a-4419-8972-318be1c318af (Microsoft Dynamics CRM 2011 SHS) not found on WSUS
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Subscription contains categories unknown to WSUS.
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Done using DOMAIN\Administrator credentials
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    Failed to set Subscriptions on the WSUS Server. Error:(-2147467259)Unspecified error
    SMS_WSUS_CONFIGURATION_MANAGER 15/01/2013 8:29:42 a.m.
    3556 (0x0DE4)
    STATMSG: ID=6603 SEV=E LEV=M SOURCE="SMS Server" COMP="SMS_WSUS_CONFIGURATION_MANAGER" SYS=SCCM01.domain SITE=AKL PID=1544 TID=3556 GMTDATE=Mon Jan 14 19:29:42.723 2013 ISTR0="SCCM01.domain" ISTR1="" ISTR2="" ISTR3="" ISTR4="" ISTR5="" ISTR6="" ISTR7="" ISTR8=""
    ISTR9="" NUMATTRS=0 SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:29:42 a.m. 3556 (0x0DE4)
    Waiting for changes for 59 minutes SMS_WSUS_CONFIGURATION_MANAGER
    15/01/2013 8:29:42 a.m. 3556 (0x0DE4)
    Thanks Christoph

  • Macbook pro mid 2012 is not recognizing I tb internal HDD

    I recently purchased a mid-2012 15'' macbook pro, 2.3 ghz, 500 gb HDD, 4 gb RAM. I took it into a service last weekend to have it upgraded to 8 gb RAM, 250 GB SSD Samsung, and a 1 TB HDD HITACHI 5400 rpm. Everything was fine until yesterday when suddenly the computer stopped recognizing the I tb HDD. You can see it in disk utility but the disk drive is just shaded gray. This morning I noticed that when I start the computer with only the battery it doesnt recongize the HDDD but when the charger is plugged in and start the computer the disk is recongized but a window pops up saying that I can access the files that are on the disk but no changes can be made and nothing can be saved onto the disk.  It also says the disk needs to be reformatted as soon as possible. Could this be the SATA cable problem? Or a power shortage? Or something with the motherboard?

    KazTav wrote:
    Apple could have disabled what option?
    Replacing the Superdrive with a hard drive, that's not a factory configuration.
    That it doesn't work on battery and only on power is a obvious sign it's drawing too much current and the Mac will tend to disable things that are.

  • RT build not recognized by LabVIEW 2012

    Recently I began upgrading an existing RT project from LV 2011 to 2012, and I have run into a problem when I attempt to build the RT application. The application builds without errors, but when completed the icon within the project is a blue circle with a white question mark on the inside, and does not deploy correctly. According to LV help this icon represents a file with an unknown editor. My initial thought is that I am missing a toolkit, or something else that I need to install. 
    system specs:
    W7 32bit
    LV 2012
    4x RT targets
    Any insights would be appreciated. Thanks.

    Hello,
    In terms of required installation, when upgrading from LabVIEW 2011 to LabVIEW 2012, you will also need to install LabVIEW Real-Time 2012 and NI-RIO 12.0.  You will then have to make sure your RT targets also have their software components upgraded to match your host.
    Which icon in your project is a blue circle with a white question mark?  A screen shot would be helpful.  I have seen this question mark, and removing then re-adding the offending file (.lvproj in my case) removed the question mark.  Assuming your software is all installed, you might try this method.  You could also try navigating to the location of the file in your Windows Explorer and launching it into LabVIEW from there.  This should associate LabVIEW with that type of file, and allow LabVIEW to work with it.
    Patrick
    CLA

  • IPhone 4s is not recognized by new 2012 Honda civic, any sugg?

    Does anyone have a problem sinc iPhone 4s with new Honda civic

    On my insight I had to do the following
    1 Switch off the car radio at the radio power switch
    2 turn off the car
    3 power off the iphone (not sleep!)
    4 connect the iPhone to the car
    5 Power up the car
    6 switch on the radio
    At this point the iPhone should power up. part of the power up it will re-negotiate with the radio and it should now work normally.
    Hope this helps.

  • SCCM 2012 SP1 - OS Deployment - hash could not be matched for the downloded content

    I've got a newly deployed SCCM 2012 SP1 running on Windows Server 2012. The W2K12 runs as vm on ESX 5.1. I'm having very odd issues with OS deployment. The TS keeps failing when processing SCCM client installation - it downloads the package but then it fails
    straight away with the 80091007 - hash values couldn't be matched error - some extract from smsts.log attached below. It's very consistent, it happens every time - it downloads and applies the image fine straight after that it bombs out.
    What is very interesting is that it works perfectly fine when I deploy vms (on the same or different host) - the issue seems to be be only affecting physical machines (laptops desktops). This might suggest some network issues (vSwitch with Cisco switches) but
    the config on the switch is very simple and this shouldn't be the case.
    I had a few virtualised SCCM 2007 installations (ESX 5 and 4) and it always worked with no problems.
    I tried to recreate the package (changing source directory), turn binary differential replication on and off, copy the content of the package to the dist point or not copy. Push client installation (or other package deployments) work fine
    When I tried to deploy with no download - sometimes it works but most of the time I'd get the files/folder corrupt error (can't remember the No)
    This is starting to drive me crazy - There are some significant changes in the way SCCM 2012 is validating package integrity (like Content Lib folder) but the consistency of this problem is just very odd.
    Anyone has any clues?
    thanks
     - Downloaded file from http://GTKVMGMT05.GTK.LOC...m?/x64/wic_x64_enu.exe to C:\_SMSTaskSequence\Packages\GTK0000C\x64/wic_x64_enu.exe 
     - Download done setting progress bar to 100
    VerifyContentHash: Hash algorithm is 32780
    c:\_smstasksequence\packages\GTK0000c\i386 is a directory. Setting directory security
    c:\_smstasksequence\packages\GTK0000c\x64 is a directory. Setting directory security
     - Hash could not be matched for the downloded content. Original ContentHash = 5EF3A189C48F3469440A83026EC8ECD36EAD6EAF3B5D35663F8201BDE175413C, Downloaded ContentHash = FA4516EDD2D7907F8FA472A3E1B717DF2DD4A0976CD4CEAE11045EE62EC8C661
    0L == TS::Utility::VerifyPackageHash(pszContentID, sDestination), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,2999)
     - DownloadContentAndVerifyHash(pszPackageID, L"SMSPackage", saHttpContentSources, saSMBContentSources, saMulticastContentSources, sDestination, dwFlags, L"", 0, dwPackageFlags, pszUserName, pszUserPassword ), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3106)
     - DownloadContentLocally(pszSource, sSourceDirectory, dwFlags, hUserToken, pszUserName, pszUserPassword), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3331)
    ResolveSource(pszSource, sSourceDirectory, dwFlags, 0, 0, 0), HRESULT=80091007 (e:\nts_sccm_release\sms\framework\tscore\resolvesource.cpp,3221)
    TS::Utility::ResolveSource(sClientPackageID, sClientPackagePath), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\basesetuphook.cpp,1655)
     - Failed to resolve package source "GTK0000C"
     - Exiting ConfigureEx: 0x80091007
     - BaseSetupHook::configure(sWindowsDir), HRESULT=80091007 (e:\nts_sccm_release\sms\client\osdeployment\osdgina\osdsetuphook.cpp,292)
     - Failed to configure OSD setup hook (0x80091007)
     - Failed to configure OSD setup hook (0x80091007)

    is this the only indication of a problem in your smsts.log file ? did you apply the
    authenticode hotfix or have you
    downloaded the SP1 media after that hotfix was applied ?
    Step by Step Configuration Manager Guides >
    2012 Guides |
    2007 Guides | I'm on Twitter > ncbrady

  • SCCM 2012 connector not working roperly in Service Manager 2012 Sp1

    I'm using SCSM 2012 Sp1 and I've SCCM 2012 in my environment. I already configured the SCCM connector in SCSM. But it not showing the software inventory on the software tab. Reather then software inventory it showing every things.
    Please any one help me to solve this issue.
    Mithun Dey Web: http://cloudmithun.wordpress.com If this may give your necessary resolution please mark it as Answre.

    Hi
    It can be the
    Asset Intelligence that you have to enable in SCCM.
    Look here how you do it:
    http://www.windows-noob.com/forums/index.php?/topic/1225-what-is-asset-intelligence-and-how-can-i-use-it-in-sccm/
    Remy BOVI

  • OMServer.msi returns error 1603 when trying to upgrade first management server from Operations Manager 2012 SP1 to Operations Manager 2012 R2

    Hi All, looking for some assistance with the following issue.
    We are attempting to upgrade our Operations Manager 2012 SP1 environment to Operations Manager 2012 R2.
    We have completed all the pre-upgrade tasks detailed here
    http://technet.microsoft.com/en-us/library/dn249704.aspx
    We are then following the guidance detailed here regarding upgrading distributed management groups
    http://technet.microsoft.com/en-us/library/dn249721.aspx. The upgrade fails on the first management server with the following screen being displayed.
    OMServer.log file is as follows.
    === Verbose logging started: 22/01/2014 10:21:27 Build type: SHIP UNICODE 5.00.9200.00 Calling process: C:\Users\scomaction\AppData\Local\SCOM\Setup\SetupChainerUI.exe ===
    MSI (c) (78:34) [10:21:27:040]: Resetting cached policy values
    MSI (c) (78:34) [10:21:27:040]: Machine policy value 'Debug' is 0
    MSI (c) (78:34) [10:21:27:040]: ******* RunEngine:
    ******* Product: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    ******* Action:
    ******* CommandLine: **********
    MSI (c) (78:34) [10:21:27:040]: Client-side and UI is none or basic: Running entire install on the server.
    MSI (c) (78:34) [10:21:27:040]: Grabbed execution mutex.
    MSI (c) (78:34) [10:21:27:071]: Cloaking enabled.
    MSI (c) (78:34) [10:21:27:071]: Attempting to enable all disabled privileges before calling Install on Server
    MSI (c) (78:34) [10:21:27:071]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (D4:30) [10:21:27:082]: Running installation inside multi-package transaction F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    MSI (s) (D4:30) [10:21:27:082]: Grabbed execution mutex.
    MSI (s) (D4:A0) [10:21:27:086]: Resetting cached policy values
    MSI (s) (D4:A0) [10:21:27:086]: Machine policy value 'Debug' is 0
    MSI (s) (D4:A0) [10:21:27:086]: ******* RunEngine:
    ******* Product: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    ******* Action:
    ******* CommandLine: **********
    MSI (s) (D4:A0) [10:21:27:175]: Machine policy value 'DisableUserInstalls' is 0
    MSI (s) (D4:A0) [10:21:27:181]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
    MSI (s) (D4:A0) [10:21:27:190]: SRSetRestorePoint skipped for this transaction.
    MSI (s) (D4:A0) [10:21:27:192]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
    MSI (s) (D4:A0) [10:21:27:200]: File will have security applied from OpCode.
    MSI (s) (D4:A0) [10:21:27:234]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi' against software restriction policy
    MSI (s) (D4:A0) [10:21:27:234]: SOFTWARE RESTRICTION POLICY: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi has a digital signature
    MSI (s) (D4:A0) [10:21:27:354]: SOFTWARE RESTRICTION POLICY: F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi is permitted to run at the 'unrestricted' authorization level.
    MSI (s) (D4:A0) [10:21:27:354]: MSCOREE not loaded loading copy from system32
    MSI (s) (D4:A0) [10:21:27:360]: End dialog not enabled
    MSI (s) (D4:A0) [10:21:27:360]: Original package ==> F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    MSI (s) (D4:A0) [10:21:27:360]: Package we're running from ==> C:\Windows\Installer\4b8344.msi
    MSI (s) (D4:A0) [10:21:27:371]: APPCOMPAT: Compatibility mode property overrides found.
    MSI (s) (D4:A0) [10:21:27:372]: APPCOMPAT: looking for appcompat database entry with ProductCode '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'.
    MSI (s) (D4:A0) [10:21:27:372]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (D4:A0) [10:21:27:378]: Machine policy value 'TransformsSecure' is 1
    MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'DisablePatch' is 0
    MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'AllowLockdownPatch' is 0
    MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'DisableLUAPatching' is 0
    MSI (s) (D4:A0) [10:21:27:379]: Machine policy value 'DisableFlyWeightPatching' is 0
    MSI (s) (D4:A0) [10:21:27:380]: APPCOMPAT: looking for appcompat database entry with ProductCode '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'.
    MSI (s) (D4:A0) [10:21:27:380]: APPCOMPAT: no matching ProductCode found in database.
    MSI (s) (D4:A0) [10:21:27:380]: Transforms are not secure.
    MSI (s) (D4:A0) [10:21:27:380]: Note: 1: 2205 2: 3: Control
    MSI (s) (D4:A0) [10:21:27:380]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Users\scomaction\AppData\Local\SCOM\Logs\OMServer.log'.
    MSI (s) (D4:A0) [10:21:27:380]: Command Line: OM_INSTALLDIR=F:\Program Files\Microsoft System Center 2012 R2\Operations Manager SEND_CEIP_REPORTS=0 MU_SETTING=0 ROOT_MANAGEMENT_SERVER_PORT=5723 SC_DB_SERVER=SCOM-XXX-AG SCDATABASENAME=OperationsManager DW_DB_SERVER=SCOM-XXX-AG DWDATABASENAME=OperationsManagerDW REBOOT=ReallySuppress CURRENTDIRECTORY=C:\Users\scomaction\AppData\Local\SCOM\Setup CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=4472
    MSI (s) (D4:A0) [10:21:27:380]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{58EFE971-58C1-4DBD-A400-A7607A745475}'.
    MSI (s) (D4:A0) [10:21:27:380]: Product Code passed to Engine.Initialize: ''
    MSI (s) (D4:A0) [10:21:27:380]: Product Code from property table before transforms: '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'
    MSI (s) (D4:A0) [10:21:27:380]: Product Code from property table after transforms: '{C92727BE-BD12-4140-96A6-276BA4F60AC1}'
    MSI (s) (D4:A0) [10:21:27:380]: Product not registered: beginning first-time install
    MSI (s) (D4:A0) [10:21:27:380]: Product {C92727BE-BD12-4140-96A6-276BA4F60AC1} is not managed.
    MSI (s) (D4:A0) [10:21:27:380]: MSI_LUA: Credential prompt not required, user is an admin
    MSI (s) (D4:A0) [10:21:27:381]: PROPERTY CHANGE: Adding ProductState property. Its value is '-1'.
    MSI (s) (D4:A0) [10:21:27:381]: Entering CMsiConfigurationManager::SetLastUsedSource.
    MSI (s) (D4:A0) [10:21:27:381]: User policy value 'SearchOrder' is 'nmu'
    MSI (s) (D4:A0) [10:21:27:381]: Adding new sources is allowed.
    MSI (s) (D4:A0) [10:21:27:381]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:381]: Package name extracted from package path: 'OMServer.msi'
    MSI (s) (D4:A0) [10:21:27:381]: Package to be registered: 'OMServer.msi'
    MSI (s) (D4:A0) [10:21:27:383]: Note: 1: 2262 2: AdminProperties 3: -2147287038
    MSI (s) (D4:A0) [10:21:27:383]: Machine policy value 'DisableMsi' is 1
    MSI (s) (D4:A0) [10:21:27:383]: Machine policy value 'AlwaysInstallElevated' is 0
    MSI (s) (D4:A0) [10:21:27:383]: User policy value 'AlwaysInstallElevated' is 0
    MSI (s) (D4:A0) [10:21:27:383]: Product installation will be elevated because user is admin and product is being installed per-machine.
    MSI (s) (D4:A0) [10:21:27:383]: Running product '{C92727BE-BD12-4140-96A6-276BA4F60AC1}' with elevated privileges: Product is assigned.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding OM_INSTALLDIR property. Its value is 'F:\Program Files\Microsoft System Center 2012 R2\Operations Manager'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding ROOT_MANAGEMENT_SERVER_PORT property. Its value is '5723'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Modifying SC_DB_SERVER property. Its current value is 'OperationsManager'. Its new value: 'SCOM-XXX-AG'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding DW_DB_SERVER property. Its value is 'SCOM-XXX-AG'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding DWDATABASENAME property. Its value is 'OperationsManagerDW'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding REBOOT property. Its value is 'ReallySuppress'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'C:\Users\scomaction\AppData\Local\SCOM\Setup'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '4472'.
    MSI (s) (D4:A0) [10:21:27:383]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
    MSI (s) (D4:A0) [10:21:27:383]: RESTART MANAGER: Disabled by MSIRESTARTMANAGERCONTROL property; Windows Installer will use the built-in FilesInUse functionality.
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:383]: TRANSFORMS property is now:
    MSI (s) (D4:A0) [10:21:27:383]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '300'.
    MSI (s) (D4:A0) [10:21:27:395]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming
    MSI (s) (D4:A0) [10:21:27:396]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Favorites
    MSI (s) (D4:A0) [10:21:27:398]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Network Shortcuts
    MSI (s) (D4:A0) [10:21:27:399]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Documents
    MSI (s) (D4:A0) [10:21:27:401]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
    MSI (s) (D4:A0) [10:21:27:402]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Recent
    MSI (s) (D4:A0) [10:21:27:404]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\SendTo
    MSI (s) (D4:A0) [10:21:27:405]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Templates
    MSI (s) (D4:A0) [10:21:27:405]: SHELL32::SHGetFolderPath returned: C:\ProgramData
    MSI (s) (D4:A0) [10:21:27:406]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Local
    MSI (s) (D4:A0) [10:21:27:408]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Pictures
    MSI (s) (D4:A0) [10:21:27:411]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
    MSI (s) (D4:A0) [10:21:27:413]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
    MSI (s) (D4:A0) [10:21:27:414]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
    MSI (s) (D4:A0) [10:21:27:415]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
    MSI (s) (D4:A0) [10:21:27:417]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
    MSI (s) (D4:A0) [10:21:27:420]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
    MSI (s) (D4:A0) [10:21:27:421]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
    MSI (s) (D4:A0) [10:21:27:423]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
    MSI (s) (D4:A0) [10:21:27:424]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Start Menu
    MSI (s) (D4:A0) [10:21:27:426]: SHELL32::SHGetFolderPath returned: C:\Users\scomaction\Desktop
    MSI (s) (D4:A0) [10:21:27:427]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
    MSI (s) (D4:A0) [10:21:27:428]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
    MSI (s) (D4:A0) [10:21:27:428]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
    MSI (s) (D4:A0) [10:21:27:433]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
    MSI (s) (D4:A0) [10:21:27:434]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'Windows User'.
    MSI (s) (D4:A0) [10:21:27:434]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\Windows\Installer\4b8344.msi'.
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi'.
    MSI (s) (D4:A0) [10:21:27:434]: Machine policy value 'MsiDisableEmbeddedUI' is 0
    MSI (s) (D4:A0) [10:21:27:434]: EEUI - Disabling MsiEmbeddedUI due to existing external or embedded UI
    MSI (s) (D4:A0) [10:21:27:434]: EEUI - Disabling MsiEmbeddedUI for service because it's not a quiet/basic install
    MSI (s) (D4:A0) [10:21:27:434]: Note: 1: 2205 2: 3: PatchPackage
    MSI (s) (D4:A0) [10:21:27:434]: Machine policy value 'DisableRollback' is 0
    MSI (s) (D4:A0) [10:21:27:434]: User policy value 'DisableRollback' is 0
    MSI (s) (D4:A0) [10:21:27:434]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
    === Logging started: 22/01/2014 10:21:27 ===
    MSI (s) (D4:A0) [10:21:27:435]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
    MSI (s) (D4:A0) [10:21:27:436]: APPCOMPAT: [DetectVersionLaunchCondition] Launch condition already passes.
    MSI (s) (D4:A0) [10:21:27:438]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
    MSI (s) (D4:A0) [10:21:27:438]: Doing action: INSTALL
    Action start 10:21:27: INSTALL.
    MSI (s) (D4:A0) [10:21:27:444]: Running ExecuteSequence
    MSI (s) (D4:A0) [10:21:27:444]: Doing action: SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76
    MSI (s) (D4:A0) [10:21:27:447]: PROPERTY CHANGE: Adding SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76 property. Its value is 'C:\Windows\SysWOW64\'.
    Action start 10:21:27: SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76.
    MSI (s) (D4:A0) [10:21:27:448]: Doing action: System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76
    Action ended 10:21:27: SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76. Return value 1.
    MSI (s) (D4:A0) [10:21:27:450]: PROPERTY CHANGE: Adding System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76 property. Its value is 'C:\Windows\system32\'.
    Action start 10:21:27: System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76.
    MSI (s) (D4:A0) [10:21:27:450]: Doing action: WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6
    Action ended 10:21:27: System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76. Return value 1.
    MSI (s) (D4:A0) [10:21:27:452]: PROPERTY CHANGE: Adding WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6 property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6.
    MSI (s) (D4:A0) [10:21:27:453]: Doing action: System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522
    Action ended 10:21:27: WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6. Return value 1.
    MSI (s) (D4:A0) [10:21:27:455]: PROPERTY CHANGE: Adding System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522 property. Its value is 'C:\Windows\system32\'.
    Action start 10:21:27: System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522.
    MSI (s) (D4:A0) [10:21:27:456]: Doing action: WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C
    Action ended 10:21:27: System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522. Return value 1.
    MSI (s) (D4:A0) [10:21:27:458]: PROPERTY CHANGE: Adding WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C.
    MSI (s) (D4:A0) [10:21:27:458]: Doing action: SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C
    Action ended 10:21:27: WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C. Return value 1.
    MSI (s) (D4:A0) [10:21:27:461]: PROPERTY CHANGE: Adding SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C property. Its value is 'C:\Windows\SysWOW64\'.
    Action start 10:21:27: SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C.
    MSI (s) (D4:A0) [10:21:27:461]: Doing action: WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7
    Action ended 10:21:27: SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C. Return value 1.
    MSI (s) (D4:A0) [10:21:27:463]: PROPERTY CHANGE: Adding WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7.
    MSI (s) (D4:A0) [10:21:27:463]: Doing action: System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7
    Action ended 10:21:27: WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7. Return value 1.
    MSI (s) (D4:A0) [10:21:27:466]: PROPERTY CHANGE: Adding System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 property. Its value is 'C:\Windows\system32\'.
    Action start 10:21:27: System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7.
    MSI (s) (D4:A0) [10:21:27:467]: Doing action: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8
    Action ended 10:21:27: System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7. Return value 1.
    MSI (s) (D4:A0) [10:21:27:468]: PROPERTY CHANGE: Adding WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8 property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8.
    MSI (s) (D4:A0) [10:21:27:469]: Doing action: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9
    Action ended 10:21:27: WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8. Return value 1.
    MSI (s) (D4:A0) [10:21:27:471]: PROPERTY CHANGE: Adding WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9.
    MSI (s) (D4:A0) [10:21:27:472]: Doing action: WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE
    Action ended 10:21:27: WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9. Return value 1.
    MSI (s) (D4:A0) [10:21:27:474]: PROPERTY CHANGE: Adding WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE property. Its value is 'C:\Windows\'.
    Action start 10:21:27: WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE.
    MSI (s) (D4:A0) [10:21:27:475]: Doing action: ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0
    Action ended 10:21:27: WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE. Return value 1.
    MSI (s) (D4:A0) [10:21:27:477]: PROPERTY CHANGE: Adding ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0 property. Its value is 'C:\ProgramData\Microsoft\Windows\Start Menu\Programs\'.
    Action start 10:21:27: ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0.
    MSI (s) (D4:A0) [10:21:27:477]: Doing action: FindRelatedProducts
    Action ended 10:21:27: ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0. Return value 1.
    Action start 10:21:27: FindRelatedProducts.
    MSI (s) (D4:A0) [10:21:27:481]: PROPERTY CHANGE: Adding CORECOMPONENTPRESENT_AGENT property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
    MSI (s) (D4:A0) [10:21:27:483]: Skipping action: _StopCoreServices.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
    MSI (s) (D4:A0) [10:21:27:483]: Skipping action: _KillOMProcesses.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 (condition is false)
    MSI (s) (D4:A0) [10:21:27:483]: Skipping action: _SearchOpsMgrShellPath.CFE2C791_D05A_4240_90ED_DEB20161DFB0 (condition is false)
    MSI (s) (D4:A0) [10:21:27:483]: Doing action: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0
    Action ended 10:21:27: FindRelatedProducts. Return value 1.
    MSI (s) (D4:08) [10:21:27:501]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI847C.tmp, Entrypoint: SetMonadFilePath
    MSI (s) (D4:B0) [10:21:27:502]: Generating random cookie.
    MSI (s) (D4:B0) [10:21:27:505]: Created Custom Action Server with PID 4964 (0x1364).
    MSI (s) (D4:34) [10:21:27:527]: Running as a service.
    MSI (s) (D4:34) [10:21:27:529]: Hello, I'm your 64bit Impersonated custom action server.
    Action start 10:21:27: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0.
    MSI (s) (D4!DC) [10:21:27:638]: PROPERTY CHANGE: Modifying MONAD_SHELL_PATH property. Its current value is 'Error: Value Never Set. Check the CACore:SetMonadFilePath CA'. Its new value: 'C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe'.
    GetRegistyStringValue: Registy key value found.. C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
    MSI (s) (D4:A0) [10:21:27:640]: Doing action: _Set_CORECOMPONENTPRESENT
    Action ended 10:21:27: _SetMonadFilePath.CFE2C791_D05A_4240_90ED_DEB20161DFB0. Return value 1.
    MSI (s) (D4:A0) [10:21:27:643]: PROPERTY CHANGE: Adding CORECOMPONENTPRESENT property. Its value is '{8B21425D-02F3-4B80-88CE-8F79B320D330}'.
    Action start 10:21:27: _Set_CORECOMPONENTPRESENT.
    MSI (s) (D4:A0) [10:21:27:644]: Skipping action: _AbortDowngradeProductAttempt (condition is false)
    MSI (s) (D4:A0) [10:21:27:644]: Doing action: _AbortIncompatibleComponents
    Action ended 10:21:27: _Set_CORECOMPONENTPRESENT. Return value 1.
    Action start 10:21:27: _AbortIncompatibleComponents.
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5044 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 1580 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5512 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 4268 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5024 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 6064 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 3396 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 2704 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5568 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 5940 could not be cancelled. Error: 1168
    MSI (s) (D4:30) [10:21:27:652]: I/O on thread 1968 could not be cancelled. Error: 1168
    MSI (s) (D4:A0) [10:21:27:652]: Product: System Center Operations Manager 2012 Server -- The Operations Manager management server cannot be installed on a computer on which the Operations Manager agent, Operations Manager gateway, System Center Essentials, or System Center Service Manager is already installed. These must be uninstalled to proceed.
    The Operations Manager management server cannot be installed on a computer on which the Operations Manager agent, Operations Manager gateway, System Center Essentials, or System Center Service Manager is already installed. These must be uninstalled to proceed.
    Action ended 10:21:27: _AbortIncompatibleComponents. Return value 3.
    Action ended 10:21:27: INSTALL. Return value 3.
    Property(S): DiskPrompt = Please Insert Disk 1
    Property(S): UpgradeCode = {17058653-A628-4C03-8F80-5E2B179ECD55}
    Property(S): SCDATABASENAME = OperationsManager
    Property(S): SC_DB_SERVER = SCOM-XXX-AG
    Property(S): SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650 = **********
    Property(S): CORECOMPONENTPRESENT = {8B21425D-02F3-4B80-88CE-8F79B320D330}
    Property(S): OM_INSTALLDIR = F:\Program Files\Microsoft System Center 2012 R2\Operations Manager
    Property(S): ProgramFiles64Folder = C:\Program Files\
    Property(S): Privileged = 1
    Property(S): ARPSYSTEMCOMPONENT = 1
    Property(S): DONOTSKIPDELETESERVICES = 0
    Property(S): DONOTSKIPINSTALLSERVICES = 0
    Property(S): OM_COMMON_PRODUCT_REGISTRY_PATH = SOFTWARE\Microsoft\System Center Operations Manager
    Property(S): OM_COMMON_PRODUCT_RELEASE_REGISTRY_KEY = 12
    Property(S): OM_COMMON_PRODUCT_DEFAULT_INSTALL_DIR = System Center Operations Manager
    Property(S): NetFxVersion = v2.0.50727
    Property(S): IS_OM_SERVER = 1
    Property(S): InstallAPMAgent = 1
    Property(S): INSTALLLEVEL = 100
    Property(S): ALLUSERS = 1
    Property(S): ARPNOREPAIR = 0
    Property(S): ARPURLINFOABOUT = http://www.microsoft.com/mom
    Property(S): ARPURLUPDATEINFO = http://www.microsoft.com/mom
    Property(S): ARPHELPLINK = http://support.microsoft.com
    Property(S): MSIRESTARTMANAGERCONTROL = Disable
    Property(S): SQL_PORT = 1433
    Property(S): DbSizeGood = 1
    Property(S): DbFileOptionsGood = 1
    Property(S): DbFilesSpaceGood = 1
    Property(S): DbNameGood = 1
    Property(S): SqlServicesStarted = 1
    Property(S): _SetSDKServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650 = **********
    Property(S): _SetConfigServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650 = **********
    Property(S): DialogWizardTitle = System Center 2012 R2 Operations Manager Setup
    Property(S): MinimumOSMsg = This product must be installed on Windows Server 2008 R2 or higher.
    Property(S): MOMSDKPortDesc = Operations Manager SDK.
    Property(S): MOMConnectorPortDesc = Operations Manager Connector Framework.
    Property(S): MOMAEMPortDesc = Operations Manager Application Error Monitoring.
    Property(S): MOMSQMPortDesc = Operations Manager Customer Experience Improvement Program.
    Property(S): MOMHSPortDesc = System Center Management Health Service
    Property(S): SCOMV3SP1ProgramName = System Center 2012 R2 Operations Manager
    Property(S): FWRulePingRequestName = Operations Manager Ping Request (Echo Request - ICMPv4 OUT)
    Property(S): FWRulePingRequestDesc = Operations Manager network monitoring ping request
    Property(S): FWRulePingResponseName = Operations Manager Ping Response (Echo Response - ICMPv4 IN)
    Property(S): FWRulePingResponseDesc = Operations Manager network monitoring ping response
    Property(S): FWRuleSnmpRequestName = Operations Manager SNMP Request
    Property(S): FWRuleSnmpRequestDesc = Operations Manager network monitoring SNMP request
    Property(S): FWRuleSnmpResponseName = Operations Manager SNMP Response
    Property(S): FWRuleSnmpResponseDesc = Operations Manager network monitoring SNMP response
    Property(S): FWRuleSnmpTrapListenerName = Operations Manager SNMP Trap Listener
    Property(S): FWRuleSnmpTrapListenerDesc = Operations Manager network monitoring SNMP trap listener
    Property(S): Manufacturer = Microsoft Corporation
    Property(S): ProductCode = {C92727BE-BD12-4140-96A6-276BA4F60AC1}
    Property(S): ProductLanguage = 1033
    Property(S): ProductName = System Center Operations Manager 2012 Server
    Property(S): ProductVersion = 7.1.10226.0
    Property(S): SecureCustomProperties = ACTIONSPASSWORD;CORECOMPONENTPRESENT_AGENT;CORECOMPONENTPRESENT_GW;CORECOMPONENTPRESENT_RC;CORECOMPONENTPRESENT_SCE;CORECOMPONENTPRESENT_SMB2;CORECOMPONENTPRESENT_SMRTM;IS_AVICODE_AGENT_INSTALLED;IS_MOMASPAGENT_INSTALLED;MOM_DB_SERVER;MOMDATABASENAME_OLD;OM_NEWER_PRODUCT_FOUND;SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650;SQL_PORT
    Property(S): MsiHiddenProperties = _SetConfigServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650;_SetSDKServiceAccount.540EA3C0_A5E9_41EA_A585_822C09EA2650;ACTIONSPASSWORD;SDK_PASSWORD.540EA3C0_A5E9_41EA_A585_822C09EA2650
    Property(S): WixPdbPath = d:\btvsts\20867\private\product\setup\wix\msi\server\om\obj\amd64\OMServer.wixpdb
    Property(S): CORECOMPONENTPRESENT_AGENT = {8B21425D-02F3-4B80-88CE-8F79B320D330}
    Property(S): ProgramMenuFolder.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
    Property(S): MONAD_SHELL_PATH = C:\Windows\System32\WindowsPowerShell\v1.0\powershell.exe
    Property(S): EnableEV.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = 1
    Property(S): AddInstallPath.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = add
    Property(S): RemoveInstallPath.CFE2C791_D05A_4240_90ED_DEB20161DFB0 = remove
    Property(S): WindowsFolder.3A3B255D_E19B_4D2E_8687_D6EF0314AFBE = C:\Windows\
    Property(S): VersionNT = 602
    Property(S): DW_DB_SERVER = SCOM-XXX-AG
    Property(S): DWDATABASENAME = OperationsManagerDW
    Property(S): OMDATABASENAME = OperationsManger
    Property(S): MaximumDataAgeMinutes = 10080
    Property(S): MaximumQueueSizeKB = 102400
    Property(S): MOMSDKPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 5724
    Property(S): MOMConnectorPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 51905
    Property(S): MOMAEMPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 51906
    Property(S): MOMSQMPort.1451A536_2C9B_42F2_A37A_C9C6460E7EEA = 51907
    Property(S): SDK_SERVICE_TYPE = 4
    Property(S): ROOT_MANAGEMENT_SERVER_PORT = 5723
    Property(S): SERVER_MANAGEMENT_GROUP_TYPE.C6F00077_9737_419B_A8B6_B309BA6F8FC8 = 1
    Property(S): MaximumForwardedVirtualQueuePercentage = 8
    Property(S): QueueSendDataSinglePriority = 0
    Property(S): ADMIN_ROLE_GROUP.C6F00077_9737_419B_A8B6_B309BA6F8FC8 = Administrators
    Property(S): USE_MANUALLY_SPECIFIED_SETTINGS = 1
    Property(S): WindowsFolder.80B659D9_F758_4E7D_B4FA_E53FC737DCC9 = C:\Windows\
    Property(S): CommonFiles64Folder = C:\Program Files\Common Files\
    Property(S): CAN_REGISTER_FOR_MU = 0
    Property(S): MU_SETTING = 0
    Property(S): IS_ROOT_HEALTH_SERVICE = 0
    Property(S): IS_MOM_SERVER = 0
    Property(S): IS_MOM_GATEWAY = 0
    Property(S): WindowsFolder.399B61E4_41A2_4BE4_889A_A0D0761C88A8 = C:\Windows\
    Property(S): WindowsFolder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 = C:\Windows\
    Property(S): System64Folder_amd64_VC.1C11561A_11CB_36A7_8A47_D7A042055FA7 = C:\Windows\system32\
    Property(S): DirectoryTable100_amd64.1C11561A_11CB_36A7_8A47_D7A042055FA7 = DirectoryTable
    Property(S): WindowsFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C = C:\Windows\
    Property(S): SystemFolder_x86_VC.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C = C:\Windows\SysWOW64\
    Property(S): DirectoryTable100_x86.DF495DFD_79F6_34DF_BB1E_E58DB5BDCF2C = DirectoryTable
    Property(S): SEND_CEIP_REPORTS = 0
    Property(S): System64Folder.A7850EAF_DD6F_4ED6_9581_E958CBD8A522 = C:\Windows\system32\
    Property(S): ACS_AGENT_ACCOUNT.A7850EAF_DD6F_4ED6_9581_E958CBD8A522 =
    Property(S): WindowsFolder.62894CB9_4320_40DB_B4E4_C0347FAB97B6 = C:\Windows\
    Property(S): SC_COMMON_REGISTRY_PATH = SOFTWARE\Microsoft\System Center\2010\Common
    Property(S): DISCOVERY_DATA_AUTHORIZATION_ENABLED = 0
    Property(S): IcmpProtocol.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 1
    Property(S): IcmpRequestType.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 8:*
    Property(S): IcmpResponseType.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 0:*
    Property(S): SnmpProtocol.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 17
    Property(S): SnmpPort.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 161
    Property(S): SnmpTrapPort.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 162
    Property(S): DirectionIn.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 0
    Property(S): DirectionOut.ADADB3CF_4DA7_4040_90AE_3E4E0E0A6FBF = 1
    Property(S): SystemFolder.A591E3B4_D228_431D_BF89_99D52C8FFB76 = C:\Windows\SysWOW64\
    Property(S): System64Folder.A591E3B4_D228_431D_BF89_99D52C8FFB76 = C:\Windows\system32\
    Property(S): ADVISOR_UPLOADFREQUENCY_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1
    Property(S): ADVISOR_UPLOADDAY_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #-1
    Property(S): ADVISOR_UPLOADTIMEHOUR_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #-1
    Property(S): ADVISOR_UPLOADTIMEMIN_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #-1
    Property(S): ADVISOR_MAXCACHESIZE_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1024
    Property(S): ADVISOR_MAXMAILBOXSIZE_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1024
    Property(S): ADVISOR_ARCHIVEPERIOD_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #5
    Property(S): ADVISOR_LOGLEVEL_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #3
    Property(S): ADVISOR_NEEDMPINITIALIZE_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #1
    Property(S): ADVISOR_LYNC_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #0
    Property(S): ADVISOR_SHAREPOINT_PROP.192DDC2A_1CC5_4B2A_9D76_D8D0FC70175A = #0
    Property(S): MsiLogFileLocation = C:\Users\scomaction\AppData\Local\SCOM\Logs\OMServer.log
    Property(S): PackageCode = {58EFE971-58C1-4DBD-A400-A7607A745475}
    Property(S): ProductState = -1
    Property(S): PackagecodeChanging = 1
    Property(S): REBOOT = ReallySuppress
    Property(S): CURRENTDIRECTORY = C:\Users\scomaction\AppData\Local\SCOM\Setup
    Property(S): CLIENTUILEVEL = 3
    Property(S): MSICLIENTUSESEXTERNALUI = 1
    Property(S): CLIENTPROCESSID = 4472
    Property(S): MsiSystemRebootPending = 1
    Property(S): VersionDatabase = 300
    Property(S): VersionMsi = 5.00
    Property(S): VersionNT64 = 602
    Property(S): WindowsBuild = 9200
    Property(S): ServicePackLevel = 0
    Property(S): ServicePackLevelMinor = 0
    Property(S): MsiNTProductType = 3
    Property(S): WindowsFolder = C:\Windows\
    Property(S): WindowsVolume = C:\
    Property(S): System64Folder = C:\Windows\system32\
    Property(S): SystemFolder = C:\Windows\SysWOW64\
    Property(S): RemoteAdminTS = 1
    Property(S): TempFolder = C:\Users\SCOMAC~1\AppData\Local\Temp\
    Property(S): ProgramFilesFolder = C:\Program Files (x86)\
    Property(S): CommonFilesFolder = C:\Program Files (x86)\Common Files\
    Property(S): AppDataFolder = C:\Users\scomaction\AppData\Roaming\
    Property(S): FavoritesFolder = C:\Users\scomaction\Favorites\
    Property(S): NetHoodFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Network Shortcuts\
    Property(S): PersonalFolder = C:\Users\scomaction\Documents\
    Property(S): PrintHoodFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Printer Shortcuts\
    Property(S): RecentFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\Recent\
    Property(S): SendToFolder = C:\Users\scomaction\AppData\Roaming\Microsoft\Windows\SendTo\
    Property(S): TemplateFolder = C:\ProgramData\Microsoft\Windows\Templates\
    Property(S): CommonAppDataFolder = C:\ProgramData\
    Property(S): LocalAppDataFolder = C:\Users\scomaction\AppData\Local\
    Property(S): MyPicturesFolder = C:\Users\scomaction\Pictures\
    Property(S): AdminToolsFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools\
    Property(S): StartupFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup\
    Property(S): ProgramMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\Programs\
    Property(S): StartMenuFolder = C:\ProgramData\Microsoft\Windows\Start Menu\
    Property(S): DesktopFolder = C:\Users\Public\Desktop\
    Property(S): FontsFolder = C:\Windows\Fonts\
    Property(S): GPTSupport = 1
    Property(S): OLEAdvtSupport = 1
    Property(S): ShellAdvtSupport = 1
    Property(S): MsiAMD64 = 6
    Property(S): Msix64 = 6
    Property(S): Intel = 6
    Property(S): PhysicalMemory = 8192
    Property(S): VirtualMemory = 7854
    Property(S): AdminUser = 1
    Property(S): MsiTrueAdminUser = 1
    Property(S): LogonUser = scomaction
    Property(S): UserSID = S-1-5-21-607126847-70518424-489426498-210484
    Property(S): UserLanguageID = 2057
    Property(S): ComputerName = SCOMMS1-VM
    Property(S): SystemLanguageID = 2057
    Property(S): ScreenX = 1024
    Property(S): ScreenY = 768
    Property(S): CaptionHeight = 23
    Property(S): BorderTop = 1
    Property(S): BorderSide = 1
    Property(S): TextHeight = 16
    Property(S): TextInternalLeading = 3
    Property(S): ColorBits = 32
    Property(S): TTCSupport = 1
    Property(S): Time = 10:21:27
    Property(S): Date = 22/01/2014
    Property(S): MsiNetAssemblySupport = 4.0.30319.17929
    Property(S): MsiWin32AssemblySupport = 6.2.9200.16384
    Property(S): RedirectedDllSupport = 2
    Property(S): MsiRunningElevated = 1
    Property(S): USERNAME = Windows User
    Property(S): DATABASE = C:\Windows\Installer\4b8344.msi
    Property(S): OriginalDatabase = F:\InstallFiles\SCOMR2\Setup\AMD64\Server\OMServer.msi
    Property(S): UILevel = 2
    Property(S): ACTION = INSTALL
    MSI (s) (D4:A0) [10:21:27:697]: Note: 1: 1708
    MSI (s) (D4:A0) [10:21:27:698]: Product: System Center Operations Manager 2012 Server -- Installation operation failed.
    MSI (s) (D4:A0) [10:21:27:698]: Windows Installer installed the product. Product Name: System Center Operations Manager 2012 Server. Product Version: 7.1.10226.0. Product Language: 1033. Manufacturer: Microsoft Corporation. Installation success or error status: 1603.
    MSI (s) (D4:A0) [10:21:27:744]: Deferring clean up of packages/files, if any exist
    MSI (s) (D4:A0) [10:21:27:744]: MainEngineThread is returning 1603
    MSI (s) (D4:30) [10:21:27:744]: No System Restore sequence number for this installation.
    === Logging stopped: 22/01/2014 10:21:27 ===
    MSI (s) (D4:30) [10:21:27:746]: User policy value 'DisableRollback' is 0
    MSI (s) (D4:30) [10:21:27:746]: Machine policy value 'DisableRollback' is 0
    MSI (s) (D4:30) [10:21:27:746]: Incrementing counter to disable shutdown. Counter after increment: 0
    MSI (s) (D4:30) [10:21:27:746]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (D4:30) [10:21:27:746]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
    MSI (s) (D4:30) [10:21:27:746]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
    MSI (s) (D4:30) [10:21:27:747]: Destroying RemoteAPI object.
    MSI (s) (D4:B0) [10:21:27:747]: Custom Action Manager thread ending.
    MSI (c) (78:34) [10:21:27:748]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
    MSI (c) (78:34) [10:21:27:749]: MainEngineThread is returning 1603
    === Verbose logging stopped: 22/01/2014 10:21:27 ===
    Any assistance anyone can provide will be greatly appreciated.

    Verify from permission of user that you use it in upgrade, make sure that scom machine and user that you use it in upgrade in sysadmin group in database of operationsManager and OperationsManagerDW
    Also Verify from Prerequisites of Upgrade SCOM 2012 sp1 as below link
    http://technet.microsoft.com/en-us/library/jj656654.aspx
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question, please click "Mark As Answer"

  • System Center Virtual Machine Manager SC VMM 2012 SP1 Installation fails: Unable to assign the name NO_PARAM to this host because this name is already in use.

    I'm trying to install VMM 2012 SP1 on a Windows Server 2012 machine and it fails with this error,
    the scenario is as follows,
    Old database (from 2012 RTM) exists on remote SQL 2012 SP1 server
    Server was 2008 R2 SP1 so I decided to make a fresh installation of 2012 with the same name
    installed ADK
    specific error: 01:42:13:VMMPostinstallProcessor threw an exception: Threw Exception.Type: Microsoft.VirtualManager.Setup.Exceptions.BackEndErrorException, Exception.Message: Unable to assign the name NO_PARAM to this host because this name is already in
    use.
    please help

    I had a similar problem today when upgrading from SCVMM 2012 RTM to SCVMM 2012 SP1 RTM. To re-create the issue you describe originally you can actually just uninstall SCVMM 2012 SP1 RTM with "retain data" option and re-install the software on the same
    computer (with the same name of course), attaching it to the retained DB. If you change the SCVMM server name I believe it will make some things go wrong after your install, like missing VM template passwords for example as the data gets encrypted in
    the DB. Maybe it didn't but I didn't risk it. I definitely know if you change service accounts on a scenario like this you will be without the encrypted DB data which isn't much fun. To avoid changing the computer name, if you look in the setup log
    files in %systemdrive%\ProgramData\VMMLogs\, specifically the SetupWizard.log file. You will see details on it failing because the same computer name is in the DB table "dbo.tbl_ADHC_AgentServer" and until it is removed from that table I wasn't able to get
    the install to complete at all. The error in my logs looked something like this "InnerException.Type: System.Data.SqlClient.SqlException, InnerException.Message: Violation of UNIQUE KEY constraint 'unique_ADHC_AgentServer_ComputerName'. Cannot insert duplicate
    key in object 'dbo.tbl_ADHC_AgentServer'. The duplicate key value is (computername.is.writtenhere). The statement has been terminated." In the row data in the DB it also seems to suggest that the computer name had "Virtual Machine Manager Library Files" on
    it which is strange since I always remove the local SCVMM server as a library server after I install it and use an off box library server.

  • Issue upgrading SCOM 2012 SP1 to SCOM 2012 R2

    I have been having a really fun time trying to get my test SCOM 2012 SP1 environment upgraded to SCOM 2012 R2.  I initially had an issue with the DB server not accepting connections to SMB which was causing the upgrade to fail stating database permission
    issues (that was a fun one to troubleshoot).  Once I figured out that problem I am now getting an error in the OpsMgrSetupWizard log that is stating the following:
    [14:46:47]: Always:
    :LaunchMsiSetup: Complete: 2 seconds
    [14:46:47]: Error:
    :LaunchMsiSetup: Failed, return code: 1612
    [14:46:47]: Error:
    :Error:Failed to uninstall previous MOM product on this machine, cannot proceed with upgrade
    [14:46:47]: Error:
    :Error:Failed to uninstall Operations Manager Agent on this machine. This is fatal error, we cannot proceed with upgrade
    [14:46:50]: Error:
    :LaunchMSI: MSI E:\Setup\AMD64\Server\OMServer.msi returned error 1603
    [14:46:50]: Error:
    :ProcessInstalls: Install Item Management Server failed to install.  We did not launch the post process delegate.
    In the application log I am getting the following error:
    "Product: System Center Operations Manager 2012 Server -- The Operations Manager management server cannot be installed on a computer on which the Operations Manager agent, Operations Manager gateway, System Center Essentials, or System Center Service
    Manager is already installed. These must be uninstalled to proceed."
    I have verified that I don't have any of these installed and have even gone so far as to remove my Config man agent and System Center Endpoint Protection just in case it was getting confused with System Center Essentials.
    I am at a loss as to what to try next.  Any suggestions?

    Hi,
    Check if you have the following registry. If so, please back it up first, then delete for a test.
     HKEY_CLASSES_ROOT\Installer\UpgradeCodes\C96403E8AD6025B4F9E1FE9C574E34AE
    Also, please uninstall MOM product and Operations Manager Agent manually to check the result.
    Upgrading System Center 2012 SP1 - Operations Manager to System Center 2012 R2
    http://technet.microsoft.com/en-us/library/dn249707.aspx
    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.

  • Move Virtual Machine from Hyper-V Server 2008 R2 SP1 to Hyper-V Server 2012 fails with Error 2901

    I have six Hyper-V 2008 R2 SP1 servers and two Hyper-V 2012 servers. I am running SCVMM 2012 SP1. I am trying to use "move virtual machine" from within SCVMM to move VMs from a 2008 host to a 2012 host. I have tried different VMs on different hosts
    and they all fail with this error:
    ==========
    Error (2901)
    The operation did not complete successfully because of a parameter or call sequence that is not valid.
    The parameter is incorrect (0x80070057)
    Recommended Action
    Ensure that the parameters are valid, and then try the operation again.
    ==========
    I have successfully created a VM on one of the 2012 hosts and moved it to the other 2012 hosts.  I can move VMs from 2008 host to 2008 host.  I just cannot move VMs from 2008 host to 2012 host.
    Does SCVMM 2012 SP1 not support moving VMs from Hyper-V 2008 to Hyper-V 2012?

    Hello Kevin,
    Have you got an resolution yet ? Do you have latest update roll up pack applied to SCVMM 2012 SP1?
    With SCVMM 2012 SP1  " Running VMs (Live Migartion) and VMs which are in Saved state or having checkpoints can not be migrated from 2008R2 host to 2012 Host " 
    above was fixed in SCVMM 2012 Update Roll up 1
    Apart this please check the approx. size of data (VHDs) which will get transferred over the network , If you have large files chances are more to get such errors.
    Thanks
    ~NY

Maybe you are looking for

  • Why not 1 Database

    Hi! We have one Exchange 2003 Server with only a single database for 400 Users and it is working fine. We need to upgrade it to Exchange 2010 virtual server. Can we create only one database in Exchange 2010 and transfer the accounts from Exchange 200

  • How to make a form from a flow chart.

    I want to make a flow chart into a form for a website.  For example, I have a flow chart that leads to various solutions based on yes/no answers.  I want the user to be able to enter in yes or no, and be directed to further questions or answers based

  • Printing Flex Chart Application with FireFox 2 and later

    Hi, I have problem with printing functionality in FireFox. The print preview shows an empty page. So the user ends with this step and thinks no print is available. Another problem is when I try to print directly not the whole application will be prin

  • ECC6 TO 4.6C

    Hi Guys, I have developed a object in ECC 6.0. in that object i want move 4.6C with Transport Request and same functionality? what can i do.

  • Connector access via JNDI?

    I have a project on java.net - https://lucenerar.dev.java.net/ if you're interested - and I have a client class meant to hide all the JNDI and connector plumbing from my application. However, this class needs to look up the connector via JNDI. This i