ISTech Support Forum - Moving Old DBA Classic to new Server.

Welcome, Guest. Please Login.

	05/13/25 at 21:47:28 News: \| IS Tech Support \| Evo~ERP \| Evo Wiki \| Forum \|

ISTech Support Forum › Evo-ERP and DBA Classic › Installation

‹ Previous topic | Next topic ›

Pages: 1

Moving Old DBA Classic to new Server. (Read 7054 times)

mack-limelight

Browser

Only the Paranoid
will survive....

Posts: 5
Gender: male

Moving Old DBA Classic to new Server.
10/03/08 at 13:58:34

Hello,

I have been currently tasked to migrate an old DBA classic database to a newer machine running Windows 2003 server.

We are currently running DBA-Classic v2002.4 with Pervasive SQL 97. I did some testing and can migrate the data from the database to any version of pervasive SQL all the way up to v9 & v10. But can only get DBA-Classic to work with Pervsaive SQL up to version 2000i.

DBA-Classic crashes or generates Btreive errors when I open the DBA-Classic application with any database greater than Pervasive SQL 2000i (SP4). Unfortunatly the company I work lost the license keys for Pervasive SQL 97/2000i. I am hard pressed trying to find the Pervasive 2000i software for sale on the internet anywhere.

One of my cow-workers stated that she saw several people post on this forum that it is possible to migrate and successfully get DBA-Classic v2002.4 to run on Pervasive SQL v9+.

My question is if it is possible to get DBA-Classic to run on Pervasive SQL v9/v10, and if so what settings or options do i need to configure to get it running? because DBA-Classic seems to not know how to query the new SQL databases and pukes error codes every time I load up DBA-Classic.

IP Logged

Lynn_Pantic Administrator evolution (n) - gradual change to a different form Posts: 5663	Re: Moving Old DBA Classic to new Server. Reply #1 - 10/04/08 at 16:17:49 It can definitely work. Please provide more detail as to the errors you are getting.
Back to top	Lynn Pantic IS Tech Support lynn@istechsupport.com IP Logged

mack-limelight Browser Only the Paranoid will survive.... Posts: 5 Gender:	Re: Moving Old DBA Classic to new Server. Reply #2 - 10/06/08 at 08:32:18 I was mainly receiving Btreive -35 errors every step of the way. I am going to recreate the setup in the test lab to get the exact errors. Is there any preference to v9 or v10 of pervasive SQL to get it to work?
Back to top	IP Logged

kkmfg Senior Member Ghost of the code Posts: 375 Gender:	Re: Moving Old DBA Classic to new Server. Reply #3 - 10/06/08 at 08:36:51 If it's a btrieve error 35 then it means that the database server was unable to read the directory that the database files are in. That would probably be a permissions issue. But, it will be good if you can dig up anything else.
Back to top	Collin K & K Manufacturing, Inc EvoERP Version 1-22-10 SP3 5 User Workgroup Pervasive 10 IP Logged

mack-limelight

Browser

Only the Paranoid
will survive....

Posts: 5
Gender: male

Re: Moving Old DBA Classic to new Server.
Reply #4 - 10/08/08 at 10:16:26

Sorry for the late reply, I have other tasks at my position i needed to take care of.

I just loaded up PSQL v10 and DBA-Classic v2002.4 on a virtual machine running windows 2003 and 2008 server. on both instantaces of installation DBA worked fine on both servers and I can see all the data, and receiving no errors.

I think the domain group policy or something was creating the previous btreive errors when i tried to install it on the actual running DBA server. We are going to purchase a copy of PSQL v10 and install it on the production server to see if there are any errors.

Quick question: on my virtual machine setup I dont have it setup to connect to the virtual machine remotely so DBA loaded fine locally, but when i need a client to talk over the network will the dba-classic know to use the psql v10 client, or can it work with the psql 2000i client that is installed with DBA-Classic? I'm assuming that it needs to be the PSQL v10 client and DBA will somehow know to use that client to work.

