This SAS KB article provides instructions about how to set the SAS^® Content Server consistencyCheck flag to true for further debugging of inconsistency issues related to the SAS Content Server Repository.

Enabling SAS^® 9.4 Content Server consistencyCheck Traces

To enable consistencyCheck traces, complete the following steps:

1. Navigate to the SAS-configration-directory/Lev1/AppData/SASContentServer/Repository folder.
   Note: Replace SAS-configuration-directory with the actual SAS configuration-level path in your environment.
2. Open the repository.xml file in the Repository folder mentioned in step 1. Then, set the VALUE= option in the following parameter to true, as shown below:

<PersistenceManager class="com.sas.contentserver.persistence.pool.
TenantPostgreSQLPersistenceManager">
<param name="consistencyCheck" value="true"/>

3. Navigate to the SAS-configration-directory/Lev1/AppData/SASContentServer/Repository/workspaces/default folder.

4. Open the workspace.xml file in the default folder. Then set the VALUE= option in the following parameter to true, as shown below:

<PersistenceManager class="com.sas.contentserver.persistence.pool.TenantPostgreSQL
PersistenceManager">
<param name="consistencyCheck" value="true"/>

5. Stop and then restart the SASServer1_1 web application server so that the changes that you made take effect.

6. Collect the following log and configuration information for further review:

• • Zip up the contents of the entire SAS-configration-directory/Lev1/AppData/SASContentServer/Repository folder.
  • Collect the SASContentServer9.4 log file from SAS-configration-directory/Lev1/Web/Logs/SASServer1_1/
  • Collect the SASLogonManager9.4.log file from SAS-configration-directory/Lev1/Web/Logs/SASServer1_1/.
  • Collect the server.log file from SAS-configration-directory/Lev1/Web/WebAppServer/SASServer1_1/logs/.
  • Collect the Shared Services PostgreSQL database dump by following instructions the instructions in SAS KB0036299, "Obtaining a dump file for the Shared Services database (PostgreSQL) in the SAS^® 9.4 Web Infrastructure Platform Data Server."

Then, follow the instructions in SAS KB0036136, “How to upload and download files using the SASTSDrive file sharing server,” to upload the log and configuration information.

Note: Be careful when you set the consistencyCheck parameter to true if you meet the following criteria:

When performing an upgrade in place from an existing version of SAS^® 9.4M6 (TS1M6) to SAS^® 9.4M8 (TS1M8)—or if you have a SAS 9.4M8 environment—SAS Content Server Validation errors might occur if you set the consistencyCheck parameter to true for the following files:

• SAS-configration-directory/Lev1/AppData/SASContentServer/Repository/repository.xml 
• SAS-configration-directory/Lev1/AppData/SASContentServer/Repository/workspaces/default/workspace.xml

As a result, the following SAS Content Server validation errors might occur:

In addition, the following errors might occur in SASContentServer9.4.log:

2026-03-05 09:46:38,838 [Catalina-utility-13] ERROR org.apache.jackrabbit.j2ee.RepositoryStartupServlet - RepositoryStartupServlet initializing failed: org.apache.jackrabbit.j2ee.ServletExceptionWithCause: Error while creating repository

org.apache.jackrabbit.j2ee.ServletExceptionWithCause: Error while creating repository

at org.apache.jackrabbit.j2ee.RepositoryStartupServlet.initRepository
(RepositoryStartupServlet.java:423)
~[jackrabbit-webapp.jar:?]

……

at java.lang.Thread.run(Thread.java:829) ~[?:?]

Caused by: javax.jcr.RepositoryException: Cannot instantiate persistence manager com.sas.contentserver.persistence.pool.TenantPostgreSQLPersistenceManager

at org.apache.jackrabbit.core.RepositoryImpl.createPersistenceManager
(RepositoryImpl.java:1384)
~[jackrabbit-core.jar:2.20.3]

….…

... 21 more

Caused by: java.lang.NullPointerException

at org.postgresql.core.CachedQueryCreateAction.create
(CachedQueryCreateAction.java:41)
~[postgresql.jar:42.6.2]

……

at org.apache.jackrabbit.j2ee.RepositoryStartupServlet.initRepository
(RepositoryStartupServlet.java:421)
~[jackrabbit-webapp.jar:?]

... 21 more

Workaround

Collecting artifacts early, even before you open a case, helps SAS Technical Support determine the following information quickly:

• Do symptoms match known problems (rediscovery)?
• Is there a non-defect problem that can be identified and resolved?
• Is there a defect that identifies a workaround to reduce severity?
• What is the root cause of the problem? Determining the root cause helps developers find a solution quickly.