Partilhar via

Released: System Center Management Pack for SQL Server and Dashboards (6.7.7.0)

  • Artigo

We are happy to announce that updates to SQL Server and Dashboard Management Packs have been released!

Downloads available:

Microsoft System Center Management Pack for SQL Server 2016 Microsoft System Center Management Pack for SQL Server 2014 Microsoft System Center Management Pack for SQL Server (2008-2012) Microsoft System Center Management Pack for SQL Server Dashboards

 

Please see below for the new features and improvements. Most of them are based on your feedback. More detailed information can be found in guides that can be downloaded from the links above.

Important note to the release:

To provide support for monitoring SQL Server on Windows machines having names that longer 15 symbols, we had to add additional requests to WMI and Windows registry, and this change affects security configuration in some cases. Therefore, certain essential settings might need to be applied (see below).

To monitor SQL Server Always On Availability Groups under Local System account, each node's Local System account must also have sufficient permissions on other server nodes of the Availability Group. In case it is approved by your company security policy, you can grant such permissions by adding each computer account to the local Administrators group of each participating node. In case it is not approved, you should create a domain account for monitoring and either add it to the local Administrators group on each node or grant it with the minimal required permission set as described in "Low-privilege configurations" section of the Management Pack Guide.

New SQL Server Dashboards MP Features and Fixes

  • Improved Dashboards performance
  • Fixed issue: expanding "arrow" has low-contrast color when a health group is collapsed in Instance view (High-Contrast #2 color scheme)
  • Fixed issue: in Web console, Dashboards continuously send requests to the database
  • Fixed issue: not the first object gets selected in the object list after drill-down
  • Fixed issue: horizontal scroll position resets after refreshing the Instance view
  • Fixed issue: "No Data" message is displayed on some tiles after upgrading Dashboards management pack from version 6.7.2.0 to 6.7.4.0 or later version
  • Fixed issue: on Web console, Dashboards crash when drilling down from Datacenter view to Instance view
  • Restored the correct group order in SQL Server Summary dashboard views
  • Fixed issue: Regular\Virtual group tile will show 0 objects if user adds a new group before the previous one has been saved
  • Fixed issue: virtual group filtering for Generic Distributor does not work
  • Fixed issue: tooltips on some menus appear in unexpected places
  • Fixed issue: Web Console is crashing upon right-clicking the Hamburger menu
  • Fixed issue: button captions are cropped in some dashboard localization packs
  • Fixed issue: Instance dashboard displays data for the item that is the first in the list if no items appear after applying a filter
  • Fixed issue: the first group object is not in focus after clearing "Filter" field if there were no search results
  • Fixed issue: Summary dashboards appear to be in a strange state if one installs only Dashboards MP without SQL MPs
  • Fixed issue: Bulk Add Tiles does not trigger the refresh action
  • Fixed issue: object and alert counters of Virtual groups containing real groups display zeros
  • Fixed issue: an error appears in Web Console when using keyboard for navigation in "Add Aggregated Monitor" dialog
  • Fixed issue: unexpected scrolling behavior in the instance view when using mouse scroll
  • Fixed issue: markup of the dialog for adding classes gets broken when the scrollbars are displayed
  • Fixed issue: wrong width value of the Edit dialog
  • Fixed issue: there is no refresh action after saving the edited Virtual Group configuration
  • Fixed issue: white-screen exception when working with a dialog in Web console
  • Fixed issue: Datacenter and Instance queries fail when a special set of classes is selected

New SQL Server 2008-2012 MP Features and Fixes

  • Added support for configurations where computer host names are longer than 15 symbols
  • Added support for databases stored on SMB Shares
  • Added "Event ID" to descriptions of all the alerts generated by the alerting rules
  • Updated the visualization library
  • Removed files of SQL 2005 MP from the installer since this MP is no longer supported
  • Added 2 rules to generate alerts when there are problems with execution of the monitoring scripts: "MSSQL: Monitoring failed" and "MSSQL: Monitoring warning"
  • Added "MSSQL 20XX: Discovery warning" rules to generate alerts when there are non-critical problems with execution of the discovery scripts (warning events in the Operations Manager log)
  • Changed "MSSQL 20XX: Discovery failed" rules to generate alerts for only critical errors during executing discovery scripts
  • Improved error logging in the MP scripts
  • Made detection condition stricter for DB User Policy event-based discovery: added management group name
  • Made detection condition stricter for Script Failed alerting rule: added management group name
  • Deprecated "Run As Account does not exist on the target system, or does not have enough permissions" rule
  • Fixed issue: SQL Server 2012 Always On discoveries fail after stopping WSFC service
  • Fixed issue: "Set DB offline" task does not work when the database is in Availability Group
  • Fixed issue: user policy discovery script fails with "Invalid namespace "ROOT\Microsoft\SqlServer\ComputerManagement12" error
  • Fixed issue: Always On console task does not work
  • Fixed some issues in the scripts, which could lead to unstable work with WMI
  • Fixed error logging in a script for Blocking Sessions monitor
  • Fixed issue: CPU Usage monitor and rule did not work for SQL Server cluster instance
  • Fixed issue: connection to an SQL Server instance was not closing when the destination was wrong
  • Fixed Non-Readable Replica detection (Always On)

New SQL Server 2014-2016 MP Features and Fixes

  • Added support for configurations where computer host names are longer than 15 symbols
  • Added "Event ID" to descriptions of all the alerts generated by the alerting rules
  • Added a new overridable parameter to monitor "Stale Checkpoint File Pairs Ratio" in order to ignore databases having the number of checkpoint file pairs less than the threshold (300 by default)
  • Updated the visualization library
  • Added 2 rules to generate alerts when there are problems with execution of the monitoring scripts: "MSSQL: Monitoring failed" and "MSSQL: Monitoring warning"
  • Added "MSSQL 2016: Discovery warning" rules to generate alerts when there are non-critical problems with execution of the discovery scripts (warning events in the Operations Manager log)
  • Changed "MSSQL 2016: Discovery failed" rules to generate alerts for only critical errors during executing discovery scripts
  • Improved error logging in the MP scripts
  • Fixed issue: "Set DB offline" task does not work when the database is in Availability Group
  • Fixed issue: Always On console task does not work
  • Deprecated "Run As Account does not exist on the target system, or does not have enough permissions" rule
  • Fixed some issues in the scripts, which could lead to unstable work with WMI
  • Fixed the issue when not all available performance counters were presented at "All Performance Data" view in Memory-Optimized Data sub-folder
  • Made "Resources Pool Memory Consumption (rollup)" enabled by default
  • Disabled Memory-Optimized Data Garbage Collection Fill Factor monitor and rule by default
  • Disabled Memory-Optimized Data workflows for all SQL Server editions that do not support Memory-Optimized Data feature
  • Fixed issue: CPU Usage monitor and rule did not work for SQL Server cluster instance
  • Fixed issue: connection to an SQL Server instance was not closing when the destination was wrong
  • Fixed issue: in some cases, Set Database Online/Offline tasks did not work for databases of SQL Server cluster instance (SQL 2016 MP)
  • Made detection condition stricter for DB User Policy event-based discovery: added management group name
  • Made detection condition stricter for Script Failed alerting rule: added management group name

We are looking forward to hearing your feedback.

Comments

  • Anonymous
    October 07, 2016
    I'm getting a lot of errors like this...MSSQL 2014: Monitoring warningEvent ID: 4201. Management Group: MG-Main. Script: GetSQL2014DB.vbs. Version: 6.7.7.0 : The next errors occured:Cannot get a list of enabled Sql Server protocolsError Number: -2147023170Description: The remote procedure call failed. Instance: INSTANCE3
    • Anonymous
      October 11, 2016
      Hi Timothy,You probably have some security/firewall/WMI performance/WMI service accessibility issue.Could you please contact us at SQLMPsfeedback@microsoft.com for further investigation?Thank you,Dmitry.
      • Anonymous
        November 03, 2016
        The comment has been removed
        • Anonymous
          November 07, 2016
          Thank you for the further message. You're right that those alerts might be caused by performance degradation on the servers. We'll be happy to know investigation results.
  • Anonymous
    October 09, 2016
    Hi!After updating MP to 6.7.7.0 I have a compilation error:MSSQL 2014: Monitoring failedEvent ID: 4201. Management Group: (name hidden). Script: Main Module: CPUUsagePercentDataSource.ps1 Version: 6.7.7.0 : Error occured during CPU Usage for SQL Instances data source executing.Computer:(name hidden)Reason: Cannot add type. There were compilation errors. Position:319 Offset:29Detailed error output: Cannot add type. There were compilation errors.--------(0) : No inputs specified(1) : using System;--------(0) : Source file 'C:\Windows\TEMP\ojmt2k4c.0.cs' could not be foundSame for older SQL versions.
    • Anonymous
      October 10, 2016
      If you add the Temp folder on C:\Windows drive. Possible the problem will be sorted.Good Luck.. :)
    • Anonymous
      October 10, 2016
      The comment has been removed
      • Anonymous
        October 11, 2016
        My monitoring account is a local admin on my sql servers and therefore has access to c:\windows\temp yet I still get this error on the majority of my servers.
        • Anonymous
          October 11, 2016
          just noting my errors are :Position:324 Offset:29otherwise the same.
          • Anonymous
            October 11, 2016
            Apologies for the multiple replies :-)I appear to have resolved some of my issues, I have a number of boxes with this error where my monitoring account did not have local perms and I have several boxes where it did but user access control is enabled. I am still working through it but looks like after adding the monitoring accounts permissions a monitoring service restart is needed to clear the errors.I'm not sure if the access control is a factor or not, still working through that, need to put to the side for other work now but wanted to mention the service restart for other...
  • Anonymous
    October 10, 2016
    Those errors makes scom admins cryWe need more detailed errors!"blabla.ps1 failedTo reproduce error run blabla.ps -param1....param10"Will we see it ?
  • Anonymous
    October 11, 2016
    The always on discover seems to have been broken with this update?""Management Group: SCOM_MGMT01. Script: ModuleAction Module: GeneralAlwaysOnDiscovery.ps1 Version: 6.7.7.0 : Error occurred during Always On discovery.Computer: SQLSRV01Reason: Access denied Position:254 Offset:26 Instance:MSSQLSERVERDetailed error output: Access denied --------Property _CreationTime does not exist at path HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Operations Manager\3.0\Modules"
    • Anonymous
      October 11, 2016
      And to clearify. Yes that path exists. And it contains a couple of records. For example: SQLSRV01_CreationTime - 2016-10-10T13:02:31Z
      • Anonymous
        October 11, 2016
        To monitor SQL Server Always On Availability Groups under Local System account, each node’s Local System account must also have sufficient permissions on other server nodes of the Availability Group. In case it is approved by your company security policy, you can grant such permissions by adding each computer account to the local Administrators group of each participating node. In case it is not approved, you should create a domain account for monitoring and either add it to the local Administrators group on each node or grant it with the minimal required permission set as described in “Low-privilege configurations” section of the Management Pack Guide.
        • Anonymous
          October 11, 2016
          I have run this config on the servers so I guess it should not use system?https://blogs.technet.microsoft.com/kevinholman/2016/04/26/sql-mp-run-as-accounts-no-longer-required/But maybe this setup does not work on a cluster setup?
          • Anonymous
            October 11, 2016
            Looks like I am not alone?https://social.technet.microsoft.com/Forums/systemcenter/en-US/a7d7d4cc-ba08-4263-b08a-6455d75b4e1c/sql-mp-6770-access-denied-for-always-on?forum=operationsmanagermgmtpacks
          • Anonymous
            October 12, 2016
            The comment has been removed
          • Anonymous
            October 12, 2016
            The comment has been removed
          • Anonymous
            October 12, 2016
            The comment has been removed
        • Anonymous
          October 13, 2016
          I have the same problem when using solution with using ServiceSID for HealthService on target servers, is there some extra rights needed on all nodes of the cluster hosting AG environment? According to Kevin Holman, he has tested it also non AG and it works properly,maybe after update to 6.7.7.0 there is new way of retrieving variable for computer name and then it is trying to find property "_CreationTime" without prefix which does not exist.Does somebody fixed this when using Kevin Holman's SQL Server addendum solution? Otherwise I have to set up "Low privilege configuration". Thank you in advance.
          • Anonymous
            October 14, 2016
            The comment has been removed
    • Anonymous
      October 14, 2016
      The comment has been removed
  • Anonymous
    October 12, 2016
    Hi,does anybody else see console crashes after importing version 6.7.7.0 within SCOM?Alerts View works fine - but State Views are loadint the contenct and than crash the SCOM console:Problem signature: Problem Event Name: APPCRASH Application Name: Microsoft.EnterpriseManagement.Monitoring.Console.exe Application Version: 7.1.10226.1239 Application Timestamp: 57bd213f Fault Module Name: StackHash_5e8b Fault Module Version: 6.3.9600.18438 Fault Module Timestamp: 57ae642e Exception Code: c0000374 Exception Offset: PCH_9F_FROM_ntdll+0x0000000000090C6A OS Version: 6.3.9600.2.0.0.272.7 Locale ID: 3079 Additional Information 1: 5e8b Additional Information 2: 5e8b4fd3a3fdb033fe601bc1be5e4f0f Additional Information 3: 46b1 Additional Information 4: 46b1464dd8a2c6ce66c709065d0d3d74
    • Anonymous
      October 12, 2016
      Hi,sounds like the issue is caused by one of these Windows Updates:KB3182203KB3188743KB3188732KB3186208KB3185331KB3192392I've installed these updates early in the morning and later 6.7.7.0 of the SQL MPI've now uninstalled all updates and SQL MP 6.7.7.0 is working fine - without console crashes.
    • Anonymous
      October 12, 2016
      Hi Peter,This was not observed earlier. Did you see this crashes in another State Views, in another MPs (if you have such)?And for instance, try to clear cache, open the Operations console with the /clearcache parameter.Best Regards,Dmitry.
    • Anonymous
      October 14, 2016
      Hello, PeterWe have reproduced this issue. It seems that Windows Update KB3185331 was the reason of Operations Console crash. The problem was solved after the removal of this update.Best regards,Artem Timoshenko.
  • Anonymous
    October 19, 2016
    https://support.microsoft.com/en-us/kb/3200006 fixes the console crash issue!
    • Anonymous
      October 26, 2016
      Hi gais!After rollup 11 and updating MP to 6.7.7.0 I have a compilation error:MSSQL 2014: Monitoring failedEvent ID: 4201. Management Group: GDD. Script: Main Module: CPUUsagePercentDataSource.ps1 Version: 6.7.7.0 : Error occured during CPU Usage for SQL Instances data source executing.Computer:SQLC2 Reason: Position:33 Offset:27Detailed 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()--------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()--------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()Offset:29How can I resolve this problem?
      • Anonymous
        October 27, 2016
        Hi,Thank you for your message. We need to get extra details on your case. Please share them with us.1. Which SQL MP version did you have before updating to the version 6.7.7.0?2. Do you use Local System account for monitoring your SQLs?3. Is it a cluster instance of SQL Server for which you see such errors?4. Did you look into Operations Manager log on the affected machine? Please check whether you have or not CPU Usage script errors for the current day.You can share them here as a new comment or just email us at SQLMPsfeedback@microsoft.com.
  • Anonymous
    October 27, 2016
    The comment has been removed
    • Anonymous
      November 01, 2016
      The comment has been removed
      • Anonymous
        November 01, 2016
        Hi Alex!1. My domain monitoring account in local admin group of the server. But when I'm trying to use wbemtest using credentials of monitoring account, it say user credentials cannot be used for local connections. Also I checked wmimgmt console, I have full access for local admin group.2. No, this is standalone SQL server3. No, I use domain account, which is added to local admin group of each sql server.
        • Anonymous
          November 02, 2016
          Try to use powershell to query WMI. In open powershell console, type: Start-Process powershell.exe -Credential "YourDomain\YourAccount" After you press Enter, you'll get a new console window running under the account you specified. Type:Get-WmiObject -Namespace 'root\Microsoft\SqlServer\ComputerManagement11' -Query 'SELECT PropertyStrValue FROM SQLServiceAdvancedProperty WHERE ServiceName = "MSSQLSERVER" AND PropertyName = "VERSION"'And a couple more questions:1. How many servers are affected by the issue?2. Which version of SQL MP did you have before updating to 6.7.7.0?
          • Anonymous
            November 02, 2016
            The comment has been removed
        • Anonymous
          November 03, 2016
          The comment has been removed
          • Anonymous
            November 04, 2016
            Hi Alex! Email was sent to your email address.Best regards,Dmitry
          • Anonymous
            November 07, 2016
            The comment has been removed
          • Anonymous
            November 07, 2016
            Karlis, thanks for your message. WOW64 configurations (32-bit SQL Server on 64-bit Windows Server) are not supported by SQL MPs.
          • Anonymous
            November 08, 2016
            Karlis, thanks for your message. WOW64 configurations (32-bit SQL Server on 64-bit Windows Server) are not supported by SQL MPs.It will be nice to see such rule as warning 'Attention!32x not supported on 64x....'
  • Anonymous
    November 03, 2016
    We are getting the same WMI permissions and registry "path does not exist" errors with SQL 2012 and 2014 since the MP updates, and we use the least-privileged mode. We have a RunAs domain account for AlwaysOn, Discovery, and Monitoring that is both a local admin and has all of the necessary permissions in SQL (datareader on all DBs, plus additional roles and permissions on master and mssdb) on all of our SQL servers. We have not had any issues until upgrading to the latest MPs, and now we are getting these errors.We are especially getting errors on our AAG nodes. All of them use the same RunAs account though, not to mention all of the servers in the same AAG use the same service accounts for SQL. I'm not understanding how or why a COM permissions change would help, not to mention everything I'm reading has to do with using issues when using the Local System account. We use Local System for the MS Monitoring Agent, but we are using RunAs accounts for SQL monitoring, so that should not matter.....
    • Anonymous
      November 07, 2016
      Hi Evan, thanks for your message. It was a surprise for us that adding some domain account to the Local Administrators group doesn't guarantee that this account will have full access to WMI. So, please check the following:1. Run As profiles for Always On workflows are configured to use the same domain account as the other SQL MPs profiles. I mean the next ones: SQL 2012 MPs: Always On Discovery, Always On MonitoringSQL 2014 MPs: Microsoft SQL Server 2014 Always On Discovery Run As Profile and Microsoft SQL Server 2014 Always On Monitoring Run As Profile2. Domain account you use for monitoring SQLs has the next permissions on all the nodes of your AAGs:Enable Account and Remote Enable for the Root\CIMV2 namespacePlease notify us about results here or at SQLMPsfeedback@microsoft.com.
      • Anonymous
        November 14, 2016
        Our SQL Monitoring account is a Domain Admin, which means it is a local admin on all of the SQL servers. The local admin group already has remote launch and activation permissions. We use this same account for all SQL monitoring profiles (SQL 2005-2014 including Always On, etc.).
        • Anonymous
          November 15, 2016
          Please take a look at this page: https://social.technet.microsoft.com/Forums/windowsserver/en-US/4f33837b-1cb1-4648-85b1-3ba87cbfe93e/wmi-remote-access-denied?forum=winserverManagement. Seems similar to your case. Could you verify that your monitoring account has sufficient permissions and your machines are configured to enable remote access?
          • Anonymous
            November 15, 2016
            I can connect to WMI remotely just fine. The command "WMIC /node:"" /user:"" /password:******** computersystem get totalphysicalmemory" returns "TotalPhysicalMemory 17179262976" when I use my SQL Monitoring/Discovery account. I use the same account for all aspects of SQL monitoring and discovery, so there shouldn't be a question about which account at least should be using.WinRM is also configured correctly, and remote PowerShell works to all of my servers using my SCOM SQL Monitoring/Discovery account. The nodes in my AAGs are in different time zones, but that shouldn't make any difference. I can connect via "Enter-PSSession " to all of the nodes just fine.
        • Anonymous
          November 16, 2016
          This thread has reached the limit of nested comments so that I'll answer your last message here. We need some time to prepare a diagnostic MP which will enable us to test the Run As profile configuration you have. While we're preparing, could you check that all the Always On Run As Profiles are targeted at the right class or group. Svante left his comment below that they resolved their issue by correcting the Run As profiles configuration.
  • Anonymous
    November 07, 2016
    I also had various new alerts with this MP.The solution for many of my servers was to recompile the sql mof file on the target server using mofcomp, as described here:-https://support.microsoft.com/en-gb/kb/956013 This stopped many of the alerts post MP install.Hope it helps someone.
    • Anonymous
      November 07, 2016
      Thank you very much for this message. If some alerts aren't yet resolved by the recompilation, feel free to reach us out. We'll be happy to help you. Just leave a comment or email us at SQLMPsfeedback@microsoft.com.
    • Anonymous
      November 19, 2016
      That helped me too on 95% of problem servers
      • Anonymous
        November 22, 2016
        Thank you for letting us know.
    • Anonymous
      December 07, 2016
      The comment has been removed
  • Anonymous
    November 10, 2016
    I’ve just found out that there is a problem with SQL 2014 MP 6.7.7.0 monitoring AlwaysOn availability groups using Run As Accounts. The problem is that the workflow running the scripts GeneralAlwaysOnDiscovery.ps1 and DatabaseReplicaAlwaysOnDiscovery.ps1 are running as SYSTEM and NOT as the associated Run As Account. To solve error messages indicating "Access is denied" you must assign the computer account of the other nodes in the availability group permission to each other. E.g. ServerB should have permission to ServerA and ServerA should have permission to ServerB. This is true even if you have configured and distributed Run As Accounts to the servers.
    • Anonymous
      November 10, 2016
      Svante, thanks for your message. Could you check in your environment whether the next Run As profiles have been mapped to the domain account you use for monitoring SQL Servers:Microsoft SQL Server 2014 Always On Discovery Run As Profile,Microsoft SQL Server 2014 Always On Monitoring Run As Profile.Map them in case they aren't yet. Please tell us about your results.
      • Anonymous
        November 16, 2016
        My mistake. We had the Run As Profile targeted at the "SQL Server 2014 Role" and not on the "MSSQL 2014: Always On Seed". The discoveries are working now. Thank you!
        • Anonymous
          November 16, 2016
          Svante, thank you for this message. We're glad that you've resolved those issues. When you target the Run As profiles at the "SQL Server 2014 Role" class, you, in fact, target them at SQL Server 2014 DB Engine. Always On classes, in their turn, are hosted on Windows Computer class, not on DB Engine. You can use the "SQL Server 2014 Computers" class/group as a general target for all the SQL 2014 MP Run As Profiles. But I wonder why you use targeting. The "All targeted objects" is the greatly preferable option and it should be used in most cases. Could you please tell us why you use targeting? It's really important to us learning more about real user cases. Thank you.
    • Anonymous
      November 14, 2016
      Svante, where are you adding permissions for the computer accounts belonging to the other nodes? I tried adding Ensble Account and Remote Access permissions to the computer accounts for the other nodes in the AlwaysOn Group, but am still receiving the same discovery error for all of my SQL servers that belong to an AAG:"Event ID: 7104. Management Group: CED. Script: ModuleAction Module: GeneralAlwaysOnDiscovery.ps1 Version: 6.7.7.0 : Error occurred during Always On discovery. Computer: MY-SQL-AAG-NODES Reason: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED)) Position:254 Offset:26 Instance:MSSQLSERVER Detailed error output: Access is denied. (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))"This is becoming EXTREMELY frustrating as everything was working perfectly fine prior to this latest update. I'm hesitant to even open a ticket with MS at this point because it sounds like even they do not know what is causing the issues in this latest release. Does MS even have a QA department anymore???
      • Anonymous
        November 16, 2016
        The comment has been removed
  • Anonymous
    November 16, 2016
    When excluding a DB Engine from the 'Discover Databases for a Database Engine' Discovery using the Exclude list override the DB Engine is not fully undiscovered, the instance is still discovered but seems to go into a not monitored state, is this by design?Most enterprise organisations do not want to monitor Express editions of SQL or commonly Developer editions as well. It would be nice to be able to discover\override by Edition.
    • Anonymous
      November 18, 2016
      Thanks for your message. You should override an exclude list of the 'Discovery SQL Server 20XX Database Engines' to disable discovering particular instances. After you add an instance in this Exclude list, it will get undiscovered and disappear from appropriate views.Add an override for excluding instances of particular editions is a good idea. I'll add it to our product backlog but can't promise you that we'll do it in a next release.
  • Anonymous
    November 28, 2016
    Having a few issues with this MP.---------------------------------Event ID: 4001. Management Group: Ops. Script: ModuleAction Module: ActiveConnectionsDataSource.ps1 Version: 6.7.7.0 : Error occured during Active connection data source executing.Computer: LYCReason: Exception calling "Fill" with "1" argument(s): "The user does not have permission to perform this action." Position:416 Offset:3 Instance:RTCLOCALDetailed error output: Exception calling "Fill" with "1" argument(s): "The user does not have permission to perform this action."=====================================================================================Event ID: 4001. Management Group: KHAOps. Script: Main Module: CPUUsagePercentDataSource.ps1 Version: 6.7.7.0 : Error occured during CPU Usage for SQL Instances data source executing.Computer:KOFReason: Cannot connect to the target Sql Server instance.Connection log:Failed to connect to data source 'KOF\KOFAXCAPTURE': Exception calling "Open" with "0" argument(s): "Login failed for user 'DOMAIN\OMSQLM'."Failed to connect to data source 'KOF,49349': Exception calling "Open" with "0" argument(s): "Login failed for user 'DOMAIN\OMSQLM'." Position:768 Offset:7 Instance:KOFAXCAPTURE
    • Anonymous
      November 30, 2016
      Thanks for your message. We need some details, could you share them with us:1. SQL Server version2. Can you connect to mentioned SQL Server instances using your Action Account DOMAIN\OMSQLM? Am I right that you use DOMAIN\OMSQLM for monitoring SQL Servers?These alerts look like problems caused by a lack of permissions. So, let's check this first. You can answer leaving a comment here or emailing us at sqlmpsfeedback@microsoft.com
  • Anonymous
    December 08, 2016
    I get a error on a new installed SQL 2014 server:Event ID: 4201. Management Group: PA-SCOM. Script: DiscoverSQL2014DBEngineDiscovery.vbs. Version: 6.7.7.0 : The next errors occured:Access denied while reading registry value [\SRV-VM-SQL185.politieacademie.local\HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQLServer\Parameters(Default)]:
    • Anonymous
      December 09, 2016
      Thank you for letting us know. Looks like a lack of permissions for an account you use for SQL Server monitoring. Could you tell us more about your security configuration (Run As profiles, SQL MP monitoring accounts, how you distribute run as profiles, etc.)?You can tell the above by replying my message here or emailing us at sqlmpsfeedback@microsoft.com.
      • Anonymous
        December 13, 2016
        Hi Alex,I use for the Run As Account a domain account. This account is sysadmin on the SQL server. We distribute this account More Secure to the server. The server object is added to the profiles Discovery and Monitoring.Futher I enabled HealtService SidState and Create the HealthService login as SA Role. The account has sysadmin rights.Hope that this is the information your looking for.
        • Anonymous
          December 14, 2016
          Thanks for providing us with the details. At the moment, I can see that the monitoring account couldn't access the Windows Registry. If your account has sysadmin rights, I can guess that it's an obsolete alert which might be already closed. Please, look into Operations Manager log of the new server and find when such an event appeared the last time. Probably, this event appeared before you added the server object to the profiles Discovery and Monitoring.
  • Anonymous
    December 13, 2016
    Still there is problem with SQL Dashboards in the latest SQL MP, version 6.7.7.0. In slightly larger SQL environments the dashboards timeouts and create the EventID 26319 in SCOM log. Would this not been resolved in this version???//Mats A
  • Anonymous
    December 19, 2016
    I´m getting a lot of 4001 event id like this....Event ID: 4001. Management Group: sefazscom01. Script: Main Module: CPUUsagePercentDataSource.ps1 Version: 6.7.7.0 : Error occured during CPU Usage for SQL Instances data source executing.Computer:SRV10445 Reason: Position:33 Offset:27Detailed 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()--------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()--------Cannot find path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\000' because it does not exist.I have checked this registry key in the target server and the correct key is 009. The OS and SQL are 2008
    • Anonymous
      December 19, 2016
      Arthur, thank you for reporting the issue. We need to get some extra details on the affected machine. Please drop us a message at sqlmpsfeedback@microsoft.com so that we'll be able to send you a script for collecting info and ask you a couple of questions.
  • Anonymous
    December 07, 2017
    The comment has been removed
  • Anonymous
    December 08, 2017
    The comment has been removed
    • Anonymous
      December 13, 2017
      Thank you for your message. Those errors were probably caused by a lack of permissions to query WMI (at least WMI). Did they appear after you'd updated SQL MP? Or immediately after you configured the SQL MP Run As Profiles? Do you have stand-alone SQL Server instances? Are there errors in the OpsMan log of the servers hosting such instances?Please make sure that you monitoring account has rights to connect WMI remotely. You can answer here or at sqlmpsfeedback@microsoft.com.
      • Anonymous
        December 15, 2017
        Thank you for the reply Alex, I sent an email from my work account there.