Skip to Content
avatar image
Former Member

WAS stops working after JDI and SLD configuration

Hello,

I am wondering if anyone has run into this problem before.

I installed JDI using the pdf document "SAP NetWeaver Java Development Infrastructure".

This document also lists post-installation steps after JDI installation. One section is "Prepare the System Landscape Directory (SLD)". In it, we "Import the SAP Master Component Information". It states to do what is mentioned in SAP Note 669669.

I imported the first file mentioned in this document (CRCONTENTxx_0-....zip ). After this, the WAS server does not work anymore.

Does anyone know how to fix this issue? I would re-install and skip this part, but the document states that this is important to make productive use of the JDI.

Thanks.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Apr 18, 2005 at 08:23 PM

    OK,

    There's a new twist here. The j2ee engine has now started working (on its own. I made no changes). But now the administrator login does not work. When I go to the SLD home page - http://localhost:50000/sld/index.jsp

    and logon with the administrator credentials (which worked before), I keep getting the logon dialog, meaning that the logon is wrong.

    On clicking "Cancel" I get the "401 Unauthorized" error.

    Add comment
    10|10000 characters needed characters exceeded