ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Installation >> FILE LOC ERROR WITH UPDATE
http://www.istechforum.com/YaBB.pl?num=1140796869

Message started by johng on 02/24/06 at 08:01:09

Title: FILE LOC ERROR WITH UPDATE
Post by johng on 02/24/06 at 08:01:09

Help! We have updated to 2004.1 with IS TECH and can not do anything. Warning error record not found for each specific file. Update was completely finished. We need help fast!!!!!

Title: Re: FILE LOC ERROR WITH UPDATE
Post by ericmcgill on 07/21/06 at 05:11:17

I wonder if this was ever resolved. We get the fileloc.dbf error on some clients after the 05/08/06 update.

Title: Re: FILE LOC ERROR WITH UPDATE
Post by JNAPIER on 07/21/06 at 10:40:43

On some of my installs, I had to check the FORCE box during the install. This takes a whole lot longer to run the setup, but it did resolve that issue.

John

Title: Re: FILE LOC ERROR WITH UPDATE
Post by LeAnn Cucchiara on 02/07/07 at 05:48:43

Just added a new user - prior to adding this person EVO was opening on that particular workstation okay, as far as I know - once we added the new user she now gets the following fatal err every time she trys to open EVO: Data dictionary file could not be opened: R:\DBAMFG\FILELOC.DBF

One problem that was occurring with that workstation was a tp7runtime.exe - Application Error:
"The instruction at "0x02d29536"referenced memory at "0x02d55f78". The memory could not be "read".

I don't think that is happening now. Any suggestions?

Title: Re: FILE LOC ERROR WITH UPDATE
Post by kkmfg on 02/07/07 at 06:28:40

LeAnn,

This may sound silly but I had something similar happen on a workstation today. What I did was go into the Windows File Explorer and go into the directory containing the file. So, in your instance, you might try opening explorer and going to R:\DBAMFG. If you are unable to go there then you've got networking trouble. If you can go there then try Evo again. Sometimes the mere act of viewing the directory clears out the problem. If it still persists I would try rebooting (if you have not already). If that doesn't work then hopefully you, me, or someone can brainstorm something better.