7

When trying to start the Remote Access Connection Manager service, I always get an error message saying:

Error 1068: The dependency service or group failed to start.

I configured and included all dependencies listed here, but Remote Access Connection still won't start. Instead, other dependencies that are running as automatic start up.

I'm using Windows 7 64-bit.

Below is a screenshot of the error message:

enter image description here

1
  • Go to this list answers.microsoft.com/en-us/windows/forum/windows_7-performance/… Manually start the services they show there, and tell the results of doing that. Some services will start , then stop again, that is normal. Also just for good measure an older one, make sure that the "windows event log" serv also functioning. What are you trying to "connect" exactly (the service type or any info)? What is your "windows update status"? then go into device manager and check the net stuff in devices.
    – Psycogeek
    Mar 5, 2012 at 19:23

7 Answers 7

3

Well I went through a lot of posts and I finally figured out that I had, last week, disabled Windows Event Log service. Turn that on and Joy to my World. That was the cause for all my grief. Hope this helps.

1

Here is the best fix:

  1. Used msconfig to switch to safe mode boot
  2. Booted to safe mode
  3. Ran cmd.exe as an administrator
  4. Typed "cd C:\Windows\System32\LogFiles\WMI"
  5. Typed "rename RtBackup RtBackup2"
  6. Used msconfig to switch to normal boot mode
  7. Reboot and found event viewer working
1

I bet you can't open the Event Viewer in Administrative Tools too. I found out that Windows Event Log was disabled.

So in case to solve all this, go to

  1. Control Panel → Administrative Tools → Services → Windows Event Log
  2. Right-click "Properties → Startup type" if disabled, turn it on to automatic

Enabling this unblocks the opportunity to Enable/start the Remote Access Connection Manager and Remote Access Auto Connection Manager.

It worked for me.

1

FIXED! After several days of absolute frustration, trying to fix this Error 1068 and related issues, I am overjoyed to have finally found a solution! Read further only if you are encountering Error 1068 or Error 5 AND are having trouble starting up the relevant services:

ISSUE DETAILS: Basically my intent was to turn my laptop into a WiFi router, so I went through online tutorials which somehow didn't seem to work. When I got into troubleshooting mode, I found out that the ICS (Internet Connection Sharing) required a few services to be enabled and working properly. A couple of them were not started, so I fixed those, but then I encountered a couple of services which wouldn't start (Error 1068) even when I tried, I knew I was onto something.

THE FIX:

1) Enable all services as advised in the "Let me fix it myself" section of this page. If you're having trouble finding Services, go to msconfig.exe (through Start Menu search) and then go to tab "Services"

2) If you encounter a problem (such as Error 1068) while trying to enable the service "Remote Access Connection Manager" like I did, then it may actually be dependent on the service "Windows Event Log", which in my case wasn't started and refused to start manually (Error 5, if I remember correctly). To start it, first change the security/permissions on the logs folder as described on this page

3) Then make sure you reboot, then start up the service "Windows Event Log", followed by the other offending services that weren't starting earlier. Once all relevant services are running, reboot again and you should be all set. Last but not the least, don't forget to turn on your WiFi radio before you attempt to tether!

LONG STORY SHORT: the culprits are: services "Remote Access Connection Manager" and "Remote Access Auto Connection Manager", which depend on service "Windows Event Log", which depends on the correct permissions on folder %WINDIR%\System32\WinEvt\Logs

Let me know if this ends up working for you!

1
  • This should be the recommended answer. Sorted me out in seconds :) Apr 24, 2018 at 23:04
1

It's always a great idea to read the event logs. From Event viewer > Windows log > System You will see logs related to your problem. mine was like this:

The Remote Access Connection Manager service depends on the Secure Socket Tunneling Protocol Service service which failed to start because of the following error: The operation completed successfully. Windows event viewer screenshot

4
  • 1
    How did you fix this? I have the exact same problem.
    – adigostin
    Dec 5, 2019 at 7:48
  • @adigostin if I'm not mistaken I tried to start Secure Socket tunneling protocol service first and afterwards Remote Access Connection Manager service worked fine
    – M at
    Dec 6, 2019 at 6:06
  • When I start the SSTP service I get right away the message "the service started and then stopped, which is normal for some services". I believe this "normal stopping" is what causes in the Event Log the "following error: operation completed successfully" text, which I'm getting too.
    – adigostin
    Dec 7, 2019 at 7:06
  • @adigostin My SSTP service is running so something is stopping it. please check it's error logs. try creating a new user and see if things are the same over there.
    – M at
    Dec 7, 2019 at 11:27
1

i had the same problem but i found the solution:

Step 1:

Make sure all the dependency services of "Remote Access Connection Manager"" are started in services list..

a. Click Start, type services.msc in the Start Search box.

b. Select Services in the Programs list. If you are prompted for an administrator password or confirmation, type your password or click Continue

c. Right-click Remote Access Connection Manager service and then click Properties.

d. On the General tab, click Manual next to Startup type.

e. On the General tab, click Start under Service status, and then click OK.

f. Also check for the Dependency services.

The following are the dependency services of "Remote Access Connection Manager":

i. Secure Socket Tunneling Protocol Service

ii. Telephony

iii. Plug and Play

iv. Remote Procedure Call (RPC)

v. DCOM Server Process Launcher

vi. RPC Endpoint Mapper

Make sure the above services are started in the services list. If not, start all of the above services and check.

-1

Follow these instructions:

  1. Go to Start → Run → services.msc to open the Services control panel.
  2. For each of the following services, right-click on it, select Properties and set startup type to Manual or Automatic to enable the service:
    • Remote Access Auto Connection Manager
    • Remote Access Connection Manager
    • Telephony
    • Windows Remote Management (WS-Management)
    • TCP/IP NetBIOS Helper

That should fix the problem.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .