次の方法で共有

Released: System Center Management Pack for SQL Server, Replication, AS, RS, Dashboards (6.7.15.0)

  • [アーティクル]

We are happy to announce new updates to SQL Server Management Pack family. All Management Packs are available in all 11 languages!

  • Microsoft System Center Management Pack for SQL Server enables the discovery and monitoring of SQL Server Database Engines, Databases, SQL Server Agents, and other related components.

Microsoft System Center Management Pack for SQL Server

Microsoft System Center Management Pack for SQL Server 2014

Microsoft System Center Management Pack for SQL Server 2016

  • Microsoft System Center Management Pack for SQL Server Replication enables the monitoring of Replication as set of technologies for copying and distributing data and database objects from one database to another and then synchronizing between databases to maintain consistency.

Microsoft System Center Management Pack for SQL Server 2008 Replication

Microsoft System Center Management Pack for SQL Server 2012 Replication

Microsoft System Center Management Pack for SQL Server 2014 Replication

Microsoft System Center Management Pack for SQL Server 2016 Replication

  • Management Pack for SQL Server Analysis Services enables the monitoring of Instances, Databases and Partitions.

Microsoft System Center Management Pack for SQL Server 2008 Analysis Services

Microsoft System Center Management Pack for SQL Server 2012 Analysis Services

Microsoft System Center Management Pack for SQL Server 2014 Analysis Services

Microsoft System Center Management Pack for SQL Server 2016 Analysis Services

  • Management Pack for SQL Server Reporting Services (Native Mode) enables the monitoring of Instances and Deployments.

Microsoft System Center Management Pack for SQL Server 2008 Reporting Services (Native Mode)

Microsoft System Center Management Pack for SQL Server 2012 Reporting Services (Native Mode)

Microsoft System Center Management Pack for SQL Server 2014 Reporting Services (Native Mode)

Microsoft System Center Management Pack for SQL Server 2016 Reporting Services (Native Mode)

  • Management Pack for SQL Server Dashboards

Microsoft System Center Management Pack for SQL Server Dashboards

Please see below for the new features and improvements. More detailed information can be found in guides that can be downloaded from the links above.

New SQL Server 2008/2008 R2/2012 MP 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”
  • Added retry policy in some Always On workflows to make PS-scripts work more stable
  • Updated the visualization library
  • Changed behavior of Always On scripts for cases when WSFC service is stopped

New SQL Server 2014/2016 MP 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”
  • Added retry policy in some Always On workflows to make PS-scripts work more stable
  • Updated the visualization library
  • Fixed: Always On objects get undiscovered when any Always On discovery crashes

New SQL Server Replication 2008/2012/2014/2016 MP Features and Fixes

  • Added support for configurations where computer host names are longer than 15 symbols
  • Fixed: MonitorDistributorSnapshotFreeSpace fails when being launched against SQL Server 2014 SP2
  • Fixed: Wrong source detection in logging
  • Updated the visualization library

New SQL Server Analysis Services 2008/2012/2014/2016 MP Features and Fixes

  • Added support for configurations where computer host names are longer than 15 symbols
  • Fixed: AS workflows sometimes crash
  • Updated the visualization library

New SQL Server Reporting Services 2008/2012/2014/2016 MP Features and Fixes

  • Added support for configurations where computer host names are longer than 15 symbols
  • Fixed: Web Service monitors do not support URL reservation https://+:<port>/<ReportServerPage> (protocol is HTTPS)
  • Updated the visualization library

New SQL Server Dashboards Features and Fixes

  • Fixed: Tiles content is replaced with question signs after a long period of inactivity

We are looking forward to hearing your feedback.

