SQL 2012 SP1 VMM Deployment

Is it even possible to deploy sql 2012 sp1 with vmm?
The below are the high level steps I followed.
1. Create VM with Windows Server 2012 R2
2. Prepare the SQL Server 2012 SP1 image and note down the instance id used
3. Sysprep the VHD (generalize, oobe)
4. Copy the Syspreped VHD into VMM Library
5. Create VM template and map the syspreped VHD
6. Under SQL Configuration, specify all the SQL Configuration details(use the same instance id that was given during sql image preparation)
7. Create the Service Template
8. Create the Service and deploy to cloud or host groups
Error (22703)
The SQL media configured on the template is not supported by Virtual Machine Manager. Virtual Machine Manager only supports SQL2008 and SQL2012 for SQL deployment.
Recommended Action
Fix the SQL media path to point to a valid setup location for SQL2008 or SQL2012
Just to clarify, VM gets created just fine, sql setup doesn't even start, the error above is everything I could find regarding this issue.
The media is at c:\sql on the VHD file, I used the same path in deployment options.

Ok, you can close this. Here's a solution for my trouble (So yes, works with SQL 2012 SP1):
1. Create VM with Windows Server 2012 R2
2. Extract and copy the SQL Server ISO to C:\SQL, "install" sql, note the instance ID
3. Sysprep the VHD (generalize, oobe)
4. Copy the Syspreped VHD into VMM Library
5. Create VM template and map the syspreped VHD
6. Under SQL Configuration, specify all the SQL Configuration details, use the same instance id and media path that was given during sql image preparation. (Media path is case sensitive, but do not take my word for it. In case it's case insensitive
you got nothing to lose).
7. Create the Service Template
8. Create the Service and deploy to cloud or host groups
It works ONLY THIS WAY. NO installs from ISO or FILE share, only install SQL from locally copied setup files. I cannot believe how retarded that is. I got to give credits to the person that made me try all various ways to install it.
http://www.systemcentercentral.com/scvmm-2012-beta-sql-server-deployment/

Similar Messages

SCOM 2012 R2 Report Server component install to SQL 2012 Sp1 error?

Hi All
Im having issues installing SCOM 2012 R2 Report Server component to a SQL 2012 Sp1 Server (which is a Windows 2012 R2 Standard server). Im trying to install to the SQL Default server instance, note that the server also has a named instance
which hosts the SCOM databases. SQL Reporting Services is up and running fine (can access the web urls etc). Im also using the SCOM install account wich has full SQL and SCOM Server admin rights for the install. Ive checked that the Firewall
is off locally on the SQL Server, Ive also checked that the existing SCOM components are all in a Healthy state in the SCOM console.
The installed version of SQL Server could not be verified or is not supported. Verify that the computer and the installed version of SQL Server meet the minimum requirements for installation, and that the firewall settings are correct. See the Supported
Configurations document for further information.
Ive attempted the install on a standalone SQL Server away from the SQL Server hosting the SCOM databases, but encounter the same error. The full SCOM MSI Installer log details are below, line that appears most relevant is below but unsure why
this would be the case (same account that I used for SQL install etc). Any help much appreciated! : )
Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:51:46]: Debug: :CheckPrerequisites: IsComputerNameValidTitle: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :**************************************************
[11:51:46]: Debug: :<![CDATA[CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x86: 0CheckPrerequisites:   Logic Type:and AvicodeAgentInstalled-x64: 0]]>
[11:51:46]: Debug: :
[11:51:46]: Debug: :CheckPrerequisites: AVIcodeAgentCheck: Passed
[11:51:46]: Debug: :
[11:51:46]: Debug: :**************************************************
[11:51:46]: Always: :CheckPrerequisites: Return Value 0
[11:51:46]: Always: :Entering Page: AdditionalPrerequisitesPage
[11:51:48]: Always: :Entering Page: ShortEulaPage
[11:51:48]: Always: :Displaying localized EULA for localization: en
[11:51:48]: Always: :Displaying Eula: C:\Users\opsmgr\AppData\Local\SCOM\Setup\en\eula_en_notice.rtf
[11:51:49]: Info: :Info:User has agreed to EULA.
[11:51:50]: Always: :Entering Page: SelectManagementServerForReporting
[11:52:08]: Info: :Info:Management Server matches the current version of setup.
[11:52:08]: Always: :Entering Page: SelectReportingInstance
[11:52:08]: Always: :SQL Server SRS Instance (escaped name) RS_MSSQLSERVER
[11:52:08]: Info: :Attempting to get the SSRS version from:
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER:__NAMESPACE
[11:52:08]: Debug: :Path is
\\WDC-SYSSQL01\Root\Microsoft\SqlServer\ReportServer\RS_MSSQLSERVER\V11:MSReportServer_Instance
[11:52:08]: Always: :SRS instance on WDC-SYSSQL01. Version 11.0.3000.0.
[11:52:08]: Always: :No SRS instances on WDC-SYSSQL01.
[11:52:08]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:08]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:08]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:08]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:11]: Info: :Attempting to check SRS version
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
[11:52:11]: Error: :StackTrace:   at System.Version.TryParseVersion(String version, VersionResult& result)
   at System.Version.Parse(String input)
   at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckSRSVersion(String srsInstance, String requiredSRSVersion)
