-----Original Message-----
I removed the informational events and then commented below each of the
other events.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7009
Date: 9/11/2104
Time: 6:00:47 PM
User: N/A
Computer: ERIC-EBFCFEE4AF
Description:
Timeout (30000 milliseconds) waiting for the
Remote_Procedure_Call service to connect.
* I think this one is an effect of the other issues.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 9/11/2104
Time: 6:00:47 PM
User: N/A
Computer: ERIC-EBFCFEE4AF
Description:
The Remote_Procedure_Call service failed to start due to
the following error:
The service did not respond to the start or control
request in a timely fashion.
* This might be an effect of the other issues so let's resolve them first.
Event Type: Error
Event Source: ipnathlp
Event Category: None
Event ID: 30013
Date: 9/11/2104
Time: 6:00:51 PM
User: N/A
Computer: ERIC-EBFCFEE4AF
Description:
The DHCP allocator has disabled itself on IP address
66.214.45.206, since the IP address is outside the
192.168.0.0/255.255.255.0 scope from which addresses are
being allocated to DHCP clients. To enable the DHCP
allocator on this IP address, please change the scope to
include the IP address, or change the IP address to fall
within the scope.
* If you stop the DHCP server service this one shoulp go away. (assuming you
don't need it?) or possibly ICS
Event Type: Information
Event Source: NNTPSVC
Event Category: None
Event ID: 93
Date: 9/11/2104
Time: 6:00:58 PM
User: N/A
Computer: ERIC-EBFCFEE4AF
Description:
The Microsoft NNTP Service 5.00.0984 Version:
5.0.2195.6702 Virtual server 1 has been started.
* Curios that you're running this one and the next one
Event Type: Information
Event Source: NNTPSVC
Event Category: None
Event ID: 93
Date: 9/11/2104
Time: 6:00:58 PM
User: N/A
Computer: ERIC-EBFCFEE4AF
Description:
The Microsoft NNTP Service 5.00.0984 Version:
5.0.2195.6702 Virtual server 1 has been started.
Event Type: Information
Event Source: DhcpServer
Event Category: None
Event ID: 1044
Date: 9/11/2104
Time: 6:01:21 PM
User: N/A
Computer: ERIC-EBFCFEE4AF
Description:
The DHCP/BINL service on the local machine, belonging to
the Windows Administrative domain WORKGROUP, has
determined that it is authorized to start. It is servicing
clients now.
Data:
0000: 00 00 00 00 ....
* Generally you'll only want one DHCP sever on your network so you may want
to stop this one.
Event Type: Error
Event Source: Removable Storage Service
Event Category: None
Event ID: 17
Date: 9/11/2104
Time: 6:01:31 PM
User: N/A
Computer: ERIC-EBFCFEE4AF
Description:
RSM cannot manage library PhysicalDrive2. It encountered
an unspecified error. This can be caused by a number of
problems including, but not limited to, database
corruption, failure communicating with the library, or
insufficient system resources.
* The RSM database might be corrupted. These may help.
http://support.microsoft.com/default.aspx?scid=kb;EN- US;288856
us/default.asp?url=/windows2000/techinfo/reskit/en-
us/core/fncd_str_wmyb.asp
Event Type: Warning
Event Source: Dhcp
Event Category: None
Event ID: 1007
Date: 9/11/2104
Time: 6:01:39 PM
User: N/A
Computer: ERIC-EBFCFEE4AF
Description:
Your computer has automatically configured the IP address
for the Network Card with network address 00C09F337631.
The IP address being used is 169.254.181.209.
Data:
0000: 00 00 00 00 ....
* No DHCP server was found. If you have no DHCP server on your network then
manually assign an IP address to the connection.
Event Type: Information
Event Source: Application Popup
Event Category: None
Event ID: 26
Date: 9/11/2104
Time: 6:02:14 PM
User: N/A
Computer: ERIC-EBFCFEE4AF
Description:
Application popup: Service Control Manager : At least one
service or driver failed during system startup. Use Event
Viewer to examine the event log for details.
* An effect of the other issues.
--
Regards,
Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect
| Here is chronological list of events on start-up. As you
| can see, I have other issues. I figure one thing at a
| time. The Remote_Procedure_Call system seems to generate
| the error popup. Basic setup is a stand-alone server with
| one client PC. Server has static IP address. Server
| configuration is not complete.
|
| Event Type: Information
| Event Source: EventLog
| Event Category: None
| Event ID: 6009
| Date: 9/11/2104
| Time: 6:00:36 PM
| User: N/A
| Computer: ERIC-EBFCFEE4AF
| Description:
| Microsoft (R) Windows 2000 (R) 5.0 2195 Service Pack 4
| Uniprocessor Free.
|
| Event Type: Information
| Event Source: EventLog
| Event Category: None
| Event ID: 6005
| Date: 9/11/2104
| Time: 6:00:36 PM
| User: N/A
| Computer: ERIC-EBFCFEE4AF
| Description:
| The Event log service was started.
|
| Event Type: Error
| Event Source: Service Control Manager
| Event Category: None
| Event ID: 7009
| Date: 9/11/2104
| Time: 6:00:47 PM
| User: N/A
| Computer: ERIC-EBFCFEE4AF
| Description:
| Timeout (30000 milliseconds) waiting for the
| Remote_Procedure_Call service to connect.
|
| Event Type: Error
| Event Source: Service Control Manager
| Event Category: None
| Event ID: 7000
| Date: 9/11/2104
| Time: 6:00:47 PM
| User: N/A
| Computer: ERIC-EBFCFEE4AF
| Description:
| The Remote_Procedure_Call service failed to start due to
| the following error:
| The service did not respond to the start or control
| request in a timely fashion.
|
| Event Type: Error
| Event Source: ipnathlp
| Event Category: None
| Event ID: 30013
| Date: 9/11/2104
| Time: 6:00:51 PM
| User: N/A
| Computer: ERIC-EBFCFEE4AF
| Description:
| The DHCP allocator has disabled itself on IP address
| 66.214.45.206, since the IP address is outside the
| 192.168.0.0/255.255.255.0 scope from which addresses are
| being allocated to DHCP clients. To enable the DHCP
| allocator on this IP address, please change the scope to
| include the IP address, or change the IP address to fall
| within the scope.
|
| Event Type: Information
| Event Source: NNTPSVC
| Event Category: None
| Event ID: 93
| Date: 9/11/2104
| Time: 6:00:58 PM
| User: N/A
| Computer: ERIC-EBFCFEE4AF
| Description:
| The Microsoft NNTP Service 5.00.0984 Version:
| 5.0.2195.6702 Virtual server 1 has been started.
|
| Event Type: Information
| Event Source: NNTPSVC
| Event Category: None
| Event ID: 93
| Date: 9/11/2104
| Time: 6:00:58 PM
| User: N/A
| Computer: ERIC-EBFCFEE4AF
| Description:
| The Microsoft NNTP Service 5.00.0984 Version:
| 5.0.2195.6702 Virtual server 1 has been started.
|
| Event Type: Information
| Event Source: DhcpServer
| Event Category: None
| Event ID: 1044
| Date: 9/11/2104
| Time: 6:01:21 PM
| User: N/A
| Computer: ERIC-EBFCFEE4AF
| Description:
| The DHCP/BINL service on the local machine, belonging to
| the Windows Administrative domain WORKGROUP, has
| determined that it is authorized to start. It is servicing
| clients now.
| Data:
| 0000: 00 00 00 00 ....
|
| Event Type: Error
| Event Source: Removable Storage Service
| Event Category: None
| Event ID: 17
| Date: 9/11/2104
| Time: 6:01:31 PM
| User: N/A
| Computer: ERIC-EBFCFEE4AF
| Description:
| RSM cannot manage library PhysicalDrive2. It encountered
| an unspecified error. This can be caused by a number of
| problems including, but not limited to, database
| corruption, failure communicating with the library, or
| insufficient system resources.
|
| Event Type: Warning
| Event Source: Dhcp
| Event Category: None
| Event ID: 1007
| Date: 9/11/2104
| Time: 6:01:39 PM
| User: N/A
| Computer: ERIC-EBFCFEE4AF
| Description:
| Your computer has automatically configured the IP address
| for the Network Card with network address 00C09F337631.
| The IP address being used is 169.254.181.209.
| Data:
| 0000: 00 00 00 00 ....
|
| Event Type: Information
| Event Source: Application Popup
| Event Category: None
| Event ID: 26
| Date: 9/11/2104
| Time: 6:02:14 PM
| User: N/A
| Computer: ERIC-EBFCFEE4AF
| Description:
| Application popup: Service Control Manager : At least one
| service or driver failed during system startup. Use Event
| Viewer to examine the event log for details.
|
.