WEbpage could not be displayed for ESS/MSS

[Former Member]

Hello All,

Iam a newbie in EP adminsitration and have no clue how to go about this issue that user is facing in EP version 7.3

Iam not sure which backend system we are using , but will get back to you on that. In the meantime can you please suggest wat needs to be checked for such issues in portal system. It is a DEV system.

Question 1 : What needs to be checked in Backend system and how ?

Question 2 : What needs to be checked in portal system and how ?

One thing is for sure that user is using the same web browser and it worked fine for him earlier. Now there is this issue.

For addition info : if it was a browser issue, what needs to be checked.

Please let me know.

[TomXing]

Hi,

Besides what is suggested by RAM, you can additionally check below:

1. The error 'Internet Explorer cannot display the webpage' usually occurs when the URL is not accessible (wrong URL, system is down, firewall, proxy problem....)
To check the exact URL you are accessing (within content area), you can collect HTTP Watch trace or Fiddler trace.

2. You can try accessing the URL above directly on the problematic PC, and see if it's responding.

3. Speaking of 'Browser issue', the proxy setting might affect accessibility of URL. It still falls into 1. above.

BR, Tom

[Former Member]

Hello Tom,

sorry for the late reply.

I have pasted the error log above with screenshots. Can you please let me know if you know the solution please.

BR

Vishwanath B

[Former Member]

Hi Vishwanath,

As per your screenshots, the problem lies in the SSO connection of your Portal system with the backend system.

Please ensure if all the steps have been properly followed to establish SSO between Portal and SAP ECC system.

Just a quick question, do you have different User Ids in Portal and SAP ECC systems for the same user?

If not, you can use SSO using SAP Logon Tickets. In this way, you won't have to maintain user mapping for each user.

BR,

Anurag

[former_member197475]

Viswa,

As I told already, please take care of User at first. I mean the user should be available in both the back end and portal, ideally through SSO.

Also just check, whether your JCo connectoin is working well.

BR,

RAM.

[Former Member]

Hello,

I have checked the user exists in both portal and backend system through SSO.

How to test the JCo connection?

BR

Vishwanath B

[anil_kumar259]

goto NWA-->configuration-->destionations-->RFC destinations ,select the destination and click on ping.

And also ping the backend system using cmd and check once.

[Former Member]

Hello Anil,

Backend system working fine !

i checked the NWA-->configuration-->destionations-->RFC destinations.

i clicked the destination named as <SID of backend system > and did ping . I got the following error

NWA-->configuration-->destionations-->RFC destinations

Error during ping operation: Password logon no longer possible - too many failed attempts on <SID host >

what needs to be done now ?

BR

Vishwanath B

[Former Member]

Hi Vishwanath,

So, it is evident that the RFC user is locked due to too many failed attempts.

Get the RFC user unlocked in ECC system or reset the password of the RFC user and update the same in NWA.

You can follow the below steps:

Login to ECC system with Administrator.

Go to Txn SU01 and search for the RFC user.

Change the User Type from Communication User to Dialog User and set the initial password for the user.

After that login to ECC system with RFC user's credentials and change the initial password.

Then, login again to ECC with Administrator credentials and change the RFC user type from Dialog user to Communication User.

Finally, maintain the same password for the RFC user in NWA and save.

Ping and test the RFC connection to SID with RFC user. This should be okay now.

BR,

Anurag

[anil_kumar259]

Please follow the steps which @Anurag has suggested and check the screens.

[former_member197475]

Hi Viswanath,

Please check on the below points.

1. Make sure that the System Alias is created for your backend system and it works well.

2. Check that the JCo destinations are configured correctly.

3. Make sure that the user you are using in Portal exists at the back end also(SSO).

4. Try to run the same application from back end.

5. There could be a security issue if you are working with the standard role. You can check the security trace using ST01.

6. Check in ST05, for lack of any authorization.

Let me know, still if you face the problem.

BR,

RAM.

[Former Member]

Hello ramakrishnan,

Sorry for the late reply. I found out that there are some business packages associated with MSS/ESS as attached in the screenshot

As you can see , when i test connection, for all these, it fails with the following error log:

No connection to system SystemConn_<SID>found:
com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: A nested exception occurred. Could not initialize physical connection.
Connection Failed: A nested exception occurred. Could not initialize physical connection.
Connection Failed: A nested exception occurred. Could not create JCO connection.
Name or password is incorrect (repeat logon)

Moreover for the user, when i navigate thru - >user adminstration -> select the user - >user mapping for system aliases, i dont find any entry for username and password. is this required to be maintained if SSO is configured.

Please let me know

BR,

Vishwanath B