Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5446
  • Last Modified:

Routing And Remote Access Service will not start - Service Specific Error 340 (0x154).

Hi,
I have a problem with routing and remote access service on a Windows 2003 SBS server (I've posted in the standard W2K3 area as I don't think that this is an SBS specific issue). After restarting the server routing and remote access failed to start. I had made no changes to RRAS prior to restarting the server. The following error appeared in the system log.

Service Control Manager
Event ID: 7024
The Routing and Remote Access service terminated with service-specific error 340 (0x154).

After researching this error online I found a suggestion that this may be due to corrupt remote access policies and a fix would be to delete and recreate them. I deleted all three policies and tried to restart the service and it worked fine. I then added a policy to allow VPN access and tried to restart the service. It failed again with the same error described above. Does anyone have any ideas how I might fix this?

Thank you
0
ShinyApples
Asked:
ShinyApples
1 Solution
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
In all likelihood, this error is being caused by a corrupt Internet Authentication Service database rather than the RRAS policies.  There is a KB article which describes how to repair the databases, and although it mentions errors which are not an exact match to yours it couldn't hurt to try.  Although before attempting this procedure it is advised that you execute a SYSTEM STATE backup.  Additionally if this does not work, your best remedy may be to restore the SYSTEM STATE from a recent backup if you have one available.

The KB is http://support.microsoft.com/kb/840686

Also, make sure that RRAS is being run under the Local System account by checking the properties in the Service Manager.

Lastly, The SBS Topic area exists because there are MANY issues which are not handled the same way on an SBS even if it is a Server 2003 problem.  Many of the experts in the Windows Server 2003 have never worked with SBS and do not necessarily have direct experience in working with the interdependencies of the many services within a single machine.  So, you are always better off posting to the SBS Topic Area for ANYTHING which occurs on an SBS machine or on it's network.

Jeff
TechSoEasy
0
 
tmartin69Commented:
I was having the same problem in SBS-2003 followed the attached instructions and its all go now. Thanks heaps!!
0
 
ShinyApplesAuthor Commented:
Thanks for your advice guys - I will give this a go and let you know how I get on.

Cheers
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now