Diagnostics

The Code Collaborator server offers several diagnostics you can run to check the health of your installation. A failure result from one of the diagnostics does not necessarily represent an actual error, but may assist you and/or SmartBear technical support in debugging a problem with your server.

Accessing Diagnostics

To get to the diagnostics go to the Code Collaborator web server and click the System link at the bottom of the screen:

Scroll down to the "Debugging" section and click on "Diagnostic Utility".

To run a diagnostic click on one of the links, or click on the RUN ALL DIAGNOSTICS link to run all diagnostics. Some of the diagnostics take a long time to complete, and may impact the performance of your server while the diagnostic is running. See notes for each diagnostic below.

This diagnostic checks the schema of your database to make sure that it is what Code Collaborator expects. This diagnostic runs very quickly and will not impact performance on your server.

This diagnostic looks for invalid data in the database and fixes the data to be inside allowable ranges. If you have a large database this diagnostic may take some time to complete and could impact performance on your server while it is running. Generally it is only necessary to run this diagnostic if you have been told to do so by Smart Bear technical support.

This diagnostic looks for users whose logins differ only by case and merges them to a single user account. This is used to repair problems caused by a bug in older versions of the Code Collaborator server that allowed users to be created whose logins differed only by case. This diagnostic usually runs quickly and will not impact performance on your server.

This diagnostic checks that database data is self-consistent and sensible. Some failures in this diagnostic are common and do not necessarily represent real errors. This diagnostic may take a long time to run (scales linearly with size of your database) and will impact performance on your server while it's running so it's best to run it only when the server is not in use.

This diagnostic checks that the on-disk file content cache is present, readable, and that all content therein is properly indexed. This diagnostic takes a long time to run (scales linearly with number and size of files in your content cache).

This diagnostic deletes files from the on-disk file content cache that is not properly indexed, meaning the MD5 of the file content does not match the name of the file. This diagnostic takes approximately the same time to run as the Content Cache Integrity Check. You should back up your Content Cache before running this diagnostic.