Windows Server 2008

  1. Cluster NFS Share : Online service sanity check failed - the resource id passed in '%2' did not match the internal resource ...
  2. Cluster NFS Share : Open: Unable to open Parameters registry key. You can try deleting and creating the resource again. Error: ...
  3. Cluster NFS Share : ResourceControl sanity check failed - the resource id passed in '%2' did not match the internal resource ...
  4. Cluster NFS Share : Terminate sanity check failed - the resource id passed in '%2' did not match the internal resource id ...
  5. Cluster NFS Share : The NFS share resource is required to be dependent on exactly one storage resource and that Storage resource ...
  6. Cluster NFS Share : The Server for NFS component is not installed. Delete the NFS Share resource, install the Server for ...
  7. Cluster NFS Share : There was a sharing violation of a particular resource. Please try again after some time or contact your ...
  8. Cluster NFS Share : Unable to bring the resource online as a required Client Access Point (Network Name) dependency is missing. ...
  9. Cluster NFS Share : Unable to bring the resource online as a required Storage dependency is missing. Add a Storage dependency ...
  10. Cluster NFS Share : Unable to determine if NFS share resource is dependent on a Client Access Point (Network Name) resource. ...
  11. Cluster NFS Share : Unable to determine if the NFS share resource is dependent on a Storage resource. Check the Storage dependency ...
  12. Cluster NFS Share : Unable to determine the name of the dependent storage resource. Check the Storage dependency for this ...
  13. Cluster node '%1' was removed from the active failover cluster membership. The Cluster service on this node may have stopped. ...
  14. Cluster node cleanup encounted at least one error. You may be unable to create or join a cluster with this machine until ...
  15. Cluster physical disk resource '%1' cannot be brought online because the associated disk could not be found. The expected ...
  16. Cluster resource '%1' (resource type '%2', DLL '%3') either crashed or deadlocked. The Resource Hosting Subsystem (RHS) process ...
  17. Cluster resource '%1' cannot be brought online because the associated service failed an attempted restart. The error code ...
  18. Cluster resource '%1' cannot be brought online because the associated service failed to start. The service return code is ...
  19. Cluster service failed to change the trace log size. Please verify the ClusterLogSize setting with the 'cluster.exe /prop' ...
  20. Cluster service failed to retrieve the list of clustered disks while destroying the cluster. The error code was '%1'. If ...
  21. Cluster service failed to start the cluster log trace session. The error code was '%2'. The cluster will function properly, ...
  22. Cluster service failed to update the cluster configuration data on the witness resource. Please ensure that the witness resource ...
  23. Cluster service has detected that its service account is missing one or more from the required set of privileges. The missing ...
  24. Cluster to which this Terminal server belongs. Typically, it is a DNS entry which represents the Virtual IP address of computers. ...
  25. Clustered disk with ID '%2' was not released by the Partition Manager while destroying the cluster. The error code was '%1'. ...
  26. Clustered disks have been released by the Partition Manager while destroying the cluster. These disks will be left in an ...
  27. Clustering Services have been detected on this node. Certain clustering functionality may be impaired by Internet Connection ...
  28. Clustering Services have been detected on this node. Certain clustering functionality may be impaired by the Network Bridge. ...
  29. Clusters provide high availability for applications and services installed on clustered servers. High availability means ...
  30. CMD.EXE was started with the above path as the current directory. UNC paths are not supported. Defaulting to Windows directory. ...
  31. cmd.exe,"/k echo This environment should only be used to recover from a failed installation. Type EXIT and press Enter to ...
  32. Coalesce is either not used properly or this form is not currently supported. Check for possible mixing of grouping with ...
  33. Code Integrity determined an unsigned kernel module %2 is loaded into the system. Check with the publisher to see if a signed ...
  34. Code integrity determined that the image hash of a file is not valid. The file could be corrupt due to unauthorized modification ...
  35. Code Integrity is unable to verify the image integrity of the file %2 because a file hash could not be found on the system. ...
  36. Code Integrity is unable to verify the image integrity of the file %2 because the set of per-page image hashes could not ...
  37. Code Integrity is unable to verify the image integrity of the file %2 because the set of per-page image hashes could not ...
  38. CoId=%1: A user was unable to connect on port %2. No more connections can be made to this remote computer because the computer ...
  39. CoId=%1: Layer=%2: SubLayer=%3: The connection attempt failed on port: %4 because of the authentication protocol selected. ...
  40. CoId=%1: The account for user %2\%3 connected on port %4 does not have Remote Access privilege. The line has been disconnected. ...
  41. CoID=%1: The port %2 has been disconnected because the user reached the maximum connect time allowed by the administrator. ...
  42. CoId=%1: The Remote Access Server's attempt to callback user %2 on port %3 at %4 failed because of the following error: %5 ...
  43. CoID=%1: The user %2 connected on port %3 on %4 at %5 and disconnected on %6 at %7. The user was active for %8 minutes %9 ...
  44. CoId=%1: The user %2 connected on port %3 on %4 at %5 and disconnected on %6 at %7. The user was active for %8 minutes %9 ...
  45. CoId=%1: The user %2 connected to port %3 has been disconnected because no network protocols were successfully negotiated. ...
  46. CoID=%1: The user %2 has connected and has been successfully authenticated on port %3. Data sent and received over this link ...
  47. CoID=%1: The user %2 has connected and has been successfully authenticated on port %3. Data sent and received over this link ...
  48. CoId=%1: The user %2 has dialed a connection named %3 to the Remote Access Server which has successfully connected. The connection ...
  49. CoId=%1: The user %2 has started dialing a %3 connection using a %4 connection profile named %5. The connection settings ...
  50. CoId=%1: The user %2 is trying to establish a link to the Remote Access Server for the connection named %3 using the following ...
  51. CoId=%1: The user connected to port %2 has been disconnected because the authentication process did not complete within the ...
  52. Collection is an abstract class that provides a common superclass for data elements that represent collections of ManagedElements ...
  53. Collections of type "{0}" do not allow duplicate items. An attempt was made to add an duplicate item identified by the key ...
  54. CollectionSetting represents the association between a CollectionOfMSEs class and the Setting class(es) defined for them. ...
  55. Collects and stores configuration information for the network and notifies programs when this information is modified. If ...
  56. Color settings are stored separately for each user. To make changes for new users and shared printers, click Change System ...
  57. Colors and sizes selected here only apply if you have selected a Windows Classic color scheme. If any other scheme is applied, ...
  58. Column {0} may not be used for lookups of '{1}' values because the column is not indexed or is not indexed as type '{1}'. ...
  59. Columns cannot be added after ResultNode instances have been added to the list view. To add columns, first remove all ResultNode ...
  60. Columns cannot be removed after ResultNode instances have been added to the list view. To remove columns, first remove all ...
  61. COM cannot locate a provider referenced in the schema. This error may be caused by any of the following: The provider is ...
  62. COM+ could not add the user '%1' to the role '%2'. The COM+ admin or the Distributed Transaction Coordinator may not be working ...
  63. COM+ could not create the object '%1' with GUID '%2' in the collection '%3'. The COM+ admin or the Distributed Transaction ...
  64. COM+ could not import the component '%1' into the application '%2'. The COM+ admin or the Distributed Transaction Coordinator ...
  65. COM+ could not install the component from '%1' into the application '%2'. The COM+ admin or the Distributed Transaction Coordinator ...
  66. COM+ could not set a property of the component '%1' in the application '%2'. The COM+ admin or the Distributed Transaction ...
  67. COM+ could not set a property of the object '%1' in the collection '%2'. The COM+ admin or the Distributed Transaction Coordinator ...
  68. COM+ failed to find the correct partition for the admin SDK. The admin SDK will use the base partition. Check that users ...
  69. COM+ has determined that your machine is running very low on available memory. In order to ensure proper system behavior, ...
  70. COM+ Network Access enables Application Server to host and allow remote invocation of applications built with COM+ or Enterprise ...
  71. COM+ provides an enterprise development environment, based on the Microsoft Component Object Model (COM), for creating component-based, ...
  72. COM+ requires that ODBC version 2.0 or greater be installed on your machine. The version of ODBC that ships with Windows ...
  73. COM+ Services was unable to authorize the incoming call due to an unexpected failure. The incoming call was denied and a ...
  74. COM+ Services was unable to determine the caller's identity because of an unexpected error. This may be caused by a shortage ...
  75. COM+ Services was unable to initialize due to a failure in the system API shown below. This is often caused by a shortage ...