UI Translation

Windows Server 2003

  1. WINS could not get information about the DATAFILES key. Check to see if the permissions on the key are set properly, system ...
  2. WINS could not get information about the Pull key. Check to see if the permissions on the key are set properly, system resources ...
  3. WINS could not get information about the Push key. Check to see if the permissions on the key are set properly, system resources ...
  4. WINS could not get information about the SPEC_GRP_MASKS key. Check to see if the permissions on the key are set properly, ...
  5. WINS could not initialize properly with the security subsystem. At initialization, WINS creates a security object and attaches ...
  6. WINS could not initialize the administrator interface because of a problem with the Remote Procedure Call (RPC) service. ...
  7. WINS could not look up the association block for a NetBIOS over TCP/IP (NetBT) association. Check to see if the message read ...
  8. WINS could not open a Pull subkey. Check to see if the permissions on the key are set properly, system resources are low, ...
  9. WINS could not open a Push subkey. Check to see if the permissions on the key are set properly, system resources are low, ...
  10. WINS could not open the log file. Check the log path specified in the registry under WINS\Parameters\LogFilePath and restart ...
  11. WINS could not properly set up the WINS database. Look at the application log for errors from the Exchange component, ESENT. ...
  12. WINS could not read the ConsistencyCheck value (type DWORD) from the Parameters\ConsistencyCheck subkey in the registry. ...
  13. WINS could not read the MaxRecsAtATime value (type DWORD) in the Wins\Parameters\ConsistencyCheck subkey of the registry. ...
  14. WINS could not read the UseRplPnrs value of the Wins\Parameters\ConsistencyCheck key. If this value is set to a non-zero ...
  15. WINS could not start because of a database error. WINS restored the old database from the backup directory and will come ...
  16. WINS could not start because the existent database must be converted to the Windows 2000 format. If this is the first invocation ...
  17. WINS could not start because the existing database needs to be converted to the Windows 2000 format. If this is the first ...
  18. WINS could not start due to a missing or corrupt database. Restore the database using WINS Manager (or winscl.exe found in ...
  19. WINS could not update the Owner ID-to-Address mapping table in the database. This means the in-memory table that maps to ...
  20. WINS created a socket and called the 'bind' WinSock API to bind a handle to it. On calling 'getsockname' to determine the ...
  21. WINS did not send a notification message to the WINS server whose address is given in the data section. There were a number ...
  22. WINS encountered a database error. This may or may not be a serious error. WINS will try to recover from it. You can check ...
  23. WINS encountered a PnP failure that caused it to terminate. The error code is contained in the second word of the data section. ...
  24. WINS encountered an error while deleting one or more records of a WINS. The WINS address is in the second DWORD in data section. ...
  25. WINS encountered an error while processing a push trigger or update notification. The error code is given in the data section. ...
  26. WINS found a name in the WINS database with a length of more than 255 characters. The name was truncated to 17 characters. ...
  27. WINS found some database corruption. The record named, %1, is corrupt. It could be that recovery from the last crash did ...
  28. WINS has deleted records of a partner. The internal ID of the partner whose records were deleted, the minimum version number ...
  29. WINS has encountered an error that caused it to shut down.The exception code is the second DWORD of the data section. Check ...
  30. WINS has exceeded the wait time for all threads to terminate. The number of threads still active is given in the second DWORD ...
  31. WINS has found some database corruption. It will try to recover. This recovery process can take a long time. Do not kill ...
  32. WINS has received a PnP notification that the IP address of the server has changed. The old IP address and the new IP address ...
  33. WINS is scavenging a chunk of N records in the version number range from X to Y. N, X and Y (low word, high word for version ...
  34. WINS is scavenging the locally owned records from the database. The version number range that is scavenged is given in the ...
  35. WINS is trying to update the version number of a database record that it does not own. This is a serious error if the WINS ...
  36. WINS just did a consistency check on the records owned by the WINS with the address, %1. The number of records inserted, ...
  37. WINS performed a consistency check on the records. The number of records pulled, The address of the WINS whose records were ...
  38. WINS Pull thread encountered an error during the process of sending a push notification to another WINS. The error code is ...
  39. WINS pulled records from a WINS while doing %1. The partner's address and the owner's address whose records were pulled are ...
  40. WINS received a release for the non-owned name, %1. This name is owned by the WINS whose owner ID is given in the data section. ...
  41. WINS received a replica whose state is incorrect. For example, the state may be RELEASED or the replica might be an Internet ...
  42. WINS received an error while registering replicas. It will not register any additional replicas of this WINS at this time ...
  43. WINS received an error while trying to register a group's replica with name, %1. The replica is owned by the WINS with the ...
  44. WINS received an error while trying to register a unique replica with name %1. The replica is owned by WINS with address ...
  45. WINS Reverse Lookup Received/sec is the average number of WINS reverse lookup requests received by the server in each second. ...
  46. WINS sent a name query or a name release with a certain transaction ID. It received a response to the request that differed ...
  47. WINS was forced to scavenge replica tombstones of a WINS. The person with administrative rights on the computer forced the ...
  48. WINS will not start because the existing WINS database needs to be converted to the Windows 2000 format. WINS has initiated ...
  49. WINS's Replicator could not find any records in the WINS database. This means there are no active or tombstone records in ...
  50. Winsock Catalog Provider Entry - Entry Type: %1!s! Description: %2!s! Provider ID: %3!s! Provider Path: %4!s! Catalog Entry ...
  51. Wireless Network Policy Administration. Manage the Zero Configuration settings and IEEE 802.1x Security Settings for IEEE ...
  52. WiseDialogFontDefault]By default, Setup installs the ProductName in the folder listed below. To accept the default folder, ...
  53. WiseDialogFontDefault]Change which application features are installed. Displays the Select Features dialog, which lets you ...
  54. WiseDialogFontDefault]Click Cancel to quit Setup and close any programs you have running. Click Next to continue with the ...
  55. WiseDialogFontDefault]Click Cancel to quit the setup program, then close any programs you have running. Click Next to continue ...
  56. WiseDialogFontDefault]Installation is not complete. If you quit the setup program now, the application will not be installed. ...
  57. WiseDialogFontDefault]It is strongly recommended that you exit all Windows programs before running this Setup Program. Click ...
  58. WiseDialogFontDefault]Out of disk space. The highlighted volumes do not have enough disk space available for the selected ...
  59. WiseDialogFontDefault]Reinstall missing or corrupt files, registry keys, and shortcuts. Preferences stored in the registry ...
  60. WiseDialogFontDefault]Setup failed to locate a qualifying product on your hard drive(s). Please select the drive that contains ...
  61. WiseDialogFontDefault]Setup has failed to locate a qualifying product. This installation requires a valid qualifying product ...
  62. WiseDialogFontDefault]Setup is not complete. If you quit the setup program now, the program will not be installed. You may ...
  63. WiseDialogFontDefault]The current selections require the following amount of disk space on the different volumes. The highlighted ...
  64. WiseDialogFontDefault]The most common application features will be installed. This option is recommended for most users. ...
  65. WiseDialogFontDefault]The settings for this application can be installed for the current user or for all users that share ...
  66. WiseDialogFontDefault]The settings for this application can be installed for the current user or for all users that share ...
  67. WiseDialogFontDefault]The Wise Installation Wizard will install the files for ProductName in the following folder. To install ...
  68. WiseDialogFontDefault]This ADMT Password Migration DLL installation requires a valid password encryption key for this source ...
  69. WiseDialogFontDefault]This will remove ProductName from your machine. Are you sure you want to continue? Click the Next button ...
  70. WiseDialogFontDefault]This will remove ProductName from your machine. Are you sure you want to continue? Press the Next button ...
  71. WiseDialogFontDefault]This wizard helps you install the ProductName]. By using the ProductName], you can easily migrate your ...
  72. WiseDialogFontDefault]Unauthorized reproduction or distribution of this program, or any portion of it, may result in severe ...
  73. WiseDialogFontDefault]Use this option to choose which application features you want installed and where they will be installed. ...
  74. WiseDialogFontDefault]WARNING: This program is protected by copyright law and international treaties. Unauthorized reproduction ...
  75. WiseDialogFontDefault]You can choose not to install ProductName by clicking Cancel to exit the Wise Installation Wizard. ...
日本語
Japanese English
English (United States)