PBM is coming up with errors when executing policies against groups in CMS groups

• vicky-434164

  SSC Enthusiast

  Points: 184

  More actions

  June 11, 2013 at 1:31 pm

  #276204

  Hi All,

  I have SQL 2012 SQL server which I am using as central server for Central management server. Also I have created varous policies to manage the server which are mostly SQL 2008 or R2 or 2012.

  I am running the PBM (policy based management) tool as the SQL server scheduled job and its working for local server, however not working for servers under CMS . Policies are correct and can be run for local or for multiple remote server, if I execute this via management studio or manually. However When i run this as SQL server job, it keeps on failing. I have attached the error below. Also I have already created proxy server account for this and alreay checked permission for SQL server agent account on all servers.

  Configuration of SQL server is also checked for remote connection, TCP/IP enabled, named pipes enabled and for firewall. Every thing else works fine and I am able to connect to other server via CBM and from local server. However when I run this code , It keeps on failing with connectivity issue... Any idea will be really helpful.

  Attach is the error message

  <DMF:Exception type="string">Microsoft.SqlServer.Management.Dmf.PolicyEvaluationException: Exception encountered while executing policy DATABASE MAINT - LastLogBackupDate. ---> Microsoft.SqlServer.Management.Common.ConnectionFailureException: Failed to connect to server . ---> System.Data.SqlClient.SqlException: A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)<?char 13?> at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)<?char 13?> at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)<?char 13?> at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)<?char 13?> at System.Data.SqlClient.SqlConnection.Open()<?char 13?> at Microsoft.SqlServer.Management.Common.ConnectionManager.InternalConnect(WindowsIdentity impersonatedIdentity)<?char 13?> at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()<?char 13?> --- End of inner exception stack trace ---<?char 13?> at Microsoft.SqlServer.Management.Common.ConnectionManager.Connect()<?char 13?> at Microsoft.SqlServer.Management.Common.ConnectionManager.get_ServerVersion()<?char 13?> at Microsoft.SqlServer.Management.Common.ServerConnection.Microsoft.SqlServer.Management.Common.ISfcConnection.get_ServerVersion()<?char 13?> at Microsoft.SqlServer.Management.Sdk.Sfc.SqlStoreConnection.get_ServerVersion()<?char 13?> at Microsoft.SqlServer.Management.Dmf.ObjectSet.<CalculateTargets>d__1d.MoveNext()<?char 13?> at Microsoft.SqlServer.Management.Dmf.ObjectSet.CalculateTargets(IEnumerable objectSet, Condition condition, AdHocPolicyEvaluationMode evaluationMode, Object[]& conforming, TargetEvaluation[]& violating)<?char 13?> at Microsoft.SqlServer.Management.Dmf.ObjectSet.CalculateTargets(SqlStoreConnection targetConnection, Condition condition, AdHocPolicyEvaluationMode evaluationMode, String policyCategory, Object[]& conforming, TargetEvaluation[]& violating)<?char 13?> at Microsoft.SqlServer.Management.Dmf.Policy.EvaluatePolicyUsingConnections(AdHocPolicyEvaluationMode evaluationMode, SfcQueryExpression targetQueryExpression, Int64& historyId, ISfcConnection[] targetConnections)<?char 13?> --- End of inner exception stack trace ---</DMF:Exception>

  <DMF:ID type="long">1</DMF:ID>

  <DMF:Result type="boolean">false</DMF:Result>