cancel
Showing results for 
Search instead for 
Did you mean: 

SSO Connection Test fails - Nested Exception

Former Member
0 Kudos

Hi Experts,

When we tried connection test for system type SAP_R3 with UIDPWD logon method. It shows the below error. Am unsure where to maintain the settings.

Thanks,

Preetha Balan

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

This message was moderated.

former_member185239
Active Contributor
0 Kudos

Hi Preetha,

With which user you are checking the OSS connection from portal.

With Regards

Ashutosh Chaturvedi

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Preetha ,

Hope you are doing good.

Issue is clear. The user that you are using for the backend user mapping is either locked or has its password expired in the backend.
try to login to the backend using this user and make sure that it has enough roles assigned (like s_rfc for RFC communication etc).
This will solve the issue.

Else try to map to another user and see if this works.
Check:

<http://scn.sap.com/docs/DOC-17145>

Thank you!

_____________

Kind Regards,

Hemanth

SAP AGS
 

Former Member
0 Kudos

Hi Ashutosh,

Using backend system credentials to test the connection.

Regards,

Preetha Balan

Former Member
0 Kudos

Hi Hemanth,

I have checked the users, but no user seems to be locked. Am unable to find where the user mapping for that particular system is maintained.

Regards,

Preetha Balan

former_member185239
Active Contributor
0 Kudos

Hi Preetha,

Can you paste the default trace.

With Regards

Ashutosh Chaturvedi

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Preetha ,

Hope you are doing good.

The user that you are using to login and reproduce the issue;  navigate to /useradmin and open this user.
Open the user mapping tab and here you should find some detail. Else in the personalization option for the user, this data will be available.

When you check the JCo's, make sure that you check with the user that you are facing the issue with and not the admin user.

Thank you!

_____________

Kind Regards,

Hemanth

SAP AGS

Former Member
0 Kudos

Ashutosh,

Please find the below default trace:

 

#2.0 #2014 07 21 06:00:37:681#0-700#Error#com.sap.portal.ivs.connectorService#

#EP-PIN#com.sap.portal.common#C000A7EEAF63009000000000000019B8#11738651000000004#sap.com/tc~pp~adm~wu~system_landscape#com.sap.portal.ivs.connectorService.DestinationsService#C945017#11##68C6940510C111E4802D000000B31E1B#d38af32410d611e4a27c000000b31e1b#d38af32410d611e4a27c000000b31e1b#0#Thread[HTTP Worker [@2021030686],5,Dedicated_Application_Thread]#Plain##

PortalSystemLandscapeSource.getConnection(IUser,String,DestinationFilter,Map) Failed to get connection. Original exception: A nested exception occurredCould not initialize physical connection. Linked Exception: A nested exception occurredCould not create JCO connection. Linked Exception: Name or password is incorrect (repeat logon)

[EXCEPTION]

com.sapportals.connector.connection.ConnectionFailedException: Connection Failed: A nested exception occurred. Could not initialize physical connection.

at com.sapportals.connectors.SAPCFConnector.SAPConnectorException.getNewConnectionFailedLocalizedException(SAPConnectorException.java:182)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorManagedConnectionFactory.createManagedConnection(SAPCFConnectorManagedConnectionFactory.java:155)

at com.sap.engine.services.connector.jca.ConnectionHashSet.match(ConnectionHashSet.java:401)

at com.sap.engine.services.connector.jca.ConnectionManagerImpl.allocateConnection(ConnectionManagerImpl.java:295)

at com.sap.engine.services.connector.jca.ShareableConnectionManager.allocateConnection(ShareableConnectionManager.java:54)

at com.sapportals.connectors.SAPCFConnector.connection.SAPCFConnectorConnectionFactory.getConnectionEx(SAPCFConnectorConnectionFactory.java:173)

at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:401)

at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:354)

at com.sap.portal.ivs.internalconnector.ConnectionProvider.getConnection(ConnectionProvider.java:305)

at com.sap.portal.connectivity.destinations.portal.PortalSystemLandscapeSource.getConnectionWithOverridingProps(PortalSystemLandscapeSource.java:120)

at com.sap.portal.connectivity.destinations.portal.PortalSystemLandscapeSource.getConnection(PortalSystemLandscapeSource.java:93)

at com.sap.portal.connectivity.destinations.impl.DestinationServiceImpl.getConnection(DestinationServiceImpl.java:185)

at com.sap.portal.connectivity.destinations.DestinationsService.getConnection(DestinationsService.java:102)

dev_jrfc.trc shows:

 

Error> occurred >Mon Jul 21 06:00:37,619< >RfcGetException rc (7) message: Name or password is incorrect (repeat logon)

<RfcGetException

Error> occurred >Mon Jul 21 06:00:37,677< >RfcGetException rc (7) message: Name or password is incorrect (repeat logon)

<RfcGetException

Former Member
0 Kudos

Hi Hemanth,

I have found that user, but the same user does not exist in backend system. Can you please tell me the roles that should be given to the user, so that i can create and do the user mapping.

former_member185239
Active Contributor
0 Kudos

Hi Preetha,

Check the security audit log file at os level.

With Regards

Ashutosh Chaturvedi

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

Great. We have isolated the issue now.
Just provide the user with the standard roles that you have in the backend server. For testing purpose assign sap_all profile (youcan take it out later) and then check if the issue persists.

Kind Regards,

Hemanth


Former Member
0 Kudos

Thanks a lot Hemanth that has worked

Regards,

Preetha Balan

hemanth2
Product and Topic Expert
Product and Topic Expert
0 Kudos

great news indeed Preetha

Answers (1)

Answers (1)

amarghuge
Discoverer
0 Kudos

Hello,

i had same issue there are two possibilities for this kind of scenarioes

1. Check all the jco connection and make sure that all are connecing succesfully jco cn ping successfully

make sure to test the jco connection also make sure that correct system details are maintained

2. in connector setings change the logon method to 2 nd opion of sso ticket

let us know the result once tested

regards,

Amar