When I clcik on Computer Management, System Tools, Event Viewer, Sysytem
three error mressages are repeated all the way down the page..

7001- The telephone service failed to start
7009 - Timeout waiting for the telephone dervic
7000 - Remote access service failed - depends on telephone service

I am not hooked-up to a telephone. DSL comes-in wireless router, and I am
connected to it by 802.11g.

What should I do about the error message?

--
KC

KCav <KCav@discussions.microsoft.com> wrote on Tue, 27 Mar 2007:

>When I clcik on Computer Management, System Tools, Event Viewer, Sysytem
>three error mressages are repeated all the way down the page..
>
>7001- The telephone service failed to start
>7009 - Timeout waiting for the telephone dervic
>7000 - Remote access service failed - depends on telephone service
>
>I am not hooked-up to a telephone. DSL comes-in wireless router, and I am
>connected to it by 802.11g.

Hi KC

I think you must mean the telephony service :-) Go to Start > Run, type
"services.msc" (without quotes) and check that it's not disabled. The
recommended setting for XP is Manual.

--
Nightowl

Hi Nightowl,

You are right it is Telephony, however it is set to manual. The error
messages seem to be triggered because the services expect Telephony to be
running. I wonder why the expect it to be running?

--
KC


"Nightowl" wrote:

> KCav <KCav@discussions.microsoft.com> wrote on Tue, 27 Mar 2007:
>
> >When I clcik on Computer Management, System Tools, Event Viewer, Sysytem
> >three error mressages are repeated all the way down the page..
> >
> >7001- The telephone service failed to start
> >7009 - Timeout waiting for the telephone dervic
> >7000 - Remote access service failed - depends on telephone service
> >
> >I am not hooked-up to a telephone. DSL comes-in wireless router, and I am
> >connected to it by 802.11g.
>
> Hi KC
>
> I think you must mean the telephony service :-) Go to Start > Run, type
> "services.msc" (without quotes) and check that it's not disabled. The
> recommended setting for XP is Manual.
>
> --
> Nightowl
>

Well, some of the other network services depend on it to be there --
without it they won't run. I wonder why yours isn't starting? Mine is on
Manual and looking at Event Viewer, it's always the first service that
starts on my computer after a reboot.

In your Services list do you have Plug and Play (not Universal Plug and
Play) and Remote Procedure Call (RPC) enabled and set to Automatic?

If both of those are correct, you might try, as an experiment, setting
Telephony to Automatic and rebooting to see whether it runs then. But
I'd think if the other two above are enabled and running and Telephony
isn't starting, it means something is broken. Hopefully someone who
knows a bit more may be along soon to help :-)


KCav <KCav@discussions.microsoft.com> wrote on Wed, 28 Mar 2007:

>You are right it is Telephony, however it is set to manual. The error
>messages seem to be triggered because the services expect Telephony to be
>running. I wonder why the expect it to be running?

--
Nightowl

Hi Nightowl,

I went to Services found Telephony and tried to start it. Instead of
starting I got error 1053 Service did not respond.
C:\Windows\system32\svchost.exe-k tapsiv.

What should I do?
--
KC


"Nightowl" wrote:

> Well, some of the other network services depend on it to be there --
> without it they won't run. I wonder why yours isn't starting? Mine is on
> Manual and looking at Event Viewer, it's always the first service that
> starts on my computer after a reboot.
>
> In your Services list do you have Plug and Play (not Universal Plug and
> Play) and Remote Procedure Call (RPC) enabled and set to Automatic?
>
> If both of those are correct, you might try, as an experiment, setting
> Telephony to Automatic and rebooting to see whether it runs then. But
> I'd think if the other two above are enabled and running and Telephony
> isn't starting, it means something is broken. Hopefully someone who
> knows a bit more may be along soon to help :-)
>
>
> KCav <KCav@discussions.microsoft.com> wrote on Wed, 28 Mar 2007:
>
> >You are right it is Telephony, however it is set to manual. The error
> >messages seem to be triggered because the services expect Telephony to be
> >running. I wonder why the expect it to be running?
>
> --
> Nightowl
>

Hi KCav

That message is basically a timeout, saying the service didn't start
within the expected time.

Did you check the other 2 services I mentioned, Plug and Play and Remote
Procedure Call, are both running and set to Automatic?

Also, the original error messages you saw in Event Viewer | System
should give more detail on what's going wrong than what you originally
posted. You said:
>7001- The telephone service failed to start
>7009 - Timeout waiting for the telephone dervic
>7000 - Remote access service failed - depends on telephone service

