If a service fails to start, is that not a failure?


  • Occasionally the "Net.Tcp Port Sharing Service" does not start, because of a time-out. The failure to start is recorded in the System Event log with Event Id 7009. Based on our configuration of this service on the Recovery tab, I would expect that the system would attempt to restart this service every two minutes, but that doesn't happen. Hence I'm wondering if a service must start successfully in order to fail in such a way that it can trigger the failure logic (IE: "First failure", "Second failure", "Subsequent failures", etc.)

    If this is the case, then what are other people doing to handle situations like this?

    On a related note, Server 2008 introduces a new service start-up mode "Automatic (Delayed Start)". Given that our occasional time-out may be happening because the CPU is busy starting many things all at once, we're considering trying this option. On the plus side, there's no point in starting this service until the risk of a time-out due to CPU activity is removed. On the minus side, when the service starts it will apparently have a very low priority, which may actually increase the probability of a time-out. This is all theory. Does anyone have any recommendations based on practical experience.

    Last thing. We are also considering simply increasing the WCF time-out period.
    Tuesday, December 15, 2009 5:21 PM


  • Hello Scott,


    According to your description, I understand the Net.Tcp Port Sharing Service does not start on your server. Please first check the following KB addresses your issue.


    970766  Net.Tcp Port Sharing Service is not starting, fails with "Error 1067";EN-US;970766


    Generally speaking, The Service Control Manager will generate the Event ID:7009 if a service does not respond within the defined timeout period (the default timeout period is 30000 milliseconds).


    To resolve this issue, you can also increase the default service timeout period. You can refer to the following link's steps:



    If the Net.Tcp Port Sharing Service still failed to start, you may run Process Monitor to monitor the process while start the service.


    For you convenience, I included the steps below:

    a)    Download Process Monitor. To do this, visit the following Microsoft Web site:

    b)    Click Download Process Monitor and then click Save.

    c)     Save the file in a folder of your choice.

    d)    Right-click the file that you downloaded, and then click Extract to.

    e)    Specify where you want to extract the file, and then click Extract.

    f)     Double Click the Procmon.exe to start Process Monitor.

    g)    In the File menu, tick off “Capture Events”.

    h)    Click “Clear” in the tool bar.

    i)      Select the events type “Registry Activities”, “File System Activities”,  “Network Activities” “Process and Thread Activities”,  “Profiling Events”  in the tool bar

    j)     Tick on “Capture Events” in the File Menu.

    k)    start  the "Net.Tcp Port Sharing Service" service.

    l)      On the File menu, click Save to save the Process Monitor log file.

    m)   Under Events to save, click to select the All events check box.

    n)    Under Format, click to select the Native Process Monitor Format (PML) check box.

    o)    In the Path box, specify a location on the local hard disk where you want to save the file.


    For more information, you can refer to:


    Net.TCP Port Sharing

    How to: Enable the Net.TCP Port Sharing Service


    Hope it helps.



    Wilson Jia

    This posting is provided "AS IS" with no warranties, and confers no rights.
    • Marked as answer by Wilson Jia Monday, December 21, 2009 7:14 AM
    Wednesday, December 16, 2009 10:07 AM