Access Gateway services failed to start post In-place upgrade from W2016 to W2019 fail with R12.8 SP6a version
search cancel

Access Gateway services failed to start post In-place upgrade from W2016 to W2019 fail with R12.8 SP6a version

book

Article ID: 246337

calendar_today

Updated On:

Products

SITEMINDER

Issue/Introduction

Access Gateway R12.8 SP6a services failed to start Post OS upgrade from Windows 2016 to Windows 2019.

 

Environment

Release : 12.8.06a

Component : SITEMINDER - Access Gateway

Resolution

Observed that highlighted  registry entries are missing post upgrade of OS from Windows 2016 to Windows2019. 

On adding the below highlighted registry has resolved the issue for Access gateway services issue.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\AppID\{F5272D2C-B8F8-46F5-A3D6-A68F67D308E2}]
@="SpsTomcatService"
"LocalService"="SpsTomcatService"
"ServiceParameters"="-Service"

Additional Information

More precisely this is an OS upgradation issue and the upgradation should handle the applications and data properly.

It has also been observed in some cases that upon upgrade the requests were not reaching tomcat and not leaving a trace.

The only visible error was

com.ca.sps.adminui.backingbean.HttpRequestWrapperBean - no protocol: https

in file httpd logs.

To resolve this additional error please run

configssl.bat -enable