Support Support Downloads Knowledge Base Juniper Support Portal Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

Database is blank after upgrading to Steel-Belted RADIUS 6.1x from 6.0x or below



Article ID: KB14960 KB Last Updated: 05 Mar 2017Version: 2.0
Steel-Belted RADIUS database has no data in it after an apparent successful upgrade on Windows platform
A customer is upgrading Steel-Belted RADIUS to version 6.1x from an earlier version on the Windows platform

The upgrade appears to work normally. There are no error messages displayed.

However, when the administrator logs into the server Administrator GUI, the database is blank. There are not RADIUS clients, Users, Groups or another data previously contained in the configuration database.

The issue only occurs when the upgrade is done via Microsoft Terminal Services (RDP) and not physically at the server. During the upgrade process, the underlying database used by Steel-Belted RADIUS is converted. The database conversion tool does not run under a Terminal Service session. The only way to run the upgrade via Terminal Services (RDP) is to connect to the console session by using the /c option when running the mstsc utility.

mstsc /c

There are a couple different options available to recover from this issue.
  1. If an XML export was done prior to the upgrade, simply use the XML file and re-import all of the data
  2. Assuming the service directory was backed up prior to the upgrade, the old database files are still available. The files are called radads.dat and radclnt.dat.   You can use a tool located in the “Service” directory called ‘dbconvert.exe’.

If you are going to attempt option 2, do the following:
  1. Stop the Steel-Belted RADIUS service by using the Windows Services control panel.
  2. By default, dbconvert looks in the current directory for the database files; it will error out if the database is not there. If the radads.dat and radclnt.dat files are in a different location, use the ‘-p’ parameter and specify the location of the two .dat files. 
  3. Once the database has been converted, restart the Steel-Belted RADIUS service and login to the Admin GUI to see if the database was converted

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search