Event ID - 1024

Event Id1024
SourceWDSServer
DescriptionAn error occurred while trying to initialize the RPC server on port %1. Error Information: %2
Event Information According to Microsoft :

Cause :

This event is logged when an error occurred while trying to initialize the RPC server on port.

Resolution :

Contact the vendor or analyze network traffic

If you also received WDSServer event 512, this means that a noncritical provider failed. Because only custom providers are marked as noncritical, this one must be a custom provider. You should contact the provider's vendor for troubleshooting guidelines.

If you did not receive WDSServer event 512, this means that a computer may be sending out malicious code. To resolve this issue, obtain a network trace that shows the failed boot attempt. It is a best practice to obtain this trace from the client and server simultaneously to accurately assess whether the failure is occurring at the sending server or the receiving client. You do this by using the following steps:
  1. Place a client and a third computer (laptop or desktop) on a hub.
  2. Start network traces from the server and the third computer.
  3. Start the client by doing a network boot (a PXE boot).
Analyze the network traffic to determine which computer the invalid packets are coming from. Then determine which process is sending the packets, and stop the offending process. If you are using Microsoft Network Monitor to obtain the traces, ensure that the buffer size is at least 20 MB. If you configure a buffer size too small for the capture, the data packets will not appear in the capture output.

Verify :

You can verify network connectivity either from a client computer or from the server by using one of the following two procedures.

To verify that the server has connectivity (from a client computer):
  1. Open the Command Prompt window. (Click Start , point to All Programs , click Accessories , and then click Command Prompt .)
  2. At the command prompt, type ping <IP address|fully qualified domain name> to contact the Windows Deployment Services server.
  3. Try to boot the client computer by doing a Pre-Boot Execution Environment (PXE) boot. Make sure that the boot menu and image selection pages are displayed.
To verify that the server has connectivity (from the Windows Deployment Services server):
  1. Open the Command Prompt window. (Click Start , point to All Programs , click Accessories , and then click Command Promp .)
  2. At the command prompt, type ping <IP address|fully qualified domain name> to contact a remote computer.
Reference LinksEvent ID 1024 from Source WDSServer

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.
 Refresh