Community Tip - Did you get an answer that solved your problem? Please mark it as an Accepted Solution so others with the same problem can find the answer easily. X
Check that the database is in working order. Profiling it during startup can help spot any long running queries that could be being executed. Can you tell if its timing out or stuck for a period at a certain step? You should ensure that the system is tuned properly based on the Windchill configurator (WCA). It should have the right amount of memory to start up and operate.
Additionally....
Anti-virus can add a lot of overhead/delay to starting Windchill if it wasn't configured for Windchill.
Infrastructure issues that show as poor disk IO can really slow down startup.
Tomcat scans codebase for jar files on startup. Poor disk performance can make this a VERY long process.
And more "Additionally..."
See article: https://www.ptc.com/en/support/article/CS434417
I have implemented that here in our 13.0.2 production and my 13.1.2 test server.
