Event ID: 7024 - The Routing and Remote Access service terminated with service-specific error codes

Chicago Area Laptop for rent: $35 per day plus $10 for additional day

Event ID: 7024 - The Routing and Remote Access service terminated with service-specific error codes

The Routing and Remote Access service terminated with service-specific error 87 (0x57).
The Routing and Remote Access Service service terminated with the service-specific error 110.
The Routing and Remote Access Service service returned service specific error 127
The Routing and Remote Access service terminated with service-specific error 505.
The Routing and Remote Access Service service returned service specific error 691
The Routing and Remote Access service terminated with service-specific error 711.
The routing and Remote Access Service service returned service specific error 1003.
The Remote Access Server service terminated with the following server-specific error 1066.
The Routing and Remote Access Service service returned service specific error 1068
Event ID 7024 - The Net Logon service terminated with service-specific error 3095.
Event ID 7024 - The Computer Browser service terminated with service-specific error 2550 (0x9F6).
The Routing and Remote Access Service service returned service specific error16389

The Routing and Remote Access service terminated with service-specific error 87 (0x57). This issue may occur if the Internet Authentication Service (IAS) database is damaged. IAS and the Routing and Remote Access service use the IAS database.
To resolve this issue, follow these steps:
1. Extract the Ias.mdb file and extract the Dnary.mdb file from the Windows 2000 Server CD or the Windows Server 2003 CD to the %WinDir%\System32\Ias folder on the disk. To do this, follow these steps:
a. Click Start, click Run, type cmd in the Open box, and then click OK.
b. At the command prompt, type the following lines. Press ENTER after each line:
Drive:
cd i386
ren %windir%\system32\ias\ias.mdb %windir%\system32\ias\iasOLD.mdb
ren %windir%\system32\ias\dnary.mdb %windir%\system32\ias\dnaryOLD.mdb
expand ias.md_ %windir%\system32\ias\ias.mdb
expand dnary.md_ %windir%\system32\ias\dnary.mdb
Note In this step, Drive is a placeholder for the drive letter of the CD-ROM drive or of the DVD-ROM drive that contains the Windows 2000 Server or the Windows Server 2003 CD.
2. Register the Oledb32r.dll file and register the Oledb32.dll file. To do this, follow these steps:
. At the command prompt, type the following lines. Press ENTER after each line:
Drive:
cd program files\common files\system\ole db
regsvr32 oledb32r.dll
Note In this step, Drive is a placeholder for the drive letter where the Program Files folder is stored.
a. When you receive a message that indicates that the operation is successful, click OK.
b. At the command prompt, type the following line, and then press ENTER:
regsvr32 oledb32.dll
c. When you receive a message that indicates that the operation is successful, click OK.
d. Type exit, and then press ENTER to quit Command Prompt.
3. Register the Vbscript.dll file. To do this, follow these steps:
. At the command prompt, type the following lines. Press ENTER after each line:
Drive:
cd %systemroot%\system32
regsvr32 vbscript.dll
Note In this step, Drive is a placeholder for the drive letter where the System32 folder is stored.
a. When you receive a message that indicates that the operation is successful, click OK.
b. Type exit, and then press ENTER to quit Command Prompt.
4. Start the Routing and Remote Access service. To do this, follow these steps:
. Click Start, point to Programs, point to Administrative Tools, and then click Services.
a. Right-click the Routing and Remote Access service, and then click Start.

The Routing and Remote Access Service service terminated with the service-specific error 110.
RRAS does not install the file Ipfltdrv.sys if it detects that Microsoft Proxy Server is already installed on the computer.
To workaround this issue, use one of the following methods:
Manually copy the file Ipfltdrv.sys from the RRAS directory into the %Systemroot%\System32\Drivers folder.

NOTE: The default folder for RRAS is C:\Routing, but it may vary depending on how you installed the update.

-or- Upgrade to Microsoft Proxy Server version 2.0.

-or- Uninstall RRAS and reinstall the update on a different server.

The Routing and Remote Access Service service returned service specific error 127
Case 1: This problem may occur because an incorrect version of the Oledb32.dll file is on the computer.
To resolve this problem, follow these steps:
1. Make sure that the version of the Oledb32.dll file on the server is version 2.82.3959.0.

