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

cannot load J2EE Server

Posted on Oct 16, 2006 at 07:09 AM 12 Views

Hello,

I have installed the SAP ERP 2005 : ECC 6.0 with the both Java and ABAP Application Server.

But I have now a problem with the disp+work.exe still yellow.

In the J2EE process Table, the dispatcher and server0 have the statut "Starting Framework".

In the std_server0.out file, I have this :

SAP J2EE Engine Version 7.00 PatchLevel is starting...

Loading: LogManager ... 1969 ms.

Loading: PoolManager ... 15 ms.

Loading: ApplicationThreadManager ... 266 ms.

Loading: ThreadManager ... 62 ms.

Loading: IpVerificationManager ... 63 ms.

Loading: ClassLoaderManager ... 62 ms.

Loading: ClusterManager ... 844 ms.

Loading: LockingManager ...

The server cannot load the LockingManager !

What can I do ?

Regards,

Mathieu

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

2 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Oct 16, 2006 at 09:09 AM
    0

    Hi

    Make an entry in

    C:\WINDOWS\system32\drivers\etc\services

    <SAPMESSAGESERVER> <PORT>/tcp

    See this Thread

    /message/2565424#2565424 [original link is broken]

    Kind Regards

    Mukesh

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member
      Oct 16, 2006 at 09:47 AM

      Hi,

      Thank you for your help, but I have already read the thread, but no solution was found for me !

      In C:\WINDOWS\system32\drivers\etc\services I have already this entry !

      Best regards,

      Mathieu

  • author's profile photo Benny Schaich-Lebek
    Benny Schaich-Lebek
    Posted on Oct 16, 2006 at 03:12 PM
    0

    Check the error messages from the logs.

    Regards,

    Benny

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member
      Oct 18, 2006 at 05:53 AM

      Hi,

      problem solved by SAP Support :

      "The first problem was that in the SCS instance there was no running

      enqueue server as its starting line had no line break at the end in the

      start profile. Without this NT cannot parse the line. After adding the

      line break the enqueue server could start.

      The second problem was that in the global dispatcher configuration for

      the LockingManager the en.port was set to 3201 instead of 3200 (which

      is correct as the SCS instance has the intance number 00).

      After correcting these problems the J2EE engine could be started fine."

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.