RRAS will not start with EventID 20152

[Craig Ongers]

Hi there,

I have received no reply from "microsoft.public.windows.server.sbs", so if
anyone could offer some advice I would really appreciate it.

One of our clients performed an in-place upgrade from SBS2000 to SBS2003.
All is fine, but regardless of the RRAS config, the RRAS service will not
start and the following are the only two events logged:

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 2004/01/28
Time: 02:31:15
User: N/A
Computer: CPS
Description:
The Routing and Remote Access service terminated with service-specific error
87 (0x57).

Event Type: Error
Event Source: RemoteAccess
Event Category: None
Event ID: 20152
Date: 2004/01/28
Time: 02:31:12
User: N/A
Computer: CPS
Description:
The currently configured authentication provider failed to load and
initialize successfully. The parameter is incorrect.

Anyone out there that can help ? I believe this error is not specific to
SBS, but to upgrades from a Win2k OS.

Thanks in advance,
Craig.

 

[Sandeep Rikhi [MSFT]]

Craig
What all services are running on the server ? You can check this using "net
start" command or through services.msc.

Please ensure that the required services (such as TCP/IP, Server, RPC, TAPI,
IPSec) are running for RRAS to start.

Thanks,
--
Sandeep

When replying, please post to GROUP so that everyone can benefit from the
knowledge.

This posting is provided "AS IS" with no warranties

 

[Craig Ongers]

Hi there Sandeep, appreciate the help. List as requested:

These Windows services are started:

Automatic Updates
Background Intelligent Transfer Service
COM+ Event System
Computer Browser
Cryptographic Services
DHCP Client
DHCP Server
Distributed File System
Distributed Link Tracking Client
Distributed Link Tracking Server
Distributed Transaction Coordinator
DNS Client
DNS Server
Error Reporting Service
Event Log
Fax
File Replication
FTP Publishing Service
Help and Support
HTTP SSL
Human Interface Device Access
IIS Admin Service
IPSEC Services
Kerberos Key Distribution Center
License Logging
Logical Disk Manager
Microsoft Exchange Information Store
Microsoft Exchange Management
Microsoft Exchange Routing Engine
Microsoft Exchange System Attendant
Microsoft Firewall
Microsoft H.323 Gatekeeper
Microsoft ISA Server Control
Microsoft Scheduled Cache Content Download
Microsoft Search
Microsoft Web Proxy
MSSQL$SHAREPOINT
MSSQLSERVER
Net Logon
Network Connections
Network Location Awareness (NLA)
NT LM Security Support Provider
OfficeScan Master Service
Plug and Play
Print Spooler
Protected Storage
Remote Access Connection Manager
Remote Installation
Remote Procedure Call (RPC)
Remote Registry
SBCore Service
ScanMail_MailAction
ScanMail_Monitor
ScanMail_RealTimeScan
ScanMail_Web
Secondary Logon
Security Accounts Manager
Server
SharePoint Timer Service
Shell Hardware Detection
Simple Mail Transport Protocol (SMTP)
Single Instance Storage Groveler
System Event Notification
Task Scheduler
TCP/IP NetBIOS Helper
Telephony
Terminal Services
Trend ServerProtect
Trend ServerProtect Agent
Trivial FTP Daemon
WebClient
Windows Internet Name Service (WINS)
Windows Management Instrumentation
Windows Management Instrumentation Driver Extensions
Windows Time
Workstation
World Wide Web Publishing Service

The command completed successfully.

Regards,
Craig.

 

[Craig Ongers]

Hi,

An update: Previously I mentioned RRAS fails regardless of the RRAS config.
That is untrue. It only fails when the "Remote access server" role is
selected. RRAS starts just fine if it is only configured as the "Router"
role.

Still stumped at the moment...
Craig.

 

[Chetan Raghavendra [MSFT]]

You are right. This is mostly to do with how one has configured RAS to
authenticate the clients. If the confugration says "RADIUS authentication"
and if the server is unavailable, RRAS would fail to start.

You can check how it is configured by going to Run -> rrasmgmt.msc -> main
node -> right click, properties ->Security ->Authentication Provider. It
can be set to "Windows Authentication"

--
Thanks
Chetan
(e-mail address removed)

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Danny Slye - [MSFT}]

First make sure that RRAS logging is pointing to a valid path with the
correct permissions, RRAS will not start if it cannot log. If that is not
the problem, it is possible that the remote access policies are corrupted,
or if the files are missing after the upgrade. You may need to do the
following:
1 - Verify RRAS is disabled.
2 - Make a back up copy of the IAS folder as a precaution.
3 - Delete the dnary.mdb and the ias.mdb files from the IAS folder.
Note: you may have to boot to Safe Mode to delete the ias.mdb file.
4 - Expand dnary.md_ and ias.md_ from the SBS CD and copy them into the
WINNT\System32\IAS folder.
5 - Open a command prompt and navigate to the following directory:
C:\Program
Files\Common Files\System\Ole DB
6 - Run the following commands:
regsvr32 oledb32r.dll
regsvr32 oledb32.dll

7 - Open the TO DO List and run the Configure Remote Access wizard

====================================================================
This posting is provided "AS-IS" with no warranties and confers no rights
=======================================================================

 

[Craig Ongers]

Hi there Chetan,

Thanks for the reply. Not using RADIUS and have verified it is not selected
anywhere.

As mentioned, it works fine when only configured as a 'Router', so I am
assuming a problem with it configuring remote access ports or something like
that. (as opposed to file/permission/RAS settings etc)

Any help would be cool,
Craig.

 

[Tomas Meller]

Having Exactly the smae issue. DId you solve it?

-----Original Message-----
Hi there Chetan,

Thanks for the reply. Not using RADIUS and have verified it is not selected
anywhere.

As mentioned, it works fine when only configured as a 'Router', so I am
assuming a problem with it configuring remote access ports or something like
that. (as opposed to file/permission/RAS settings etc)

Any help would be cool,
Craig.

"Chetan Raghavendra [MSFT]"

You are right. This is mostly to do with how one has configured RAS to
authenticate the clients. If the confugration

says "RADIUS
authentication"

and if the server is unavailable, RRAS would fail to start.

You can check how it is configured by going to Run -> rrasmgmt.msc -> main
node -> right click, properties ->Security - Authentication Provider. It
can be set to "Windows Authentication"

--
Thanks
Chetan
(e-mail address removed)

This posting is provided "AS IS" with no warranties,

and confers no
rights.

regardless of the RRAS
config.

can check this
using

everyone can benefit from
the from "microsoft.public.windows.server.sbs",
so

the RRAS service
will with

service-specific

error is not
specific

to

.