Jump to content


Search the Community

Showing results for tags 'ConfigMgr_DViewAccess'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Cloud
    • Azure
    • Microsoft Intune
    • Office 365
  • General Stuff
    • General Chat
    • Events
    • Site News
    • Windows News
    • Suggestion box
    • Jobs
  • MDT, SMS, SCCM, Current Branch &Technical Preview
    • How do I ?
    • Microsoft Deployment Toolkit (MDT)
    • Official Forum Supporters
    • SMS 2003
    • Configuration Manager 2007
    • Configuration Manager 2012
    • System Center Configuration Manager (Current Branch)
    • Packaging
    • scripting
    • Endpoint Protection
  • Windows Client
    • how do I ?
    • Windows 10
    • Windows 8
    • Windows 7
    • Windows Vista
    • Windows XP
    • windows screenshots
  • Windows Server
    • Active Directory
    • Microsoft SQL Server
    • System Center Operations Manager
    • KMS
    • Windows Deployment Services
    • NAP
    • Failover Clustering
    • PKI
    • Windows Server 2008
    • Windows Server 2012
    • Windows Server 2016
    • Windows Server 2019
    • Hyper V
    • Exchange
    • IIS/apache/web server
    • System Center Data Protection Manager
    • System Center Service Manager
    • System Center App Controller
    • System Center Virtual Machine Manager
    • System Center Orchestrator
    • Lync
    • Application Virtualization
    • Sharepoint
    • WSUS

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. Hello, I`m trying to upgrade from ConfigMgr 2012 SP1 CU5 to ConfigMgr 2012 R2 (and then CM 2012 R2 SP1 CU3) and during the upgrade wizard I receive the following error: “Setup failed to configure SQL Service Broker. Possible cause: Each Configuration Manager site must have its own SQL Server instance. Verify that the SQL Server instance is not in use by another Configuration Manager site” Looking into the ConfigMgrSetup.log I see these errors: INFO: SQL Connection succeeded. Connection: SMS_ACCESS, Type: Secure *** IF NOT EXISTS (SELECT * FROM sys.server_principals WHERE name='SQL02P\ConfigMgr_DViewAccess') BEGIN CREATE LOGIN [sql02P\ConfigMgr_DViewAccess] FROM WINDOWS END *** [42000][15025][Microsoft] [sql Server]The server principal 'SQL02P\ConfigMgr_DViewAccess' already exists. ERROR: SQL Server error: [42000][15025][Microsoft][sql Server Native Client 11.0][sql Server]The server principal 'SQL02P\ConfigMgr_DViewAccess' already exists. INFO: Executing SQL Server command: <IF NOT EXISTS (SELECT * FROM sys.server_principals WHERE name='SQL02P\ConfigMgr_DViewAccess') BEGIN CREATE LOGIN [sql02P\ConfigMgr_DViewAccess] FROM WINDOWS END> ERROR: ExecuteSqlCommand failed to execute IF NOT EXISTS (SELECT * FROM sys.server_principals WHERE name='SQL02P\ConfigMgr_DViewAccess') BEGIN CREATE LOGIN [sql02P\ConfigMgr_DViewAccess] FROM WINDOWS END, SQL error <> ERROR: Failed to create group for distributed view access. ~===================== Failed Configuration Manager 2012 Server Setup - Upgrade ===================== For the installation I`m using a domain administrator account with sysadmin privileges on the SQL Cluster where the CM database resides (2 nodes with Microsoft SQL 2008 R2 SP2 Standard without any Cumulative Update installed). I also checked the compatibility matrix CM-SQL https://technet.microsoft.com/en-us/library/gg682077.aspx and it seems that the minimum required SQL Server cumulative update is CU9 for my scenario, but I`m not sure that this is the real issue here. Of course the CM server is not working anymore, so the only option at the moment seems to be a restore, but I would like to find out why the upgrade failed. Any help would be greatly appreciated. Regards.
×
×
  • Create New...