[11:52:28]: Info: :The user canceled setup
[11:52:28]: Always: :Begin: Property bag dump.
[11:52:28]: Always: :SetupStartTime = 26/03/2014 11:51:38
[11:52:28]: Always: :Collection ProtectedProperties (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = ActionAccountPassword
[11:52:28]: Always: : [1] = DASAccountPassword
[11:52:28]: Always: :DefaultLogName = C:\Users\opsmgr\AppData\Local\SCOM\Logs\OpsMgrSetupWizard.log
[11:52:28]: Always: :DefaultLogPath = C:\Users\opsmgr\AppData\Local\SCOM\Logs
[11:52:28]: Always: :path = F:\Setup\AMD64\
[11:52:28]: Always: :setupexepath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :ArchitectureIs64Check = True
[11:52:28]: Always: :OperationManagerAgentInstalled = 1
[11:52:28]: Always: :Collection ListOfSupportedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMCONSOLE
[11:52:28]: Always: : [1] = OMSERVER
[11:52:28]: Always: : [2] = OMWEBCONSOLE
[11:52:28]: Always: : [3] = OMREPORTING
[11:52:28]: Always: :install = 1
[11:52:28]: Always: :installpath = C:\Program Files\Microsoft System Center 2012 R2\Operations Manager
[11:52:28]: Always: :EulaFilesPath = C:\Users\opsmgr\AppData\Local\SCOM\Setup
[11:52:28]: Always: :HealthServiceTypeId = AB4C891F-3359-3FB6-0704-075FBFE36710
[11:52:28]: Always: :hsPort = C51B7833-DA54-1653-D8FD-1A738EF8DED5
[11:52:28]: Always: :ServerBlockReason = A Operations Manager agent was found on this computer. Please remove the agent and then run Setup again.
[11:52:28]: Always: :ScreensLoaded = 1
[11:52:28]: Always: :Collection ListOfSelectedComponents (System.Collections.ArrayList):
[11:52:28]: Always: : [0] = OMREPORTING
[11:52:28]: Always: :OMREPORTING = 1
[11:52:28]: Always: :SelectDatabaseInstanceReloadScreenInformation = 1
[11:52:28]: Always: :ReloadPrerequisitesPageChoice = PrerequisitesProgressPage
[11:52:28]: Always: :LoadedPrerequisiteXmlFile = True
[11:52:28]: Always: :PrerequisitesCheckXMLLoaded = True
[11:52:28]: Always: :CountFilteredPrerequisites_Failed = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Warning = 0
[11:52:28]: Always: :CountFilteredPrerequisites_PassedWithChoices = 0
[11:52:28]: Always: :CountFilteredPrerequisites_Passed = 10
[11:52:28]: Always: :PrerequisiteState = Passed
[11:52:28]: Always: :XmlFilteredPrerequisites_Passed : Begin XML property
[11:52:28]: Always: :<?xml version="1.0" encoding="utf-8"?><Root><Title TitleText="OMREPORTING"><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="memoryCheckTitle" descriptionBody="" descriptionTitle="ReportingMemCheckPassed" resolution="ReportingMemCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ntfsCheckTitle" descriptionBody="" descriptionTitle="ntfsCheckPassed" resolution="ntfsCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="DriveSpaceCheckTitle" descriptionBody="" descriptionTitle="ServerDriveSpaceCheckPassed" resolution="ServerDriveSpaceCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="OSVersionCheckTitle" descriptionBody="" descriptionTitle="OSVersionCheckPassed" resolution="OSVersionCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="WindowsInstallerCheckTitle" descriptionBody="" descriptionTitle="WindowsInstallerCheckPassed" resolution="WindowsInstallerCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="RemoteRegistryCheckTitle" descriptionBody="" descriptionTitle="RemoteRegistryCheckPassed" resolution="RemoteRegistryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="PendingRebootCheckTitle" descriptionBody="" descriptionTitle="PendingRebootCheckPassed" resolution="PendingRebootCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="ActiveDirectoryCheckTitle" descriptionBody="" descriptionTitle="ActiveDirectoryCheckPassed" resolution="ActiveDirectoryCheckResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="IsComputerNameValidTitle" descriptionBody="" descriptionTitle="IsComputerNameValidPassed" resolution="IsComputerNameValidResolution" /><Detail state="Passed" image="pack://application:,,,/SetupChainerUI;component/GreenCheck.png"
name="AVIcodeAgentCheck" descriptionBody="" descriptionTitle="AVICodeAgentCheckPassed" resolution="AVICodeAgentCheckResolution" /></Title></Root>
[11:52:28]: Always: :End XML property
[11:52:28]: Always: :ManagementServer = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :DefaultSDKMachine = WDC-SYSOPS01.landmarc.local
[11:52:28]: Always: :UserCanceledInstall = 1
[11:52:28]: Always: :InstallSuccess = 1
[11:52:28]: Always: :End: Property bag dump.
[11:52:28]: Debug: :CEIP disabled. CEIP data will NOT be sent.
[11:52:28]: Always: :Application Ended: Successful
[11:52:28]: Always: :
[2014-03-26T11:52:28.4724357+00:00]: Always: Trace Session Ended

Hi,
According to the error message:
[11:52:11]: Error: :getSQLInstanceVersion: Unable to find the SRS Instance Key: MSSQLSERVER
[11:52:11]: Info: :Info: WDC-SYSSQL01 SRS version =
[11:52:11]: Error: :Couldn't check SRS version: Threw Exception.Type: System.ArgumentException, Exception Error Code: 0x80070057, Exception.Message: Version string portion was too short or too long.
The issue is SQL report server database related, I would like to suggest you create a new report database for SCOM and then check the reuslt. Please refer to the below links and follow it to set up SCOM 2012 R2:
http://blogs.technet.com/b/kevinholman/archive/2013/01/16/opsmgr-2012-sp1-quickstart-deployment-guide.aspx
In addition, here is thread for your reference also:
http://social.technet.microsoft.com/Forums/en-US/3f883b7f-5a33-49f0-a40d-f3311e68609d/unable-to-connect-to-the-data-access-service-installing-report-server?forum=operationsmanagerreporting
Regards,
Yan Li
Regards, Yan Li

Moving Service Manager Database From SQL 2008 R2 SP2 to SQL 2012 SP1

Hi Guys,
Just looking for some clarification about moving our Service Manager 2012 R2 database to a new SQL Server.
Our Service Manager database is currently on a remote SQL server, shared with other databases, running SQL 2008 R2 SP2. It was originally setup this way as we only deployed Change Management but we are now wanting to deploy everything, fully
utilising SCSM/Orchestrator and Cireson's suite. Due to the limited resources available on that SQL server we are seeing performance issues before even getting it all up and running.
I want to move the Service Manager database to a new dedicated SQL server running SQL 2012 SP1. I am aware of the official DB move procedure but it does not specifically mention moving up SQL versions. I have seen some comments around here that
it is fine to do but some feedback would be good, it is not something I have done before.
All servers in this are fully patched Windows 2008 R2. Also, we do not currently have a Data Warehouse so do not need to worry about that. It was dropped and uninstalled before upgrading to Service Manager 2012 R2 and will be reinstalled after this DB move
using a separate dedicated SQL server.
Thanks, Chris.

As long as your collations and permissions are the same as before it
should not be a problem. That sad i could not find any other documentation saying it's not supported.
I have moved SCSM databases between different SQL-versions before and it has worked fine if the collations etc are correct.
Cheers,
Thomas Strömberg
System Center Specialist
Blog:
Twitter: LinkedIn:
Please remember to 'Propose as answer' if you find a reply helpful

Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5015. SQL 2012 SP1

Hi,
Please help. I was trying to remove a SQL 2012 SP1 two node clustered instance using setup (Mantenance -> Remove Node)
I started by doing this on passive node (and was successful) but when I ran setup on active node just before finishing successfully I got this error:
TITLE: Microsoft SQL Server 2012 Service Pack 1 Setup
The following error has occurred:
The resource 'BCK_SG1DB' could not be moved from cluster group 'SQL Server (SG1DB)' to cluster group 'Available Storage'.
Error: There was a failure to call cluster code from a provider. Exception message: Generic failure . Status code: 5015.
Description: The operation failed because either the specified cluster node is not the owner of the resource, or the node
is not a possible owner of the resource.
For help, click:
http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft%20SQL%20Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=11.0.3000.0&EvtType=0xE8049925%25400x42B4DED7
BUTTONS:
OK
I noticed that SG1DB instance was removed on both nodes but on Failover Cluster Manager -> Services and Applications the SQL server instance for SG1DB is still there. So I tried to delete it but got the error:
Failed to delete SQL Server SG1DB. An error was encountered while deleting the cluster service or
application SQL Server SG1DB. Could not move the resource to available storage. An error occured
while moving the resource BCK_SG1DB to the clustered service or application Available Storage
Any ideas why it failed or how could I delete the SQL server instance from Clauster?
Thx

Hello,
Please read the following resource.
https://support.microsoft.com/en-us/kb/kbview/313882?wa=wsignin1.0
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Reporting Services install on SQL 2012 SP1 instance blank

Sorry for the duplicate . . . didn't think the first on posted due to VDI locking up.
I have looked at all the links and tried the suggestions and I am still having the problem:
SCCM 2012 R2 SQL 2012 SP1 SSRS installed and configured (separate boxes)
When I try to add the reporting services role, it finds the SCCM database and verifies connectivity to it, the SSRS instance drop down is blank.
Using a domain service accout with local admin rights on both machines and sa rights in SQL.
There is a firewall between the Primary Server and the SQL Server and ports 80, 135, 443, 445, 1433 and the high RPC range.
Does anyone know how it is determining the instance? I have read it is via WMI but I am not sure if it is a query or executing a method. I have verified the svc acct has the correct DCOM privs.

Hi,
How are things going? Please let us know if there is any progress.
Regards.
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.

Reporting Service Error Code 7403, on SCCM 2012 R2 with SQL 2012 SP1 CU6

Dear All,
I am facing issue to install Reporting Services Point on SCCM 2012 R2 with SQL 2012 SP1 CU6. getting error messages id 7403. please let me know if SQL 2012 SP1 CU6 is supported with SCCM 2012 R2 or not & if you have any solution on it.
Error Message: The report server service is not running on Reporting Service Point server "SCCM2012"; start the service to enable reporting.

I am getting below error msg when trying to browse both sites
1) For Reports
The report server cannot decrypt the
symmetric key that is used to access sensitive or encrypted data in a report
server database. You must either restore a backup key or delete all encrypted
content. (rsReportServerDisabled)
Get Online Help
Keyset does not exist (Exception from
HRESULT:
0x80090016)
2) For Reportserver
Reporting Services Error
The report server cannot decrypt the symmetric key that is used to access
sensitive or encrypted data in a report server database. You must either restore
a backup key or delete all encrypted content. (rsReportServerDisabled)
Get Online Help
Keyset does not exist (Exception from HRESULT: 0x80090016)
SQL Server Reporting Services

