Docs Viewer no longer working after installing CR7 for Cnx 8

HCL Connections Connections Forum
1

Last week, I've installed CR7 for Connections 8. I think it's that change which caused that the Viewer is no longer working. Every document gives a this message: "The connection is denied. Viewer cannot connect to the file repository. Try again later or contact your system administrator."

HCL Docs itself is working fine. I can view the documents by simply editting them. It's just the Viewer that's failing.

SystemOut.log shows:

[10/09/24 20:36:06:979 CEST] 0000010d SessionUserFi I Got request /viewer/app/lcfiles/6137b2ea-39cc-4487-9116-107a0f774c80/content
[10/09/24 20:36:07:078 CEST] 0000010d ServerToServe E com.ibm.connections.httpClient.ServerToServerHttpClient checkResultsForRetry SONATA: Not Found @'http://c<removed>/files/form/api/document/6137b2ea-39cc-4487-9116-107a0f774c80/entry?acls=true'
[10/09/24 20:36:07:147 CEST] 0000010d ServerToServe E com.ibm.connections.httpClient.ServerToServerHttpClient checkResultsForRetry SONATA: Not Found @'http://<removed>/files/form/api/document/6137b2ea-39cc-4487-9116-107a0f774c80/entry?acls=true'
[10/09/24 20:36:07:147 CEST] 0000010d LCFilesQCSRep W [S2S call Response Code]: 404
[10/09/24 20:36:07:152 CEST] 0000010d LCFilesQCSRep W com.ctc.wstx.exc.WstxParsingException: Unexpected close tag </head>; expected </link>.
at javax.xml.stream.SerializableLocation@18b684ec
org.apache.abdera.parser.ParseException: com.ctc.wstx.exc.WstxParsingException: Unexpected close tag </head>; expected </link>.
at javax.xml.stream.SerializableLocation@18b684ec
Caused by: com.ctc.wstx.exc.WstxParsingException: Unexpected close tag </head>; expected </link>.
at javax.xml.stream.SerializableLocation@18b684ec
at com.ctc.wstx.sr.StreamScanner.constructWfcException(StreamScanner.java:606)
at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:479)
at com.ctc.wstx.sr.StreamScanner.throwParseError(StreamScanner.java:464)
at com.ctc.wstx.sr.BasicStreamReader.reportWrongEndElem(BasicStreamReader.java:3283)
at com.ctc.wstx.sr.BasicStreamReader.readEndElem(BasicStreamReader.java:3210)
at com.ctc.wstx.sr.BasicStreamReader.nextFromTree(BasicStreamReader.java:2829)
at com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1072)
at org.apache.abdera.parser.stax.FOMBuilder.getNextElementToParse(FOMBuilder.java:163)
at org.apache.abdera.parser.stax.FOMBuilder.next(FOMBuilder.java:187)
... 58 more

[10/09/24 20:36:07:156 CEST] 0000010d ViewDocServle E Request on HCL Docs Component : request CMw6OE6LJqNfzsku1mg+rj9eKUAg6LpxURu38nJohy5mSG48LnbROqiQ8b+4aS8U with information {CLFAF400W: Can't access the document repository.}

Have others seen problems with the Viewer after installing CR7? And any hints on how to solve this?

2

No problems with CR7 and the Viewer 2.0.2 so far. ("version":"2.0.2","build_timestamp":"20220819-1124")

Did you check the usual suspects ?
- ltpa cookie domain
- custom security settings
- TAI settings

3

I noticed that the soffice task was (no longer?) running, but that's fixed now. Still no change in the viewer problem and the message. I do wonder where the http://-links come from as all my links in the configuration refer to https://

Maybe an important aspect. This environment uses OIDC with Keycloak to authenticate

4

Hi

Please open a case with HCL Connections for us to further review the issue.

Thanks

Ariel

5

I managed to fix the problem. In the end it was a mistake in the cfg.properties (http:// instead of https://) that got triggered by a change in the reverse proxy.

What is definitely related to CR7 and the upgrade, is that after the upgrade to CR7, the PDF export button is no longer showing. I noticed that the CR7 installation changed my http.hostname in the Resource Environmnent-ic360-custom properties. Maybe that's the reason, but I saw it after I put the backup back. I don't feel like putting in extra time to install CR7 again and check if just that setting makes the difference.

Has anyone else also noticed that the CR7 installation breaks the PDF export?

6

Hi Martijn,

at least I can confirm that every CR actually breaks some WAS-variables including ic360-resource environment entries and jvm-settings.
You should always run a cell-config backup and compare all files to see what actually happened with your websphere cell-configuration during the update process and re-apply modifications & adjustments.
I have opened a few cases on that topic "CR installer modifies cell configuration" but usually HCL can not find the root cause and closes the case.

Regards,
Jan