Windows Server 2003

  1. IPMGM could not schedule a task to be executed. This may have been caused by a memory allocation failure. The data is the ...
  2. IPRIP could not join the multicast group 224.0.0.9 on the local interface with IP address %1. The data is the error code. ...
  3. IPRIP could not register the service with the Service Control Manager. Please make certain the service is correctly installed. ...
  4. IPRIP was unable to create a socket. The network subsystem may have failed, or there may be insufficient resources to complete ...
  5. IPRIP was unable to do WSAEventSelect on a socket bound to the local interface with IP address %1. The data is the error ...
  6. IPRIP was unable to enumerate network events on a socket bound to the local interface with IP address %1. The data is the ...
  7. IPRIP was unable to initialize the Windows Sockets DLL. Please make certain the correct version of Windows Sockets is installed. ...
  8. IPRIP was unable to load the list of interfaces on the system: either there are insufficient resources, or no network interfaces ...
  9. IPRIP was unable to load the list of routes on the system: either there are insufficient resources, or IP routing is disabled. ...
  10. IPRIPv2 could not bind to IP address %1. Please make sure TCP/IP is installed and configured correctly. The data is the error ...
  11. IPRIPv2 could not bind to port 520 on the socket for the local interface with IP address %1. The data is the error code. ...
  12. IPRIPv2 could not enable broadcasting on the socket for the local interface with IP address %1. The data is the error code. ...
  13. IPRIPv2 could not join the multicast group 224.0.0.9 on the local interface with IP address %1. The data is the error code. ...
  14. IPRIPv2 could not schedule a task to be executed. This may have been caused by a memory allocation failure. The data is the ...
  15. IPRIPv2 detected an error on the local interface with IP address %1. The error occurred while the interface was receiving ...
  16. IPRIPv2 discarded a packet received on the interface with IP address %1 from a neighboring router with IP address %2, because ...
  17. IPRIPv2 discarded a response packet from a neighbor with IP address %1. IPRIPv2 is not configured to accept packets from ...
  18. IPRIPv2 discarded a response packet from a neighbor with IP address %1. The packet was not sent from the standard IP RIP ...
  19. IPRIPv2 discarded a version %1 packet received on the interface with IP address %2 from a neighbor with IP address %3. The ...
  20. IPRIPv2 has deleted its route to %1 with next-hop %2, since the route timed-out and no neighboring routers announced the ...
  21. IPRIPv2 has learnt of a new route. The route is to network %1 with next-hop %2, and the route was learnt from the neighbor ...
  22. IPRIPv2 has timed-out its route to %1 with next-hop %2, since no neighboring routers announced the route. The route will ...
  23. IPRIPv2 is ignoring a default route with next-hop %2 which was advertised by a neighbor with IP address %3, because the interface ...
  24. IPRIPv2 is ignoring a host route to %1 with next-hop %2 which was advertised by a neighbor with IP address %3, because the ...
  25. IPRIPv2 is ignoring a route on the local interface with IP address %1. The route is to the network %1 and it was received ...
  26. IPRIPv2 is ignoring a route to %1 with next-hop %2 which was advertised by a neighbor with IP address %3, because the interface ...
  27. IPRIPv2 is ignoring a route to %1 with next-hop %2 which was advertised by a neighbor with IP address %3, since the route ...
  28. IPRIPv2 is ignoring a route to %1 with next-hop %2 which was advertised by a neighbor with IP address %3. The route's network ...
  29. IPRIPv2 is ignoring a route to the broadcast network %1 with next-hop %2 which was advertised by a neighbor with IP address ...
  30. IPRIPv2 is ignoring a route to the loopback network %1 with next-hop %2 which was advertised by a neighbor with IP address ...
  31. IPRIPv2 received a packet which was smaller than the minimum size allowed for IPRIP packets. The packet has been discarded. ...
  32. IPRIPv2 received a packet with an invalid header. The packet has been discarded. It was received on the local interface with ...
  33. IPRIPv2 received a packet with an invalid version in its header. The packet has been discarded. It was received on the local ...
  34. IPRIPv2 received an error in a call to select(). This may indicate underlying network problems. The data is the error code. ...
  35. IPRIPv2 was unable to add a route to the Routing Table Manager. The route is to %1 with next-hop %2 and it was received from ...
  36. IPRIPv2 was unable to add a route to the Routing Table Manager. The route is to network %1 with next-hop %3. The data is ...
  37. IPRIPv2 was unable to initialize a table to hold information about configured network interfaces. The data is the error code. ...
  38. IPRIPv2 was unable to initialize a table to hold information about neighboring IPRIP routers. The data is the error code. ...
  39. IPRIPv2 was unable to receive an incoming message on the local interface with IP address %1. The data is the error code. ...
  40. IPRIPv2 was unable to request notification of events on the socket for the local interface with IP address %1. The data is ...
  41. IPRIPv2 was unable to send a packet from the interface with IP address %1 to the IP address %2. The data is the error code. ...
  42. IPSec driver is starting in Stateful mode. IPSec stateful filtering is being applied while this computer starts up. During ...
  43. IPSec inbound packet integrity check failed: Packet Source: %1 Inbound SA: %2 Number Of Packets: %3 Received packet from ...
  44. IPSec inbound packet replay check failed, inbound packet had too low a sequence number to ensure it was not a replay: Packet ...
  45. IPSec inbound packet replay check failed, inbound packet had too low a sequence number to ensure it was not a replay: Packet ...
  46. IPSec inbound packet replay check failed: Packet Source: %1 Inbound SA: %2 Number of Packets: %3 Received packet from over ...
  47. IPSec inbound packet replay check failed: Packet Source: %1 Inbound SA: %2 Number of Packets: %3 Received packet from over ...
  48. IPSec received inbound clear text packet that should have been secured: Packet Source: %1 Inbound SA: %2 Number of Packets: ...
  49. IPSec Services failed to get the complete list of network interfaces on the machine. This can be a potential security hazard ...
  50. IPSec Services failed to process some IPSec filters on a plug-and-play event for network interfaces. This is a security hazard ...
  51. IPSec Services has experienced a critical failure and has shut down with error code: %1. Stopped IPSec Services can be a ...
  52. IPsec will be used to enforce the local interface restrictions defined for this port. Since IPsec is incompatible with dynamically ...
  53. IPv6 Host (AAAA) Host address (AAAA) record for IPv6 hosts. Maps a DNS domain name to a single 128-bit IPv6 address. (RFC ...
  54. IPX is not installed or is disabled for Routing and Remote Access. You can install/enable IPX by viewing the properties of ...
  55. IRQ trigger level indicating whether the interrupt is triggered by the hardware signal going high (value=4) or low (value=3). ...
  56. IRQ trigger type indicating whether edge (value=4) or level triggered (value=3) interrupts occur. Also, \"Other\" (1) and ...
  57. is a 16-bit application. You do not have permissions to execute 16-bit applications. Check your permissions with your system ...
  58. is a global catalog (GC) server. The infrastructure operations master role should not be transferred to a GC server. Please ...
  59. is a name suffix exclusion and cannot be disabled. Use the Active Directory Domains Trusts snapin to enable the corresponding ...
  60. is a name suffix exclusion and cannot be disabled. Use the Active Directory Domains Trusts snapin to remove this exclusion. ...
  61. is a Windows NT 4.0 IAS server. Remote administration of Windows NT 4.0 IAS servers is not supported from 64-bit operating ...
  62. is already running %2. Two users cannot run this program at the same time. You can close the program %3 is running so that ...
  63. is an invalid IP address. An IP address must be specified in the form xxx.xxx.xxx.xxx, where xxx represents a decimal number ...
  64. is an invalid subnet mask. A subnet mask must be specified in the form xxx.xxx.xxx.xxx, where xxx represents a decimal number ...
  65. is contained within another folder in the Briefcase. This folder will not be updated. Update the parent folder to update ...
  66. is improperly configured.%rThe adapter cannot process the remote management features and be a member of a network team at ...
  67. is incompatible with Windows XP. You must obtain Windows XP-compatible software from %2, the manufacturer of this component.%0 ...
  68. is incompatible with Windows XP. You must obtain Windows XP-compatible software from the manufacturer of this component.%0 ...
  69. is not a valid IP (Internet Protocol) address. An IP address has four numbers in the range 0-255 separated by periods, such ...
  70. is not a valid name. The entry name must contain at least one character that is not a space and cannot begin with a period. ...
  71. is not a valid name. The entry name must contain at least one character that is not a space and cannot contain any of the ...
  72. is required by the following component(s): %2 Removing it will also remove these components. Do you want to remove %1 and ...
  73. is set up for auto-negotiation but the link partner is not configured for auto-negotiation. A duplex mismatch may occur. ...
  74. is the system drive. You cannot turn off System Restore on this drive without turning it off on all drives. To do this, click ...
  75. is the system drive. You cannot turn off System Restore on this drive without turning it off on all drives. To do this, click ...