Critical SMS_NOTIFICATION_SERVER ERROR sccm 2012 R2 WITH SQL 2012 SP1

Environement
SCCM 2012 R2
SQL 2012 SP1
On the same server
In sccm console i have in Monitoring - System Status - Component Status
critical SMS_NOTIFICATION_SERVER ERROR
Here are the two error that keep popping up
ERROR 1016
Site Component Manager failed to install this component on this site system.
Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in 60 minutes. To force Site Component Manager to immediately retry the installation, stop and restart
Site Component Manager using the Configuration Manager Service Manager.
Folowing message
ERROR 4951
Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install.
Refer to the BgbSetup.log, the bgbisapimsi.log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.
Here are the 2 logs
bgbsetuplog
<02/28/14 09:00:53> ====================================================================
<02/28/14 09:00:53> SMSBGB Setup Started....
<02/28/14 09:00:53> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:TCI-SCCMR2-LAV SMSBGB 0
<02/28/14 09:00:53> Installing Pre Reqs for SMSBGB
<02/28/14 09:00:53>         ======== Installing Pre Reqs for Role SMSBGB ========
<02/28/14 09:00:53> Found 1 Pre Reqs for Role SMSBGB
<02/28/14 09:00:53> Pre Req SqlNativeClient found.
<02/28/14 09:00:53> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<02/28/14 09:00:53> Pre Req SqlNativeClient is already installed. Skipping it.
<02/28/14 09:00:53>         ======== Completed Installation of Pre Reqs for Role SMSBGB ========
<02/28/14 09:00:53> Installing the SMSBGB
<02/28/14 09:00:53> Passed OS version check.
<02/28/14 09:00:53> IIS Service is installed.
<02/28/14 09:00:53> SMSBGB already installed (Product Code: {A78E8003-2307-4B70-B7CD-1A07C0A31D21}). Upgrading/Reinstalling SMSBGB
<02/28/14 09:00:53> New SMSBGB is the same product code. This is a minor upgrade.
<02/28/14 09:00:53> Enabling MSI logging. bgbisapi.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log
<02/28/14 09:00:53> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration
Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<02/28/14 09:01:01> bgbisapi.msi exited with return code: 0
<02/28/14 09:01:01> Installation was successful.
<02/28/14 09:01:01> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /u "D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<02/28/14 09:01:04> CTool::RegisterComPlusService: Failed to unregister D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<02/28/14 09:01:04> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /extlb /tlb:"D:\Program Files\SMS_CCM\microsoft.configurationmanager.bgbserverchannel.tlb" "D:\Program
Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<02/28/14 09:01:07> CTool::RegisterComPlusService: Failed to register D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<02/28/14 09:01:07> Cannot register BGB server channel DLL D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
<02/28/14 09:01:07> Fatal MSI Error - bgbisapi.msi could not be install
bgpisapi.log
MSI (s) (00:60) [09:01:01:660]: Product: BGB http proxy -- Configuration completed successfully.
MSI (s) (00:60) [09:01:01:661]: Windows Installer reconfigured the product. Product Name: BGB http proxy. Product Version: 5.00.7958.1000. Product Language: 1033. Manufacturer: Microsoft Corporation. Reconfiguration success or error status: 0.
MSI (s) (00:60) [09:01:01:665]: Deferring clean up of packages/files, if any exist
MSI (s) (00:60) [09:01:01:665]: MainEngineThread is returning 0
MSI (s) (00:04) [09:01:01:670]: RESTART MANAGER: Session closed.
MSI (s) (00:04) [09:01:01:670]: No System Restore sequence number for this installation.
=== Logging stopped: 2/28/2014 9:01:01 ===
MSI (s) (00:04) [09:01:01:674]: User policy value 'DisableRollback' is 0
MSI (s) (00:04) [09:01:01:674]: Machine policy value 'DisableRollback' is 0
MSI (s) (00:04) [09:01:01:674]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (00:04) [09:01:01:675]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:04) [09:01:01:677]: Note: 1: 2265 2: 3: -2147287035
MSI (s) (00:04) [09:01:01:678]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (00:04) [09:01:01:678]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (00:04) [09:01:01:679]: Destroying RemoteAPI object.
MSI (s) (00:B8) [09:01:01:679]: Custom Action Manager thread ending.
MSI (c) (3C:B8) [09:01:01:686]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (3C:B8) [09:01:01:686]: MainEngineThread is returning 0
MSI (c) (3C:B0) [09:01:01:690]: RESTART MANAGER: Session closed.
=== Verbose logging stopped: 2/28/2014 9:01:01 ===

