My Oracle Support Banner

FRDomain Admin Server fails to start (Doc ID 2425455.1)

Last updated on DECEMBER 04, 2019

Applies to:

Oracle Clinical - Version 5.0.1 to 5.2.0 [Release 5.0 to 5.2.0]
Information in this document applies to any platform.

Symptoms

The automatic startup of OC services steps were followed as per section 'Setting Up Automatic Startup in Release 5.0.1 and Higher' which is documented in 'Creating Scripts to Automatically Start the Admin and Managed Servers for RDC Onsite and TMS (Doc ID 1628413.1)'.

However, after restarting the OC 5.0.1 Application server only the 'OPADomain' Admin Server and the managed 'OpaServer1' server are RUNNING. The 'FRDomain' Admin Server failed to start which in turn means the managed servers (WLS_FORMS and WLS_REPORTS) also failed to start. The following errors appeared in the FRDomain 'auto start' log files :

===================
autostartfrdomain2.err.txt :
===================
WARNING - Unable to create log file <C:\Oracle\MIDDLE~1\modules/../logs/wlst_20140820172059.log>.
Problem invoking WLST - Traceback (innermost last):
File "c:\opapps50\config\autostartfrdomainscript.py", line 3, in ?
File "<iostream>", line 22, in connect
File "<iostream>", line 648, in raiseWLSTException
WLSTException: Error occured while performing connect : Error getting the initial context. There is no server running at t3://localhost:7001
Use dumpStack() to view the full stacktrace

 

You have tried the solution in Note: 'FRDomain' Admin Server fails to start when the OC 5.0.1 Application Server is rebooted. (Doc ID 1922513.1) but the issue persists.

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Cause
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.