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

Enabling SAS^® 9.4 Content Server consistencyCheck Traces

To enable consistencyCheck traces:

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.TenantPostgreSQLPersistenceManager"> <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 KB0036136, “How to upload and download files using the SASTSDrive file sharing server,” to upload the log and configuration information.

Resolving the Problem

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

• Do symptoms match known problems (rediscovery)?
• Is there is a non-defect problem that can be identified and resolved?
• Is there is 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.