Also thanks to the msg board for being in existance or else I never would of known it was possible to get dba-classic to work on the new psql version databases. hopefully at the end everything works as planned.

IP Logged

kkmfg

Senior Member

Ghost of the code

Posts: 375
Gender: male

Re: Moving Old DBA Classic to new Server.
Reply #5 - 10/08/08 at 10:49:30

You always want only one version of Pervasive installed on your machines and it had better be the same version as the server it is connecting to. Don't let DBA Classic install Pervasive 2000i.

And, I suppose that I should mention that, yes, DBA Classic will know to use the installed version of Pervasive. Whichever version is installed it will try to use.

Collin
K & K Manufacturing, Inc

EvoERP Version 1-22-10 SP3
5 User Workgroup Pervasive 10

IP Logged

Kelloggs Active Member Do crazy people know they are crazy? Posts: 784 Gender:	Re: Moving Old DBA Classic to new Server. Reply #6 - 10/08/08 at 11:49:12 what we did is this: 1.- install pervasive on the win2003. 2.- set up the same share drive (X:\) on the win2003 as the old server. 3.- copy the entire X:\DBAMFG\ from the old to the win2003 server. 4.- check the securty (Everybody - All rights) on the win2003 server. We have never have any problems Kelloggs
Back to top	Evo ERP - 35 Users Dumped MS Access like a hot potato (VB.Net rules!!!) IP Logged

mack-limelight

Browser

Only the Paranoid
will survive....

Posts: 5
Gender: male

Re: Moving Old DBA Classic to new Server.
Reply #7 - 10/14/08 at 13:16:42

Ok,

I just installed Pervasive PSQL Summit v10 Server for 32-bit Windows. In the database control center its lists [3x] pre-installed databases's "DEFAULTDB, TEMPDB, and DEMODB" and I can only delete the demodb database. the rest I cannot delete manually.

DBA-Classic is installed and the data files are moved over to the correct directory. However when I try to create the DBA database named "DBATOEZI" in PSQL v10 it states that "the database name is already in use." even though there is no database called DBATOEZI. I do have a database named DBATOEZI for DBA-NextGen running on the FireBird database engine.

Do I need to use the DBATOEZI per DBA manufacturing instructions, or can i create any database name and just point the database to the DBA file folder, or just change the DEFAULTDB database file directory to the DBA folder?

IP Logged

Kelloggs Active Member Do crazy people know they are crazy? Posts: 784 Gender:	Re: Moving Old DBA Classic to new Server. Reply #8 - 10/14/08 at 13:35:47 Create a New Database Database Name: DBATOEZI Location: E:\DBA\DBAMFG\Default Dont use the Network Path: F:\DBAMFG !! Use the local drive: E:\DBA\DBAMFG\Default Kelloggs
Back to top	Evo ERP - 35 Users Dumped MS Access like a hot potato (VB.Net rules!!!) IP Logged

Kelloggs Active Member Do crazy people know they are crazy? Posts: 784 Gender:	Re: Moving Old DBA Classic to new Server. Reply #9 - 10/14/08 at 14:06:33 Actually you can call it whatever you want, try DBA. The problem could be that there is already a DSN called DBATOEZI DBA/EVO do not use ODBC to talk to the pervasive engine, so call it anything you want. Kelloggs
Back to top	Evo ERP - 35 Users Dumped MS Access like a hot potato (VB.Net rules!!!) IP Logged

mack-limelight Browser Only the Paranoid will survive.... Posts: 5 Gender:	Re: Moving Old DBA Classic to new Server. Reply #10 - 10/15/08 at 07:19:57 Yes you are correct it seems to work with any name. looks like we finally got DBA-Classic migrated to newer server, and it run alot faster now. thanks for the assistance.
Back to top	IP Logged

Pages: 1

ISTech Support Forum › Evo-ERP and DBA Classic › Installation

‹ Previous topic | Next topic ›