Problem not fixed SORRY GUY'S
Environement
1 SERVER
WINDOWS SERVER 2012 R2
SQL SERVER 2012 SP1
SCCM 2012 R2
ERROR in system center
Message ID 1016
Site Component Manager failed to install this component on this site system.
Solution: Review the previous status messages to determine the exact reason for the failure. Site Component Manager will automatically retry the installation in 60 minutes. To force Site Component Manager to immediately retry the installation, stop and restart
Site Component Manager using the Configuration Manager Service Manager.
Message ID
4951
Site Component Manager failed to install this component, because the Microsoft Installer File for this component (bgbisapi.msi) could not install.
Refer to the BgbSetup.log, the bgbisapimsi.log, as well as the ConfigMgr Documentation and the Microsoft Knowledge Base for further information.
BGPSETUP.LOG
<03/05/14 09:49:33> ====================================================================
<03/05/14 09:49:33> SMSBGB Setup Started....
<03/05/14 09:49:33> Parameters: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe /install /siteserver:TCI-SCCMR2-LAV SMSBGB 0
<03/05/14 09:49:33> Installing Pre Reqs for SMSBGB
<03/05/14 09:49:33>         ======== Installing Pre Reqs for Role SMSBGB ========
<03/05/14 09:49:33> Found 1 Pre Reqs for Role SMSBGB
<03/05/14 09:49:33> Pre Req SqlNativeClient found.
<03/05/14 09:49:33> SqlNativeClient already installed (Product Code: {D411E9C9-CE62-4DBF-9D92-4CB22B750ED5}). Would not install again.
<03/05/14 09:49:33> Pre Req SqlNativeClient is already installed. Skipping it.
<03/05/14 09:49:33>         ======== Completed Installation of Pre Reqs for Role SMSBGB ========
<03/05/14 09:49:33> Installing the SMSBGB
<03/05/14 09:49:33> Passed OS version check.
<03/05/14 09:49:33> IIS Service is installed.
<03/05/14 09:49:33> SMSBGB already installed (Product Code: {A78E8003-2307-4B70-B7CD-1A07C0A31D21}). Upgrading/Reinstalling SMSBGB
<03/05/14 09:49:33> New SMSBGB is the same product code. This is a minor upgrade.
<03/05/14 09:49:33> Enabling MSI logging. bgbisapi.msi will log to D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log
<03/05/14 09:49:33> Installing D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR="D:\Program Files\SMS_CCM" CCMSERVERDATAROOT="D:\Program Files\Microsoft Configuration
Manager" USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1
<03/05/14 09:49:41> bgbisapi.msi exited with return code: 0
<03/05/14 09:49:41> Installation was successful.
<03/05/14 09:49:41> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /u "D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<03/05/14 09:49:43> CTool::RegisterComPlusService: Failed to unregister D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<03/05/14 09:49:43> CTool::RegisterComPlusService: run command line: "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe" /extlb /tlb:"D:\Program Files\SMS_CCM\microsoft.configurationmanager.bgbserverchannel.tlb" "D:\Program
Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll"
<03/05/14 09:49:45> CTool::RegisterComPlusService: Failed to register D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll with .Net Fx 4.0
<03/05/14 09:49:45> Cannot register BGB server channel DLL D:\Program Files\Microsoft Configuration Manager\bin\x64\microsoft.configurationmanager.bgbserverchannel.dll. Installation cannot continue.
<03/05/14 09:49:45> Fatal MSI Error - bgbisapi.msi could not be installed.
<03/05/14 09:49:45> ~RoleSetup().
BGBISAPI.LOG
=== Verbose logging started: 3/5/2014 9:49:33 Build type: SHIP UNICODE 5.00.9600.00 Calling process: D:\Program Files\Microsoft Configuration Manager\bin\x64\rolesetup.exe ===
MSI (c) (08:C0) [09:49:33:974]: Resetting cached policy values
MSI (c) (08:C0) [09:49:33:974]: Machine policy value 'Debug' is 0
MSI (c) (08:C0) [09:49:33:974]: ******* RunEngine:
           ******* Product: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (08:C0) [09:49:33:974]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (08:C0) [09:49:33:974]: Grabbed execution mutex.
