12.2 OEM on Win64

Posted by tpavlovic on 13-Apr-2020 08:15

Windows 10 v1909

I installed 12.2 from OEDK (OE studio/OE Mgt. SE/OE Adv. Ent. RDBMS/Progress Dev Studio OE) and the Progress OpenEdge Management Service won't start. When I installed it I saw in services that Progress OpenEdge AdminServer Service 12.2 (64-bit) was set to manual start and Progress OpenEdge Management Service 12.2 to automatic start and it was running. Then I changed the AdminServer to start automagically and rebooted. Now the AdminService is started and Management Service is not and when I try to start it manually I get an error and this is what is writes to EventLog:

The Progress OpenEdge Management Service 12.2 service terminated with the following service-specific error: 

Incorrect function.

AdminService is running and all my databases are started and all command line utilities work (dbman/nsman/pasman) but I can't open the Management Console in the browser. I looked into admserv.log but I can't see anything weird there. Is there anything else I can look at? Does the OEM have some other .log file or what?

Community Groups - Forum

All Replies

Posted by Kondra Mohan Raju on 13-Apr-2020 09:28

Yes, OEM has its own .log file from 12.0 version. its at $oemgmt/logs/fathom.<date>.log.

Please check if there is any error in the log

Posted by tpavlovic on 13-Apr-2020 11:27

This is what I've found:

2020-04-13 09:45:14,138 ERROR [org.apache.shiro.web.env.EnvironmentLoader] [Catalina-utility-1] - Shiro environment initialization failed
java.lang.NoClassDefFoundError: Could not initialize class com.progress.isq.ipqos.Initialization

...

2020-04-13 09:45:14,865 INFO [Fathom] [Catalina-utility-1] - Unregistered fathom extension Fathom
2020-04-13 09:45:14,865 INFO [Fathom] [Catalina-utility-1] - Shutting down fathom web application
2020-04-13 09:45:14,918 INFO [Fathom] [Catalina-utility-1] - Error accessing message #7020267394140481452.

I have no idea what is that supposed to mean.

Also there are error messages in other .log files in that folder, e.g.

Catalina.log:

13-Apr-2020 09:45:09.304 INFO [main] org.apache.coyote.AbstractProtocol.init - Initializing ProtocolHandler ["http-nio-9090"]
13-Apr-2020 09:45:09.323 INFO [main] org.apache.coyote.AbstractProtocol.init - Initializing ProtocolHandler ["https-jsse-nio-9443"]
13-Apr-2020 09:45:09.325 INFO [main] org.apache.catalina.startup.Catalina.load - Server initialization in [568] milliseconds
13-Apr-2020 09:45:09.447 INFO [main] o.a.catalina.core.StandardService.startInternal - Starting service [Catalina]
13-Apr-2020 09:45:09.448 INFO [main] o.a.catalina.core.StandardEngine.startInternal - Starting Servlet engine: [Apache Tomcat/9.0.30]
13-Apr-2020 09:45:09.841 INFO [Catalina-utility-1] o.apache.catalina.startup.HostConfig.deployWAR - Deploying web application archive [D:\oemgmt64\webapps\ROOT.war]
13-Apr-2020 09:45:13.474 WARN [Catalina-utility-1] o.a.t.util.scan.StandardJarScanner.scan - Failed to scan JAR [war:file:/D:/oemgmt64/webapps/ROOT.war*/WEB-INF/lib/encoder-jsp-1.2.2.jar] from /WEB-INF/lib
java.nio.file.AccessDeniedException: D:\oemgmt64\temp\jar_cache11418208132219591695.tmp

...

13-Apr-2020 09:45:14.539 ERROR [Catalina-utility-1] o.a.catalina.core.StandardContext.startInternal - One or more listeners failed to start. Full details will be found in the appropriate container log file
13-Apr-2020 09:45:14.855 WARN [Catalina-utility-1] o.a.c.util.SessionIdGeneratorBase.createSecureRandom - Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [315] milliseconds.
13-Apr-2020 09:45:14.856 ERROR [Catalina-utility-1] o.a.catalina.core.StandardContext.startInternal - Context [] startup failed due to previous errors
13-Apr-2020 09:45:14.928 INFO [Catalina-utility-1] o.apache.catalina.startup.HostConfig.deployWAR - Deployment of web application archive [D:\oemgmt64\webapps\ROOT.war] has finished in [5,087] ms

...

common-daemon.log:

[2020-04-13 09:45:05] [info] [15252] Apache Commons Daemon procrun (1.2.2.0 64-bit) started.
[2020-04-13 09:45:06] [info] [15252] Running Service 'fathom_12.2'...
[2020-04-13 09:45:06] [info] [11384] Starting service...
[2020-04-13 09:45:08] [info] [11384] Service started in 1555 milliseconds.
[2020-04-13 09:53:13] [info] [13776] Console SHUTDOWN event signaled.
[2020-04-13 09:53:13] [info] [13776] Stopping service...
[2020-04-13 09:53:14] [info] [13776] Service stop thread completed.
[2020-04-13 09:53:14] [info] [15252] Run service finished.
[2020-04-13 09:53:15] [info] [15252] Apache Commons Daemon procrun finished.
[2020-04-13 09:53:44] [info] [ 5696] Apache Commons Daemon procrun (1.2.2.0 64-bit) started.
[2020-04-13 09:53:44] [info] [ 5696] Running Service 'fathom_12.2'...
[2020-04-13 09:53:44] [info] [ 6424] Starting service...
[2020-04-13 09:53:44] [error] [ 6424] Pid file 'D:\oemgmt64\logs\catalina-fathom_12.2.pid' exists.
[2020-04-13 09:53:44] [error] [ 6424] Access is denied.
[2020-04-13 09:53:44] [error] [ 6424] ServiceStart returned 1.
[2020-04-13 09:53:44] [error] [ 6424] Access is denied.
[2020-04-13 09:53:44] [info] [ 5696] Run service finished.
[2020-04-13 09:53:44] [info] [ 5696] Apache Commons Daemon procrun finished.

