Hi everybody, My network connections don't work anymore on my W2K Advanced Server. They're gone in the network folder. The "Remote Access Connection Manager" service can't start anymore. I get this message in the event log: "The Remote Access Connection Manager service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion" and "The description for Event ID ( 2001 ) in Source ( rasctrs ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: The event log file is corrupt" Is there a way to reinstall the service ? Thanks in advance for your help. Regards, Eric.
I'd start with the steps in this article. http://support.microsoft.com/kb/329050 -- Regards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect "Eric" wrote: > Hi everybody, > > My network connections don't work anymore on my W2K Advanced Server. > They're gone in the network folder. > The "Remote Access Connection Manager" service can't start anymore. I > get this message in the event log: "The Remote Access Connection > Manager service failed to start due to the following error: > The service did not respond to the start or control request in a > timely fashion" > > and "The description for Event ID ( 2001 ) in Source ( rasctrs ) > cannot be found. The local computer may not have the necessary > registry information or message DLL files to display messages from a > remote computer. The following information is part of the event: The > event log file is corrupt" > > > Is there a way to reinstall the service ? > Thanks in advance for your help. > > Regards, > Eric.
Hi, Thanks for your answer. I followed the note and the related ones but nothing has changed: impossible to start the Remote Access Connection Manager service although the Telephony one is started. Regards, Eric. On Sat, 3 Mar 2007 10:29:24 -0700, "Dave Patrick" wrote: >I'd start with the steps in this article. > >http://support.microsoft.com/kb/329050
Have you checked the dependency tab and made sure none are disabled? -- Regards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect "Eric" wrote: > Hi, > > Thanks for your answer. > I followed the note and the related ones but nothing has changed: > impossible to start the Remote Access Connection Manager service > although the Telephony one is started. > > Regards, > Eric.
Yes I have Dave. Here is the error (EventID: 7000) I get in the System log every few seconds: The Remote Access Connection Manager service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion. Thanks for trying to help me. On Mon, 5 Mar 2007 08:58:24 -0700, "Dave Patrick" wrote: >Have you checked the dependency tab and made sure none are disabled?
Nothing else in the system event log? -- Regards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect "Eric" wrote: > Yes I have Dave. > > Here is the error (EventID: 7000) I get in the System log every few > seconds: > > The Remote Access Connection Manager service failed to start due to > the following error: > The service did not respond to the start or control request in a > timely fashion. > > > Thanks for trying to help me.
Maybe it's important: I forgot to say that this server is a node of a W2K cluster. On Mon, 5 Mar 2007 08:58:24 -0700, "Dave Patrick" wrote: >Have you checked the dependency tab and made sure none are disabled?
Yes :-) Event ID: 7009 Timeout (30000 milliseconds) waiting for the Remote Access Connection Manager service to connect. On Mon, 5 Mar 2007 09:45:42 -0700, "Dave Patrick" wrote: >Nothing else in the system event log?
What error message when you try to start it manually? -- Regards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect "Eric" wrote: > Yes :-) > > Event ID: 7009 > > Timeout (30000 milliseconds) waiting for the Remote Access Connection > Manager service to connect.
When I try to start manually, I get this: "Could not start the "...." service on local computer. Error 1053: the service did not respond to the start or control request in a timely fashion" On Mon, 5 Mar 2007 10:11:03 -0700, "Dave Patrick" wrote: >What error message when you try to start it manually?
Have you tried removing and reinstalling the network adapter? What was the last thing done before this problem showed up? -- Regards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect "Eric" wrote: > When I try to start manually, I get this: > > "Could not start the "...." service on local computer. > Error 1053: the service did not respond to the start or control > request in a timely fashion"
You mean, physically or reinstalling the driver ? I'm afraid to do that because of the configuration of the cluster. The last thing was a reboot after the installation of a bunch of hotfixes On Mon, 5 Mar 2007 10:32:24 -0700, "Dave Patrick" wrote: >Have you tried removing and reinstalling the network adapter? What was the >last thing done before this problem showed up?
Do you know which ones? Customers in the U.S. and Canada can receive technical support from Microsoft Product Support Services at 1-866-PCSAFETY. There is no charge for support calls that are associated with security updates. -- Regards, Dave Patrick ....Please no email replies - reply in newsgroup. Microsoft Certified Professional Microsoft MVP [Windows] http://www.microsoft.com/protect "Eric" wrote: > You mean, physically or reinstalling the driver ? > I'm afraid to do that because of the configuration of the cluster. > > The last thing was a reboot after the installation of a bunch of > hotfixes
