locked
SQL Server MP, AlwaysOn, Run As Account not enough permissions. RRS feed

  • Question

  • After upgrading to management pack 6.6.4.0 we get this error on two servers:  "Run As Account does not exist on the target system or does not have enough permissions." The two servers in question are the passive nodes of two SQL Server AlwaysOn Availability groups. Seems like a bug, or is it? We did not have this error before we upgraded the MP.

    To confirm my suspicions, I did a failover on both AlwaysOn clusters. Still the same error message as above. Any  new configuration with these management packs I have overlooked? Any work-around? Mostly we prefer not to disable monitors if not strictly necessary. SQL Server management packs are version 6.6.4.0, some 6.6.7.6. One is 6.4.1.0 and one 6.4.1.


    MCTS: Messaging | MCSE: S+M

    Tuesday, March 15, 2016 2:22 PM

Answers

  • It's a bug. The passive nodes will complain about not being able to perform the file group discovery, and will even reference master DB, even though that is not correct.

    SA + Local Admin doesn't matter, the failure looks to be a problem when any DB is in a non-readable secondary mode.


    Kevin Holman http://blogs.technet.com/b/kevinholman

    Wednesday, March 16, 2016 11:01 PM
  • By the way - get rid of the 6.4.1 stuff - if you are talking about:

    Microsoft.SQLServer.Presentation           SQL Server 2012 Presentation    6.4.1.0

    Microsoft.SystemCenter.Visualization.Component.Extensions.Library      Visualization Component Extensions Library  6.4.1.0

    The above are artifacts left over from a previous SQL MP that we no longer use.   These should be deleted if you are using the new MP's and the new dashboards in them.


    Kevin Holman http://blogs.technet.com/b/kevinholman

    Wednesday, March 16, 2016 11:03 PM

All replies

  • Can you confirm that your action accounts and correlated profiles are configured with an account that has the appropriate permissions on each SQL Server? Make sure to check the three SQL Server run-as profiles as well as the discovery and monitoring AlwaysOn profiles. 

    EDIT: 

    Here are some references. 

    http://thoughtsonopsmgr.blogspot.com/2014/09/sql-mp-challenge-run-as-accounts.html

    https://technet.microsoft.com/en-us/library/hh212714.aspx

    https://blogs.technet.microsoft.com/kevinholman/2010/09/08/configuring-run-as-accounts-and-profiles-in-opsmgr-a-sql-management-pack-example/

    • Edited by Matt Hansen0 Tuesday, March 15, 2016 3:33 PM
    • Proposed as answer by Matt Hansen0 Tuesday, March 15, 2016 3:33 PM
    Tuesday, March 15, 2016 3:19 PM
  • The SQL guide states that Always on isn't supported with the low-privilege profiles. They need SA and local admin (probably not true, but the low privilege accounts isn't enough).

    Rob Korving
    http://jama00.wordpress.com/

    Tuesday, March 15, 2016 3:36 PM
  • They have sa and local admin rights. As stated, there were no such errors with the previous SQL MP. The error only shows up on the passive node of the AlwaysOn cluster. When SQL01 is active, there is no error on that server, but on SQL02. If I fail over and SQL02 becomes active, no error here, but on SQL01. All this makes me think it could be a bug.

    MCTS: Messaging | MCSE: S+M

    Tuesday, March 15, 2016 3:48 PM
  • Did you add the run as account (in distribution) and in the SQL profiles to both nodes or just to the cluster?


    Rob Korving
    http://jama00.wordpress.com/


    • Edited by rob1974 Wednesday, March 16, 2016 12:13 PM
    Wednesday, March 16, 2016 12:07 PM
  • It's a bug. The passive nodes will complain about not being able to perform the file group discovery, and will even reference master DB, even though that is not correct.

    SA + Local Admin doesn't matter, the failure looks to be a problem when any DB is in a non-readable secondary mode.


    Kevin Holman http://blogs.technet.com/b/kevinholman

    Wednesday, March 16, 2016 11:01 PM
  • By the way - get rid of the 6.4.1 stuff - if you are talking about:

    Microsoft.SQLServer.Presentation           SQL Server 2012 Presentation    6.4.1.0

    Microsoft.SystemCenter.Visualization.Component.Extensions.Library      Visualization Component Extensions Library  6.4.1.0

    The above are artifacts left over from a previous SQL MP that we no longer use.   These should be deleted if you are using the new MP's and the new dashboards in them.


    Kevin Holman http://blogs.technet.com/b/kevinholman

    Wednesday, March 16, 2016 11:03 PM
  • Thanks a lot for the confirmation.

    MCTS: Messaging | MCSE: S+M

    Friday, March 18, 2016 12:13 PM
  • I'll do so.

    MCTS: Messaging | MCSE: S+M

    Friday, March 18, 2016 12:13 PM