locked
SQL Migration database for SCCM2012 RRS feed

  • Question

  • I will follow tomorrow this procedure previously suggested ,   in the step 5, where you place the new SQL server settings i have a question, in all the proccess i never see where they Create a new site System Server with the SQL role,  ifs that skipped because will be done in the "Perform site maintenance or reset this Site on the Setup Wizard" when modifying the Sql server Configuration?

    Thank you very much for your always help!

    http://blogs.technet.com/b/configurationmgr/archive/2013/04/02/how-to-move-the-configmgr-2012-site-database-to-a-new-sql-server.aspx

    Tuesday, January 12, 2016 11:59 PM

Answers

  • [SQL Server]Login failed for user 'rbi\mrosales.adm'. --> Domain admin and SCCM_global group seem not to be enough because you need SQL sysadmin rights on the SQL server.

    Torsten Meringer | http://www.mssccmfaq.de

    • Proposed as answer by Garth JonesMVP Thursday, January 14, 2016 5:44 PM
    • Marked as answer by Frank Dong Tuesday, January 26, 2016 8:41 AM
    Thursday, January 14, 2016 7:17 AM

All replies

  • Dear Sir,

    At the first time you install your, for example, stand-alone primary site,  after run the Splash, the wizard started.

    In the wizard, Database Information page you have to specify the SQL to store the settings and data.

    If this is not your question, could you clarify what's yours?

    Thanks in advance.

    Best regards

    Frank

    Wednesday, January 13, 2016 2:22 AM
  • I will migrate the sql server to a new server. I want to know that if that wizard setup to chanche the sql server also setup the site in that wizard process.
    Wednesday, January 13, 2016 2:36 AM
  • "Move" the database to the new server, run the wizard and point to the new SQL server. Done.

    Torsten Meringer | http://www.mssccmfaq.de

    Wednesday, January 13, 2016 7:25 AM
  • Torsten.

    It fail, can you help me know why my user profile  mrosales.adm its not working?   Im on the SCCM_global group, and im domain admin.

    <12-11-2013 16:21:35> ***** Exiting ConfigMgr 2012 Setup Bootstrapper ***** 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <12-11-2013 16:21:35> ***************************************************** 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-12-2016 17:44:37> ********************************************* 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-12-2016 17:44:37> ***** ConfigMgr 2012 Setup Bootstrapper ***** 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-12-2016 17:44:37> ********************************************* 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-12-2016 17:44:37> Commandline: 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-12-2016 17:44:37> "D:\Config Manager\bin\X64\SetupWpf.exe" 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-12-2016 17:44:37> INFO: Checking dotnet framework versions... 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-12-2016 17:44:37> INFO: Dotnet 3.5 installed 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-12-2016 17:44:37> Starting SetupWpf.exe... 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-12-2016 17:47:44> ***************************************************** 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-12-2016 17:47:44> ***** Exiting ConfigMgr 2012 Setup Bootstrapper ***** 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-12-2016 17:47:44> ***************************************************** 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-13-2016 16:17:41> ********************************************* 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-13-2016 16:17:41> ***** ConfigMgr 2012 Setup Bootstrapper ***** 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-13-2016 16:17:41> ********************************************* 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-13-2016 16:17:41> Commandline: 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-13-2016 16:17:41> "D:\Config Manager\bin\X64\SetupWpf.exe" 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-13-2016 16:17:41> INFO: Checking dotnet framework versions... 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-13-2016 16:17:41> INFO: Dotnet 3.5 installed 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    <01-13-2016 16:17:41> Starting SetupWpf.exe... 1/1/1601 12:00:00 AM 2006012043 (0x7791508B)
    INFO: Registered type IDCSQL02.RBI.LOCAL MASTER for IDCSQL02.rbi.local master Configuration Manager Setup 1/13/2016 4:19:03 PM 2260 (0x08D4)
    INFO: Registered type SMS Master for IDCSQL02.rbi.local master Configuration Manager Setup 1/13/2016 4:19:03 PM 2260 (0x08D4)
    INFO: Registered type IDCSQL02.RBI.LOCAL SCCM2012_UDT for IDCSQL02.rbi.local SCCM2012_UDT Configuration Manager Setup 1/13/2016 4:19:03 PM 2260 (0x08D4)
    INFO: Registered type SMS ACCESS for IDCSQL02.rbi.local SCCM2012_UDT Configuration Manager Setup 1/13/2016 4:19:03 PM 2260 (0x08D4)
    INFO: SQL Server version detected is 11.0, 11.0.3000.0 (SP1). Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Return code:0, Major:11, Minor:0, BuildNum:3000 Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    ~===================== << Starting Configuration Manager 2012 Setup >> ===================== Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: ConfigMgr2012 Setup was started by rbi\mrosales.adm. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Command line specified was: "D:\Config Manager\bin\X64\SetupWpf.exe" Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    FQDN for server IDCSCCM01 is IDCSCCM01.rbi.local Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Target computer is a 64 bit operating system. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Checking for existing setup information. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Setting setup type to  1. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Checking for existing SQL information. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: 'IDCSCCMSQL01.rbi.local' is a valid FQDN. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Verifying the registry entry for Asset Intelligence installation Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Found registry key for installation of Asset Intelligence full version Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Setup detected an existing Configuration Manager installation. Currently installed version is 7958 Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Phase is 1C7 Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    WARNING: Failed to initialize COM to get SDK Providers. It might already be initialized. return code: 80010106. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: SDK Provider is on IDCSCCM01.rbi.local. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Setting the default CSV folder path Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Language: Mobile Device (INTL), LangPack: 0. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Configuration Manager Build Number = 7958 Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Configuration Manager Version = 5.0 Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Configuration Manager Minimum Build Number = 800 Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Verifying Configuration Manager Active Directory Schema Extensions. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Found DS Root:CN=Schema,CN=Configuration,DC=rbi,DC=local Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Verifying Configuration Manager Active Directory Schema Extensions. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Found DS Root:CN=Schema,CN=Configuration,DC=rbi,DC=local Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: SqlMasterDB = master Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    Removed SQL alias IDCSCCMSQL01.rbi.local successfully. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Registered type IDCSCCMSQL01.RBI.LOCAL MASTER for IDCSCCMSQL01.rbi.local master Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Registered type SMS Master for IDCSCCMSQL01.rbi.local master Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Registered type IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT for IDCSCCMSQL01.rbi.local SCCM2012_UDT Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Registered type SMS ACCESS for IDCSCCMSQL01.rbi.local SCCM2012_UDT Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: 'IDCSCCM01.rbi.local' is a valid FQDN. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Run Site Maintenance on the primary site. Configuration Manager Setup 1/13/2016 4:19:04 PM 2260 (0x08D4)
    INFO: Checking for existing setup information. Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    INFO: Setting setup type to  1. Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    INFO: Checking for existing SQL information. Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    INFO: 'IDCSCCMSQL01.rbi.local' is a valid FQDN. Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    INFO: Verifying the registry entry for Asset Intelligence installation Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    INFO: Found registry key for installation of Asset Intelligence full version Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    INFO: SDK Provider is on IDCSCCM01.rbi.local. Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    INFO: Retrieving current site control image... Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'rbi\mrosales.adm'. Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    *** [28000][18456][Microsoft][SQL Server Native Client 11.0][SQL Server]Login failed for user 'rbi\mrosales.adm'. Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][SQL Server Native Client 11.0][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    *** Failed to connect to the SQL Server, connection type: SMS ACCESS. Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    CSiteSettings::ReadActualSCFFromDatabase: Failed to get sql connection Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    ERROR: Failed to retrieve verifiable site control data Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    INFO: Evaluating for Site Maintenance process. Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    INFO: File C:\Windows\smstsvc_test_1.exe does not exist. No zapping needed. Configuration Manager Setup 1/13/2016 4:19:05 PM 2260 (0x08D4)
    INFO: test loop count:0. Configuration Manager Setup 1/13/2016 4:19:11 PM 2260 (0x08D4)
    INFO: smstsvc_test_1 Return result <0> Configuration Manager Setup 1/13/2016 4:19:11 PM 2260 (0x08D4)
    INFO: g_SetupCmdLine.bMoveSql 1, g_SetupCmdLine.sNewSqlServer IDCSQL02.rbi.local, g_SetupCmdLine.sNewSqlDatabaseName SCCM2012_UDT, pSetupInf->SqlMasterDB master. Configuration Manager Setup 1/13/2016 4:19:13 PM 2260 (0x08D4)
    INFO:Query on dm_os_cluster_nodes succeeded. Configuration Manager Setup 1/13/2016 4:19:13 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:13 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:13 PM 2260 (0x08D4)
    *** Failed to connect to the SQL Server, connection type: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT. Configuration Manager Setup 1/13/2016 4:19:13 PM 2260 (0x08D4)
    INFO: SQL Connection failed. Connection: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT, Type: Unsecure Configuration Manager Setup 1/13/2016 4:19:13 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:16 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:16 PM 2260 (0x08D4)
    *** Failed to connect to the SQL Server, connection type: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT. Configuration Manager Setup 1/13/2016 4:19:16 PM 2260 (0x08D4)
    INFO: SQL Connection failed. Connection: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT, Type: Unsecure Configuration Manager Setup 1/13/2016 4:19:16 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:19 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:19 PM 2260 (0x08D4)
    *** Failed to connect to the SQL Server, connection type: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT. Configuration Manager Setup 1/13/2016 4:19:19 PM 2260 (0x08D4)
    INFO: SQL Connection failed. Connection: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT, Type: Unsecure Configuration Manager Setup 1/13/2016 4:19:19 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:22 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:22 PM 2260 (0x08D4)
    *** Failed to connect to the SQL Server, connection type: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT. Configuration Manager Setup 1/13/2016 4:19:22 PM 2260 (0x08D4)
    INFO: SQL Connection failed. Connection: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT, Type: Unsecure Configuration Manager Setup 1/13/2016 4:19:22 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:25 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:25 PM 2260 (0x08D4)
    *** Failed to connect to the SQL Server, connection type: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT. Configuration Manager Setup 1/13/2016 4:19:25 PM 2260 (0x08D4)
    INFO: SQL Connection failed. Connection: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT, Type: Unsecure Configuration Manager Setup 1/13/2016 4:19:25 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:28 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:28 PM 2260 (0x08D4)
    *** Failed to connect to the SQL Server, connection type: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT. Configuration Manager Setup 1/13/2016 4:19:28 PM 2260 (0x08D4)
    INFO: SQL Connection failed. Connection: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT, Type: Unsecure Configuration Manager Setup 1/13/2016 4:19:28 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:31 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:31 PM 2260 (0x08D4)
    *** Failed to connect to the SQL Server, connection type: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT. Configuration Manager Setup 1/13/2016 4:19:31 PM 2260 (0x08D4)
    INFO: SQL Connection failed. Connection: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT, Type: Unsecure Configuration Manager Setup 1/13/2016 4:19:31 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:34 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:34 PM 2260 (0x08D4)
    *** Failed to connect to the SQL Server, connection type: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT. Configuration Manager Setup 1/13/2016 4:19:34 PM 2260 (0x08D4)
    INFO: SQL Connection failed. Connection: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT, Type: Unsecure Configuration Manager Setup 1/13/2016 4:19:34 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:37 PM 2260 (0x08D4)
    *** [42000][4060][Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open database "SCCM2012_UDT" requested by the login. The login failed. Configuration Manager Setup 1/13/2016 4:19:37 PM 2260 (0x08D4)
    *** Failed to connect to the SQL Server, connection type: IDCSCCMSQL01.RBI.LOCAL SCCM2012_UDT. Configuration Manager Setup 1/13/2016 4:19:37 PM 2260 (0x08D4)
    INFO: SQL 

    Wednesday, January 13, 2016 10:53 PM
  • [SQL Server]Login failed for user 'rbi\mrosales.adm'. --> Domain admin and SCCM_global group seem not to be enough because you need SQL sysadmin rights on the SQL server.

    Torsten Meringer | http://www.mssccmfaq.de

    • Proposed as answer by Garth JonesMVP Thursday, January 14, 2016 5:44 PM
    • Marked as answer by Frank Dong Tuesday, January 26, 2016 8:41 AM
    Thursday, January 14, 2016 7:17 AM
  • Thanks torsten, it was kinda deep looking with system operators and SQL guys, but we made. Thank you very much for all the help, we are finally done!
    Thursday, January 14, 2016 4:48 PM