MSI (c) (08:C0) [09:49:34:021]: Cloaking enabled.
MSI (c) (08:C0) [09:49:34:021]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (08:C0) [09:49:34:025]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (C4:E4) [09:49:34:039]: Running installation inside multi-package transaction D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
MSI (s) (C4:E4) [09:49:34:039]: Grabbed execution mutex.
MSI (s) (C4:E8) [09:49:34:045]: Resetting cached policy values
MSI (s) (C4:E8) [09:49:34:045]: Machine policy value 'Debug' is 0
MSI (s) (C4:E8) [09:49:34:045]: ******* RunEngine:
           ******* Product: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
           ******* Action:
           ******* CommandLine: **********
MSI (s) (C4:E8) [09:49:34:047]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (C4:E8) [09:49:34:053]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (C4:E8) [09:49:34:057]: SRSetRestorePoint skipped for this transaction.
MSI (s) (C4:E8) [09:49:34:058]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer 3: 2
MSI (s) (C4:E8) [09:49:34:060]: File will have security applied from OpCode.
MSI (s) (C4:E8) [09:49:34:065]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi' against software restriction policy
MSI (s) (C4:E8) [09:49:34:065]: SOFTWARE RESTRICTION POLICY: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi has a digital signature
MSI (s) (C4:E8) [09:49:34:067]: SOFTWARE RESTRICTION POLICY: D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi is permitted to run because the user token authorizes execution (system or service token).
MSI (s) (C4:E8) [09:49:34:067]: MSCOREE not loaded loading copy from system32
MSI (s) (C4:E8) [09:49:34:077]: End dialog not enabled
MSI (s) (C4:E8) [09:49:34:077]: Original package ==> D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi
MSI (s) (C4:E8) [09:49:34:077]: Package we're running from ==> C:\Windows\Installer\3897f9.msi
MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall Flags override found.
MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall VersionNT override found.
MSI (s) (C4:E8) [09:49:34:080]: APPCOMPAT: Uninstall ServicePackLevel override found.
MSI (s) (C4:E8) [09:49:34:081]: APPCOMPAT: looking for appcompat database entry with ProductCode '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'.
MSI (s) (C4:E8) [09:49:34:081]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (C4:E8) [09:49:34:094]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisablePatch' is 0
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'AllowLockdownPatch' is 0
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (C4:E8) [09:49:34:094]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (C4:E8) [09:49:34:095]: APPCOMPAT: looking for appcompat database entry with ProductCode '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'.
MSI (s) (C4:E8) [09:49:34:095]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (C4:E8) [09:49:34:096]: Transforms are not secure.
MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'D:\Program Files\Microsoft Configuration Manager\logs\bgbisapiMSI.log'.
MSI (s) (C4:E8) [09:49:34:096]: Command Line: REINSTALL=ALL REINSTALLMODE=vmaus CCMINSTALLDIR=D:\Program Files\SMS_CCM CCMSERVERDATAROOT=D:\Program Files\Microsoft Configuration Manager USESMSPORTS=TRUE SMSPORTS=80 USESMSSSLPORTS=TRUE SMSSSLPORTS=443 USESMSSSL=TRUE
SMSSSLSTATE=0 CCMENABLELOGGING=TRUE CCMLOGLEVEL=1 CCMLOGMAXSIZE=1000000 CCMLOGMAXHISTORY=1 CURRENTDIRECTORY=D:\Program Files\Microsoft Configuration Manager\bin\x64 CLIENTUILEVEL=3 MSICLIENTUSESEXTERNALUI=1 CLIENTPROCESSID=5384
MSI (s) (C4:E8) [09:49:34:096]: Product Code passed to Engine.Initialize:           '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
MSI (s) (C4:E8) [09:49:34:096]: Product Code from property table before transforms: '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
MSI (s) (C4:E8) [09:49:34:096]: Product Code from property table after transforms: '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}'
MSI (s) (C4:E8) [09:49:34:096]: Product registered: entering maintenance mode
MSI (s) (C4:E8) [09:49:34:096]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.
MSI (s) (C4:E8) [09:49:34:096]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is admin assigned: LocalSystem owns the publish key.
MSI (s) (C4:E8) [09:49:34:096]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is managed.
MSI (s) (C4:E8) [09:49:34:096]: MSI_LUA: Credential prompt not required, user is an admin
MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.
MSI (s) (C4:E8) [09:49:34:096]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:096]: Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (s) (C4:E8) [09:49:34:096]: Specifed source is already in a list.
MSI (s) (C4:E8) [09:49:34:096]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (C4:E8) [09:49:34:096]: Machine policy value 'DisableBrowse' is 0
MSI (s) (C4:E8) [09:49:34:096]: Machine policy value 'AllowLockdownBrowse' is 0
MSI (s) (C4:E8) [09:49:34:096]: Adding new sources is allowed.
MSI (s) (C4:E8) [09:49:34:097]: Package name retrieved from configuration data: 'bgbisapi.msi'
MSI (s) (C4:E8) [09:49:34:099]: Note: 1: 2262 2: AdminProperties 3: -2147287038
MSI (s) (C4:E8) [09:49:34:099]: Machine policy value 'DisableMsi' is 1
MSI (s) (C4:E8) [09:49:34:099]: Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (C4:E8) [09:49:34:099]: User policy value 'AlwaysInstallElevated' is 0
MSI (s) (C4:E8) [09:49:34:099]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is admin assigned: LocalSystem owns the publish key.
MSI (s) (C4:E8) [09:49:34:099]: Product {A78E8003-2307-4B70-B7CD-1A07C0A31D21} is managed.
MSI (s) (C4:E8) [09:49:34:099]: Running product '{A78E8003-2307-4B70-B7CD-1A07C0A31D21}' with elevated privileges: Product is assigned.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding REINSTALL property. Its value is 'ALL'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding REINSTALLMODE property. Its value is 'vmaus'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMINSTALLDIR property. Its value is 'D:\Program Files\SMS_CCM'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMSERVERDATAROOT property. Its value is 'D:\Program Files\Microsoft Configuration Manager'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSPORTS property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSPORTS property. Its value is '80'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSSSLPORTS property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSSSLPORTS property. Its value is '443'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding USESMSSSL property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding SMSSSLSTATE property. Its value is '0'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMENABLELOGGING property. Its value is 'TRUE'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGLEVEL property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGMAXSIZE property. Its value is '1000000'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CCMLOGMAXHISTORY property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CURRENTDIRECTORY property. Its value is 'D:\Program Files\Microsoft Configuration Manager\bin\x64'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CLIENTUILEVEL property. Its value is '3'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding MSICLIENTUSESEXTERNALUI property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:099]: PROPERTY CHANGE: Adding CLIENTPROCESSID property. Its value is '5384'.
MSI (s) (C4:E8) [09:49:34:100]: Machine policy value 'DisableAutomaticApplicationShutdown' is 0
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding MsiRestartManagerSessionKey property. Its value is '1ea81ab83bbb7c48a58c04b46f112051'.
MSI (s) (C4:E8) [09:49:34:104]: RESTART MANAGER: Session opened.
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding MsiSystemRebootPending property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:104]: TRANSFORMS property is now:
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding PRODUCTLANGUAGE property. Its value is '1033'.
MSI (s) (C4:E8) [09:49:34:104]: PROPERTY CHANGE: Adding VersionDatabase property. Its value is '200'.
MSI (s) (C4:E8) [09:49:34:106]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming
MSI (s) (C4:E8) [09:49:34:106]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Favorites
MSI (s) (C4:E8) [09:49:34:108]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Network Shortcuts
MSI (s) (C4:E8) [09:49:34:109]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Documents
MSI (s) (C4:E8) [09:49:34:109]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Printer Shortcuts
MSI (s) (C4:E8) [09:49:34:110]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Recent
MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\SendTo
MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Templates
MSI (s) (C4:E8) [09:49:34:111]: SHELL32::SHGetFolderPath returned: C:\ProgramData
MSI (s) (C4:E8) [09:49:34:112]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Local
MSI (s) (C4:E8) [09:49:34:114]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Pictures
MSI (s) (C4:E8) [09:49:34:124]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (C4:E8) [09:49:34:128]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (C4:E8) [09:49:34:129]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu\Programs
MSI (s) (C4:E8) [09:49:34:131]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Start Menu
MSI (s) (C4:E8) [09:49:34:132]: SHELL32::SHGetFolderPath returned: C:\Users\Public\Desktop
MSI (s) (C4:E8) [09:49:34:135]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Administrative Tools
MSI (s) (C4:E8) [09:49:34:137]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup
MSI (s) (C4:E8) [09:49:34:138]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs
MSI (s) (C4:E8) [09:49:34:139]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\AppData\Roaming\Microsoft\Windows\Start Menu
MSI (s) (C4:E8) [09:49:34:141]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Desktop
MSI (s) (C4:E8) [09:49:34:144]: SHELL32::SHGetFolderPath returned: C:\ProgramData\Microsoft\Windows\Templates
MSI (s) (C4:E8) [09:49:34:144]: SHELL32::SHGetFolderPath returned: C:\Windows\Fonts
MSI (s) (C4:E8) [09:49:34:144]: Note: 1: 2898 2: MS Sans Serif 3: MS Sans Serif 4: 0 5: 16
MSI (s) (C4:E8) [09:49:34:156]: MSI_LUA: Setting AdminUser property to 1 because the product is already installed managed and per-machine
MSI (s) (C4:E8) [09:49:34:156]: MSI_LUA: Setting MsiRunningElevated property to 1 because the install is already running elevated.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding MsiRunningElevated property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding Privileged property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:156]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding USERNAME property. Its value is 'Windows User'.
MSI (s) (C4:E8) [09:49:34:156]: Note: 1: 1402 2: HKEY_CURRENT_USER\Software\Microsoft\MS Setup (ACME)\User Info 3: 2
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding Installed property. Its value is '00:00:00'.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding DATABASE property. Its value is 'C:\Windows\Installer\3897f9.msi'.
MSI (s) (C4:E8) [09:49:34:156]: PROPERTY CHANGE: Adding OriginalDatabase property. Its value is 'D:\Program Files\Microsoft Configuration Manager\bin\x64\bgbisapi.msi'.
MSI (s) (C4:E8) [09:49:34:156]: Machine policy value 'MsiDisableEmbeddedUI' is 0
MSI (s) (C4:E8) [09:49:34:156]: EEUI - Disabling MsiEmbeddedUI due to existing external or embedded UI
MSI (s) (C4:E8) [09:49:34:156]: EEUI - Disabling MsiEmbeddedUI for service because it's not a quiet/basic install
MSI (s) (C4:E8) [09:49:34:159]: Note: 1: 2205 2: 3: PatchPackage
MSI (s) (C4:E8) [09:49:34:159]: Machine policy value 'DisableRollback' is 0
MSI (s) (C4:E8) [09:49:34:159]: User policy value 'DisableRollback' is 0
MSI (s) (C4:E8) [09:49:34:159]: PROPERTY CHANGE: Adding UILevel property. Its value is '2'.
MSI (s) (C4:E8) [09:49:34:159]: PROPERTY CHANGE: Adding QFEUpgrade property. Its value is '1'.
=== Logging started: 3/5/2014 9:49:34 ===
MSI (s) (C4:E8) [09:49:34:161]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038
MSI (s) (C4:E8) [09:49:34:161]: PROPERTY CHANGE: Adding Preselected property. Its value is '1'.
MSI (s) (C4:E8) [09:49:34:161]: APPCOMPAT: [DetectVersionLaunchCondition] Launch condition already passes.
MSI (s) (C4:E8) [09:49:34:163]: PROPERTY CHANGE: Adding ACTION property. Its value is 'INSTALL'.
MSI (s) (C4:E8) [09:49:34:163]: Doing action: INSTALL
Action start 9:49:34: INSTALL.
MSI (s) (C4:E8) [09:49:34:165]: Running ExecuteSequence
MSI (s) (C4:E8) [09:49:34:165]: Doing action: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61
MSI (s) (C4:E8) [09:49:34:166]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61'
MSI (s) (C4:E8) [09:49:34:167]: PROPERTY CHANGE: Adding SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61 property. Its value is 'C:\Windows\SysWOW64\'.
Action start 9:49:34: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61.
MSI (s) (C4:E8) [09:49:34:167]: Doing action: System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61
Action ended 9:49:34: SystemFolder.F65FD590_5BEA_48BE_8408_26F7244E8B61. Return value 1.
MSI (s) (C4:E8) [09:49:34:169]: Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'System64Folder.F65FD590_5BEA_48BE_8408_26F7244E8B61'
MSI

