if you have an old install file go to pervasive step 1

and start setup by clicking on it in the file

if I remember right it should ask if its a workstation or server.

While I appreciate you responding, GUSB, I don't have a clue what you mean.

I have installed Pervasive SQL server on the new server. That isn't the issue. It is with the migration itself. When I open up the control center on the new machine it will not let me have access to the databases.

When I try to expand "Databases" under the server name, I get an error "7004: General failure code".

It was at this point that I started looking for help with the migration, but my google skills were falling short on this one.

Thanks,

Aaron.

try deleting this file on the new server's data base ~PVSW~.LOC

and try again

let us know if it works

Can you explain how to delete a file on a data base?

on the new server right click on your data folder

click on properties and check the hidden box

open your data folder and find the ~PVSW~.LOC file right click on it and delete it

make sure there are no spaces in the data folder's name

If I right-click on C:\ProgramData\Pervasive Software\PSQL and select the "Hidden" check box, it will hide the PSQL folder. I'm not sure what that would accomplish. The folder is named whatever the installer named it. I didn't change it.

it is not pervasive you are to worry about.

I said your data folder where your BV data is.

No you didn't. You said "on the new server right click on your data folder." you haven't mentioned BV once this entire conversation. My point is exactly the same. If you select the "hidden" check box, it hides the folder. Second of all, I have no folder called Data.

I assumed you understood that you have a data folder for BV named by default "BVDATA" or what ever it was named.

as above it was said open your data folder and no spaces in your data folder name.

you must move the data folder to the new server, it will be listed in the working directory area when you log on to BV in your existing server

you may have to map it to each workstation to the folder

you will have to amend each users' directory to include the new location

you may need to get a partner to do it for you

have a nice day

Oh okay. I thought I needed Pervasive. I'll uninstall it.

Thanks!

didn't say to uninstall pervasive

the file ~PVSW~.LOC  in your BV data folder locks the data to the old server and should be deleted so a new one can be created

and you may have to update the license location if it is moved to the new server

I've deleted any ~PVSW~.LOC files, but still have the same problem. I do not know how to configure Pervasive. Per my original question, if any one could help me find some installation documentation for BV32 2013 so I can configure Pervasive properly, I would appreciate it. Thanks!

try reading this link

https://www.google.com/url?sa=t&rct=j&q=&esrc=s&source=web&cd=2&ved=2ahUKEwjg-uzn_LrmAhUKQK0KHfqvAZgQFjABegQIBBAC&url=https%3A%2F%2Fsupport.na.sage.com%2Fselfservice%2FviewAttachment.do%3FattachID%3DUnderstanding%2520Gateways%2520and%2520the%2520Pervasive%2520WorkGroup%2520Engine.pdf%26documentID%3D17375%26draftNum%3D0&usg=AOvVaw3Lv6zaABXyrL2By-s2m4Vj

Since the responses I received on here were utterly useless and didn't in any way even attempt to answer my questions, I figured it out on my own. Here's what I had to do, for any one in a similar situation.

1. Install Pervasive Workgroup on the new file server (database server). Do all interaction through the server console and not through RDP or you may run into issues.

2. Create blank folders where your new database locations will be. Open up CC and create new databases named the same as the ones you wish to migrate and located in the blank folder you just created.

3. Kill the pervasive service on the new server. Old server too. Copy all of the files from the old database locations to the new. Delete any lock ~PVSW~.LOC files in those directories.

4. Fire Pervasive back up. In my case it read all the new data files just fine.

5. In BV, add the new locations to the company list.

6. Validate.