The dashboard (SSL) does not work externally


Highly appreciated community,

The customer has switched from http to https.
The certificate was created correctly and integrated in the IIS.
Internal access via http and https works without restrictions, dashboard included, but with the exception of systemhealth.
The CRM is accessible from the outside, but the dashboard does not work.

When used internally, green check marks are displayed in the systemstatus. With external access oder internal https, however, you see many buttons in red (See screenshots).

access from protokoll dashboard working systemhealth
intern http yes
intern https yes
extern https no

We have tried these solutions without success:

Unfortunately, we can't find any clues to localize the problem in the CRM and Tomkat logs.

What else can we try?

Thank you in advance for your support.

Best regards,
Thomas

  • 0

    Add 127.0.0.1 <your external CRM url> to the hosts file

  • 0 in reply to Vega

    Hello Vega,

    Thank you very much.
    After the implementation, accessing the dashboard directly from the server via the external URL works, but not accessing it outside the server via the external URL.

    The status about the systemhealth remains as specified above.

    Are there any other suggested solutions?

  • 0 in reply to ThomasAsen

    What is the CRM version please?

  • 0 in reply to dskantor

    2021 R1 / Enterprise

  • 0

    Hi Thomas!

    I'm not sure if this issue persists or not. If it is, would you be able to provide some screenshots of specific screens that do not behave on HTTPS as they did on HTTP?

    Subsequently, what does the below value display for you in "Administration --> System --> System Behavior"? 


    To some of us "grizzled" Sage CRM veterans, "the dashboards don't work" is potentially a bag of cats that could be trying to solve with multiple potential outcomes.

  • 0 in reply to Basil Malik

    Hello Basil,

    Thank you very much for your message.
    Indeed, the problem still exists.

    The setting under "Custom server name for internal reqs" is, as with you, "">http://localhost".

    What else could we check?

    Thanks in advance for your ideas.

    Many greetings,
    Thomas

  • 0

    Hiya

    I could be wrong but you could edit the URL Rewrite, I have something in the back of my head about adjusting this to do with Dashboards over a remote connection 

    I have something in my head about changing all the entries from HTTP_HOST to 127.0.0.1

    Been a long time since I've played in here though so could be barking up the wrong tree. 

  • 0 in reply to ThomasAsen

    Good morning, Thomas!

    Hmm... without screenshots of the error or log files, there are two ways that you can go about further diagnosing the problem. That would be dissecting the log files of the CRM system and Tomcat.

    1) CRM Logs: [installed_directory]:\Program Files (x86)\Sage\CRM\CRM\Logs : these logs don't show in Sage CRM's Administration area, but provide context on what's happening with the Apache Tomcat server.

    2) Tomcat Logs: [installed_directory]:\Program Files (x86)\Sage\CRM\CRM\tomcat\logs : if you're getting an error of any kind, it can be traced back to here. I would also suggest attempting to perform some other functions that leverage the Apache Tomcat server. i.e., mail merge, export to file, etc. See if you can get additional errors to generate and refer back to the log file to somewhat trace the flow of errors.


    If you can provide screenshots of the errors the end-users are seeing, that would help get a better idea of what you mean by, "the dashboard doesn't work." 

  • 0 in reply to ThomasAsen

    Also - it could be something to do with your IIS settings. i.e. anything that accesses Sage CRM from HTTP gets redirected to HTTPS. If that's the case, it could very well be the crux of the problem depending on whether or not your internal requests are being routed properly. If you have a rule like that enabled, try disabling it and see if it fixes the issue temporarily. If it does, that also gives you something finite to solve for instead of something more abstract.

  • 0 in reply to Matthew Shaw

    Hello Matthew,
    thank you very much for the hint. Unfortunately, this did not bring the solution, but possibly a step further.

  • 0 in reply to Basil Malik

    Hello Basil,

    here is the logfile crmtomcat9-stderr.2021-08.09.log:

    2021-08-09 18:41:01 Apache Commons Daemon procrun stderr initialized.
    09-Aug-2021 18:41:01.617 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log
    Server Version: Application Server
    09-Aug-2021 18:41:01.621 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Server built: unknown
    09-Aug-2021 18:41:01.621 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Server version number: 9.0.x
    09-Aug-2021 18:41:01.621 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log OS Name: Windows Server 2016
    09-Aug-2021 18:41:01.621 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log OS Version: 10.0
    09-Aug-2021 18:41:01.622 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Architektur: x86
    09-Aug-2021 18:41:01.622 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Java Home: D:\Program Files (x86)\Sage\CRM\Services\JRE\jre8
    09-Aug-2021 18:41:01.622 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Version: 1.8.0_152-b16
    09-Aug-2021 18:41:01.622 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log JVM Hersteller: Oracle Corporation
    09-Aug-2021 18:41:01.622 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log
    CATALINA_BASE: D:\Program Files (x86)\Sage\CRM\CRM\tomcat
    09-Aug-2021 18:41:01.622 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log CATALINA_HOME: D:\Program Files (x86)\Sage\CRM\CRM\tomcat
    09-Aug-2021 18:41:01.624 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.home=D:\Program Files (x86)\Sage\CRM\CRM\tomcat
    09-Aug-2021 18:41:01.625 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dcatalina.base=D:\Program Files (x86)\Sage\CRM\CRM\tomcat
    09-Aug-2021 18:41:01.625 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Dignore.endorsed.dirs=D:\Program Files (x86)\Sage\CRM\CRM\tomcat\endorsed
    09-Aug-2021 18:41:01.625 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.io.tmpdir=D:\Program Files (x86)\Sage\CRM\CRM\tomcat\temp
    09-Aug-2021 18:41:01.625 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
    09-Aug-2021 18:41:01.625 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Djava.util.logging.config.file=D:\Program Files (x86)\Sage\CRM\CRM\tomcat\conf\logging.properties
    09-Aug-2021 18:41:01.625 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -XX:MaxPermSize=512m
    09-Aug-2021 18:41:01.625 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: exit
    09-Aug-2021 18:41:01.625 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: abort
    09-Aug-2021 18:41:01.625 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xms64m
    09-Aug-2021 18:41:01.625 INFORMATION [main] org.apache.catalina.startup.VersionLoggerListener.log Command line argument: -Xmx1024m
    09-Aug-2021 18:41:01.625 INFORMATION [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent Loaded APR based Apache Tomcat Native library [1.2.23] using APR version [1.7.0].
    09-Aug-2021 18:41:01.625 INFORMATION [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
    09-Aug-2021 18:41:01.625 INFORMATION [main] org.apache.catalina.core.AprLifecycleListener.lifecycleEvent APR/OpenSSL configuration: useAprConnector [false], useOpenSSL [true]
    09-Aug-2021 18:41:01.629 INFORMATION [main] org.apache.catalina.core.AprLifecycleListener.initializeSSL OpenSSL successfully initialized [OpenSSL 1.1.1c 28 May 2019]
    09-Aug-2021 18:41:01.880 INFORMATION [main] org.apache.coyote.AbstractProtocol.init Initialisiere ProtocolHandler["http-nio-10001"]
    09-Aug-2021 18:41:01.981 INFORMATION [main] org.apache.catalina.startup.Catalina.load Server initialization in [590] milliseconds
    09-Aug-2021 18:41:02.004 INFORMATION [main] org.apache.catalina.core.StandardService.startInternal Starting service [Catalina]
    09-Aug-2021 18:41:02.004 INFORMATION [main] org.apache.catalina.core.StandardEngine.startInternal Starting Servlet engine: [Application Server]
    09-Aug-2021 18:41:02.054 INFORMATION [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [D:\Program Files (x86)\Sage\CRM\CRM\tomcat\webapps\crmExchangeSyncEngine.war]
    09-Aug-2021 18:41:17.401 INFORMATION [main] 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.
    09-Aug-2021 18:41:25.401 INFORMATION [main] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [D:\Program Files (x86)\Sage\CRM\CRM\tomcat\webapps\crmExchangeSyncEngine.war] has finished in [23.347] ms
    09-Aug-2021 18:41:25.403 INFORMATION [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [D:\Program Files (x86)\Sage\CRM\CRM\tomcat\webapps\crmj.war]
    09-Aug-2021 18:41:36.499 INFORMATION [main] 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.
    09-Aug-2021 18:41:54.168 WARNUNG [main] java.util.prefs.WindowsPreferences.<init> Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5.
    09-Aug-2021 18:42:03.833 INFORMATION [main] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [D:\Program Files (x86)\Sage\CRM\CRM\tomcat\webapps\crmj.war] has finished in [38.430] ms
    09-Aug-2021 18:42:03.835 INFORMATION [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [D:\Program Files (x86)\Sage\CRM\CRM\tomcat\webapps\crmjspell.war]
    09-Aug-2021 18:42:03.876 INFORMATION [main] 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.
    09-Aug-2021 18:42:03.878 INFORMATION [main] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [D:\Program Files (x86)\Sage\CRM\CRM\tomcat\webapps\crmjspell.war] has finished in [43] ms
    09-Aug-2021 18:42:03.880 INFORMATION [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [D:\Program Files (x86)\Sage\CRM\CRM\tomcat\webapps\crmSPSyncEngine.war]
    09-Aug-2021 18:42:14.678 INFORMATION [main] 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.
    09-Aug-2021 18:42:17.587 INFORMATION [main] org.apache.catalina.startup.HostConfig.deployWAR Deployment of web application archive [D:\Program Files (x86)\Sage\CRM\CRM\tomcat\webapps\crmSPSyncEngine.war] has finished in [13.707] ms
    09-Aug-2021 18:42:17.590 INFORMATION [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-10001"]
    09-Aug-2021 18:42:17.599 INFORMATION [main] org.apache.catalina.startup.Catalina.start Server startup in [75.618] milliseconds
    09-Aug-2021 18:42:17.600 INFORMATION [Thread-18] org.apache.coyote.AbstractProtocol.pause Pausing ProtocolHandler ["http-nio-10001"]
    09-Aug-2021 18:42:17.656 INFORMATION [Thread-18] org.apache.catalina.core.StandardService.stopInternal Stopping service [Catalina]
    09-Aug-2021 18:43:16.974 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [crmExchangeSyncEngine] registered the JDBC driver [com.microsoft.sqlserver.jdbc.SQLServerDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    09-Aug-2021 18:43:16.975 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [crmExchangeSyncEngine] appears to have started a thread named [Log4j2-TF-9-Scheduled-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    sun.misc.Unsafe.park(Native Method)
    java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    java.lang.Thread.run(Thread.java:748)
    09-Aug-2021 18:43:16.975 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [crmExchangeSyncEngine] appears to have started a thread named [Log4j2-TF-9-Scheduled-2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    sun.misc.Unsafe.park(Native Method)
    java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
    java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    java.lang.Thread.run(Thread.java:748)
    09-Aug-2021 18:43:16.976 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [crmExchangeSyncEngine] appears to have started a thread named [Timer-0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    java.lang.Object.wait(Native Method)
    java.util.TimerThread.mainLoop(Timer.java:552)
    java.util.TimerThread.run(Timer.java:505)
    09-Aug-2021 18:43:16.976 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [crmExchangeSyncEngine] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    java.lang.Object.wait(Native Method)
    com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:534)
    09-Aug-2021 18:43:16.976 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [crmExchangeSyncEngine] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    java.lang.Object.wait(Native Method)
    com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:534)
    09-Aug-2021 18:43:16.977 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [crmExchangeSyncEngine] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    java.lang.Object.wait(Native Method)
    com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:534)
    09-Aug-2021 18:43:16.977 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [crmExchangeSyncEngine] appears to have started a thread named [Log4j2-TF-9-Scheduled-3] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    sun.misc.Unsafe.park(Native Method)
    java.util.concurrent.locks.LockSupport.park(LockSupport.java:175)
    java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2039)
    java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1088)
    java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    java.lang.Thread.run(Thread.java:748)
    09-Aug-2021 18:43:16.977 SCHWERWIEGEND [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [crmExchangeSyncEngine] created a ThreadLocal with key of type [java.lang.ThreadLocal] (value [java.lang.ThreadLocal@1921637]) and a value of type [org.apache.cxf.bus.CXFBusImpl] (value [org.apache.cxf.bus.CXFBusImpl@a06744]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
    09-Aug-2021 18:43:16.978 SCHWERWIEGEND [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [crmExchangeSyncEngine] created a ThreadLocal with key of type [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1] (value [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1@1b31c1a]) and a value of type [com.microsoft.sqlserver.jdbc.ActivityId] (value [6a956bdb-7fcf-4f9b-8d7c-6cb239aafc03-2]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
    09-Aug-2021 18:43:16.978 SCHWERWIEGEND [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [crmExchangeSyncEngine] created a ThreadLocal with key of type [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1] (value [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1@1b31c1a]) and a value of type [com.microsoft.sqlserver.jdbc.ActivityId] (value [261a701e-2ad3-4e34-97ba-c35f2807c6c9-1]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
    09-Aug-2021 18:43:16.978 SCHWERWIEGEND [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [crmExchangeSyncEngine] created a ThreadLocal with key of type [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1] (value [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1@1b31c1a]) and a value of type [com.microsoft.sqlserver.jdbc.ActivityId] (value [1a7bf9ca-2fca-4c1b-a977-e97611d98432-2]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
    09-Aug-2021 18:43:17.050 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [crmj] registered the JDBC driver [net.sf.log4jdbc.DriverSpy] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    09-Aug-2021 18:43:17.050 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [crmj] registered the JDBC driver [com.microsoft.sqlserver.jdbc.SQLServerDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    09-Aug-2021 18:43:17.051 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesJdbc The web application [crmj] registered the JDBC driver [oracle.jdbc.OracleDriver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.
    09-Aug-2021 18:43:17.051 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [crmj] appears to have started a thread named [Log4j2-TF-21-Scheduled-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    sun.misc.Unsafe.park(Native Method)
    java.util.concurrent.locks.LockSupport.parkNanos(LockSupport.java:215)
    java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.awaitNanos(AbstractQueuedSynchronizer.java:2078)
    java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:1093)
    java.util.concurrent.ScheduledThreadPoolExecutor$DelayedWorkQueue.take(ScheduledThreadPoolExecutor.java:809)
    java.util.concurrent.ThreadPoolExecutor.getTask(ThreadPoolExecutor.java:1074)
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1134)
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    java.lang.Thread.run(Thread.java:748)
    09-Aug-2021 18:43:17.051 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [crmj] appears to have started a thread named [Timer-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    java.lang.Object.wait(Native Method)
    java.util.TimerThread.mainLoop(Timer.java:552)
    java.util.TimerThread.run(Timer.java:505)
    09-Aug-2021 18:43:17.052 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [crmj] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#0] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    java.lang.Object.wait(Native Method)
    com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:534)
    09-Aug-2021 18:43:17.052 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [crmj] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    java.lang.Object.wait(Native Method)
    com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:534)
    09-Aug-2021 18:43:17.052 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [crmj] appears to have started a thread named [com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread-#2] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    java.lang.Object.wait(Native Method)
    com.mchange.v2.async.ThreadPoolAsynchronousRunner$PoolThread.run(ThreadPoolAsynchronousRunner.java:534)
    09-Aug-2021 18:43:17.053 WARNUNG [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.clearReferencesThreads The web application [crmj] appears to have started a thread named [taskScheduler-1] but has failed to stop it. This is very likely to create a memory leak. Stack trace of thread:
    java.lang.Object.wait(Native Method)
    java.lang.Thread.join(Thread.java:1252)
    java.lang.Thread.join(Thread.java:1326)
    org.apache.commons.exec.PumpStreamHandler.stop(PumpStreamHandler.java:180)
    org.apache.commons.exec.DefaultExecutor.executeInternal(DefaultExecutor.java:363)
    org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:160)
    org.apache.commons.exec.DefaultExecutor.execute(DefaultExecutor.java:147)
    com.sage.crm.core.async.ProcessWatchdog.gatherJavaProcesses(ProcessWatchdog.java:169)
    com.sage.crm.core.async.ProcessWatchdog.run(ProcessWatchdog.java:66)
    sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    java.lang.reflect.Method.invoke(Method.java:498)
    org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:84)
    org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
    java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
    java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
    java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    java.lang.Thread.run(Thread.java:748)
    09-Aug-2021 18:43:17.053 SCHWERWIEGEND [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [crmj] created a ThreadLocal with key of type [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1] (value [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1@7af48b]) and a value of type [com.microsoft.sqlserver.jdbc.ActivityId] (value [c2e2a811-6b46-4f30-97fe-f3cf7b2f75d8-0]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
    09-Aug-2021 18:43:17.054 SCHWERWIEGEND [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [crmj] created a ThreadLocal with key of type [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1] (value [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1@7af48b]) and a value of type [com.microsoft.sqlserver.jdbc.ActivityId] (value [db402be8-2b17-47ab-a11e-03cd39f6ea00-2]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
    09-Aug-2021 18:43:17.054 SCHWERWIEGEND [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [crmj] created a ThreadLocal with key of type [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1] (value [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1@7af48b]) and a value of type [com.microsoft.sqlserver.jdbc.ActivityId] (value [2f4960f2-671a-4945-977a-5fe4a1904886-1]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
    09-Aug-2021 18:43:17.054 SCHWERWIEGEND [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [crmj] created a ThreadLocal with key of type [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1] (value [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1@7af48b]) and a value of type [com.microsoft.sqlserver.jdbc.ActivityId] (value [193cf496-3c97-4595-9fed-aebc497aad6f-2]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
    09-Aug-2021 18:43:17.054 SCHWERWIEGEND [Thread-18] org.apache.catalina.loader.WebappClassLoaderBase.checkThreadLocalMapForLeaks The web application [crmj] created a ThreadLocal with key of type [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1] (value [com.microsoft.sqlserver.jdbc.ActivityCorrelator$1@7af48b]) and a value of type [com.microsoft.sqlserver.jdbc.ActivityId] (value [54a2bfe4-e696-40e9-bd3d-ed4f17d39e1c-0]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.
    09-Aug-2021 18:43:17.054 INFORMATION [taskScheduler-1] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load [com.sage.crm.core.util.spreadsheet.model.Workbook]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
    java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [com.sage.crm.core.util.spreadsheet.model.Workbook]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
    at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1385)
    at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1373)
    at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1226)
    at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1188)
    at java.lang.ClassLoader.defineClass1(Native Method)
    at java.lang.ClassLoader.defineClass(ClassLoader.java:763)
    at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
    at org.apache.catalina.loader.WebappClassLoaderBase.findClassInternal(WebappClassLoaderBase.java:2419)
    at org.apache.catalina.loader.WebappClassLoaderBase.findClass(WebappClassLoaderBase.java:865)
    at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1334)
    at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1188)
    at com.sage.crm.core.async.ProcessWatchdog.gatherJavaProcesses(ProcessWatchdog.java:179)
    at com.sage.crm.core.async.ProcessWatchdog.run(ProcessWatchdog.java:66)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:498)
    at org.springframework.scheduling.support.ScheduledMethodRunnable.run(ScheduledMethodRunnable.java:84)
    at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:54)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
    09-Aug-2021 18:43:17.056 INFORMATION [taskScheduler-1] org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading Illegal access: this web application instance has been stopped already. Could not load [org.apache.logging.log4j.core.impl.ThrowableProxy]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
    java.lang.IllegalStateException: Illegal access: this web application instance has been stopped already. Could not load [org.apache.logging.log4j.core.impl.ThrowableProxy]. The following stack trace is thrown for debugging purposes as well as to attempt to terminate the thread which caused the illegal access.
    at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForResourceLoading(WebappClassLoaderBase.java:1385)
    at org.apache.catalina.loader.WebappClassLoaderBase.checkStateForClassLoading(WebappClassLoaderBase.java:1373)
    at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1226)
    at org.apache.catalina.loader.WebappClassLoaderBase.loadClass(WebappClassLoaderBase.java:1188)
    at org.apache.logging.log4j.core.impl.Log4jLogEvent.getThrownProxy(Log4jLogEvent.java:629)
    at org.apache.logging.log4j.core.pattern.ExtendedThrowablePatternConverter.format(ExtendedThrowablePatternConverter.java:63)
    at org.apache.logging.log4j.core.pattern.PatternFormatter.format(PatternFormatter.java:38)
    at org.apache.logging.log4j.core.layout.PatternLayout$PatternSerializer.toSerializable(PatternLayout.java:345)
    at org.apache.logging.log4j.core.layout.PatternLayout.toText(PatternLayout.java:244)
    at org.apache.logging.log4j.core.layout.PatternLayout.encode(PatternLayout.java:229)
    at org.apache.logging.log4j.core.layout.PatternLayout.encode(PatternLayout.java:59)
    at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.directEncodeEvent(AbstractOutputStreamAppender.java:197)
    at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.tryAppend(AbstractOutputStreamAppender.java:190)
    at org.apache.logging.log4j.core.appender.AbstractOutputStreamAppender.append(AbstractOutputStreamAppender.java:181)
    at org.apache.logging.log4j.core.appender.RollingFileAppender.append(RollingFileAppender.java:312)
    at org.apache.logging.log4j.core.config.AppenderControl.tryCallAppender(AppenderControl.java:156)
    at org.apache.logging.log4j.core.config.AppenderControl.callAppender0(AppenderControl.java:129)
    at org.apache.logging.log4j.core.config.AppenderControl.callAppenderPreventRecursion(AppenderControl.java:120)
    at org.apache.logging.log4j.core.config.AppenderControl.callAppender(AppenderControl.java:84)
    at org.apache.logging.log4j.core.config.LoggerConfig.callAppenders(LoggerConfig.java:543)
    at org.apache.logging.log4j.core.config.LoggerConfig.processLogEvent(LoggerConfig.java:502)
    at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:485)
    at org.apache.logging.log4j.core.config.LoggerConfig.log(LoggerConfig.java:460)
    at org.apache.logging.log4j.core.config.AwaitCompletionReliabilityStrategy.log(AwaitCompletionReliabilityStrategy.java:82)
    at org.apache.logging.log4j.core.Logger.log(Logger.java:161)
    at org.apache.logging.log4j.spi.AbstractLogger.tryLogMessage(AbstractLogger.java:2198)
    at org.apache.logging.log4j.spi.AbstractLogger.logMessageTrackRecursion(AbstractLogger.java:2152)
    at org.apache.logging.log4j.spi.AbstractLogger.logMessageSafely(AbstractLogger.java:2135)
    at org.apache.logging.log4j.spi.AbstractLogger.logMessage(AbstractLogger.java:2011)
    at org.apache.logging.log4j.spi.AbstractLogger.logIfEnabled(AbstractLogger.java:1983)
    at org.apache.commons.logging.LogAdapter$Log4jLog.log(LogAdapter.java:258)
    at org.apache.commons.logging.LogAdapter$Log4jLog.error(LogAdapter.java:210)
    at org.springframework.scheduling.support.TaskUtils$LoggingErrorHandler.handleError(TaskUtils.java:95)
    at org.springframework.scheduling.support.DelegatingErrorHandlingRunnable.run(DelegatingErrorHandlingRunnable.java:60)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
    at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
    at java.lang.Thread.run(Thread.java:748)
    09-Aug-2021 18:43:17.066 INFORMATION [Thread-18] org.apache.coyote.AbstractProtocol.stop Stopping ProtocolHandler ["http-nio-10001"]
    09-Aug-2021 18:43:17.068 INFORMATION [Thread-18] org.apache.coyote.AbstractProtocol.destroy Destroying ProtocolHandler ["http-nio-10001"]
    Java HotSpot(TM) Client VM warning: ignoring option MaxPermSize=512m; support was removed in 8.0

  • 0 in reply to ThomasAsen

    I did a double-check on the above, and I didn't see anything that is standing out. Can you provide a screenshot of the error you're seeing from a user's perspective?

    Ideally, you should be able to log onto the server (">localhost/[crm_instance]" and have no issues seeing the dashboard. But what do you see when logging in via the external URL with https? "The Dashboard has experienced an error" message? Or something else?

    I wanted to call out the two behaviors as you should not see a difference between behavior within the network (http://localhost or http://[server_name]) and the external dashboard. If you break one while trying to fix the other, you're creating more problems for yourself. It's good to be mindful of that.

    All of that said... two questions:
    1) Any insight into the error message that a user sees when trying to access via https?
    2) Do you have any http to https reroutes that exist on your IIS server?

  • 0 in reply to ThomasAsen

    can you check this setting in system behavior

    Custom server name for internal reqs:
    http://localhost  i believe it sld be https

  • 0 in reply to jtweardy

    Thank you very much for your approach. But unfortunately that did not work either.
    I am desperate.

    Could it be that the firewall is blocking something? But if the internal requests are delegated directly to the "localhost" it should not matter, or am I wrong?