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
Connection to device {0} cannot be closed because the supplied connection GUID does not match an existing connection. Verify ...
Constructor for class {0} in assembly {1} does not exist, is not accessible, or does not contain a signature matching the ...
Context property with DateTime type cannot be demoted into the message content. All properties of DateTime type must be converted ...
CopyTo() method can only work with single-dimensional arrays. Specifically, in this case, it cannot copy data into the {0}-dimensional ...
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 ...