Event id 2506 windows 2008

The server could not establish a listening endpoint on the transport listed in the event. The status code returned from the underlying transport is available in the System event log. This status code may explain why this operation failed. To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

File Services. You must be logged in to post a comment. Determine whether the problem is resolved as follows:. If Windows does not shut down after you restart your computer, you know that the interfering service is not among those services that were turned on. Therefore, it must be among those services that were turned off. Now that you have eliminated some services as the cause of the problem, you can use a process of elimination to try to determine which service might be causing the interference.

Selectively , turn on services and restart the operating system to check whether the problem is resolved. Repeat this process until you isolate a service that could be causing the interference. This could be time - consuming and results may vary. If you cannot isolate any one service as the cause of the problem, then these services are likely not causing the slow shutdown.

Now try isolating Startup items to determine whether a Startup item is causing the interference. In this step, you are trying to identify Startup programs which might be impacting slow shutdown. Click Start, and then type msconfig in the Search box. Click the Startup tab, select the Hide all Microsoft Services check box, and then clear half of the check boxes in the Startup list.

Determine whether the problem is resolved. Tcp Port Sharing Service service which failed to start because of the following error: The service did not respond to the start or control request in a timely fashion. Tcp Port Sharing Service service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.

Tcp Port Sharing Service service to connect. Group Policy settings may not be applied until this event is resolved. If you want to change the value, change it to one that is the correct type and is within the acceptable range, or delete the value to use the default.

This value might have been set up by an older program that did not use the correct boundaries. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

Did you check this? I have looked through and have not found anything that I have any idea how to even begin to fix. Everything seems to be failing because of timeouts and that correlates to the server being really sluggish. I do know that the DHCP errors are because I tried to uninstall the role but it did not uninstall cleanly.

I'm starting to think that there may be some sort of hardware reason for the slowness of the server but I'm not sure where to go from here. I think that the CPU was overheating a while back but I can't think of how any damage from overheating could cause general slowness. I would expect it to not even boot if the CPU was partially fried.

Office Office Exchange Server. Not an IT pro? Windows Server TechCenter. Sign in. United States English. Ask a question.