Error: Could not connect to middleware

[Former Member]

Hi All,

I am posting this thread after reading and implementing most of the threads available on this topic.

When I login into the NWA, with MISUPERADMIN user, and I click on Hierarchy Grouping, or Device Maintenance, I get the following error:

Reason: Could not connect to middleware

This is all we have done:

We have installed NetWeaver MI 7.0 with AS ABAP & AS JAVA Components.

After that, we have configured the SLD via Visual Admin Tool.

We have followed this link in detail: http://help.sap.com/saphelp_nw2004s/helpdata/en/43/1d7d843fce3566e10000000a11466f/frameset.htm

So it is not clear, why we are still getting that error.

Kindly provide us with guidance as to which way we should approach to solve the problem.

Thanks & Regards,

Ankur Malhotra

[AjithC]

Looks liek a Jco problem.. Check the Jco connection properly..

Ajith

[Former Member]

In the 'Maintaining JCo Destinations', I have two JCo destinations:

ME_MONITORS_METADATA_DEST

ME_MONITORS_METADATA_DEST

Both are in Green Status and 'Test' & 'Ping' is successful.

Kindly respond as to what can be the problem.

****

Kindly Help.

One Update: I am able to Sync from my MI Client and able to generate a Device ID.

Edited by: ankur_842000 on Sep 21, 2009 1:01 PM

[Former Member]

For this error I have found the following as possible reasons. (Assuming all the RFC and JCo are correct)

Both can cause this error.

I have had a 100% success in solving the problem by checking these 2 things.

1: Check your MI_SERVICE and MISUPERADMIN passwords! And that both users are unlocked and in validity period.

Some people say you should use the admin user instead of service (because the admin is a dialog user I think),

but this has never resolved my middleware issues.

2: If you have redeployed the jar file in the deployment tool, you have to restart the j2ee server.

So basically after all the setup steps have been done and checked, you have to bounce the j2ee server.