Adminui Fails to install successfully on Windows OS when 8dot3name disabled on the Drive

Article Id: 36910

Status: Published

Updated On: 14-02-2018 07:37

Legacy Id: TEC1041145

Products:

CA Single Sign On Secure Proxy Server (SiteMinder) , AXIOMATICS POLICY SERVER , CA Single Sign On SOA Security Manager (SiteMinder) , CA Single Sign-On , CA Single Sign-On

Issue/Introduction:

Issue

NOTE --> The below is applicable for all 12.x Siteminder Adminui Installation

Adminui Fails to Install / Start properly on Windows OS with below Error

Error: Could not find or load main class Files

Resolution

- The Adminui installation on Windows depends on the 8dot3name to be enabled on the Drive that the installation is taking place on .

- When 8dot3 is disabled ,the Adminui will install with no issues ,however ,the JBOSS service will not get added to the windows Services list and any manual attempt to start the Jboss instance will result in Error "Error: Could not find or load main class Files"

- For Security reasons ,most of the system Admins disable the 8dot3name on their System drives .To get the Adminui installed ,8dot3 can be enabled temporary and disabled after the installation completes.

Please find below the steps to successfully install the Adminui

Step 1 --> Make sure that 8dot3name is enabled on the Drive

1) check the 8dot3 status by running the below from Command line

C:\>FSUTIL.EXE 8dot3name query c: --> this is checking the status of 8dot3 on drive C

The volume state is: 1 (8dot3 name creation is disabled).

The registry state is: 2 (Per volume setting - the default).

The 8dot3name is set to 1 (disabled) as seen from Results

2) Enable the 8dot3name using the FSUTIL tool by running the below

C:\>fsutil 8dot3name set C: 0

Successfully Enabled 8dot3name generation on C:

Verify the above by running the 8dot3name query one more time to confirm it got enabled

C:\>FSUTIL.EXE 8dot3name query c: --> this is checking the status of 8dot3 on drive C

The volume state is: 0 (8dot3 name creation is enabled).

The registry state is: 2 (Per volume setting - the default).

Step 2 --> Install the Adminui pre-requisite and the Adminui

Step 3 --> Disable 8dot3name back if required

Disable the 8dot3name using the FSUTIL tool by running the below

C:\>fsutil 8dot3name set C: 1

Successfully Disabled 8dot3name generation on C:

Verify the above by running the 8dot3name query one more time to confirm it got Disabled

C:\>FSUTIL.EXE 8dot3name query c: --> this is checking the status of 8dot3 on drive C

The volume state is: 1 (8dot3 name creation is disabled).

The registry state is: 2 (Per volume setting - the default).

Environment:

Release: ETRSBB99000-12.52-SiteMinder-B to B
Component: