Errors in the system log after start-up

[Anthony]

Hello,

I lots of errors like these in the system log after
starting up:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7022
Date: 09/07/2003
Time: 02:59:29
User: N/A
Computer: ANDREW
Description:
The DHCP Client service hung on starting.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 09/07/2003
Time: 02:59:29
User: N/A
Computer: ANDREW
Description:
The Task Scheduler service failed to start due to the
following error:
The pipe state is invalid.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp. Event Type:
Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 09/07/2003
Time: 02:59:29
User: N/A
Computer: ANDREW
Description:
The Windows Audio service failed to start due to the
following error:
The pipe state is invalid.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 09/07/2003
Time: 02:59:29
User: N/A
Computer: ANDREW
Description:
The Workstation service failed to start due to the
following error:
The pipe state is invalid.

I would be very grateful if anyone could tell me how to
resolve these. Also, might these errors cause me a problem
in connecting to the internet (I am having a problem with
this also!)?

Thanks,

Anthony

 

[Michael Solomon \(MS-MVP-Windows Shell/User\)]

Not all errors are things about which you need to worry, especially if you
are having no problems as a result.

In this case, the error can be caused by the system attempting to log on to
a network, which also can be your ISP but because of where it is in the boot
process, the necessary hardware is not yet loaded or, you might have a
network card installed by not connected to a network in which case, you'd
always see this error as it simply indicates what you would already know,
there is no network.

I hope that was clear.