KB: Database Errors, Indexing Errors: Difference between revisions
Jump to navigation
Jump to search
| Line 13: | Line 13: | ||
:* 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. | :* 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. [http://www.commitcrm.com/downloads/commit-rebuild-indexes-50.exe Click here] to download a Rebuild Indexes program => Save it in folder <server>\Commit\Utils | :* 4. [http://www.commitcrm.com/downloads/commit-rebuild-indexes-50.exe 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 | :* 5. Run the downloaded program and have it rebuild the indexes | ||
Revision as of 18:17, 30 December 2009
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...
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.