Can't get rid of "Could not retrieve details for the user"-error

HCL Connections Connections Forum
,
1

I'm trying to upgrade my Connections demo environment, doing a side by side upgrade. I've installed everything from scratch (and redid it an extra time) and keep getting this error with every user that I login with:

00000449 UserInfoInter E CLFRQ0415E: An error occurred while executing the action. See nested exception for more details.
com.ibm.lconn.homepage.web.WebException: CLFRQ0341E: Could not retrieve details for the user with login ID: mdejong due to an exception. The exception occurred when retrieving the details via Profiles Directory Service Extension: [Ljava.lang.Object;@9e7a0922
[..]
Caused by: com.ibm.lconn.homepage.services.ServiceException: Failed to get user details for: mdejong, orgId: 00000000-0000-0000-0000-000000000000
at com.ibm.lconn.homepage.services.impl.UserServicesImpl.getUserLoginName(UserServicesImpl.java:413)

I don't know how to solve this one. The LDAP repo is the same as in my other environment. Users are visible in WebSphere. The profiles are loaded through TDI in the DB2 database (first time, I actually did an export from the old environment and import in the new one). I can't think of any reason why this fails. Any tips welcome.

Environment Details:
HCL Connections 8.0 CR4
WebSphere 8.5.5 FP24
DB2 11.5.6
Domino 14 LDAP
CentOS 9 Stream as OS for WebSphere (WebSphere 8.5.5 FP23+ and Connections 8.0 CR4 are supposed to support RHEL 9)

2

Hey Martijn,

I never tested CentOS Stream, because it is often ahead with version numbers compared to RHEL. I would suggest Rocky or Almalinux, as they are more similar, but to be really sure register for a RHEL developer account and you're allowed to use 20 RHEL boxes with update service.

About the error, looks like an issue with SSO. So Ltpatoken Domain, connectionsAdmin (j2c alias), or interservice URL. Login items in federated repository config could be involved too (uid; mail).

Christoph

3

Hi Martijn,

You can do following test:

1. Backup all Connections database. (Just copy the NODE0000 folder and paste to some other place).

2. Use DBWizard to drop all current tables.

3. Use 8.0 DBWizard to create new Connections 8 databases.

4. Use sync_all_dns to sync users from Domino LDAP to your Connections Database.

5. Try to login and see if the issue still exists.

--- This test will help us confirm if there is anything wrong with data migration between old version to 8.0

Thanks.

Rock

4

I don't think it is necessary to recreate the databases. As Martijn said that TDI syncs the profiles into the profiles database and this is working.

@Martijn de Jong check: https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0021662

5

Hi Rock,

I've tried exactly that before asking the question. So alas, that makes no difference.

Kind regards,

Martijn

6

I recommend opening a support cases for a closer look. We'll need to inspect and compare the current data in the databases for starters.

7

In the end, I fixed the problem with changes to the LotusConnctionsConfig.xml and httpd.conf, but created a new one by installing a fresh set of empty databases. If you do that, don't forget to run the connections.sql/homepage/db2/initData.sql script.