Note To obtain this version of the file, you can copy the file from the Windows\ServicePackFiles\i386 folder. Or, you can install Windows Server 2003 Service Pack 2 (SP2).
2. Type the following command at a command prompt, and then press ENTER:
regsvr32 oledb32.dll
3. Restart the computer

Case 2:
This behavior may occur because the Routing and Remote Access Service cannot start. This service cannot start if the Remote Access Connection Manager service and the Telephony service are disabled. The Hisecweb.inf security template typically disables the following services by setting the Startup Type to Disabled:
Remote Access Auto Connection Manager Remote Access Connection Manager Remote Registry Service Routing and Remote Access TelephonyTo resolve this behavior, use the Services Administrative tool to set the Startup Type of these services to Automatic. After you have configured these settings, restart the Routing and Remote
Routing and Remote Access Service service returned service specific error930 - I started getting this error when a partition was deleted and disk space relocated with Partition Magic. RRAS log file was configured to point to the deleted partition and prevented RRAS from starting. Reconfigure RRAS to change log path somewhere else.

The Routing and Remote Access service terminated with service-specific error 505.
This issue may occur if the Oledb32.dll and Oledb32r.dll files are incorrectly registered. This condition may be caused by a third-party program that is installed on the computer.

To resolve this issue, follow these steps.
Step 1: Verify that the Administrators Group Has Full Control Permissions
Verify that the Administrators group has Full Control permissions to the following files (if present) and folders, where Drive is the drive on which Windows is installed:
Drive:\Winnt\System32\Ias
Drive:\Winnt\System32\Ias\Ias.mdb
Drive:\Winnt\System32\Ias\Dnary.mdb
Drive:\Winnt\Temp
To do this:
1. Start Windows Explorer, locate and right-click the file or folder, and then click Properties.
2. Click the Security tab.
3. Verify that the Administrators group is displayed in the Name list and that it has Full Control permissions to the file or folder.

If the Administrators group does not appear on the Name list, add it. To do this, follow these steps:
a. Click Add.
b. In the Select Users or Groups dialog box, click Administrators, click Add, and then click OK.
c. To assign Full Control permission, click Administrators in the Name list, and then in the Permissions list, click to select the Allow check box next to Full Control.
d. Click OK.
Step 2: Reregister the Oledb32.dll and Oledb32r.dll Files
To register the Oledb32.dll and Oledb32r.dll files:
1. Click Start, and then click Run.
2. In the Open box, type cmd, and then click OK.
3. At the command prompt, type the following lines, pressing ENTER after each line (where Drive is the letter of the drive on which Windows is installed):
Drive:
cd program files\common files\system\ole db
regsvr32 oledb32.dll
regsvr32 oledb32r.dll
4. Click OK when you receive the messages that the operation succeeded.
5. Type exit to close the command prompt.

The Routing and Remote Access Service service returned service specific error 691 (for win 2003)- I fixed it by copying ias.mdb and dnary.mdb from another machine to %windir%\system32\ias\.

The Routing and Remote Access service terminated with service-specific error 711.
This problem may occur if the Veritas Backup Exec program is installed on your computer. A conflict between the Veritas tape device driver and the Routing and Remote Access service may prevent the service from starting.
To resolve this problem, replace the Veritas tape device driver with an updated device driver. You can replace the Veritas device driver with an updated third-party driver or with the Windows standard tape device driver.

Note Windows 2000 Server and SBS 2000 do not include standard drivers for every tape device model. See the "More Information" section for a list of the standard tape drivers that are included.

To install an updated third-party driver, follow the instructions that the manufacturer provides. To install the Windows standard driver, follow these steps:
1. Open Control Panel, and then double-click System.
2. Click the Hardware tab.
3. Click Device Manager.
4. Expand Tape Drives.
5. Right-click the tape device, and then click Properties.
6. Click the Driver tab, and then click Update Driver.

The Upgrade Device Driver wizard opens.
7. Click Next.
8. Click Display a list of the known drivers for this device so that I can choose a specific driver.
9. Click Show compatible hardware.

The wizard will list one of the standard tape drive models that are compatible with your hardware.
10. Click the listed device, and then click Next two times.
11. Click Finish.
Restart your computer.

