Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
|Source: RPC Proxy|
The following ValidPorts registry key could not be parsed. <computer name>: 100'5000. The RPC Proxy cannot load. The ValidPorts registry key might have been configured incorrectly. User Action Verify that the ValidPorts registry value is set correctly. If the value is not correct, edit the registry key to reflect the correct value.
|English: Request a translation of the event description in plain English.|
As per Microsoft: "If the ValidPorts registry entry is configured incorrectly, the Rpcproxy.dll file will not load when a client tries to access the RPC proxy server. In this scenario, this event is logged to indicate that the Rpcproxy.dll file did not load successfully. This issue only occurs if the Data value for the ValidPorts registry entry is incorrectly formatted. For example, this issue occurs if the value contains incorrect characters or punctuation. This event is not logged in a scenario where you have configured incorrect server names. Additionally, this event is only logged the first time that you connect to the RPC HTTP server after you restart the World Wide Web Publishing service". See ME827330 for more information.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated