Version v8.5.1.12 should also be applied to your v8.5 upgraded version. Several bug fixes and enhancements.
Main Topics
Browse All TopicsWe are attempting to upgrade Goldmine 6.7 dbase to Goldmine 8.5 SQL on a new server. The problem that we are experiencing is that no users accounts are migrating over during the import. Below are the steps that we have performed.
" We copied over the Goldmine 6.7 folder to a new server.
" We have installed Goldmine 8.5 SQL and SQL successfully with Demo files.
" We created an alias database in SQL.
" Using the rehost Goldmine Database wizard we have the following choices.
1. Create or copy data for contact set tables
2. Create or copy data for base Goldmine table
" We picked number 2.
" On the next screen we choose our alias database.
" Under select source of data for the new database we picked (copy data for 6x dbase tables).
" On the next screen it wants the paths to the dbase files.
For CONTACT1.DBF we picked the name of our database folder.
For CAL.DBF we picked the GMBase folder
For USERS.DBF we picked the root of the goldmine folder which we can see our user account listed.
The import is error free.
When we log back into Goldmine it appears that all the data has been carried over except the user accounts. We were told that we need to move mail attachment folder and templates over also.
Are we missing a step that would cause the user accounts from not to be available in the database?
Is there a better way to perform the import?
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: automationstationPosted on 2009-07-10 at 22:27:11ID: 24829161
That sometimes happens when you upgrade. FrontRange Solutions can provide you with a Transact SQL script that will recreate the user table with just one user... Master/Access. You can then just add back your users. This is the quickest fix, especially if everything else. upgraded.
) and OBJECTPROPERTY(id, N'IsUserTable') = 1)
AS NOT NULL , AS NULL , AS NULL , AS NULL , AS NULL , AS NULL , AS NULL , AS NULL , AS NULL , AS NULL , AS NULL , AS NOT NULL , AS NOT NULL
7G!!1?WI0$ 557G!!1?WI 0$557G!!1? WI0$557G!! W)ND@$N3AI ,#HP,MU!K^ 5A{!./5-*# RL<84$FS%{. !.V8\3 <F=2^!!?0X$ X=LH]$<`1L$!', 'MASTER', '9/23/1997', '12:15', 'ALL', '3MJ2QBCY4+6 C._')
.com/suppo rt.aspx?pa ge=61
I can post the script here as well:
+++
if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[USERS]'
drop table [dbo].[USERS]
GO
CREATE TABLE [dbo].[USERS] (
[USERNAME] [varchar] (8) COLLATE SQL_Latin1_General_CP1_CI_
[NAME] [varchar] (26) COLLATE SQL_Latin1_General_CP1_CI_
[USERGROUP] [varchar] (8) COLLATE SQL_Latin1_General_CP1_CI_
[INGROUPS] [varchar] (20) COLLATE SQL_Latin1_General_CP1_CI_
[LASTIND] [datetime] NULL ,
[LASTINT] [varchar] (5) COLLATE SQL_Latin1_General_CP1_CI_
[LASTOUTD] [datetime] NULL ,
[LASTOUTT] [varchar] (5) COLLATE SQL_Latin1_General_CP1_CI_
[SOUNDEFFCT] [varchar] (12) COLLATE SQL_Latin1_General_CP1_CI_
[USECURITY] [text] COLLATE SQL_Latin1_General_CP1_CI_
[OPTIONS] [varchar] (10) COLLATE SQL_Latin1_General_CP1_CI_
[LASTUSER] [varchar] (8) COLLATE SQL_Latin1_General_CP1_CI_
[LASTDATE] [datetime] NULL ,
[LASTTIME] [varchar] (5) COLLATE SQL_Latin1_General_CP1_CI_
[U_USERGROUP] [varchar] (8) COLLATE SQL_Latin1_General_CP1_CI_
[recid] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_
) ON [PRIMARY] TEXTIMAGE_ON [PRIMARY]
GO
CREATE
INDEX [USERS] ON [dbo].[USERS] ([USERNAME])
ON [PRIMARY]
GO
CREATE
INDEX [USERGRUP] ON [dbo].[USERS] ([U_USERGROUP])
ON [PRIMARY]
GO
CREATE UNIQUE
INDEX [USRRECID] ON [dbo].[USERS] ([recid])
ON [PRIMARY]
GO
insert into users (username, [name], usergroup, lastind, lastint, lastoutd, lastoutt, soundeffct, usecurity, lastuser, lastdate, lasttime, U_usergroup, recid) values ('MASTER', 'FrontRange Solutions Emplo', 'ALL', '11/4/2005', '12:23', '11/4/2005', '12:51', '0_5 630 34', ':`R,) `$*)# !<U)R P;_BZ$ ]+CH$0Y_), 7W_28 IG5Z=$8N*<A!P*:\7 $,2YO$J@HJG##U\#<#DSFX, T!RW* &8FK0!1?WI0$557G!!1?WI0$55
GO
+++
As far as linked documents you can physically move them to the new server... you will then need to correct the links in GoldMine to point to the new location. The best tool for that is from Prior Analytics... their Linked Doc Mover:
http://www.prior-analytics