windows could not start the routing and remote access on local computer

I was recently trying to setup a VPN for incomming connections on my system. No problem I said, I've done it more times than I can count. Not so... Uppon trying to create the connection I get:

I am trying to set up a VPN for incomming connections on my pc and I have done that pretty fine before also. But this time when I am trying to create the connection I get a message:

Incoming connections depend on the Routing and Remote Access service which was unable to start

Windows could not start the Routing and Remote Access on Local Computer. For more information, review the System Event Log

The Routing and Remote Access service terminated with service-specific error 340 (0x154).

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I have done enough searches already on this on many sites but couldnt find any results. Can anyone help me out? Thank you.

1. Verify that the follwing files are on your system:
msjetole32db40.dll
oledb32.dll
msdasc.dll

2. Then run "regsvr32 <filename>.dll" on all three above to re-register the three dll files.

3. Reboot.

4. RRAS should start.

That should do the trick and you should get that working.

Open Control Panel, and then double-click System.
Click the Hardware tab.
Click Device Manager.
Expand Tape Drives.
Right-click the tape device, and then click Properties.
Click the Driver tab, and then click Update Driver.

The Upgrade Device Driver wizard opens.

Click Next.
Click Display a list of the known drivers for this device so that I can choose a specific driver.
Click Show compatible hardware.

The wizard will list one of the standard tape drive models that are compatible with your hardware.

Click the listed device, and then click Next two times.
Click Finish.
Restart your computer.

More information here: http://support.microsoft.com/kb/842696

Go to Services and check to make sure that the Remote Access Connection Manager service is enabled. If so, try starting it. Then try to recreate your Incoming Connection.

Other possible solutions:

Check in the system32 directory for MSJETOLEDB40.DLL. This file may be missing or named incorrectly. A file by the name of MSJETOL1.DLL may exist. This is the 8.3 name for MSJETOLEDB40.DLL. If MSJETOL1.DLL is there, rename it to the long file name above. If it isn't there, copy it from another machine. After the file is renamed or copied, register the DLL by typing "regsvr32 MSJETOLEDB40.DLL".