Event ID - 1004

Event Id1004
SourceMicrosoft-Windows-TerminalServices-SessionBroker
DescriptionThe Terminal Services Session Broker service failed to start due to a problem registering an RPC endpoint. The error code was %1.
Event InformationAccording to Microsoft :
Cause :
This event is logged when the Terminal Services Session Broker service failed to start due to a problem registering an RPC endpoint.
Resolution :
Start the Terminal Services Session Broker service
To resolve this issue, try to start the Terminal Services Session Broker service. If the problem persists, restart the TS Session Broker server. After the server has restarted, confirm that the Terminal Services Session Broker service has started.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To start the service:
  1. On the TS Session Broker server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the Services pane, right-click Terminal Services Session Broker, and then click Properties.
  4. On the General tab, ensure that Startup type is set to Automatic. If it is not, click Automatic, and then click Apply.
  5. Under Service status, click Start.
  6. Click OK to close the Terminal Services Session Broker dialog box.
  7. Confirm that the Status column for the Terminal Services Session Broker service displays Started.
Verify :To verify that the TS Session Broker server is available, ensure that the Terminal Services Session Broker service is running.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To check the Terminal Services Session Broker service:
  1. On the TS Session Broker server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the Services pane, locate Terminal Services Session Broker.
  4. Confirm that the Status column for the Terminal Services Session Broker service displays Started.
Reference LinksEvent ID 1004 from Source Microsoft-Windows-TerminalServices-SessionBroker

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.