Discussion: Considerations For GoldMine Versions

•	GoldMine Corporate Edition 6.x

GoldMine 6.x uses the Borland Database Engine (BDE) to connect to SQL Server. Because of this, not only does the Remote GoldMine Service (RGMS) need to be able to access the GoldMine files on a path other than a mapped drive letter, it must also be able to access the BDE on a path other than the mapped drive letter as well. During a wMobile login attempt, the RGMS will attempt to load the GoldMine API to process the user supplied Username and Password. If the RGMS can locate the GoldMine API but cannot locate the BDE, it will return a -99 error.

GoldMine uses the HKLM\Software\Borland registry key to determine how to find the BDE. Depending on how GoldMine is installed and configured, there are basically 4 methods for initially creating the Borland registry key on the GoldMine server.

•	The key is already present: If another application that uses the BDE was installed before GoldMine, then a Borland key is already exists. GoldMine will try to use that Borland key to load the BDE.

•	Initial Install: When GoldMine is installed and the BDE is not present, it will automatically create the Borland key when it is loaded for the first time.

•	Running GoldMine from the server. If the Borland key does not exist in the registry, GoldMine will automatically create it.

•

GM.INI Method: Setting controlled in the GM.INI, using the NetIDAPI32.DLL setting. This is typically used to solve problems where lots of Borland database engines might exist on various workstations.
To determine if your GoldMine is using the NETIDAPI32.DLL setting to force the location of the BDE, do the following:

1.	On the GoldMine Server, navigate to the folder on the local path (Non-mapped drive letter) where GoldMine is installed.

2.	Open the file named GM.INI.

3.	In GM.INI, look for a setting called NETIDAPI32.DLL. NOTE: If the NETIDAPI32.DLL setting is present and is NOT preceded by a ';', then your GoldMine is configured to use the GM.INI method.

If the NETIDAPI32.DLL setting is present and is referencing a mapped drive letter, then it must be removed or ignored. To force GoldMine to ignore the setting in the GM.INI, simply place a ; at the beginning NETIDAPI32.DLL. Any line in the GM.INI that begins with a ; is ignored when GoldMine is loaded. Following this change, the HKLM\Software\Borland key must be changed.

Example: ;NETIDAPI32.DLL = w:\GoldMine\Setup\BDEShare

IMPORTANT NOTE: Be sure to Log all users out of GoldMine before changing the GM.INI. In addition, if the setting is present, contact your GoldMine Partner. Removing the setting could cause GoldMine to stop working on other workstations.

To determine if GoldMine is accessing the BDE on a mapped drive letter, do the following:

1.	Click Start and then click Run.

2.	In the Open box, type Regedit and then click OK.

3.	Look for the following key in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Borland\BLW32

4.	The BLAPIPATH key will indicate what path is being used to access the BDE. If the path is a mapped drive letter, then the RGMS will not be able to process user logins.

IMPORTANT NOTE: If a mapped drive letter is being used, contact your GoldMine Partner. Changing the setting could cause GoldMine to stop working if the server is used as a terminal server.

To change the Borland registry key to a local path or UNC path, do the following:

1.	Click Start and then click Run.

2.	In the Open box, type Regedit and then click OK.

3.	Look for the following key in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Borland.

4.	Rename the HKEY_LOCAL_MACHINE\SOFTWARE\Borland to HKEY_LOCAL_MACHINE\SOFTWARE\Borland_Old.

5.	Navigate to the folder on the local path (Non-mapped drive letter) or UNC path (Network share starting with \\) where GoldMine is installed.

6.	Double-click on the gmw6.exe file.

7.	When the GoldMine Login box appears, log into into GoldMine. IMPORTANT NOTE: If GoldMine does not open, contact your GoldMine reseller.

8.	Close GoldMine.

9.	Click Start and then click Run.

10.	In the Open box, type Regedit and then click OK.

11.	Look for the following key in the registry: HKEY_LOCAL_MACHINE\SOFTWARE\Borland\BLW32

12.	The BLAPIPATH key will indicate what path is being used to access the BDE. This path should start with the same drive letter or UNC path used to start GoldMine.

•	GoldMine Corporate Edition 7.x and GoldMine Premium Edition

Depending on the configuration of the server and GoldMine, the RGMS might have trouble finding the GoldMine API. This can be caused by several factors:

•	Many different versions of GoldMine installed.

•	GoldMine was installed to a mapped drive letter during the server install.

•	Old GoldMine DLLs in the \Windows\System32 directory. Every GoldMine installation is a little bit different. To ensure a successful install of wMobile, avoid the above mentioned issues by checking the following:

For Windows 2000, XP and 2003 Server

1.	Right-click on My Computer and select Properties.

2.	Click the Advanced tab.

3.	Click the Environment Variables button.

Find the PATH setting in the lower list of variables. If the path is set to a Mapped Drive Letter (example: G:\Apps\GoldMine), then you will need to add a setting to the local path (example: E:\Apps\GoldMine). If the path is set to a UNC Path (example: \\Server\Apps\GoldMine), then you will need to add a setting to the local path (example: E:\Apps\GoldMine) or ensure that when you install the Remote GoldMine Service, you supply a service account with Read/Write access to the UNC path. If there is NO GoldMine path, add the local path (example: E:\Apps\GoldMine).

For Windows Vista and 2008 Server

1.	Right-click on My Computer and select Properties.

2.	Click Advanced system settings.

3.	Click the Advanced tab.

4.	Click the Environment Variables button.

Return to the Pre-Installation Checklist