Hi,

Could you please have a share with the whole error messages(Which I mean to upload the event log to onedrive and post the link here)?

In addition, please take a try to reinstall the communication hardware and then restart the Remote Access Connection Manager service.

Regarding the error message, please also take a check with the following article to see if it could help here:

Event ID 20030 RASMAN Service Configuration

Best regards

Hi Michael,

I have provided the whole of the error message above, it doesn't give me any more detail unfortunately.  I have already tried re-installing the communication hardware but it hasn't made a difference and the Remote Access Connection Manager will not start.

I have had a look at the article you refer to but it seems to be related to Windows Server, I am running Windows 8.1.  I have looked for the DLL's that are mentioned in the article and they exist on my machine so it looks ok there.  I don't think there is a way to re-install routing and remote access on windows 8.1 other than to reset/repair windows so I don't think that's an option.

Thanks for your help and suggestions.

Alun

Then, have you tried to repair Windows?

the error message article is logged with server side, but the working method is similar.

Take a try to use DISM restorehealth to check the result.

Rgds

Hi,

I haven't tried to repair windows yet as it will remove any programs I have installed and basically I will have to re-build the machine, re-adding all the programs I have installed.  I will try a windows repair if I need too and I'm sure it will fix the problem but at the moment it's a last resort.

Thanks for the suggestion though.

I have provided the whole of the error message above, it doesn't give me any more detail unfortunately.

Try using ProcMon to get more context for it.  Filter with Operation Is WriteFile (or similarly but for more detail, with Category Is Write).  Then when you have guessed which "write" corresponds to a message that you have seen you can remove the filter and see before that any registry and file accesses which might have contributed to the message's content.

 

Good luck

Hi,

Have you tried the suggestions mentioned by Robert Aldwinckle?

If any further help needed, please feel free to ask.

Best regards

Hi.

I have the same problem. All began after uninstalling Hyper-V.

Now There is no way to start Remote Access Connection Manager. On Event Viewer I see this EventID:

 - 20030

 - 7023

I would like to reinstall/repair RAS Service.... there is a way?

Thanks

Hi,

I couldn't find a way to just re-install RAS, however I managed to fix the issue in the end by running the following command to reset TCP/IP:

netsh int ip reset c:\resetlog.txt
Then restart the PC.

I have exactly the same problem after enabling Virtualization in the BIOS and installing VirtualBox. Disabling Virtualization and uninstalling VirtualBox did not fix the issue, neither did a System Restore to an earlier snapshot.

"netsh int ip reset" does not help, either. It reports the following unhelpful error:

C:\Windows\system32>netsh int ip reset
Resetting Interface, OK!
Resetting Neighbor, OK!
Resetting Path, OK!
Resetting , failed.
Access is denied.

I did not find anything useful with ProcMon when running int ip reset. When I try to start the RasMan service, the only fs failures I see are ACCESS DENIED on C:\ProgramData\Microsoft\Windows\Sqm\Upload\PnrpResolveSession0.sqm (the Upload folder is empty) and NAME NOT FOUND on C:\ProgramData\Microsoft\Network\Connections\Pbk (the Connections folder is empty)

I did not find anything useful with ProcMon when running int ip reset.

Perhaps you should interpret those as incorrect responses to the actual symptom that ProcMon is showing you and try to find workarounds for them?  E.g. could you put something in the Pbk directory?   Disable SQM?  Etc.

Good luck

I noticed that all the VPN-related WAN Miniport devices were shown with an error in device manager while RasMan tries to start. I tried to get rid of them and reinstall them but failed (the workaround of replacing the driver with a dummy driver first did not work - The device did not change at all). Deleting them from the registry (in [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4d36e972-e325-11ce-bfc1-08002be10318}]) did not help, either, and even after restoring the registry settings, it's worse than before. Now the failure I get is:

"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."

sfc and SFCFix didn't help, either. I have no idea what else to try except to run a Windows refresh and spend the next weeks reinstalling everything :-(

 failed to start because of the following error:
The operation completed successfully."

Something missing between the colon and the next line?   Does ProcMon clarify?  <eg>

No, nothing missing. When I start SSTP manually, it tells me that it started successfully and immediately stopped (which is AFAIK the expected behavior for this service if nobody actually needs it). I assume all of this is related to the broken WAN Miniport devices (SSTP, IKEv2, L2TP, PPTP) but I have found not way of uninstalling and recreating them.

I was able to solve the problem now. I tried the WAN Miniport Repair tool but it couldn't remove the broken devices. A Windows Refresh was not possible for some reason. Finally I ran an Update installation of Windows 8.1 and surprisingly it actually installed (I would have expected it to abort since I was already on 8.1 update 1). Now RasMan is working fine again and pretty much everything (applications, drivers, settings) is still there.

windows remote access connection manager is connected to windows event log

the solution

1. open "services" by search for the word .
2. look for windows event log
3. start the service
4. start remote access again 
5. done .

• Proposed as answer by abdo444 7 hours 0 minutes ago

windows remote access connection manager is connected to windows event log

the solution

1. open "services" by search for the word .
2. look for windows event log
3. start the service
4. start remote access again 
5. done .

• Proposed as answer by abdo444 Sunday, July 19, 2015 12:23 AM