Jump to content


Search the Community

Showing results for tags 'ag'.



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. Hi All, I hope you are well, Currently I have an issue I have unsuccessfully been battling with for a few days now. The original plan was to have the sccm db running on a sql high availability always on group setup. 1 x primary server 1 x sup server 1 x dp server 2 x sql servers when I tried to install SCCM initially, on the clustered sql, I was getting issues with listener admin rights / ports Excerpt from sccm install log --------------- CWmiRegistry::GetStr: Failed to get string value MSSQLSERVER Configuration Manager Setup 06/03/2018 16:05:16 92 (0x005C) Failed to retrieve SQL Server instance name[MSSQLSERVER]. Configuration Manager Setup 06/03/2018 16:05:16 92 (0x005C) WARNING: failed to retrieve port number for XXX-SCCM-LST.ncc.local. Configuration Manager Setup 06/03/2018 16:05:16 92 (0x005C) WARNING: failed to retrieve port number for XXX-SCCM-LST.ncc.local. Configuration Manager Setup 06/03/2018 16:05:16 92 (0x005C) ---------------- End of Excerpt XXX-SCCM-LST = sql listener this is a named instance on the sql (SCCM) and the sql port is 1433 /broker 4022 Why is it looking for MSSQLSERVER ? why failing to retrieve port ? So - I recently gave up and installed SCCM on a named server (not the listener) (SERVER-A - which is to be used in the HA cluster) sccm installs and works fine. I have installed the DB on a single box, and SCCM is looking good and functioning / patched up to 1710 + hotfix. OK - So I think I can do SCCM site maintenance, and change the DB location to the SQL Listener. But no same errors in logs again. Any one got any ideas or further experience with sql availability groups and are we missing something simple. Hope to hear back from anyone Regards, WAZZIE
×
×
  • Create New...