Windows 8

  1. Serialization failure occurred when reading a field with WS_TYPE '%1', WS_FIELD_MAPPING '%2', name '%3' and namespace '%4'. ...
  2. Serialization failure occurred when writing a field with WS_TYPE '%1', WS_FIELD_MAPPING '%2', name '%3' and namespace '%4'. ...
  3. Serialization of a property has been skipped, because property getter failed. Property name: %1 Property owner's type name: ...
  4. Serialization of a script property has been skipped, because there is no runspace to use for evaluation of the property. ...
  5. Serialization of an enumerable object might not be complete, because object being enumerated threw an exception. Type of ...
  6. Serialization of specified properties failed, because one of the specified properties was missing. Type of object: %1 Property ...
  7. SerialNumber - Comma separated list of certificate serial numbers to revoke Reason - numeric or symbolic revocation reason: ...
  8. Server %1 resolved to these IP addresses: %2, but none of the addresses could be reached (pinged). Please check the network. ...
  9. server %2 is unavailable and cannot currently be used. Remote Access will attempt to use %1 server %3 for OTP authentication. ...
  10. Server Announce Allocations Failed/sec is the rate at which server (or domain) announcements have failed due to lack of memory. ...
  11. Server application is attempting to receive the SSL client certificate, which will be provided if available. If the client ...
  12. Server application passed response (request ID %1, connection ID %2, method %4, header length %5, number of entity chunks ...
  13. Server authentication verifies that you are connecting to the intended remote computer. The strength of the verification ...
  14. Server could not allocate memory. Please close one or more windows applications to release memory and try the operation again. ...
  15. Server for Network Information Service integrates Windows and NIS networks by exporting NIS domain maps to Directory Service ...
  16. Server for Network Information Services (NIS) Tools is deprecated beginning with this release. You should begin planning ...
  17. Server for NFS caches user authentication and can renew the cache on a regular basis to reflect changes to user priviledges. ...
  18. Server for NFS can record client request in the operational channel of the services for NFS event log. You can view the operational ...
  19. Server for NFS cannot delete the shared directory. Try deleting the shared directory again, or restart the server and try ...
  20. Server for NFS cannot initialize the Network File System (NFS) shared resource %1 at the path %2 for sharing as a result ...
  21. Server for NFS cannot initialize the Network File System (NFS) shared resource %1 at the path %2 for sharing as the file ...
  22. Server for NFS cannot initialize the Network File System (NFS) shared resource %1 at the path %2 for sharing as the file ...
  23. Server for NFS cannot initialize the Network File System (NFS) shared resource %1 at the path %2 for sharing as the path ...
  24. Server for NFS cannot initialize the volume with drive letter %1 for sharing as it does not provide the required attributes ...
  25. Server for NFS cannot initialize the volume with drive letter %1 for sharing. Network File System (NFS) shared resources ...
  26. Server for NFS cannot read the entry because the client record is malformed or there is not enough memory. Try again, or ...
  27. Server for NFS cannot remove the share information from the registry. Try deleting the shared directory again, or restart ...
  28. Server for NFS cannot unshare the shared directory. Try unsharing the shared directory again, or restart the server and try ...
  29. Server for NFS cannot update the share configuration. Try updating the shared directory again, or delete and recreate the ...
  30. Server for NFS could not connect to the Lightweight Directory Access Protocol (LDAP) server for domain %1. Without a connection ...
  31. Server for NFS could not create all the endpoints configured. Server for NFS will attempt to continue but some NFS clients ...
  32. Server for NFS could not create any RPC endpoints. Server for NFS did not start. Server for NFS creates RPC endpoints to ...
  33. Server for NFS could not find any Lightweight Directory Access Protocol (LDAP) accounts which match attribute %1. Without ...
  34. Server for NFS could not obtain mapping information from User Name Mapping. Server for NFS will make another attempt after ...
  35. Server for NFS could not obtain updated mapping information from User Name Mapping. Server for NFS will continue to use the ...
  36. Server for NFS could not read the character translation file %1. Server for NFS cannot translate characters in file names. ...
  37. Server for NFS could not register the mount protocol on the specified port. Server for NFS did not start. Without the mount ...
  38. Server for NFS could not register the Network File System (NFS) protocol on the specified port (%5). Status: %6. Server for ...
  39. Server for NFS could not register the Network Lock Manager (NLM) protocol on the specified port. Server for NFS did not start. ...
  40. Server for NFS could not register the Network Status Manager (NSM) protocol on the specified port. Server for NFS did not ...
  41. Server for NFS could not register with RPC Port Mapper on all requested port/protocol combinations. Server for NFS will attempt ...
  42. Server for NFS could not register with RPC Port Mapper. Server for NFS did not start. Network File System (NFS) clients discover ...
  43. Server for NFS enables this computer to share files with UNIX-based computers and other computers that use the network file ...
  44. Server for NFS encountered an error %3 while querying User Name Mapping. At least one user is not mapped. Users who are not ...
  45. Server for NFS encountered an error condition (%1) when attempting to a add a service principal name for this machine account ...
  46. Server for NFS encountered an error condition when checking for the presence of Failover Clustering (%1) and will continue ...
  47. Server for NFS failed while listening for update notification events. Windows may be low on system resources. Try increasing ...
  48. Server for NFS is not configured for either Active Directory Lookup or User Name Mapping. Without either Active Directory ...
  49. Server for NFS is not running. The Network File System resource can be online only when server for NFS is in running state. ...
  50. Server for NFS received a dismount notification for volume %2 (ResolvedPath %4, VolumeId %5). Closing root directory file ...
  51. Server for NFS received a mount notification for volume %2 (ResolvedPath %4, VolumeId %5). Refreshing root directory file ...
  52. Server for NFS received a size change notification for volume %2 (ResolvedPath %4, VolumeId %5). Updating cached volume size ...
  53. Server for NFS was not able to fit all the information from an audit into one audit entry. The next audit entry will be truncated. ...
  54. Server for NFS was requested to re-start volume %2 (ResolvedPath %4, VolumeId %5) currently awaiting delete processing. Re-start ...
  55. Server for NFS was unable to obtain or refresh security information for the user account %1. Check that the user account ...
  56. Server for NFS was unable to obtain security information for the configured UnmappedUnixUserUsername user account %1. Check ...
  57. Server for NFS was unable to obtain security information for the GSS user account %1. Check that the user account %1 is valid ...
  58. Server for NFS was unable to query the configured identity mapping store for the name of an account. Check that that the ...
  59. Server for NFS was unable to validate licensing information at this time, the server will be nonfunctional until this information ...
  60. Server for NIS cannot use the specified map update interval. You must select valid values. Valid values for intervals are ...
  61. Server for NIS enables a Microsoft Windows based Active Directory Domain Services - domain controller to administer UNIX ...
  62. Server for NIS has sent YPPUSH requests for updated maps to subordinate NIS servers in all domains. Check for errors in Event ...
  63. Server for NIS periodically checks for updates to maps in all NIS domains for which it is the master, and then propagates ...
  64. Server Graphical Shell provides the full Windows graphical user interface for server, including File Explorer and Internet ...
  65. Server List Requests/sec is the rate at which requests to retrieve a list of browser servers have been processed by this ...
  66. Server Manager cannot be closed right now. Some applications or processes are either still active or require user action ...
  67. Server Manager cannot load the server list. Click OK to reset the server list and continue. Click Cancel to close Server ...
  68. Server Manager cannot open the "Shut Down Windows" dialog box. Click OK to close this message, and then try to shut down ...
  69. Server Manager cannot run because of an error in a user settings file. Click OK to restore default settings and continue, ...
  70. Server Manager is collecting inventory data. If servers are found that support remote installation or removal of roles and ...
  71. Server Manager is unable to validate that selected server {0} meets configuration requirements for your selected features, ...
  72. Server Manager was unable to determine whether BitLocker is in use on the server. Before uninstalling BitLocker Drive Encryption, ...
  73. Server name {0} could not be found on the RD Virtualization Host servers in the deployment. Specify the correct server name ...
  74. Server name {0} is not a fully qualified domain name (FQDN). Specify all server names in FQDN format in the -VirtualDesktopAllocation ...
  75. Server object %3 was created in site %4, but computer %2 cannot be modified to point to the new server object. The following ...