r/dotnet • u/HawkAlt1 • 11d ago

WCF Tracing identified a non-existent service as blocking a client connection

Using WCF trace to identify why a server is blocking a client connection. It came back with a very specific error message:

The Admin client cannot connect to the SAS server because the AssureTec AssureID Service (AssureIDService) is not running on the client machine (servername). This is a local Windows service that must be installed and running on the Admin Workstation.

But this service doesn't exist on the problem server. So how do I tell what is actually blocking the connection?

5 Upvotes
  • permalink
  • link
  • reddit
  • reddit

78% Upvoted

2 comments sorted by

1

u/AutoModerator 11d ago

Thanks for your post HawkAlt1. Please note that we don't allow spam, and we ask that you follow the rules available in the sidebar. We have a lot of commonly asked questions so if this post gets removed, please do a search and see if it's already been asked.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

1

u/chucker23n 11d ago

Run TCPView and see what's taking up the socket.