Upgrading Goldmine 6.7 dbase to Goldmine 8.5 SQL

We 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?
usspareAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

automationstationCommented:
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.

I can post the script here as well:

+++
if exists (select * from dbo.sysobjects where id = object_id(N'[dbo].[USERS]') and OBJECTPROPERTY(id, N'IsUserTable') = 1)
drop table [dbo].[USERS]
GO

CREATE TABLE [dbo].[USERS] (
      [USERNAME] [varchar] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
      [NAME] [varchar] (26) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
      [USERGROUP] [varchar] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
      [INGROUPS] [varchar] (20) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
      [LASTIND] [datetime] NULL ,
      [LASTINT] [varchar] (5) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
      [LASTOUTD] [datetime] NULL ,
      [LASTOUTT] [varchar] (5) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
      [SOUNDEFFCT] [varchar] (12) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
      [USECURITY] [text] COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
      [OPTIONS] [varchar] (10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
      [LASTUSER] [varchar] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
      [LASTDATE] [datetime] NULL ,
      [LASTTIME] [varchar] (5) COLLATE SQL_Latin1_General_CP1_CI_AS NULL ,
      [U_USERGROUP] [varchar] (8) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL ,
      [recid] [varchar] (15) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL
) 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$557G!!1?WI0$557G!!1?WI0$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._')
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.com/support.aspx?page=61
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
automationstationCommented:
Version v8.5.1.12 should also be applied to your v8.5 upgraded version. Several bug fixes and enhancements.
0
usspareAuthor Commented:
We were able to perform a 6.7 dbase to Goldmine 8.5 SQL in place upgrade.

Thanks for everyones suggestions.

0
usspareAuthor Commented:
Used a different solution
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Contact Management

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.