Catalina.out:

2020-04-13 09:45:06 Apache Commons Daemon procrun stdout initialized.
2020-04-13 09:45:06 Apache Commons Daemon procrun stderr initialized.
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.catalina.loader.WebappClassLoaderBase (file:/D:/oemgmt64/lib/catalina.jar) to field java.io.ObjectStreamClass$Caches.localDescs
WARNING: Please consider reporting this to the maintainers of org.apache.catalina.loader.WebappClassLoaderBase
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
INFO [main] o.a.catalina.core.StandardEngine.startInternal - Starting Servlet engine: [Apache Tomcat/9.0.30]
13-Apr-2020 09:45:09.841 INFO [Catalina-utility-1] o.apache.catalina.startup.HostConfig.deployWAR - Deploying web application archive [D:\oemgmt64\webapps\ROOT.war]
13-Apr-2020 09:45:13.474 WARN [Catalina-utility-1] o.a.t.util.scan.StandardJarScanner.scan - Failed to scan JAR [war:file:/D:/oemgmt64/webapps/ROOT.war*/WEB-INF/lib/encoder-jsp-1.2.2.jar] from /WEB-INF/lib
java.nio.file.AccessDeniedException: D:\oemgmt64\temp\jar_cache11418208132219591695.tmp

...

13-Apr-2020 09:45:13.680 INFO [Catalina-utility-1] org.apache.jasper.servlet.TldScanner.scanJars - At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Warning: Nashorn engine is planned to be removed from a future JDK release
13-Apr-2020 09:45:14.539 ERROR [Catalina-utility-1] o.a.catalina.core.StandardContext.startInternal - One or more listeners failed to start. Full details will be found in the appropriate container log file
13-Apr-2020 09:45:14.855 WARN [Catalina-utility-1] o.a.c.util.SessionIdGeneratorBase.createSecureRandom - Creation of SecureRandom instance for session ID generation using [SHA1PRNG] took [315] milliseconds.
13-Apr-2020 09:45:14.856 ERROR [Catalina-utility-1] o.a.catalina.core.StandardContext.startInternal - Context [] startup failed due to previous errors
13-Apr-2020 09:45:14.928 INFO [Catalina-utility-1] o.apache.catalina.startup.HostConfig.deployWAR - Deployment of web application archive [D:\oemgmt64\webapps\ROOT.war] has finished in [5,087] ms


localhost.log:

13-Apr-2020 09:45:13.972 ERROR [Catalina-utility-1] o.a.catalina.core.StandardContext.listenerStart - Exception sending context initialized event to listener instance of class [com.progress.fathom.servlet.FathomContextInitializer]
com.progress.fathom.servlet.FathomContextInitException: Unable to load PROMSGS: Unable to locate promsgs file at environment variable ''PROMSGS'', system property ''Install.Dir'' or environment variable ''DLC''
...
Caused by: com.progress.common.message.IProMessage$ProMessageException: Unable to locate promsgs file at environment variable 'PROMSGS', system property 'Install.Dir' or environment variable 'DLC'
...
13-Apr-2020 09:45:13.978 ERROR [Catalina-utility-1] o.a.catalina.core.StandardContext.listenerStart - Exception sending context initialized event to listener instance of class [com.progress.fathom.extension.ExtensionLoaderListener]
java.lang.ExceptionInInitializerError: null
...

There is no PROMSGS environment variable (and I've ever used it in my life), Install.Dir and DLC point to correct location.

The only thing I can think of is that now in 12.2 you get the warning if you're not installing on drive C: and you have to enable 8.3 file names on this drive and I did it. Although I don't know why this has to be done and why would 8.3 names affect anything on Windows 10.

Posted by tpavlovic on 13-Apr-2020 12:35

I just reinstalled it and did not make any changes to any config files and the Progress OpendEdge Management Service 12.2 is running and this is what I get when I try localhost:9090

so even if it is running there is something wrong.

The last thing I could try is to install it on C: drive and see if it makes any difference.

Posted by tpavlovic on 14-Apr-2020 06:10

Just installed it on C: drive and everything works fine even after reboot.

This is unacceptable.

I'll try again with D: after I enable system-wide 8dot3 filenames.

Posted by tpavlovic on 14-Apr-2020 09:00

I enabled system-wide 8dot3 names to no avail. If you install any product that includes OEM it definitely has to be installed on C: no matter what.

This worked perfectly fine on all versions before including 12.1. What they did to screw it up is beyond my imagination.

I will contact tech-support after I gather some more nerves.

Posted by tpavlovic on 14-Apr-2020 09:00

I enabled system-wide 8dot3 names to no avail. If you install any product that includes OEM it definitely has to be installed on C: no matter what.

This worked perfectly fine on all versions before including 12.1. What they did to screw it up is beyond my imagination.

I will contact tech-support after I gather some more nerves.

This thread is closed