UI Translation

Windows Server 2003

  1. The node ID obtained during Appletalk initialization on adapter "%2" was assigned to another device. Current node ID was ...
  2. The node is no longer attached to cluster network '%1' by adapter %2. Cluster service will delete network interface '%3' ...
  3. The node owning the '%1' group must be listed as a possible owner for this resource. You must move the '%1' group to another ...
  4. The node was unable to secure its connection to cluster node %1. The error code was %2. Check that all nodes in the server ...
  5. The node's attempt to join the server cluster was aborted by the sponsor node. Check the event log of an active server cluster ...
  6. The non resident attribute of type 4 and instance tag 5 is inconsistent. The valid data length is 1, file size 2, and allocated ...
  7. The notification event log list cannot have more than 1040 characters. Check the list for duplicate entries, and then try ...
  8. The notification eventlist should have one or more events seperated by exactly one "," and event numbers must be 3 digit ...
  9. The notification URL entered is not valid when used in combination with the notification type selected. Ensure that the correct ...
  10. The NoWriters property indicates whether the shadow copy was created with the involvement of shadow copy writer components. ...
  11. The NtCreateFile API failed. This error should never be returned to an application, it is a place holder for the Windows ...
  12. The NTDS Settings object you want to delete represents Active Directory domain controller %1 in site %2. Which of the following ...
  13. The NTDS-DSA object: '%1' is not properly configured and is preventing the forest functional level from being raised. It ...
  14. The number of active IPSec quick mode security associations offloaded to hardware. Certain network adapters can accelerate ...
  15. The number of AS requests serviced by the KDC per second. AS requests are used by client to obtain a ticket granting ticket. ...
  16. The number of blocks of staging file data received from all inbound partners associated with this replica set member. The ...
  17. The number of blocks of staging file data received from the partner associated with this connection. The underlying transport ...
  18. The number of blocks of staging file data sent to any outbound partner associated with this replica set member. The underlying ...
  19. The number of blocks of staging file data sent to the partner associated with this connection. The underlying transport may ...
  20. The number of bytes of non-pageable computer memory the server is using. This value is useful for determining the values ...
  21. The number of bytes of pageable computer memory the server is currently using. Can help in determining good values for the ...
  22. The number of bytes that can be read from or written to a Media. This property is not applicable to \"Hard Copy\" (documentation) ...
  23. The number of bytes the server has sent to and received from the network. This value provides an overall indication of how ...
  24. The number of change orders received from the partner associated with this connection that have been filtered out by the ...
  25. The number of change orders received from the partner associated with this connection that have passed the inbound dampening ...
  26. The number of change orders sent to the partner associated with this connection that have been filtered out by the outbound ...
  27. The number of days a pending BITS job can remain inactive before being considered abandoned by the requestor. Once a job ...
  28. The number of disconnected sessions on this server. These sessions may still be actively consuming server resources, however ...
  29. The number of entries in the acquire heap. The acquire heap stores successful acquires. Acquires are outbound requests to ...
  30. The number of entries in the Internet Key Exchange (IKE) receive buffers. The receive buffers are used to store incoming ...
  31. The number of failed logon attempts to the MacFile server. Can indicate whether password guessing programs are being used ...
  32. The number of failed logon attempts to the server. Can indicate whether password guessing programs are being used to crack ...
  33. The number of inbound partner join requests or outbound partner ready-to-join notifications sent to all partners associated ...
  34. The number of incoming packets that are silently discarded for a reason other than "malformed," "invalid Message Authenticator," ...
  35. The number of internal files currently open in the MacFile server. This count does not include files opened on behalf of ...
  36. The number of link value updates received in the current directory replication update packet that have not yet been applied ...
  37. The number of local plus remote file updates that have been received by this replica set member. Note that depending on the ...
  38. The number of local plus remote file updates that were propagated to the outbound log of this replica set member. The update ...
  39. The number of local plus remote file updates that were retried due to a problem during the final target file rename or delete ...
  40. The number of local plus remote file updates that were retried due to a stage file fetch problem on this replica set member. ...
  41. The number of local plus remote file updates that were retried due to a stage file generation problem on this replica set ...
  42. The number of local plus remote file updates that were retried due to a stage file install problem on this replica set member. ...
  43. The number of locally originated file updates that encountered a name space collision on this replica set member. Most likely ...
  44. The number of locally originated file updates that were aborted. Most likely because a file was deleted before a change to ...
  45. The number of locally originated file updates that were propagated to the outbound log of this replica set member. The update ...
  46. The number of locally originated file updates that were retried due to a problem during the final target file rename or delete ...
  47. The number of locally originated file updates that were retried due to a stage file fetch problem on this replica set member. ...
  48. The number of locally originated file updates that were retried due to a stage file generation problem on this replica set ...
  49. The number of locally originated file updates that were retried due to a stage file install problem on this replica set member. ...
  50. The number of locally originated file updates which were created by a partner induced version vector scan that have been ...
  51. The number of locally originated replication change orders produced by a partner induced version vector scan that have been ...
  52. The number of locally originated replication change orders that have been sent to the partner associated with this connection. ...
  53. The number of main mode state entries. This counter includes successfully negotiated main modes, main mode negotiations in ...
  54. The number of NTFS change log records skipped by FRS. Most likely because the change log record was for a file not part of ...
  55. The number of object updates received in the current directory replication update packet that have not yet been applied to ...
  56. The number of panels found does not agree with the number of panels in the registry, perhaps a panel has not been configured ...
  57. The number of partner join requests (if this is an inbound connection) or ready-to-join notifications (if this is an outbound ...
  58. The number of pending outbound file updates that were dampened because the outbound partner has already received it from ...
  59. The number of pending requests to initiate an Internet Key Exchange (IKE) negotiation in order to establish a security association ...
  60. The number of print-stream pages that the Printer will render onto a single media sheet unless a Job specifies otherwise. ...
  61. The number of RADIUS Accounting-Request packets received and responded to but not recorded on this IAS server's accounting ...
  62. The number of remotely originated file updates that encountered a name space collision on this replica set member. Most likely ...
  63. The number of remotely originated file updates that have been received by this replica set member. Note that depending on ...
  64. The number of remotely originated file updates that were aborted. Most likely because of an attempt to fetch a staging file ...
  65. The number of remotely originated file updates that were dampened because the update was already delivered by another member. ...
  66. The number of remotely originated file updates that were propagated to the outbound log of this replica set member. The update ...
  67. The number of remotely originated file updates that were retried due to a problem during the final target file rename or ...
  68. The number of remotely originated file updates that were retried due to a stage file fetch problem on this replica set member. ...
  69. The number of remotely originated file updates that were retried due to a stage file generation problem on this replica set ...
  70. The number of remotely originated file updates that were retried due to a stage file install problem on this replica set ...
  71. The number of replication change orders originating upstream from this member (i.e. remote) that have been sent to the partner ...
  72. The number of seconds between requests sent to a server identified as unavailable must be equal to or greater than the number ...
  73. The number of sessions that have been closed due to their idle time exceeding the AutoDisconnect parameter for the server. ...
  74. The number of sessions that have been closed due to unexpected error conditions or sessions that have reached the autodisconnect ...
  75. The number of sessions that have been forced to logoff. Can indicate how many sessions were forced to logoff due to logon ...
日本語
Japanese English
English (United States)