Skip to Content
author's profile photo Former Member
Former Member

EP - AS Java instance taking 2+ hours to come up!

I've recently installed Enterprise Portal 7 but configuring it is proving difficult. Every time I start the service in MMC the AS Java instance is taking about 2hrs 20mins to come up!

The Message Srv / ENQ instance comes up in seconds.

I get the following error message in the Java based MMC :

javax.xml.rpc.soap.SOAPFaultException: JsfOpenAdmin failed: object not found












at Source)

This error occurs every 30 seconds for about 2:20hrs then the instance comes up (none of the Java instance log files are created till this time). Once the system is up, I can login and the instance performs as expected.

This is the 1st Java instance I've installed (have done many ABAP instances) so apologies if i've missed something obvious!

Any suggestions?



Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Aug 04, 2010 at 11:45 AM


    Was it the first ever startup which took 2+ hours or every startup ? Because thefirst one is VERY long because thousands of files are to be created from the database.

    The SAP AS Java is always very lon to come up compared to the ABAP AS. Here, on the same hardware, the ABAP AS takes 30 seconds to come up and the JAVA server takes 10 minutes if the antivirus on access scan is disabled. It takes up to 20 minutes if the antivirus is enabled.

    So if you use Windows, check the antivirus status on the server.



    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Finally solved!!!

      The issue was caused by wrong service names in strdbsj2ee.cmd. We are using a Named SQL instance which is not called correctly in strdbsj2ee.cmd.

      strdbs2jee.cmd has the following lines in it :

      ntscmgr start MSSQLSERVER -m computername

      ntscmgr start SQLSERVERAGENT -m computername

      this needs to be changed to :

      ntscmgr start MSSQL$<SQL_instance_name> -m computername

      ntscmgr start SQLAGENT$<SQL_instance_name> -m computername

      This solution is from OSS 755490. Please read for full explaination.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.