The Host "%1" was clustered, but was not made dependant on a Network Name resource. This could be because of the following reasons: 1) No Network Name resources were available in the selected cluster resource group "%2". 2) Multiple Network Name resources were available, making it ambiguous to choose one resource. You can add this dependency manually using the Cluster MMC.
The header specification name must be specified when generating a header without using the functionality for preserving headers. ...
The Health and Activity Tracking (HAT) tool provides features for reporting, analyzing, and debugging data and messages that ...
The highlighted volumes (if any) do not have enough disk space available for the currently selected features. You can either ...
The highlighted volumes do not have enough disk space available for the currently selected features. You can either remove ...
The Host "%1" was clustered, but was not made dependant on a Network Name resource. This could be because of the following ...
The host instance is in an inconsistent state for this BizTalk service. Therefore, the service will shutdown. Please delete ...
The Host was clustered, but was not made dependant on a Network Name resource. This could be because no Network Name resources ...
The HTTP port of the IIS Web site where the Windows SharePoint Services adapter Web service is installed. By default, this ...
The HTTP response status code specified in the message context is outside the acceptable range of values. You must specify ...