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

continual J2EE_GUEST error in defaultTrace log

This same error seems to repeat itself in my defaulttrace log (NW04s SPS8). I can't understand where J2EE_GUEST would be used/authenticated in the system either, so I'm not sure how to even trace where it's trying to login to/from.

#1.5#0003BADBF0DE006000000040000002B200041FB501D3DD24#1160762187046#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#J2EE_GUEST#0##nysapdev2_ND1_368784250#Guest#25c6f2005ae411dba68f0003badbf0de#SAPEngine_Application_Thread[impl:3]_8##0#0#Error#1#/System/Server#Plain###User J2EE_GUEST, IP address

HTTP request processing failed. HTTP error [401] will be returned. The error is [Authentication did not succeed.No details available].#

#1.5#0003BADBF0DE006300000001000002B200041FB5020C7C97#1160762190756#com.sap.engine.services.httpserver##com.sap.engine.services.httpserver#J2EE_GUEST#0####27fdf6405ae411dbbe310003badbf0de#SAPEngine_Application_Thread[impl:3]_21##0#0#Error#1#/System/Server#Plain###User J2EE_GUEST, IP address

HTTP request processing failed. HTTP error [401] will be returned. The error is [No login module succeeded.No details available].#

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Oct 13, 2006 at 06:03 PM

    Hi,

    1.Ensure that the required JDK is being used in the client system

    2.Try clearing the Web Start cache and try downloading again.

    3.Start>Programs>Java Web Start>File>Preferences>Advanced>Clear Folder

    4.The jars are already downloaded in some other client system, then copy them to the following path...DriveDocuments and SettingsClient-UserApplication DataSunJavaDeploymentjavawscache... in the client system and try opening the IB.

    This also causes due to Cache Can you

    )Start transaction SXI_CACHE.

    b)From the context menu XI Runtime Cache select Start Complete Cache Refresh.

    If you still face issue try this .

    Many actions require to access System Landscape Directory content from the Integration Builder. To optimize performance, this content is loaded into a cache so that the System Landscape Directory does not have to be accessed directly each time that System Landscape Directory content is required.

    However, this cache is not automatically updated if changes are made to the content of the System Landscape Directory. For this reason that we delete the System Landscape Directory cache if changes have been made to content in the System Landscape Directory. The cache is then filled each time that the System Landscape Directory is accessed. If we log on to the Integration Builder after we have made a change in the SLD, we do not need to delete the SLD cache.

    To clear the SLD cache, from the Integration Builder main menu, choose Environment ® Delete Cache for SLD Data.

    Once we have deleted the cache for SLD data, accessing objects in the SLD may take longer than usual initially.

    Regards

    Agasthuri Doss

    Add a comment
    10|10000 characters needed characters exceeded

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.