Apache Tomcat Applicationcontainers Windows Services Would Not Start After Windows Server Updates Were Automatically Applied To The Siebel Windows Servers Environment.: Windows Could Not Start The Apache Tomcat 9.0 SiebelApplicationContainer Error 1053
(Doc ID 2938114.1)
Last updated on APRIL 17, 2023
Applies to:
Siebel CRM - Version 17.0 [IP2017] and laterInformation in this document applies to any platform.
Symptoms
Apache Tomcat Applicationcontainers Windows Services would not start after Windows Server software updates were automatically applied to the Siebel Windows Servers environment.
After the Windows Server was shutdown and restarted the following Windows Server pop up Error 1053 occurred when starting the Apache Tomcat Applicationcontainers Windows Service.
Windows could not start the Apache Tomcat 9.0 SiebelApplicationContainer_Siebel_Home_c_ai_External service on Local Computer.
Error 1053: The service did not respond to the start or control request in a timely fashion.
STEPS TAKEN
-----------------------
1. Windows Server Update applied to the Siebel Windows Server environment.
2. Stop and restart the Siebel Windows Server.
3. Observe the Apache Tomcat Windows Service does not start and the Error 1053 Windows Pop Up message.
Changes
Windows Server Updates were automatically applied to the Siebel Windows Server environment.
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |