SQL MP Update - 6.7.15.0


 

image

 

 

The SQL MP’s have been updated.

 

SQL 2016 DB Engine https://www.microsoft.com/en-us/download/details.aspx?id=53008
SQL 2016 Analysis Services https://www.microsoft.com/en-us/download/details.aspx?id=53011
SQL 2016 Replication https://www.microsoft.com/en-us/download/details.aspx?id=53009
SQL 2016 Reporting https://www.microsoft.com/en-us/download/details.aspx?id=53010
   
SQL 2014 DB Engine https://www.microsoft.com/en-us/download/details.aspx?id=42573
SQL 2014 Analysis Services https://www.microsoft.com/en-us/download/details.aspx?id=44586
SQL 2014 Replication https://www.microsoft.com/en-us/download/details.aspx?id=47720
SQL 2014 Reporting https://www.microsoft.com/en-us/download/details.aspx?id=43390
   
SQL 2008-2012 DB Engine https://www.microsoft.com/en-us/download/details.aspx?id=10631
SQL 2012 Analysis Services https://www.microsoft.com/en-us/download/details.aspx?id=41658
SQL 2012 Replication https://www.microsoft.com/en-us/download/details.aspx?id=47721
SQL 2012 Reporting https://www.microsoft.com/en-us/download/details.aspx?id=43392
   
SQL 2008 Analysis Services https://www.microsoft.com/en-us/download/details.aspx?id=41659
SQL 2008 Replication https://www.microsoft.com/en-us/download/details.aspx?id=47723
SQL 2008 Reporting https://www.microsoft.com/en-us/download/details.aspx?id=43391
   
SQL Server Dashboards https://www.microsoft.com/en-us/download/details.aspx?id=51479

 

 

New Features and Fixes

  • No extra permissions on remote WMI are now required for Local System account when Always On hosts have names that are no longer than 15 symbols
  • Fixed: Always On discovery and monitoring scripts cannot read cached values in Windows registry
  • Fixed: Wrong MP version number in some Always On scripts
  • Fixed: CPUUsage and DBDiskLatency scripts fail with the reason: "Index operation failed"
  • Fixed: Always On objects get undiscovered when any Always On discovery crashes
  • Added retry policy in some Always On workflows to make PS-scripts work more stable
  • Updated the visualization library
  • Fixed: AS workflows sometimes crash
  • Changed behavior of Always On scripts for cases when WSFC service is stopped
  • Fixed: Tiles content is replaced with question signs after a long period of inactivity