but Event ID 7001 should say: "The <service name 1> service depends on
the <service name 2> service which failed to start because of the
following error: <error message>" and 7000 should say: "The <service or
device name> service failed to start due to the following error: <error
description>". It would help to see this extra information. Can you go
to one of the 7000 errors in Event Viewer, double-click on it to bring
up the Property box and then click on the icon at the top right that
looks like two little pages? That will copy the error message to your
clipboard and you can paste it into your reply. Then do the same with
one of the 7001 errors (Don't worry about 7009).

Also, do you by any chance have .NET Framework 1.1 installed?

Post back with the answers if you can :-). Talk to you soon!

--
Nightowl


KCav <KCav@discussions.microsoft.com> wrote on Wed, 28 Mar 2007:

>I went to Services found Telephony and tried to start it. Instead of
>starting I got error 1053 Service did not respond.
>C:\Windows\system32\svchost.exe-k tapsiv.

>
>"Nightowl" wrote:
>
>> Well, some of the other network services depend on it to be there --
>> without it they won't run. I wonder why yours isn't starting? Mine is on
>> Manual and looking at Event Viewer, it's always the first service that
>> starts on my computer after a reboot.
>>
>> In your Services list do you have Plug and Play (not Universal Plug and
>> Play) and Remote Procedure Call (RPC) enabled and set to Automatic?
>>
>> If both of those are correct, you might try, as an experiment, setting
>> Telephony to Automatic and rebooting to see whether it runs then. But
>> I'd think if the other two above are enabled and running and Telephony
>> isn't starting, it means something is broken. Hopefully someone who
>> knows a bit more may be along soon to help :-)
>>
>>
>> KCav <KCav@discussions.microsoft.com> wrote on Wed, 28 Mar 2007:
>>
>> >You are right it is Telephony, however it is set to manual. The error
>> >messages seem to be triggered because the services expect Telephony to be
>> >running. I wonder why the expect it to be running?

Neither Remote Procedure Call nor Plug & Play are running-- both depend on
Telephony and Telephony will not start.

Error EventID 7001
The Remote Access Conection Manager service depends on the Telephony service
which failed to start because of the following error: The service did not
respond to the start control in a timely fashion.

Error EventID 7000
The Telephony service faile because of the following error: The service did
not respond to the start control in a timely fashion.

Error EventID 7009
Timeout (30000 milliseconds ) waiting for Telephony service to connect .

Where does .Net Framework 1.1 hangout? I looked in Add Programs/Windows
Components.

Having another problem ... Automatic Updates says: The following updates
were not installed: Security Update for Excel Viewer 2003 (KB925525)
Security Update for Office 2003 and Update for Office 2003.

- KC


"Nightowl" wrote:

> Hi KCav
>
> That message is basically a timeout, saying the service didn't start
> within the expected time.
>
> Did you check the other 2 services I mentioned, Plug and Play and Remote
> Procedure Call, are both running and set to Automatic?
>
> Also, the original error messages you saw in Event Viewer | System
> should give more detail on what's going wrong than what you originally
> posted. You said:
> >7001- The telephone service failed to start
> >7009 - Timeout waiting for the telephone dervic
> >7000 - Remote access service failed - depends on telephone service
>
> but Event ID 7001 should say: "The <service name 1> service depends on
> the <service name 2> service which failed to start because of the
> following error: <error message>" and 7000 should say: "The <service or
> device name> service failed to start due to the following error: <error
> description>". It would help to see this extra information. Can you go
> to one of the 7000 errors in Event Viewer, double-click on it to bring
> up the Property box and then click on the icon at the top right that
> looks like two little pages? That will copy the error message to your
> clipboard and you can paste it into your reply. Then do the same with
> one of the 7001 errors (Don't worry about 7009).
>
> Also, do you by any chance have .NET Framework 1.1 installed?
>
> Post back with the answers if you can :-). Talk to you soon!
>
> --
> Nightowl
>
>
> KCav <KCav@discussions.microsoft.com> wrote on Wed, 28 Mar 2007:
>
> >I went to Services found Telephony and tried to start it. Instead of
> >starting I got error 1053 Service did not respond.
> >C:\Windows\system32\svchost.exe-k tapsiv.
>
> >
> >"Nightowl" wrote:
> >
> >> Well, some of the other network services depend on it to be there --
> >> without it they won't run. I wonder why yours isn't starting? Mine is on
> >> Manual and looking at Event Viewer, it's always the first service that
> >> starts on my computer after a reboot.
> >>
> >> In your Services list do you have Plug and Play (not Universal Plug and
> >> Play) and Remote Procedure Call (RPC) enabled and set to Automatic?
> >>
> >> If both of those are correct, you might try, as an experiment, setting
> >> Telephony to Automatic and rebooting to see whether it runs then. But
> >> I'd think if the other two above are enabled and running and Telephony
> >> isn't starting, it means something is broken. Hopefully someone who
> >> knows a bit more may be along soon to help :-)
> >>
> >>
> >> KCav <KCav@discussions.microsoft.com> wrote on Wed, 28 Mar 2007:
> >>
> >> >You are right it is Telephony, however it is set to manual. The error
> >> >messages seem to be triggered because the services expect Telephony to be
> >> >running. I wonder why the expect it to be running?
>
>

