SAP Knowledge Base Article - Preview

1331062 - Tomcat 5.5 (or WACS) doesn't start up anymore after applying Windows Update patches from April 2009


  • Tomcat wont start up, returns to Stopped status
  • Web Application Container Server (WACS) changes to a failed state
  • In Windows Event Viewer System log file, an error occurs on Service Control Manager. Event ID 7024:

The Apache Tomcat 5.5.20 service terminated with service-specific error 0 (0x0).
For more information, see Help and Support Center at

In Tomcat jakarta log file, the following error appears:

[2009-04-16 12:33:08] [info] Running Service...
[2009-04-16 12:33:08] [info] Starting service...
[2009-04-16 12:33:08] [info] Error occurred during initialization of VM
[2009-04-16 12:33:08] [info] Could not reserve enough space for object heap
[2009-04-16 12:33:08] [info]
[2009-04-16 12:33:08] [409  javajni.c] [error] CreateJavaVM Failed
[2009-04-16 12:33:08] [930  prunsrv.c] [error] Failed initializing java C:\Program Files\Business Objects\Tomcat55\bin\bootstrap.jar;C:\Program Files\Business Objects\javasdk\lib\tools.jar
[2009-04-16 12:33:08] [1179 prunsrv.c] [error] ServiceStart returned 2
[2009-04-16 12:33:08] [info] Run service finished.
[2009-04-16 12:33:08] [info] Procrun finished.



  • Business Objects Enterprise XI 3.0 with Tomcat 5.5.20
  • Business Objects Enterprise XI 3.1 with Tomcat 5.5.20
  • Web Application Container Server (WACS)
  • Windows 2003r2 SP2 32bits
  • Windows Update patch of April 2009 KB956572:
  • Product

    SAP BusinessObjects Enterprise XI 3.0 ; SAP BusinessObjects Enterprise XI 3.1


    KBA , BI-BIP-DEP , Webapp Deployment, Networking, Vulnerabilities, Webservices , Problem

    About this page

    This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

    Search for additional results

    Visit SAP Support Portal's SAP Notes and KBA Search.