Share this article

Improve this guide

What is Event Id 4104 & How to Quickly Fix It

Refer to this guide for the possible fixes

4 min. read

Updated onOctober 4, 2023

updated onOctober 4, 2023

Share this article

Improve this guide

Read our disclosure page to find out how can you help Windows Report sustain the editorial teamRead more

Key notes

The Event id 4104 is typically represented by the symbolic name TLS_E_RPC_LISTEN and addresses the communication issues because the remote procedure call (RPC) port is not listening.

In this troubleshooting guide, we have listed the different methods to fix the communication issues with the terminal services licensing server, which ultimately resolves the event id 4104.

What does event id 4104 mean?

What does event id 4104 mean?

The event id 4104 signifies the issue when the remote procedure call (RPC) port is not listening. The event id directly points to the communication error between the RPC client and the terminal services license server connected via a network.

The Terminal Services license server uses the Microsoft Windows Terminal Services Licensing to install, issue, and track the availability of Terminal Services client access licenses (TS CALs).

The event id 4104 is logged in the event viewer for several underlying reasons. Some of them are:

Now that you know the causes of the event id, below are the solutions that can fix the event id 4104.

What can I do to fix the event id 4104?

What can I do to fix the event id 4104?

1. Start the Terminal Services Licensing service

Starting the Terminal Services Licensing service helps verify that the Terminal Services license server is currently available.

Change the Firewall settings

There have been instances when the Firewall blocks the traffic to the RPC port and results in the RPC server having unavailable problems or not listening issues.

Hence, reconfiguring the Windows Firewall such that it unblocks the network connections for RPC.

That’s pretty much it! We hope you now have a thorough idea of the event id 4104 and what steps you should take when the event is logged in.

Before you leave, you should go through the comprehensive guide about theevent viewer and how can it help you identify the problems.

And lastly, find out what to do when Check Disk readsFailed to transfer loggedmessages.

If you need further assistance, please contact us in the comments below.

More about the topics:event log viewers,Event Viewer

Taiba Hasan

A postgraduate in Computer Applications, she is an avid technical writer who loves to craft content revolving around Windows, Android, and emerging technologies like SaaS. With How-To and troubleshooting guides, she aims to provide the best solutions for the problem and make technology less complicated for novice users.

Besides writing, she also loves to cook delicacies and spent time in her garden. In her free time, you will find her binge-watching web series or gazing the night sky.

User forum

0 messages

Sort by:LatestOldestMost Votes

Comment*

Name*

Email*

Commenting as.Not you?

Save information for future comments

Comment

Δ

Taiba Hasan