Routing and Remote Access Service service returned service specific error 1003.
Case 1: A system component, such as a protocol or service, that is used by Routing and Remote Access has been installed after applying Service Pack 3.
To resolve this problem, use the following steps:
1. Reinstall Service Pack 3.
2. When you are prompted to replace newer files, click No to All.
3. Restart the computer when prompted.
4. Update Routing and Remote Access Service
a. Click Start, point to Settings, and click Control Panel.
b. Double click the Network icon.
c. Choose the Services tab.
d. Select Routing and Remote Access Service.
e. Click Update.
f. Specify the installation location, the default is

C:\program files\routing
g. When prompted to reboot, click Yes

Case 2:
When RRAS is installed on a multihomed server (one that has two or more network interfaces) and Auto Frame Type Detection is enabled for the NWlink IPX/SPX Compatible Transport, the bindings may not be correctly enumerated for the IPXRouterManager in the registry.
To resolve this issue, use the following steps:
1. Manually set the internal network number and specify Manual Frame Type Detection for the properties of the NWLink IPX/SPX Compatible Transport.

For more information, see the following article in the Microsoft Knowledge base:
ARTICLE-ID: 150546 (http://support.microsoft.com/kb/150546/EN-US/ )
TITLE : NWLink IPX/SPX: Network Number vs. Internal Network Number
2. Click Start, point to Settings, and click Control Panel.
3. Double-click Network, click the Services tab, and click Routing and Remote Access.
4. Click Update and specify the location of the RRAS folder.

NOTE: By default, this folder is C:\Program Files\Routing

The Remote Access Server service terminated with the following server-specific error: 1066.
The above error messages may be caused by one or more of the following:
Your RAS configuration specifies Dial Out Only in the RAS properties

-or- The serial ports are disabled in the BIOS of your computer

-or- RAS is configured to use an account other than the System account

-or- Your Modem is malfunctioning or is no longer working.To correct this issue, you will need to do one of the following:
Configure one or more ports to receive calls using the following steps:·    Windows NT version 4.0
·    ----------------------
·
·    1. Click Start, point to Settings, and click Control Panel.
·
·    2. Double-click Network, click Services, click Remote Access Service,
·       and click Properties.
·
·    3. Select one of the installed ports and click Configure.
·
·    4. Click either Receive calls only or Dial out and Receive calls.
·
·    5. Click Close, click Continue, click Close, and restart Windows NT
·       when prompted.
·
·    Windows NT version 3.5 or later
·    -------------------------------
·
·    1. Double-click Control Panel and click Network.
·
·    2. In the Installed Network Software box, select Remote Access
·       Service.
·
·    3. In the Remote Access Setup dialog box, choose Configure, and then
·       choose Configure again.
·
·    4. In the Port Usage box, make sure either the Receive Calls Only or
·       the Dial Out And Receive Calls option box is selected.
·
·    5. Choose OK, shut down Windows NT, and restart.

-or-
Consult the documentation that came with your computer to enable the serial ports on your computer.

-or- Configure RAS to use the System account in Control Panel using the following steps:·    1. In Control Panel, double-click Services, and select Remote Access
·       Server in the Service list.
·
·    2. Click Startup, click System Account in the Log On As section, and
·       click OK.
·
·    3. Click Close and restart Windows NT.

-or-
Replace your modems one by one till the RAS service starts.

The Routing and Remote Access Service service returned service specific error 1068 (Dependency group failed). - You may receive this is you only have TCP/IP installed and attempt to start Routing and Remote Access under Windows XP Pro. Install the NWLINK/NetBIOS protocol (remember to set your Address to something unique, other than 00000000 if you have multiple NICs) and restart the service.

The Routing and Remote Access Service service returned service specific error16389

Case 1: Caused by RRAS service trying to access “C:\winnt\system32\system.mdb” which was surprisingly dated 1997 on a Windows 2000 SBS server. I renamed the file and RRAS now starts.

The Routing and Remote Access Service service returned service specific error16389 - From a newsgroup post: "I had the same problem on my RRAS server. The error 16389 just means that the service can not create temp-files. The service usualy runs in the local system account and try to use C:\WINNT\TEMP as the temp folder. In the NTFS permissions for this folder there has to be the user "SYSTEM" with full control permissions. I added this and it worked fine for me."

Post your questions, comments, feedbacks and suggestions

Contact a consultant