As it turns out, this is caused by a report engine log-level setting down in a file "web.xml" the deployment webapps "application" (in our case, qcbin) WEB-INF folder:

Here are the steps to fix the problem:

Go into this file web.xml in C:ProgramDataMicro FocusALMwebappsqcbinWEB-INF

Change the following log level from "WARNING" to "OFF":

<!-- BIRT PARAM: Report engine log level. -->

<context-param>

<param-name>BIRT_VIEWER_LOG_LEVEL</param-name>

<param-value>OFF</param-value>

</context-param>

Then STOP/START the service.

Please note:  If you are a user of LoadRunner Enterprise (LRE) (Performance Center) 12.6x with ALM 12.60 (patch 1 or 2) you are also effect by this java limitation

If you must upgrade the Java, it is mandatory to upgrade your LRE 12.6x to LRE 2020.x, as LRE 2020.x and high don't use Java.

I suggest you try working with a build less than 255.

I just tested this with ALM 12.6 and Java 8.261 (BUILD > 255) and it failed in my lab.
Then, I pointed to Java 8.221 (BUILD < 255) and it worked fine.

On a hunch, I also tried an open-source JAVA -- (https://adoptopenjdk.net/?variant=openjdk8&jvmVariant=hotspot)
And they are also at build 261 (OpenJDK8.261), AND it failed starting ALM the same way.

I tried OpenJDK8.252 (Java 8 build 252 equivalent) and their (NOT SUPPORTED for ALM by MicroFocus) JDK 11, and it worked.

*** CAREFUL!  Using a NEWER, unsupported JAVA 9, 10, 11 may not work completely as there are some deprecated classes ALM might need. -- You were warned! ***

FYI, ALM/QC 12.6 and 15.x only officially support JAVA 8 or Open JDK 8 -- specific BUILD numbers are not mentioned.

Perhaps you can get a variance to allow a build lower than 255.

In my recent answer, I explain WHY we really don't recommend changing JAVA after installation of ALM -- this is yet another reason.

https://eyeontesting.com/answers/our-systems-guys-want-to-upgrade-java-used-by-alm-15-will-that-be-a-problem/#gsc.tab=0