Document #506, Solving GoldMine 4.0/5.0 Database Errors
Covers GoldMine 4.x or higher
Current versions of GoldMine use the Borland Database Engine (BDE) to access data stored by the Database Management System (DBMS) in use. For more information on the BDE and GoldMine, see the document on ‘The Borland Database Engine with GoldMine.’ Error messages specific to the BDE are covered in that document.
Database errors occur when the BDE and GoldMine cannot properly access the data. Any number of issues can cause the error message including improper settings, the system environment, or the data itself. The information contained in the error message can assist with diagnosing the problem. Depending on the cause a single error message to several error messages may be reported by the BDE through GoldMine.
This document covers common error messages with dBase tables. Follow the documentation provided with your SQL server for recovering errors with an SQL DBMS. The GoldMine Knowledge bases available on the GoldMine Support pages of our web site, www.frontrange.com, also have information on resolving SQL error messages.
The information contained in this document may not resolve the errors. At this point it will become necessary to restore the affected table from a backup or use a data recovery utility that will repair dBase files to recover the data.
This is caused by one of the internal tables becoming corrupted or damaged. These errors are generally associated with the MDX files, which are the index tables, but can also occur with the data files (DBF or DBT) themselves. The index tables only store pointers to the data in the data files and a corrupt index does not mean that data has been lost. This type of error can be caused by improperly shutting down the computer with GoldMine open, hardware issues with memory or the hard disk, issues with the electrical power supply to the building, or heavy usage of GoldMine. The full text of the error message will identify the table along with the name of the file that is getting the error message. Re-indexing weekly and rebuilding the tables monthly at a minimum can prevent this error, with heavier workloads and larger databases it may become necessary to decrease the length of these intervals.
This error is caused when the pointers in the DBF file to the corresponding DBT file become damaged. This type of error has the same causes as the Corrupt Table / Index Header error message as well as other applications modifying GoldMine’s tables or incorrect BDE settings. Fully rebuilding the database files with the Verify the data and synchronization information option checked will usually correct this error.
This error message will occur due to a previously unresolved error message. Checking the GoldMine Error Log, which can be accessed by selecting View>>GoldMine Logs… and going through the Error Logs can identify the previous error. Maintaining the databases can clear this error message or more specifically identify the previous error message.
The instructions provided here are for dBase tables only. It is recommended that a backup be created prior to following these instructions. More information on backing up is available in the document ‘How to Backup Data From GoldMine dBase Installations.’
1. With network installations, make sure that all users have closed GoldMine. If GoldMine errors on opening the program, skip to Step 5.
2. Open GoldMine and select File>>Maintain Databases... (in GoldMine 4.x, use the Tools menu) to start the Maintenance Wizard.
3. To re-indexing the index tables, follow these steps.
a. Select the All Databases radio button and then click on the Next button.
b. Check the All Contact Files check box and then click on the Next button twice.
c. Click on the Finish button to re-index the tables.
4. To re-build the database or create new indexes, follow these steps.
a. Select the All Databases radio button and then click on the Next button.
b. Check the All Contact Files check box and then click on the Next button.
c. Check the Rebuild and Pack the database files checkbox and then check the Sort the database files and the Verify the data and synchronization information options. This will rebuild and pack the tables and re-index the tables. Click on the Next button to proceed.
d. Click on the Finish button to complete the process.
5. If GoldMine errors on opening close the error message dialog box then restart Windows. After Windows has restarted, open GoldMine in the following manner. Enter a Username and Password for any user that has Master Rights in GoldMine then hold down the Ctrl key and click on the OK button. This will open the Contact Set Databases (in GoldMine 4.x the GoldMine Contact Files) dialog box with the currently open Contact Set highlighted for the logged user. Click on the Maintain button to start the Maintenance Wizard and follow Step 3 or 4 as needed.
A good indication that there is an environmental issue are recurring index error messages the same day or shortly after maintenance has been completed. This can also indicate that a DBF or DBT has been corrupted. Under normal conditions with regular maintenance, error messages will not reoccur regularly.
Windows 95 OSR 2 more commonly known as Windows 95 B has been linked to corruption in GoldMine index tables. More specifically, the Virtual Redirector (VREDIR.VXD) driver for the Client for Microsoft Networks could damaged all shared files on the network if not replaced with a good file. This only affects systems in a networked environment that use Microsoft network clients. The table below covers known versions of the VREDIR.VXD for Windows 95.
|
Filename |
Date |
Size |
Version |
Usable |
Source |
|
VREDIR.VXD |
07/11/95 |
138Kb |
4.00.950 |
yes |
Windows 95 Version A (cab 12) |
|
VREDIR.VXD |
11/07/95 |
138Kb |
4.00.955 |
yes |
ftp://ftp.microsoft.com/Softlib/MSLFILES/VREDRUPD.EXE |
|
VREDIR.VXD |
12/31/95 |
138Kb |
4.00.955 |
yes |
Windows 95 Service Pack 1 |
|
VREDIR.VXD |
08/24/96 |
154Kb |
4.00.1111 |
NO |
Windows 95 Version B (OSR2) (cab 19) |
|
VREDIR.VXD |
11/14/96 |
138Kb |
4.00.954 |
yes |
Unknown |
|
VREDIR.VXD |
09/11/97 |
154Kb |
4.00.1116 |
yes |
ftp://ftp.microsoft.com/Softlib/MSLFILES/VRDRUPD.EXE |
To check the Windows version on the system, select Start>>Settings>>Control Panel and double clicking on the System icon. If the version number displayed for Windows is 4.00.950B, then check the version of the VREDIR.VXD on the system.
By default the Windows 9x operating system hides the DLL files, the virtual device drivers (VXD), and common file extensions (like EXE, COM, DOC, XLS, and DOT) from view. This setting can be turned off with the following instructions with Internet Explorer 4.x or newer installed.
1. Open Windows Explorer and select Tools>>Folder Options.
2. Select the View tab in the Folder Options dialog box.
3. Select the Show all files radio button and uncheck the Hide file extensions for known file types check box.
4. Click on the Apply button and then the OK button for the changes to take effect.
To check the VREDIR.VXD version number, follow these instructions.
1. Click on the + sign next to the Windows folder then select the System folder to display it’s contents in the right hand pane.
2. Locate the VREDIR.VXD then right click on it and select Properties from the popup menu.
3. Select the Version tab and compare the version number displayed to those shown in the table on Page 2.
Use this link to download the self-extracting install to update the VREDIR.VXD with a good file from Microsoft: ftp://ftp.microsoft.com/Softlib/MSLFILES/VRDRUPD.EXE. After the installation is completed on all affected Windows 95 B systems and they have been rebooted, follow the instructions on Page 2, Step 3 to re-index all files in GoldMine.
Database errors have also been linked to Windows NT 4.0 with Service Pack 2 installed. In order to verify the NT version, restart the machine and observe the blue start up screen. It will show Windows NT 4.0 (Build 1381: Service Pack 2) or similar information in the upper right for the installed service pack. It is recommended that the machine be upgraded to Service Pack 6 if that is not already installed.
Hardware issues can also cause issues with GoldMine’s indexes and data tables. On a network, confirm that there are not any issues with the infrastructure of the network (cards, cables, etc…). A competent network specialist can isolate and correct any networking issues. The following items should also be checked on all machines that are using or have GoldMine installed on them.
1. Ensure that GoldMine is not on a compressed disk volume. This includes but is not limited to these disk compression utilities; Stacker, DoubleSpace, DoubleDisk, Drive Space, Xtradrive, etc…
2. On Windows 9x, run a thorough ScanDisk on the local hard drives. The system administrator or a computer consultant can correct any issues that are not corrected by the software.
3. If the issues persist, then perform a complete hardware diagnostic in the machines. A computer hardware technician will have the diagnostic software to do this.
A number of GoldMine sites have reported moderate to grievous database file corruption that has been directly attributed to the use of the Novell IntranetWare Client / Client 32 drivers. It is strongly recommended that Windows built in networking capabilities be used instead of the Novell IntranetWare / Client 32 drivers. FrontRange Solutions GoldMine Technical Support team cannot assist with troubleshooting when the Novell drivers are installed. More information is available in the document on ‘Configuring the Novell IntranetWare Client / Client 32 drivers for use with GoldMine.’
In some cases, normal indexing will not correct issues with the index files in GoldMine. The system administrator or someone that is comfortable with extensive file manipulation in Windows must carry out the following steps.
1. With network installations, ensure that all users have closed GoldMine before proceeding.
2. Create a complete backup of all GoldMine files. The document on ‘How to Backup Data From GoldMine dBase Installations’ has more information on the files to backup.
3. Locate and delete all files in the GoldMine folder and sub-folders that have MDX for an extension.
4. Follow Step 5 and then Step 4 on page 2 to force GoldMine to create new index files.
If the errors are occurring on a file with DBF or DBT as the extension in the error message, then there is the possibility that the data file itself is corrupted. This is a serious issue if the instructions in Step 4 on page 2 have been completed and the error persists. The best solution is to restore the affected table(s) from a known good backup volume and then perform maintenance on all files. The system administrator or a computer consultant can be contacted to attempt to isolate and correct the cause of the data corruption.
The best recovery option is to have a backup recovery procedure in place. Files that are backed up can be restored in the event that they are damaged. More information on backing up is available in the document ‘How to Backup Data From GoldMine dBase Installations.’
A second option is to use a data recovery utility to repair the damaged files. The FrontRange Solutions GoldMine Technical Support team does not support the use of third party utilities and/or freeware software. dSalvage is one data recovery utility that is known not to harm GoldMine files; more information is available at http://www.hallogram.com/dsalvge/index.html.
The third option is to have an Authorized GoldMine Solutions partner assist in data recovery and isolating and correcting the cause of the errors. The FrontRange Solutions GoldMine Sales team at 800.654.3526 can provide the name of a local GoldMine Authorized Solutions Partner.
Copyright (c) 2002 FrontRange Solutions Inc.
All rights reserved. You may use this document for personal and informational (non-commercial) purposes, provided that the copyright notice and all other notices and permissions appear in all copies, the document is not copied or posted on any network computer or broadcast in any media and modifications are not made to the document. Use for any other purpose is expressly prohibited by law, and may result in civil or criminal penalties.
The information contained in this document is provided “as is” without warranty of any kind. To the maximum extent permitted by applicable law, FrontRange Solutions disclaims all warranties, either express or implied, including warranties for quality, accuracy, merchantability, fitness for a particular purpose, title and non-infringement; and in no event shall FrontRange Solutions or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of profits or data or special damages, even if FrontRange Solutions or its suppliers have been advised of the possibility of such damages.