Comments

  • Anonymous
    January 18, 2017
    The bug that gives a warning for non domain computer is still present. Will it be fixed in the next version?" Event ID: 4001. Management Group: MYMGMTGROUP. Script: GetSQL20XXSPNState.vbs. Version: 6.7.15.0 : The next errors occured:The computer is not domain joined.Error Number: -2147023541Description: "
    • Anonymous
      January 19, 2017
      Hi Janne, thank you for the question. We're going to introduce the fix in the next version which is expected to RTM in March-April (a CTP version is expected in February).
      • Anonymous
        January 20, 2017
        Great!
  • Anonymous
    January 23, 2017
    Hello, I am currently getting a few Discovery Failed and Monitoring Failed errors after updating the Management Pack. The knowledge information points to issues with permissions but the DBA team assures me there is no issue with that since the localsystem account is privileged in all the SQL servers in our company and we also did not experience any similar issues with our previous version of the management pack (6.5.1.0).Most of the "Monitoring Failed" errors (Event ID 4201) are related to executing ps1 or vbs:CPUUsagePercentDataSource.ps1 Version: 6.7.15.0 : Error occured during CPU Usage for SQL Instances data source executing.Computer:NJ4PDWSDSQL02A Reason: Cannot process argument because the value of argument "obj" is null. Change the value of argument "obj" to a non-null value. Position:1036 Offset:109Detailed error output: Cannot process argument because the value of argument "obj" is null. Change the value of argument "obj" to a non-null value.CPUUsagePercentDataSource.ps1 Version: 6.7.15.0 : Error occured during CPU Usage for SQL Instances data source executing.Computer:RIC1PDAPPSQL02A Reason: Position:25 Offset:29Detailed error output: System.IO.FileNotFoundException: at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()at Microsoft.PowerShell.Commands.GetWmiObjectCommand.BeginProcessing()at System.Management.Automation.Cmdlet.DoBeginProcessing()at System.Management.Automation.CommandProcessorBase.DoBegin()GetSQL2014AgentJobStatus.vbs. Version: 6.7.15.0. Instance: LON2PDIDXPRD02 : An error has occurred while executing a query or establishing a connection to the server.The next errors occured:Cannot get target instance machine's NetBios host name.Computer name: LON2PDIDXPRD02.prd.MKAPP.NETError number: -2147221020Error description:--------And the same for the "Discovery Failed" errors:GeneralAlwaysOnDiscovery.ps1 Version: 6.7.15.0 : Error occurred during Always On discovery.Computer: LON2PDAPPSQL02A Reason: The following exception was thrown when trying to enumerate the collection: "An exception occurred while executing a Transact-SQL statement or batch.". Position:100 Offset:3 Instance:LON2PDEDMSQL02Detailed error output: The following exception was thrown when trying to enumerate the collection: "An exception occurred while executing a Transact-SQL statement or batch.".DiscoverSQL2014DB.vbs. Version: 6.7.15.0. Instance: LON2PDIDXPRD02 : Database discovery script 'DiscoverSQL2014DB.vbs' for instance 'LON2PDIDXPRD02' failed.The next errors occured:Cannot get a list of enabled Sql Server protocolsError Number: 70Description: Permission deniedInstance: LON2PDIDXPRD02DiscoverSQL2014DB.vbs. Version: 6.7.15.0. Instance: LON2PDIDXIAT01 : Database discovery script 'DiscoverSQL2014DB.vbs' for instance 'LON2PDIDXIAT01' failed.The next errors occured:Cannot get target instance machine's NetBios host name.Computer name: LON2PDIDXIAT01.prd.MKAPP.NETError number: -2147221020Error description:
    • Anonymous
      January 24, 2017
      Hi Sergio, and thank you for your message. Below, I'm going to comment on each error message from your comment:1. CPUUsagePercentDataSource.ps1 "Cannot process argument because the value of argument “obj” is null" — we've already known about such an issue, it's caused by a bug in some PowerShell cmdlet. We've changed the script code a bit to get rid the warning appearance, the change is going to be presented in the next release of SQL MPs (RTM is expected in March-April, a CTP version is expected in February).2. CPUUsagePercentDataSource.ps1 "Detailed error output: System.IO.FileNotFoundException" — could you take a look at the OM log on the affected agent machine to learn how often such warnings appear? 3. GetSQL2014AgentJobStatus.vbs "Cannot get target instance machine’s NetBios hostname" — looks like an intermittent error caused by performance issues. Can you see such warnings (about troubles when getting NetBios name) only for GetSQL2014AgentJobStatus.vbs? How often do such warnings appear in the OM log?4. The last 3 look like issues caused by a lack of permissions, you right. Is the LocalSystem account privileged with SA rights in SQL Servers?You can answer here or at sqlmpsfeedback@microsoft.com.
      • Anonymous
        March 02, 2017
        Hi Alex,Please let me know the following error fix details.1. CPUUsagePercentDataSource.ps1 “Cannot process argument because the value of argument “obj” is null” — we’ve already known about such an issue, it’s caused by a bug in some PowerShell cmdlet. We’ve changed the script code a bit to get rid the warning appearance, the change is going to be presented in the next release of SQL MPs (RTM is expected in March-April, a CTP version is expected in February).
  • Anonymous
    February 01, 2017
    Suggestion:If there are no db in sql availability group there will be alertAvailability Group MMA is not ready for automatic failover while it is configured to failover automaticallyAfter adding empty db - alert gone and all is ok .
    • Anonymous
      June 01, 2017
      Hi Igor, thank you for your feedback. We don't consider this a bug so such a behaviour of the monitor won't be changed.
  • Anonymous
    February 21, 2017
    The comment has been removed
  • Anonymous
    February 21, 2017
    Also get the below alert that is newAlways On discovery script failed. Reason: Event ID: 4101. Management Group: . Script: Main Version: 6.7.15.0 : Error occured during Always On monitoring.Computer: Reason: Position:338 Offset:23 Instance:INST1Detailed error output: System.Runtime.InteropServices.COMException (0x800706BE)at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()at Microsoft.PowerShell.Commands.GetWmiObjectCommand.BeginProcessing()
    • Anonymous
      February 22, 2017
      The comment has been removed
  • Anonymous
    April 25, 2017
    MP version 6.7.20.0 doesn't appear to have corrected the error "Cannot process argument because the value of argument "obj" is null. Change the value of argument "obj" to a non-null value." Is there a timeline for when this is expected to be corrected?
    • Anonymous
      April 26, 2017
      Thank you for your comment. We understand that we haven't fixed all cases of this issue. We’re working on finding all the potential places in the script and fix them all in the next release (CTP in May, RTM in June).