J2ee error--Could not login to config tool

[Former Member]

The J2ee instance of the R/3 System is not running.

I checked the error and found out that the database initialisataion was failing in the bootstrap loader file

I also found out that i couldn ot login to Config tool . It could not connect to the database.

Please help

The ABAP Databse and Java Database are using different Schema.

[Former Member · Accepted solution]

Hi

If you want to login to the Config tool then there should be one condition and that is your database should be up.

If your DB is up then you can login to Config tool without any probel as it dosent require your java istance to be up.

and for error analysis paste your dev_disp and dev_jcontrol files here.

which port and user ur using to connect to config tool ?

Award if helpful

Cheers

[Former Member · Accepted solution]

my DB is up and running.

It was connecting before

[Former Member · Accepted solution]

paste ur j_control file ...

check ur db is running now .....

Giving proper error information may be useful ..... for further assistance

[Former Member]

Hello Balaji,

Open the config.properties under the configtool directory and make sure the following entries have the right values maintained :

rdbms.maximum_connections=

system.name=

secstorefs.keyfile=

secstorefs.secfile=

secstorefs.lib=

rdbms.driverLocation=

rdbms.connection=

rdbms.initial_connections=

Hope this helps.

REgards,

Snehal

[Former Member]

Check your bootstrap log file which will tell you about the issue. Also make sure your JDK version is correct and set it in the path. I believe some of JDK file might be missing or could not be located because correct path was not set.

Either way, bootstrap log file is the place where you need to check for more information.

Another option is to launch config tool to see what error messages pops up.

Thanks!

[Former Member]

Hi Balaji

Open your Instance.properties and check if the entires are all correct.

You can also use offlinecfgeditor.sh (unix) offlinecfgeditor.bat (window)

follow note for the correction Note 831812 - Config Tool shows incorrect parameters after System Copy

Cheers

Shaji