Comments (17)

  1. Daniel Christen says:

    Hi Kevin, why ist the new Version 6.7.15.0 and the old one is 6.7.7.0?

    1. Kevin Holman says:

      @Daniel - not sure I understand your question?

      1. Daniel Christen says:

        Hi Kevin, sorry my fault, I thought the number is less but I didn't read it right.

  2. Igor Kuznecov says:

    Look like it is bugs free. Its ok on test servers

  3. Jürgen Winter says:

    Very good. Do you think I should remove the "RunAs Addendum" Management Pack before updating?

    1. Kevin Holman says:

      No, why? The RunAs addendum works with any version of the SQL MP, it specifically monitors for misconfigurations of the Service SID and offers tasks to help configure rights. Why would you remove it, or think that would be a good idea?

      1. Jürgen Winter says:

        Because i did not know what it does exactly in the background and that it was designed to work with any version and not specifically for the buggy 6.7.7.0 MP.
        Anyway, thanks for the Info.

        1. Kevin Holman says:

          Ahh. I didnt realize 6.7.7.0 was buggy? I thought it was great. It just had some extra steps required for alwaysOn configs. THose are no longer needed with the new SQL MP, so that's good.

          The addendum MP's are documented in my blog article - specifically what they do, check out that post to better understand them. They are really there to assist with service SID implementation and ongoing support of it for new SQL servers added to the environment. https://blogs.technet.microsoft.com/kevinholman/2016/08/25/sql-mp-run-as-accounts-no-longer-required-2/

  4. Kyle says:

    Hey Kevin,

    I seem to keep having this same issue over and over in every release of this management pack.

    Stored procedure '{0}' wasn't found in Data Warehouse. It usually takes few minutes after importing the Management Pack to populate changes required for Visualization to the Data Warehouse. If this error occurs more then after 24 hours since Management Pack import then contact Operations Manager Administrator.

    An error occurred executing the command: [Microsoft.SQLServer.Visualization.Library.DataProviders!ResolveGUIDsDataProvider/GetResolvedGUIDsData] in provider: [Microsoft.SQLServer.Visualization.Library.DataProviders.ResolveGUIDsDataProvider, Microsoft.SQLServer.Visualization.Library.DataProviders, Version=6.7.15.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35]. : StoredProcedureNotAvailable
    System.Data.SqlClient.SqlError: Cannot open database "OperationsManagerDW" requested by the login. The login failed.
    System.Data.SqlClient.SqlError: Login failed for user 'Data access user here'.

    at Microsoft.EnterpriseManagement.Presentation.DataAccess.DataProviderCommandMethod.Invoke(CoreDataGateway gateWay, DataCommand command)
    at Microsoft.EnterpriseManagement.Presentation.DataAccess.CoreDataGateway.ExecuteScalarInternal[TResult](DataCommand command)
    at Microsoft.EnterpriseManagement.Presentation.DataAccess.CoreDataGateway.b__2[TResult](f__AnonymousType0`1 data)

    I am pretty sure there is a missing Stored Procedure that was never added to the DW when the MP was imported. Do you know of any articles that talk about the fix for this? I've seen one where they tell you to run a really long SQL script (which i'm definitely not running unless i have a microsoft buddy beside me saying "DO IT"). Just thought i'd ask you cause you're basically my dream team for all things SCOM 😉

    1. Kevin Holman says:

      @Kyle -

      Man I don't know on that one. I'd recommend opening a support case.

    2. Kyle, could you email to sqlmpsfeedback@microsoft.com with your issue? We'll help you to resolve it.

      1. Kyle says:

        Looks like 6.7.20.0 started working for me ! i can see Dashboards!!!!! If i run into the issue again i'll definitely forward the error onto that email address ! thanks

        1. Kevin Holman says:

          Also - it appears we still need to "pre-populate" these dashboards under some scenarios. I have visited customers where they just won't work until I do this: https://www.scom2k7.com/sql-dashboards-not-populating-with-event-26319/

  5. Sergio M says:

    Hi Kevin, I am getting a bit confused by something I saw here: https://technet.microsoft.com/en-us/library/hh212732%28v=sc.12%29.aspx?f=255&MSPPError=-2147217396
    "When a management pack is updated, update the corresponding _Overrides.xml file with the new version number. You must use an XML editor to update the version number of the _Overrides.xml file. If you make changes to an _Overrides.xml file but do not change the version attribute, you can import the file but the settings in the file will not be applied."

    I do have an unsealed Overrides MP for SQL Server that has references to the updated management packs in your post. Does that mean that if I go ahead and update the sealed SQL Server management packs in my environment then I also have to update the references in my Overrides MP?

    Do the Overrides stop being applied if they reference an older version of the sealed MP or is that just a recommendation to keep all references updates? I can't seem to find the answer to this question anywhere.

    Thanks in advance,
    Sergio

  6. Sandoss Kumar says:

    Why SQL 2016 DB's are not listing under SQL Database Class (Microsoft SQL Server Core Library), its showing up only up to SQL 2012 version.

  7. Peter says:

    Dear Kevin, I installed the 6.7.15.0 SQL MP ( 2012/2008 and 2014 and 2016 packs ) and now I have a lot of "Workflow Initialization: Failed to start a workflow that runs a process or script" warrning. What can I do?

  8. Dean says:

    Hi Kevin - I have implemented the 2014 pack and using the new Service SID. I am able to monitor my Servers and Instances however no data ever gets populated in the dashboards. Any Ideas where the problem might be?

Skip to main content