My Oracle Support Banner

"On Windows: After Upgrading OHS Standalone from 12.2.1.3 to 12.2.1.4, Startup Failed With <OHS-4033> <Unable to create SSLSocketFactory> in ohs_nm.log" (Doc ID 2751601.1)

Last updated on FEBRUARY 10, 2021

Applies to:

Oracle HTTP Server - Version 12.2.1.3.0 to 12.2.1.4.0 [Release 12c]
Microsoft Windows x64 (64-bit) - OS Version: 7

Symptoms

After upgrading the 12.2.1.3 standalone ohs to 12.2.1.4 version on Windows 64 bit OS, 

startComponent.cmd ohs1  failing with following errors

 

 

 

 

 

Changes

1)  Installed 12.2.1.3 standalone OHS on windows domain

2) Applied all CPU patches till date

 OHS_12213\OPatch>opatch lspatches
27323998;One-off
31750289;OAM WEBGATE BUNDLE PATCH 12.2.1.3.200813
29650702;One-off
31232139;OSS BUNDLE PATCH 12.2.1.3.200714
31876370;OHS (NATIVE) BUNDLE PATCH 12.2.1.3.200911
32300397;WLS PATCH SET UPDATE 12.2.1.3.201217
26550599;26550599:MERGE REQUEST ON TOP OF WINDOWS DB BP 12.1.0.2.170117 FOR BUGS 26248143 26374105
26355633;One-off
26287183;One-off
26261906;One-off
26051289;One-off
25549931;
25360603;25360603:LINK FAILURES DUE TO UNDEFINED SYMBOL IN NAUTAB.OBJ
25115951;WINDOWS DB BUNDLE PATCH 12.1.0.2.170117(64bit):25115951

3) Created a standalone OHS Domain

4) Able to bring with the servers

5) installed 12.2.1.4 standalone OHS on separate oracle home

6) Ran Reconfig.cmd and ua.cmd with out any errors

7) started the nodemanger 

8) starting ohs failed with following messages in ohs_nm.log

<SEVERE> <OHS-4033> <Unable to create SSLSocketFactory>
<SEVERE> <OHS-0> <The filename, directory name, or volume label syntax is incorrect>

 

 

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
Changes
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.