Link to home
Start Free TrialLog in
Avatar of TZRick
TZRick

asked on

How to Reinstall GoldMine 6.7 CE

Hello everyone!

I have a problem. I have been playing around with my PC working with dBase versions of GoldMine to test them out. Now, I want to finally use the shared GoldMine installation that my company is using and I am having problems.

I have done a lot of research and here is a summary of what I did:

1. Removed the installation of GoldMine
2. Installed MS-SQL Client Tools
3. Removed Borland key from registry
4. Did a search-and-delete for all files named bde* and idapi*
5. Removed c:\program files\common\borland shared folder
6. Removed bdeadmin.cpl from c:\windows\system32

My GoldMine desktop shortcut points to the correct shared executable that resides on the server.

When I try to run the program, a message comes up saying "The BDE instruction file BEDINST.INI is not found in <path>. Would you like to install the standard dBase driver only?"

When I hit yes, the exact same message box comes up again. When I hit yes again, the GoldMine login window appears. When I attempt to login, I get a number of BDE errors:

1. "Driver not known to system.

"Context: openDatabase
MSSQL: GoldMine_Sales: dbo.SYNCSITE

"1: Alias: GoldMine_Sales

"BDE Error Cat:Code: [39:29]
BDE: 500 [4/11/1999]  GoldMine: 6.70.41114

"User: TRAHAMAN
Window: taarik

"Template: 7169
Details:
ALIAS: GoldMine_Sales"

2. "Driver not known to system.

"Context: openDatabase
MSSQL: GoldMine_Sales: dbo.GMTLOG

"1: Alias: GoldMine_Sales

"BDE Error Cat:Code: [39:29]
BDE: 500 [4/11/1999]  GoldMine: 6.70.41114

"User: TRAHAMAN
Window: taarik

"Template: 7169
Details:
ALIAS: GoldMine_Sales"

3. "Driver not known to system.

"Context: openDatabase
MSSQL: GoldMine_Sales: dbo.CONTTLOG

"1: Alias: GoldMine_Sales

"BDE Error Cat:Code: [39:29]
BDE: 500 [4/11/1999]  GoldMine: 6.70.41114

"User: TRAHAMAN
Window: taarik

"Template: 7169
Details:
ALIAS: GoldMine_Sales"

4. "Driver not known to system.

"Context: openDatabase
MSSQL: GoldMine_Sales: dbo.SYSLOG

"1: Alias: GoldMine_Sales

"BDE Error Cat:Code: [39:29]
BDE: 500 [4/11/1999]  GoldMine: 6.70.41114

"User: TRAHAMAN
Window: taarik

"Template: 7169
Details:
ALIAS: GoldMine_Sales"

Then, a GoldMine error appears saying "Cannot open synchronization files".

Another BDE error then comes up: "Driver not known to system.

"Context: openDatabase
MSSQL: GoldMine_Sales: dbo.SPFILES

"1: Alias: GoldMine_Sales

"BDE Error Cat:Code: [39:29]
BDE: 500 [4/11/1999]  GoldMine: 6.70.41114

"User: TRAHAMAN
Window: &Cancel

"Template: 7169
Details:
ALIAS: GoldMine_Sales"

Any help would be VERY VERY appreciated!

Taarik.
ASKER CERTIFIED SOLUTION
Avatar of TommyTupa
TommyTupa

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of tbojoe
tbojoe

The problem lies with your steps 3 through 6.  You did not need to remove the BDE applicaiton from your system.  A simple reconfiguration is all you needed and to make sure the BDE alias for your GoldMine database was added to your BDE Configuration file.  The GoldMine installation documentation can be found at support.frontrange.com which is really helpful for this situation.
Avatar of TZRick

ASKER

Thank you both for your answers! Please remember that I am installing a server-based GoldMine installation and so there is no need for any BDE on my machine. In fact, earlier today, I installed GoldMine on to another client and everything worked perfectly.

It seems to me that there is some part of BDE that is still resident in my system that is confusing GoldMine. Besides the registry key, Control Panel applet and the 'physical' files in the path mentioned earlier, is there any other part of BDE that may still be on my system? I also uninstalled and deleted all related GoldMine files. Does GoldMine leave anything behind when an uninstall is done?

Thank you!
The Goldmine application communicates with Goldmine database via BDE.  The MSSQL client tools are necessary for BDE to communicate with the database.  This is true even if your using Goldmine from a desktop shortcut to the server.   Check a workstation where things are working and you'll see a BDE.
OH MY...its been a while....looks my last post was incorrect.

If your using a desktop shortcut to the server executeable you can have the gm.ini point to the shared BDE idapi32.dll.
E.g.
 [GoldMine]
NetIdapi32dll=\\serverpath\GoldMine\Setup\BDEShared\idapi32.dll
The uninstall normally does a great job of removing all installed files.  You can also try to make sure to clean out temp files as well.

But there has to be some sort of BDE on your machine even if it is just a pointer to the server. On your workstation that you configured earlier; in the control applet you should see BDE administrator listed and if you open that applet the physical path points to the network location.  SO if this has been corrupted in some way the best scenario would be to rerun the installation selecting the workstation setup and going from there.  BDE must be configured properly before GoldMine can properly run on any machine.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of TZRick

ASKER

Okay. You guys were right. (Go ahead and tell me "I told you so")...but not 100%. One of my co-workers gave me an install for BDE 5.2 and we also created an ODBC connection for the SQL db. So...it worked. It took a lot of time and a lot of stress, but it worked. Jeez.. I can't wait till we upgrade to 7.0!!

Thank you again!
You might want to hold off on the 7.0 upgrade.  There are some major issues.  I just went through the 7.0 upgrade and I had to completely remove the 7.0 upgrade and go back to 6.7.  A lot of issues with sync, mail client and data integrity issues. SO you might want to wait until a stable build of 7.0 is released.  Just speaking from experience.
Avatar of TZRick

ASKER

Thank you for the advice!

The bugs are the very reason we have not upgraded as yet. When the bugs are fixed, we should be moving over.