When I try to 'Change' GoldMine from Windows Programs and Features > Uninstall or Change a program > Highlight GoldMine > Change , the following error appears:
A gm.ini file was located, but neither GOLDDIR nor COMMONDIR required values were defined. Setup cannot upgrade this installation. Please choose another location to install GoldMine.
and a subsequent error: Fatal error during installation
What causes the error and how to resolve it?
This error is usually caused by a bad configuration - here most times an incorrect or inaccessible SYSDIR entry - in one or several related GM.INI files.
[STEPS TO BE VERIFIED]
- ALL related GM.INI files need to be verified for a proper setup and contents
a. REALINI entry
- Where applicable, for example on split default installations where the GoldMine application is installed into C:\Program Files\GoldMine or C:\Program Files (x86)\GoldMine and GoldMine data and config files into C:\ProgramData\GoldMine or also on networked GoldMine clients where the local GM.INI refers to the GoldMine share on the application server.
- Please keep in mind that in such cases ONLY a REALINI entry is available and NO SYSDIR/GOLDDIR/COMMONDIR entry.
b. SYSDIR entry
- Where applicable, for example on custom installations in the GoldMine installation path, on the application's server GoldMine share and on Undocked installations.
- The SYSDIR path needs to be accessible by all related machines containing a reference through the REALINI entry to the GM.INI
- A correct and unique GOLDDIR entry and a correct and unique COMMONDIR entry needs to be also verified
The following is a example where the error may occur:
A. On the workstation where this error occurs the following GM.INI is found
- Access to the server path is available and verified
- The machine does not have any mapped drives
B. On the application server the GM.INI contains the following
- On the server the G: drive is mapped and accessible
- GOLDDIR and COMMONDIR are unique and reflect a correct configured database alias
- GoldMine can be started correctly on the application server
- The reason for the error is that the networked client does not have a G: drive mapping, this needs to be fixed prior to any further attempt. Either the workstation needs a G: drive mapping or the SYSDIR entry needs to be adjusted to a UNC path.
- We recommend where possible to reference the SYSDIR path as a UNC path rather than a mapped drive!