RACM Failure on win2k

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi

I have MS Windows 2000 Professional. I'm not able to start the Remote Access
Connection Manager Service. I get the follolwing message when i try to start
it:

"Windows could not start Remote Acess Connection Manager on local computer.
For more info, review the System Event Log. If this is a non-Microsoft
service, contact the service vendor, and refer to the service-specific error
code 1717"

I've already checked that the dependant Telephony service is already started
on my computer.

This is causing me a lot of grief because i cannot connect to the network at
my work via our own VPN software. Even when i try to use Dial-up Preferences
under Network and Dial-up Prefernces, i get the following error:
"Cannot load the Remore Access Connection Manager service.
Error 711: The Remote Access Connection Manager could not start. .."

I've researched the knowledge base extensively and i find very little help -
most of the help is for windowsXP. The only solution suggested for this
problem in the knowledge base archives, is to remove and reinstall the Remote
Access Connection Manager. But i cannot find any way to reinstall this
service on windows 2000.

All helpdesk personell at my work suggest that i reintall windows, but i
believe there's got be a better and less brute force of a way to fix this
problem. Can anyone help me with figuring out how to solve this problem
and/or reinstall this service?

Thanks
Anita
 
fyi my vpn connection was working fine until last week when i tried to
download "nero" - the download failed and with it the RACM seemed to have
crashed as well.

and btw i have SP4 installed on my machine.

/a
 
Just a stab...but...

You could remove any Service Packs and patches then reapply them.

If it fails...

Repeat the above by removing all Sps and patches again, then do an inplace
upgrade of the OS over the top of itself (as opposed to wiping the drive and
doing it), then reapply the SPs and patches.

Of course it would be good if you did a good full backup first,...or better
yet, a Ghost image of the machine before you begin.
 
Back
Top