ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Windows & Network Issues >> General Windows & Network Issues >> error 3012 (file open error)
http://www.istechforum.com/YaBB.pl?num=1257863674

Message started by ddlong on 11/10/09 at 07:34:34

Title: error 3012 (file open error)
Post by ddlong on 11/10/09 at 07:34:34

Help! Noone can get on EVO. File Open Error
Error # 3012 - Unidentified file error File name BKSYMSTR
Program Name F:\DBAMFG\EVOERPMENU.RWN
EXP PATH C:\ISTS\

aLSO...tHE BETRIEVE MENU FILE (WBTRVMEMO.B) COULD NOT BE OPENED AND BTRIEVE MEMOS WILL NOT BE AVAILABLE.

WHAT NEEDS TO BE DONE. ENTIRE EVO SYSTEM IS DOWN.

Darla Long

Title: Re: error 3012 (file open error)
Post by Kelloggs on 11/10/09 at 07:56:31

Restart all Pervasive Services (Evo's Database).

That could help.

Kelloggs

Title: Re: error 3012 (file open error)
Post by GasGiant on 11/10/09 at 08:52:08

Oh, weird! We had the exact same thing a on Monday morning :o First time ever we've had PSQL.2000i die on us. We use 2000i, so it is not a version thing. What Win server version are you using?

Title: Re: error 3012 (file open error)
Post by Kelloggs on 11/10/09 at 08:55:27

Same here, Yesterday evo stop working. What we did is to restart the pervasive service
We are using pervasive 10, on a windows 2003

:-[

Kelloggs

Title: Re: error 3012 (file open error)
Post by GasGiant on 11/10/09 at 09:11:19

I just rebooted the server. It was due anyway.

We then had two users that still could not get in. We had to reinstall the Pervasive client and Evo to get them back in action.

Perhaps a trip to the Pervasive forums is in order...

Title: Re: error 3012 (file open error)
Post by GasGiant on 11/10/09 at 09:15:26

nothing

Title: Re: error 3012 (file open error)
Post by ddlong on 11/10/09 at 09:54:53

I' rebooted the server and router. And reloaded the pervasive client on my workstation. Now when I try to start EVO, I get BKMENUSU file error #2. Has anyone seen this before?

Title: Re: error 3012 (file open error)
Post by RPCAdmin on 11/10/09 at 09:56:57

Just my 2 cents - a couple of weeks ago - I had a similar problem (can't remember if it was after a crash or not), but my user profile got corrupted. Had to delete it and recreate it in TAS-G; then all was fine.

Title: Re: error 3012 (file open error)
Post by ddlong on 11/10/09 at 10:05:28

Before I rebooted the server, I could at least get on from the server. Now I'm getting the BKMENUSU file error 2 on the server too. I tried to go into look at TAS-G since I couldn't access it from my computer when I discovered that its no longer working in ther either.

Title: Re: error 3012 (file open error)
Post by RPCAdmin on 11/10/09 at 10:16:08

Darla,

Have you tried logging in as the Admin?

Title: Re: error 3012 (file open error)
Post by GasGiant on 11/10/09 at 10:20:20

May be best to restore the menu setup files from your back up. They are universal, so you'll get the same result no matter where you try it. If you can log in as admin you may be able to fix it, but your best bet is to restore the files.

Title: Re: error 3012 (file open error)
Post by RPCAdmin on 11/10/09 at 10:55:29

True...if more than one user has been corrupted, that is probably the easiest thing to do.

Title: Re: error 3012 (file open error)
Post by ddlong on 11/11/09 at 07:13:20

Thanks for all the input yesterday. Crisis is over. Because there were several BK run files found missing, Lynn suggested that I reinstall the last update with the latest patches. That took care of the missing run files, but my user files were still gone. Lynn told me that the files I would need to restore were:
BKPSUSER.B from the default file and BKMENUSU.DBF, BKMENUSU.DBT AND BKMENUSU.MDX FROM THE DBAMFG FOLDER. We got those restored and all is well.

Title: Re: error 3012 (file open error)
Post by GasGiant on 11/11/09 at 07:30:40

We had three users who could not get past that error to log in to Evo. For the two local people we had to uninstall the Pervasive client and reinstall. For the remote user we had a bigger problem. Since the client is installed on the Terminal Server for all users, reinstalling the client did not help that one user. I don't know what or where Pervasive is stashing or caching info, but we had to delete the user's Terminal Server profile and recreate it to clear the error. And we still have no idea what happened.