Hi guys There's one other thing I noticed if you're getting the script failure alerts for StolenServerMemory2008.ps1. Apart from disabling the monitor, you need to also disable the Collect DB Engine Stolen Server Memory rules as well otherwise you'll still get an alert for the collection rule trying to run.
Paul Woudwijk
4 Mar 2014 3:39 PM
I bet that everyone that is having alerts for the StolenServerMemory2008.ps1 script, is running a default instance of SQLServer on a non default port. All Microsoft software Always expects a default instance to be : default... that means running an port 1433. The browser service is not even asked for the default instance.
If you change in the powershell script
if ($InstanceName -eq "MSSQLSERVER")
{
$InstanceName = "DEFAULT"
}
$principalName = $ComputerName
if ($InstanceName -ne "DEFAULT") {
$principalName = "{0}\{1}" -f $principalName, $InstanceName
}
To
$principalName = $ComputerName
if ($InstanceName -eq "MSSQLSERVER")
{
$InstanceName = "DEFAULT"
$principalName = "{0},1234" -f $ComputerName
}
if ($InstanceName -ne "DEFAULT") {
$principalName = "{0}\{1}" -f $principalName, $InstanceName
}
Where 1234 is youre instances port number youre good to go.
27 Mar 2014 11:54 AM
Hi Kevin,
I am facing an issue with the config service.
Below is the error which is raised from monitor
Snapshot synchronization state:
Error Desc:
Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessException: Data access operation failed at Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.DataAccessOperation.ExecuteSynchronously(Int32 timeoutSeconds, WaitHandle stopWaitHandle) at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.ConfigurationStore.ExecuteOperationSynchronously(IDataAccessConnectedOperation operation, String operationName) at Microsoft.EnterpriseManagement.ManagementConfiguration.SqlConfigurationStore.ConfigurationStore.StartSnapshot() at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.SnapshotSynchronizationWorkItem.StartSnapshot() at Microsoft.EnterpriseManagement.ManagementConfiguration.Engine.SnapshotSynchronizationWorkItem.ExecuteSharedWorkItem() at Microsoft.EnterpriseManagement.ManagementConfiguration.Interop.SharedWorkItem.ExecuteWorkItem() ----------------------------------- System.Data.SqlClient.SqlException (0x80131904): Sql execution failed. Error 50000, Level 16, State 1, Procedure SnapshotSynchronizationStart, Line 49, Message: Failed to set configuration space lock. Other process uses config space at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader() at System.Data.SqlClient.SqlCommand.EndExecuteNonQuery(IAsyncResult asyncResult) at Microsoft.EnterpriseManagement.ManagementConfiguration.DataAccessLayer.NonQuerySqlCommandOperation.SqlCommandCompleted(IAsyncResult asyncResult)
Anthony
17 Apr 2014 9:44 AM
I too have this same Snapshot synchronization state: error in the last few days.
Cant find much about it online but I have no issue so is this a buggy alert?
Anthony
14 May 2014 10:27 PM
I am still getting these Snapshot sync errors now and again, they clear after a while but I am worried something is a miss and don't want to ad the latest CU until I can get an answer on this, I am going to log a call with MS tomorrow but, Kevin if you have and answer that would be great :)
14 May 2014 10:35 PM
Config service Snapshot synch failures has nothing to do with the SQL management pack.
Snapshot synch failures are when the Config service fails to run a daily full configuration update (as opposed to delta synch, (which occurs throughout each day many times).
There are many possible causes, and I am planning a blog post on this.
The most common scenario is a timeout failure just due to timing out. See:
http://blogs.technet.com/b/momteam/archive/2013/01/29/support-tip-config-service-deltasynchronization-process-fails-with-timeout-exception.aspx
One of the most common issues is that SCOM needs .NET 4.5.1 on Windows Server 2012, instead of .NET 4.5.
In your specific case, your timeout is "Failed to set configuration space lock"
That means that most likely we tried to run a snapshot, and this failed because another management server was running a synch at the same time. You can look at the config synch logging table in SQL: (select * from cs.workitems) and see if they finished or not
on the next run of snapshot synch.
When I have time I plan a much deeper dive in config service synch.
Jim D
27 May 2014 5:44 PM
Can you expand on your comment that SCOM needs .NET 4.5.1 on Windows 2012? Is that just for a server hosting the OpsMgr databases?
Michael H
16 Jun 2014 10:07 PM
I've configured the low-privilege setup on a couple 2012 SQL servers that were not working well with letting Local System be the action account. I'm getting good data now. I'm now trying the same setup with the SQL cluster used for my SCOM database instances. I am getting PowerShell script execution error messages in the OpsMgr console saying that there are not enough permissions for the account. When I look at the SQL error logs, I see that something (I'm assuming the MP scripts) is trying to log into the databases as NT AUTHORITY\SYSTEM and can't because that login is not mapped to any databases. Why wouldn't the MP be trying to execute those scripts as one of the action accounts I created as part of the low-privilege setup? Does some other object other than the nodes need the action accounts specified in the RunAs profile?
Kerim
30 Jun 2014 12:46 PM
Hi Kevin, first my compliments on the blog. I was wondering did anyone found a solution for the StolenServerMemory2008.ps1 bug? :)
3 Jul 2014 8:03 PM
There's an update for SQL MP in the Catalog - lots problem resolved.
18 Jul 2014 11:15 PM
SQL Server Core Library did not pass the security verification.
The management pack cannot be downloaded and the temporary file has been deleted.
Could not load management pack [ID=Microsoft.SQLServer.Library, Keytoken=31bf3856ad364e35, Version=6.4.1.0].