Could not connect to the cluster. This could be due to the following: 1) BizTalk Host instances are not installed on MSCS cluster nodes. In order to cluster a Host, all its BizTalk Host instances should be installed on MSCS cluster nodes. 2) The cluster is no longer available. Check if the Cluster Service is running on the nodes or restart the service. 3) You do not have the required privileges on the cluster for this operation. Server name is: %1 The system error is: %2
Controls the severity of a database sized triggered throttling condition. This parameter sets the severity of a throttling ...
Controls the severity of a process memory triggered throttling condition. This parameter sets the severity of a throttling ...
Controls triggering of .NET garbage collection (GC). When the memory consumption exceeds this percentage value of the memory ...
Coordinators can view and manage UDDI Services data. Use the Coordinate options to show or hide categorization schemes on ...
Could not connect to the cluster. This could be due to the following: 1) BizTalk Host instances are not installed on MSCS ...
Could not create a Microsoft Message Queuing (MSMQ) queue with name {0}. Either the queue already exists or the RFID Service ...
Could not create key 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
Could not create key: 2]. { System error 3].} Verify that you have sufficient access to that key, or contact your support ...
Could not create the group hierarchy because of the following reason: {0}. Resolve the issue causing the error, and then ...