Control Manager displays EventID 7035 - The Remote Access Connection Manager
was successfully sent a start control.

If Remote Access Control Manager is dependent on Telephony, and Telephony
has not started how could it recieved a start control? Who sent it?
--
KC


"KCav" wrote:

> When I clcik on Computer Management, System Tools, Event Viewer, Sysytem
> three error mressages are repeated all the way down the page..
>
> 7001- The telephone service failed to start
> 7009 - Timeout waiting for the telephone dervic
> 7000 - Remote access service failed - depends on telephone service
>
> I am not hooked-up to a telephone. DSL comes-in wireless router, and I am
> connected to it by 802.11g.
>
> What should I do about the error message?
>
> --
> KC

KCav <KCav@discussions.microsoft.com> wrote on Thu, 29 Mar 2007:

>Neither Remote Procedure Call nor Plug & Play are running-- both depend on
>Telephony and Telephony will not start.

No, KCav, you have that the wrong way round. *Telephony* depends on RPC
and Plug and Play, which should both be set to Automatic. If they're not
running, then that's probably why it's not starting.

>Error EventID 7001
>The Remote Access Conection Manager service depends on the Telephony service
>which failed to start because of the following error: The service did not
>respond to the start control in a timely fashion.
>
>Error EventID 7000
>The Telephony service faile because of the following error: The service did
>not respond to the start control in a timely fashion.
>
>Error EventID 7009
>Timeout (30000 milliseconds ) waiting for Telephony service to connect .

These are all caused by the same problem -- Telephony not starting. Try
setting RPC and Plug and Play to Automatic and rebooting and see if
Telephony will then run.
>
>
>"Nightowl" wrote:
>>
>> That message is basically a timeout, saying the service didn't start
>> within the expected time.
>>
>> Did you check the other 2 services I mentioned, Plug and Play and Remote
>> Procedure Call, are both running and set to Automatic?
>>
>> Also, the original error messages you saw in Event Viewer | System
>> should give more detail on what's going wrong than what you originally
>> posted. You said:
>> >7001- The telephone service failed to start
>> >7009 - Timeout waiting for the telephone dervic
>> >7000 - Remote access service failed - depends on telephone service
>>
>> but Event ID 7001 should say: "The <service name 1> service depends on
>> the <service name 2> service which failed to start because of the
>> following error: <error message>" and 7000 should say: "The <service or
>> device name> service failed to start due to the following error: <error
>> description>". It would help to see this extra information. Can you go
>> to one of the 7000 errors in Event Viewer, double-click on it to bring
>> up the Property box and then click on the icon at the top right that
>> looks like two little pages? That will copy the error message to your
>> clipboard and you can paste it into your reply. Then do the same with
>> one of the 7001 errors (Don't worry about 7009).
>>
>> Also, do you by any chance have .NET Framework 1.1 installed?
>>
>> Post back with the answers if you can :-). Talk to you soon!
>>
>> --
>> Nightowl
>>
>>
>> KCav <KCav@discussions.microsoft.com> wrote on Wed, 28 Mar 2007:
>>
>> >I went to Services found Telephony and tried to start it. Instead of
>> >starting I got error 1053 Service did not respond.
>> >C:\Windows\system32\svchost.exe-k tapsiv.
>>
>> >
>> >"Nightowl" wrote:
>> >
>> >> Well, some of the other network services depend on it to be there --
>> >> without it they won't run. I wonder why yours isn't starting? Mine is on
>> >> Manual and looking at Event Viewer, it's always the first service that
>> >> starts on my computer after a reboot.
>> >>
>> >> In your Services list do you have Plug and Play (not Universal Plug and
>> >> Play) and Remote Procedure Call (RPC) enabled and set to Automatic?
>> >>
>> >> If both of those are correct, you might try, as an experiment, setting
>> >> Telephony to Automatic and rebooting to see whether it runs then. But
>> >> I'd think if the other two above are enabled and running and Telephony
>> >> isn't starting, it means something is broken. Hopefully someone who
>> >> knows a bit more may be along soon to help :-)
>> >>
>> >>
>> >> KCav <KCav@discussions.microsoft.com> wrote on Wed, 28 Mar 2007:
>> >>
>> >> >You are right it is Telephony, however it is set to manual. The error
>> >> >messages seem to be triggered because the services expect Telephony to be
>> >> >running. I wonder why the expect it to be running?
>>
>>

--
Nightowl