ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Problem Reports - Sporadic >> cannot find ERRMSG.B file
http://www.istechforum.com/YaBB.pl?num=1224682170

Message started by PPB on 10/22/08 at 06:29:29

Title: cannot find ERRMSG.B file
Post by PPB on 10/22/08 at 06:29:29

i was working on a price quote and error message popped up about 50 times.
now i can't get back into DBA
it says
cannot find ERRMSG.B file. Please check for the proper files in your current subdirectory.

DBA Classic user
this is first time i ever had this problem.

Judy

Title: Re: cannot find ERRMSG.B file
Post by PPB on 10/22/08 at 06:43:01

everyone on our system has been booted out of DBA and now nobody can get back in.

???????????????

Title: Re: cannot find ERRMSG.B file
Post by GasGiant on 10/22/08 at 06:46:56

I would start by rebooting the server.

Title: Re: cannot find ERRMSG.B file
Post by mspink on 01/05/09 at 14:50:22

Anyone else? This is the error message we are getting at the workstations after having moved DBA to a new server. Rebooting the server (or the workstations) does not help. Thanks!

Title: Re: cannot find ERRMSG.B file
Post by awaretech on 01/05/09 at 14:56:16

Is the firewall turned on at the server and/or workstations?

Title: Re: cannot find ERRMSG.B file
Post by mspink on 01/06/09 at 12:12:54

Sorry for the delayed response. The firewall is off at the server and the workstations.

Title: Re: cannot find ERRMSG.B file
Post by kkmfg on 01/06/09 at 13:27:09

mspink wrote:

Anyone else? This is the error message we are getting at the workstations after having moved DBA to a new server. Rebooting the server (or the workstations) does not help. Thanks!

Has it ever worked since you moved DBA to a new server?

Title: Re: cannot find ERRMSG.B file
Post by mspink on 01/06/09 at 14:01:55

No, we moved to the new server over the weekend and it has not worked since. The connections at the workstations point to the new server, so I am not sure what is different than it was before except new hardware. The file ERRMSG.B file exists in the same location on the new server as it did on the old one, so I don't understand the "can't find" message.

Title: Re: cannot find ERRMSG.B file
Post by GasGiant on 01/06/09 at 14:11:16

Is it the dreaded PSQL client version mismatch?

Title: Re: cannot find ERRMSG.B file
Post by Vman on 01/06/09 at 15:55:28

Did you run the Gateway application (should be in the dbamfg or Evo folder) on the new server after moving to it? We had the same issue here when we moved to a new server.

Title: Re: cannot find ERRMSG.B file
Post by Lynn_Pantic on 01/06/09 at 21:07:23

Can you load hte program on the server itself?

If you can, my guess is firewall or permissions is blocking the connection. If your new server is WIN 2003 or 2008 and you are still using Pervasive 2000, they don't play well together. You can call us at 866-516-3282 and we can see what we can do to help.

Title: Re: cannot find ERRMSG.B file
Post by mspink on 01/08/09 at 09:44:08

Thanks to all for your help with this.

At the server, the error message is: An Error Occurred Trying to Load BTRIEVE: ERROR: 20
At the workstations, it is the ERRMSG.B message.

I did run the Gateway EXE.
We have the same version (as far as I can tell) of Pervasive at the server as at the workstations (9.5).
Windows Firewall is not on at either the server or the workstations. Everyone has Full Control Access to the DBA and PVSW folders (though this was never true on the old server, I just wanted to make sure that wasn't the issue).

It is a good thing we only rely on DBA for historical data as opposed to running the shop...or I think I would be out of a job! This application pre-dates me and I know nothing of SQL, so your assistance is greatly appreciated.

Title: Re: cannot find ERRMSG.B file
Post by kkmfg on 01/08/09 at 09:52:48

Error 20 means that the database server is not properly up and running. This would explain why workstations can't do anything. If the file server doesn't even have it's database up and working then you aren't going to get the clients working either. The oracle says that the reason for this error 20 problem could be one of these:

1. Corrupted files. Reinstall pervasivesql
2. Permissions problems. Try doing the operation while logged in as the administrator. If it works then you had a permissions problem
3. The database server could be broke. This might also be fixed by reinstalling.