SQL 2012 SP1 installation quick questions

I am installing my first SQL 2012 SP1 Enterprise Core (x64). The installation failed to install some services due to an error installing .Net framework 3.5. It was able to install successfully several features including Analysis Services
and Integration services, but not the Database Engine, Management tools and Reporting services.
Note: I ran the set up and my user is an administrator in the target server, but I did not right clicking on setup.exe and "Run as administrator" .
I have two questions
1) Did I had to run the setup by Right clicking on setup.exe and "Run as administrator"?
2) Now that my installation failed. After installing the missing requirements....Do I:
a) Uninstall the current failed installation
b) Do I attempt to install again "on top of the existing installation".
c) Redo the whole server and start fresh.
I am open to expert suggestions. Please help
Paulino

Hello,
1. If you are already logged in as Administrator, there is no need to use the Run as Administrator option.
2. I would choose to uninstall everything and install again. Since were are installing from the Command Prompt, and we do not have the
GUI, and we are not familiar with the command line options.
Please use the following article to install SQL Server 2012 on Windows Server Core:
http://www.sqlcoffee.com/SQLServer2012_0005.htm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Upgrading SQL 2008 R2 to SQL 2012 SP1

Hi everyone,
We are testing some upgrades in a lab environment. We have upgraded to SCCM 2012 R2 and are now looking at upgrading to SQL 2012 SP1 from SQL 2008 R2. Both SCCM and SQL are on one server. (The next step is to split SCCM and SQL but that's another topic)
The question we are asking is, what should be our process for the upgrade? Do we need to stop SCCM services before doing the SQL upgrade? If, so, which ones?

Hi,
You need to stop all Configuration Manager services at the site.
For the process of the upgrade, you could check the following document.
http://technet.microsoft.com/en-us/library/gg682077.aspx#BKMK_SupConfigUpgradeDBSrv
Best Regards,
Joyce
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.

Reports not Generated after moving SCCM 2012 SP1 DB on SQL 2012 SP1 cluster

Hi all,
i have moved my SCCM 2012 SP1 DB on SQL 2012 SP1 Failover Cluster,this cluster is a two node cluster.the DB was moved fine and the DB configuration in SCCM Site maintenance was also done successfully.After the migration process,SCCM was working fine created
few collections & packages, then checked the DB on cluster & they were updated successfully.
but when i tried to install report server on my SCCM machine,again there was no instance displayed after entering the cluster name.
I searched this & come across this post :-
http://social.technet.microsoft.com/Forums/en-US/configmanagergeneral/thread/4479e73e-8a19-4c7e-9418-b36770656b9b/
which says to install report server on the cluster node machine which is currently running the Reporting Service.I tried to install the report server & the instance was detected this time.it was installed successfully.
But when i tried to generate reports I got this error :-
Permissions are fine as i have added SCCMadmin & sccm machine in the local admin of both the nodes.
Please Help.
Thanks,
Pranay.

Yes, I know this is an old post, but I’m trying to clean them up. Did you solve this problem, if so what was the solution?
If you look at your second screenshot the Remote errors is not enabled. Use this blog to enable them.
http://www.enhansoft.com/blog/enabling-remote-errors-in-sql
If changing the data source on the report fixed it for a single report. It means that your shared Datasource is having problems. Reset the username and password within CM12 console and this should fix it for every report.
Garth Jones | My blogs: Enhansoft and
Old Blog site | Twitter:
@GarthMJ

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

Orchestrator 2012 R2 on SQL 2012 SP1 Availability Group

Hi all,
I've recently setup a new install of SCOrch 2012 R2 on a SQL 2012 SP1 Availability Group. Everything went smooth and appears to be functioning correctly up until a failover occurs (manual or automatic). Once there is a failover between database
nodes, the Orchestrator servers (Mgmt and Runbook) lose connectivity to the database and will not reconnect until the services are restarted and then they work again.
Has anyone setup Orchestrator on an Availability Group and are you seeing similar issues from a failover?
Thanks!
Jon

Hi Jon,
has each member of the availability group the same master key to read encrypted data like passwords and the license code?
https://blog.uvm.edu/jgm/2013/05/28/sql-2012-tde-and-availability-groups/
Btw, if you still interested in a SAP IP:
http://www.sc-orchestrator.eu/index.php/integration-packs/integration-pack-fuer-sap-vip4sap
Regards,
Stefan
www.sc-orchestrator.eu ,
Blog sc-orchestrator.eu

SQL 2012 sp1 EE setup disappears when installing Setup Support files ( Error: sqm does not have active session)

HI Folks,
WIndows : 2008 R2
SQL : 2012 sp1 EE
Setup disappears when installing setup support files On passiive node ( 2 node cluster), sql is runing on active node without any issue
Error : SQM does not active session ( In summary detail txt file)
blog is suggesting . Save the following in a .reg file and merge to populate the registry: (
here i am confusing how to save and where to save , how to merge and how to populate)
http://blogs.msdn.com/b/sqljourney/archive/2012/05/07/sql-2008-2008-r2-setup-disappears-fails-when-installing-setup-support-files.aspx
Can you share your views, if you need any information for clarification. pls let us know for resolution.
Thanks in Advance.

Sorry but there is already released SP2 for SQL Server 2012. Start installation on the passive node first
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

SQL 2012 SP1 and SCCM 2012 SP1

Hi,
I am installing SCCM 2012 SP1 with SQL 2012 SP1 in Stand-Alone mode. But I am receiving error:"the service broker endpoint cannot listen on port 4022 because it is in use by another process"
I saw in SQL (SQL Server Configuration Manager) that I am using port 4022 without dinamic port.
Thaks.
Lessandro Zampieri - http://lezampieri.com

Thanks for the reply.
C:\>netstat -ano
Active Connections
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING 780
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:4022 0.0.0.0:0 LISTENING 4664
TCP 0.0.0.0:5985 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:47001 0.0.0.0:0 LISTENING 4
TCP 0.0.0.0:49152 0.0.0.0:0 LISTENING 528
TCP 0.0.0.0:49153 0.0.0.0:0 LISTENING 836
TCP 0.0.0.0:49154 0.0.0.0:0 LISTENING 900
TCP 0.0.0.0:49155 0.0.0.0:0 LISTENING 624
TCP 0.0.0.0:49156 0.0.0.0:0 LISTENING 624
TCP 0.0.0.0:49217 0.0.0.0:0 LISTENING 616
TCP 0.0.0.0:49219 0.0.0.0:0 LISTENING 4184
TCP 0.0.0.0:49389 0.0.0.0:0 LISTENING 2056
TCP 0.0.0.0:49627 0.0.0.0:0 LISTENING 5060
TCP 127.0.0.1:49390 0.0.0.0:0 LISTENING 2056
TCP 127.0.0.1:49628 0.0.0.0:0 LISTENING 5060
TCP 127.0.0.1:57593 0.0.0.0:0 LISTENING 4664
TCP 192.168.100.30:139 0.0.0.0:0 LISTENING 4
TCP 192.168.100.30:445 192.168.100.20:49420 ESTABLISHED 4
TCP 192.168.100.30:445 192.168.100.20:49421 ESTABLISHED 4
TCP 192.168.100.30:445 192.168.100.20:49422 ESTABLISHED 4
TCP 192.168.100.30:445 192.168.100.20:49423 ESTABLISHED 4
TCP 192.168.100.30:4022 192.168.100.30:61430 ESTABLISHED 4664
TCP 192.168.100.30:4022 192.168.100.30:61496 ESTABLISHED 4664
TCP 192.168.100.30:49627 192.168.100.40:55914 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55915 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55921 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55922 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55926 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55927 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55928 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55929 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55930 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55967 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55992 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:55998 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56001 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56002 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56009 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56077 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56211 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56656 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56687 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56817 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56891 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56946 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:56959 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57027 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57072 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57223 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57240 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57248 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57268 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57292 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57293 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57294 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57311 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57312 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57314 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57320 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57340 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57342 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57343 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57369 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57372 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57379 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57385 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57386 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57387 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57388 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57389 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57390 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57391 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57392 ESTABLISHED 5060
TCP 192.168.100.30:49627 192.168.100.40:57393 ESTABLISHED 5060
TCP 192.168.100.30:61430 192.168.100.30:4022 ESTABLISHED 4112
TCP 192.168.100.30:61496 192.168.100.30:4022 ESTABLISHED 4112
TCP 192.168.100.30:61537 192.168.100.10:49158 TIME_WAIT 0
TCP [::]:80 [::]:0 LISTENING 4
TCP [::]:135 [::]:0 LISTENING 780
TCP [::]:443 [::]:0 LISTENING 4
TCP [::]:445 [::]:0 LISTENING 4
TCP [::]:4022 [::]:0 LISTENING 4664
TCP [::]:5985 [::]:0 LISTENING 4
TCP [::]:47001 [::]:0 LISTENING 4
TCP [::]:49152 [::]:0 LISTENING 528
TCP [::]:49153 [::]:0 LISTENING 836
TCP [::]:49154 [::]:0 LISTENING 900
TCP [::]:49155 [::]:0 LISTENING 624
TCP [::]:49156 [::]:0 LISTENING 624
TCP [::]:49217 [::]:0 LISTENING 616
TCP [::]:49219 [::]:0 LISTENING 4184
TCP [::]:49389 [::]:0 LISTENING 2056
TCP [::]:49627 [::]:0 LISTENING 5060
TCP [::1]:49390 [::]:0 LISTENING 2056
TCP [::1]:49628 [::]:0 LISTENING 5060
TCP [::1]:57593 [::]:0 LISTENING 4664
UDP 0.0.0.0:123 *:* 948
UDP 0.0.0.0:500 *:* 900
UDP 0.0.0.0:1434 *:* 3000
UDP 0.0.0.0:4500 *:* 900
UDP 0.0.0.0:5355 *:* 124
UDP 127.0.0.1:51181 *:* 4132
UDP 127.0.0.1:51338 *:* 124
UDP 127.0.0.1:55475 *:* 900
UDP 127.0.0.1:59835 *:* 1628
UDP 127.0.0.1:60840 *:* 3596
UDP 127.0.0.1:62010 *:* 1816
UDP 127.0.0.1:62390 *:* 4112
UDP 127.0.0.1:64129 *:* 624
UDP 192.168.100.30:137 *:* 4
UDP 192.168.100.30:138 *:* 4
UDP [::]:123 *:* 948
UDP [::]:500 *:* 900
UDP [::]:1434 *:* 3000
UDP [::]:4500 *:* 900
All things are correct?
Att.,
Lessandro Zampieri - http://lezampieri.com

Silent install parameters for Mgmt Studio (from SQL 2012 SP1 Express)

Hi All,
I'm looking to incorporate the installation of SQL Management studio ONLY from the SQL 2012 Sp1 Express bundle, into System Centre Configuration Manager. I need the silent installation options to install all features for it.
File used - SQLManagementStudio_x64_ENU.exe
From URL - http://www.microsoft.com/en-ca/download/details.aspx?id=35579
I'm looking for something like this:
"SQLManagementStudio_x64_ENU.exe /ACTION=INSTALL /QUIET /IAcceptSQLServerLicenseTerms="True"
/FEATURES= etc.....
Can anyone point me in the right direction? I just want to run the command and have it install SQL 2012
Management Studio (this one is the full version) without having to run through the whole setup.exe process and it's silent installation..
Thanks in advance

Hello,
First you need to extract the content of the .EXE file to a local folder, as shown below:
SQLManagementStudio_x64_ENU.exe /x
Then you can try to run the following command:
"c:\folder_containing_installation_files\setup.exe" /ACTION=INSTALL /QUIET /FEATURES=SSMS /HIDECONSOLE
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL 2012 SP1 VMM Deployment

Similar Messages

Maybe you are looking for