KB: Database Errors, Indexing Errors: Difference between revisions

From RangerMSP Wiki - PSA software for MSPs and IT services providers
Jump to navigation Jump to search
Line 1: Line 1:
=Description=  
=Description=  
Some of our customers have found that data from tickets gets mixed in with the wrong tickets. This issue can also present itself as missing data. '''Have no Fear''', for your data is quite safe. This issue is caused by an indexing error mostly caused by multiple connections to the same data within the database, causing the data not to be written to where it's supposed to go...
Sometimes the index files that govern search results from the database can be corrupted for several reasons, causing inconsistent results from searching or loading specifically affected parts of the database. This behavior can be corrected by rebuilding your database indexes so that the data can be reassessed and properly tagged by the index files. This process is considered safe to run in order to correct suspected database indexing errors; however, it is also considered good practice to periodically run this process in order to make sure that the indexes are in order and up to date.
 
<br>


=Resolution=
=Resolution=

Revision as of 19:46, 1 April 2010

Description

Sometimes the index files that govern search results from the database can be corrupted for several reasons, causing inconsistent results from searching or loading specifically affected parts of the database. This behavior can be corrected by rebuilding your database indexes so that the data can be reassessed and properly tagged by the index files. This process is considered safe to run in order to correct suspected database indexing errors; however, it is also considered good practice to periodically run this process in order to make sure that the indexes are in order and up to date.


Resolution

We fix this issue by Rebuilding the Database Indexes

To run the rebuild indexes, please follow these instructions: (Make sure you're using CommitCRM 5.0 and above)

  • 1. Close CommitCRM client on all PCs
  • 2. Stop CommitWebInterface and CommitServer services (if installed and used). Leave the Advantage Service running if you are using the CSD.
  • 3. Backup the <server>\Commit\Db and <server>\Commit\DbSys folders (use a standard zip/archive utility for this (such as Winzip), and/or, also copy the folder to a backup folder.
  • 4. Click here to download a Rebuild Indexes program => Save it in folder <server>\Commit\Utils
  • 5. Run the downloaded program and have it rebuild the indexes

Check to see if the problem has been resolved.

If the issue persists, we will need some more information in order for us to investigate:

  • Send us the log files via Help > Technical Support.

We'll analyze the logs, get you the support needed to fix this issue.

Retrieved from "https://www.rangermsp.com/w/index.php?title=KB:_Database_Errors,_Indexing_Errors&oldid=3965"