ISTech Support Forum

ISTech Support Forum
http://www.istechforum.com/YaBB.pl
Evo-ERP and DBA Classic >> Installation >> Install error on 2-28-06 build
http://www.istechforum.com/YaBB.pl?num=1141873039

Message started by timgolds on 03/08/06 at 18:57:19

Title: Install error on 2-28-06 build
Post by timgolds on 03/08/06 at 18:57:19

Help,

Cant install the 2-28-06 release. Get the error:

Evo-ERP Setup
An error occurred durring the move data process - 115

Component: Program Files
File Group: Empty Dictionary
File: p:\dbamfg\errmsg.dbf

Apps are under under DBAMFG on the P: drive, Data is on root of the T: drive.

Looked in DBAMFG and the data and I don't have an errrmsg.dbf. I do have a errmsg.b though!

Any help would be appriciated.

Tim

Title: Re: Install error on 2-28-06 build
Post by Lynn Pantic on 03/09/06 at 13:14:32

The file is there and it is open. Somebody didn't get out or somebody hung a session when they did. Brute force remedy, reboot the server.

Title: Re: Install error on 2-28-06 build
Post by timgolds on 03/09/06 at 14:52:56

OH MAN! Thanks Lynn!

I was doing the install from home over a VPN connection! I guess now I'll have to hang around until everyone goes home to reboot the server! OH WAIT!!! I can do that from home also!!! ;D

I kicked all the users off through monitor before I installed and restarted pervasive. Guess those don't do it.

Will do tonight and let you know.

Thanks,

tim

Title: Re: Install error on 2-28-06 build
Post by Lynn Pantic on 03/09/06 at 15:37:22

The Evo data dictionary files are not Pervasive files so the Pervasive monitor isn't enough...

Title: Re: Install error on 2-28-06 build
Post by timgolds on 03/10/06 at 06:57:29

OK Got it installed.

Now we are having major problems! Can't print some travelers. The screen just flashes on the WO# field until you press exit. then you get the print dialog but when you print (Screen or printer), you get seq 10 over and over and over again! Tried with my TRM and TRX but still get the same thing.

Also, Cant use the new business status or Query features. Every time they are opened get:

FATAL ERR - File: LISTG60.LIB Line: 41 You have tried to access a file that has not been previously opened, or the file number value (FNUM) passed was 0.

Then the dialog pops up.
When you click on any drilldown button, we get:

FATAL ERR - File: LISTG60.LIB: Line 237 You have tried to access a file that has not been previously opened, or the file number value (FNUM) passed was 0.

When exit is clicked, we get:

FATAL ERR - File: LISTG60.LIB Line: 59 You have tried to access a file that has not been previously opened, or the file number value (FNUM) passed was 0.

You can not exit with the exit button but have to press the red "X" in the upper right hand corner.

Also, Still can't print a range of work orders.

All dialogs come up in the middle of two monitors when opened!

HELP Please!!!! :'(

Tim

P.S. The time on your server is off. this was posted at 7:56am MST

Title: Re: Install error on 2-28-06 build
Post by wrf46 on 03/11/06 at 06:26:36

We have the same problems with the new queries module.

FATAL ERR - File: LISTG60.LIB Line: 41
You have tried to access a file that has not been previously opened, or the file number value (FNUM) passed was 0.

Did you find a solution?

Title: Re: Install error on 2-28-06 build
Post by NovaZyg on 03/12/06 at 12:14:52

Tim,

We found an error before the post went out and I had called you about it and left a voice message. Pervasive cannot open a file on a local harddrive. We came up with a solution. Under the DBAMFG folder we create a new folder called DRILL. Into this folder we write temp files that get created and removed when a drill program opens and closes. That being the case, users need to have access to this folder.

I suspect the error 41 is coming from a security issue. I have just put a test in the code to tell the user of such, if the temp file cannot be created within 5 seconds.

:)

Title: Re: Install error on 2-28-06 build
Post by timgolds on 03/13/06 at 09:34:11

Allen,

All users have Full access to DBAMFG and the Drill directory. Looks like they were inheritated during the install. The directory has a file ISDRILL.B of 18K in it.

That file also exists in the root of DBAMFG, and on the T drive where the .B files are. All of them are the same size.

I also created a Drill directory on the data drive and the local drive under ISTS with the same file but still get the error.

Looked at where the master files are pointing and it's pointing to the ISDRILL.B on the T drive with the rest of the .B files.

I am checking the properties and securitry in Pervasive as I can see the tables and read the data on the client under the Pervasive enigine but I can not pull up the properties.

Will tel you know what I find.

Tim

Title: Re: Install error on 2-28-06 build
Post by wrf46 on 03/14/06 at 02:30:00

After the upgrade I was having the same Fatal Errors when trying to use the Query Module. I also had a Fatal error when trying to use IN-A or IN-B.

I then created a new company and copied the data from the old company. Opened the new company and had no problems, but changing back to the old company produces the same Fatal Errors.

Don't know how to fix the problem in the old company but maybe this will help solve the problem.

Title: Re: Install error on 2-28-06 build
Post by timgolds on 03/14/06 at 08:02:46

Allen,

Thanks to WRF46, I think I found the problem. It is an absolute vs. relative pathing issue. I created a new company and when asked for the path I let it default to TG\ which is in the dbamfg folder.

This company works great for drill down! I then looked at the path for the company files in the master index and it's TG\ not "P:\DBAMFG\TG\" like all the others. Or "T:\" like the .B company. This company works great! After looking at my other backup companies, they all have a relative path except for my 05 end of year company. Amazingly, Drill Down works file in that company also!

Will see about changing some of the other companies to relative and see what happens. Will let you know.

Thanks again wrf46 for the suggestion.

Tim

P.S. I was told a couple of years ago that I wanted absolute paths or I would have problems. Is this still the case?

Title: Re: Install error on 2-28-06 build
Post by timgolds on 03/14/06 at 08:14:28

OK changing to a relative path fixed the problem! It also fixed the print travelers problem (Will post to that one also for mike) And fixed the problem with printing multipule travelers at the same time!

Now the problem is: My main company is under "T:\" on another drive that is being shadowed for live backups. I can use a relative mount for the drive and place it under "P:\DBAMFG\" but Windows has problems with mounts that are not at the root. (Where's Linux when you need it!)

So any suggestions on how to fix this problem?

tim

Title: Re: Install error on 2-28-06 build
Post by NovaZyg on 03/14/06 at 09:32:45

Tim,

Where are you editing these paths in DBA? If it is Fileloc, as I suspect, you must always have a "\"at the end of the path. UT-D or TAS-F is editing Fileloc.

All the DBA code does access fileloc for its paths.. that and the dpath() Dpath() is the Data Dictionary path.. the location of fileloc.b filedict.b filekey.b. The DrillDown folder is located in the dpath()+"DRILL\"

Hope this helps you Tim...

Title: Re: Install error on 2-28-06 build
Post by timgolds on 03/14/06 at 11:03:00

Allen,

Yes, In TAS-F. All files have \ at the end of their path.

Here is an example of my companies:

File Ext: Path Result
.B "T:\" error
.B05 "05\" works
.BBU "\\CEE-JAY-DATA\DBADATA\BU\" Error
.BCO "CO\" works
.BTD "P:\DBAMFG\TD\" error
.BTR "TR\" works

Is someone adding dpath to the data file path in the code? That would make since since dpath="P:\DBAMFG\" and adding dpath the the companies that would be "P:\DBAMFG\<compdir>" i.e. "P:\DBAMFG\05\" which works fine. However, where the ones that don't work would come out as "P:\DBAMFG\T:\" or "P:\DBAMFG\\\CEE-JAY-DATA\DBADATA\BU\" which of course is invalid.

Let me know.

Tim

Title: Re: Install error on 2-28-06 build
Post by timgolds on 03/20/06 at 09:26:00

Hate to beat this to death but I was hoping there would be an answer while I was out sick last week.

I tried creating a virtual mount point of "t:\" to "p:\dbamfg\default" then running TAS-F pointed the .B company to the new location as "defualt\" (since p:\dbamfg\default\" has the same problem).

It appeared to work until the next day when I was called from my sick bed that nothing was working correctly and pointing to the wrong data! So I went into work with a 104 temp to fix the problem. (had strep and the flu at the same time. Hoping this story will get someone to fix this problem!)

I would appear TAS-F doesn't work as advertised! I noticed I had two different companies being merged together! Was also getting an error in FILELOCK.B when trying to figure out waht was wrong.

Decided maybe had something to do with the update so I ran the update again with the data pointing at "P:\DBAMFG\". Everything ran fine but I was completly shocked when all the file locations where changed to their orriginal settings! All Companies that started as "P:\DBAMFG\{CO ID}\" had been changed to "{CO ID}\" and everything was working. After rerunning the update they were all changed back to "P:\DBAMFG\{CO ID}\". the .B company which was orriginally "T:\" but changed to "DEFAULT\" was changed back to T:\" and of course, WO-C, QU-* and all other problems are back! Where did it get the old settings and why were they not changed?

Help! >:( ??? :-[

Title: Re: Install error on 2-28-06 build
Post by NovaZyg on 03/21/06 at 11:09:54

Tim,

I'll let you in on the problem.. There are 2 sets of data dictionaries... One in Btreive used by Classic, and the Second one is in CodeBase used by Evo. This was not my Design and it has led to many late nights trying to make sure that they stay synchronized.

When you run the install shield update, we had to make the assumption that this is the first time you have run it and create the CodeBase dictionaries from the existing Btreive ones.. That is where your error came from. You fixed (Using TAS-F) the CodeBase FileLoc, but when you ran the install shield it took your Btreive data and updated the CodeBase ones.

What you need to do is this.. Make a folder under the DBAMFG folder call it UPDATE.
Then copy in your Taspro7.ini file from your C:\ISTS folder to the UPDATE folder. Edit the ini with wordpad, and change the Setup section to look like this

[Setup]
DataDictPath=C:\DBAMFG\
DfltCompanyCode=B
DfltRunPrg=C:\DBAMFG\EvoERPupd.rwn
MultiUser=1
MainMenu=0
FullSetup=1
DefaultPath=C:\DBAMFG\
Titlebar=Evo ~ ERP UPDATE

Next create an Icon that runs C:\ISTS\EVOERP.EXE C:\DBAMFG\UPDATE\
The parameter you are passing is the location of the .INI file to launch.

This will run just the update to the CodeBase Dictionaries if we have made any, then make any changes it needs to, to the Btreive Dictionaries.

I hope this helps..
:)

Title: Re: Install error on 2-28-06 build
Post by timgolds on 03/23/06 at 17:33:28

Thanks Allen, That worked for the errors!!!!! :D :D

I thought it has also fixed the WO-C hanging problem but it hasn't got a complaint today. It does seem to be better though. He said he printed 5 travelers before it hung.

Thanks again for the help!!!

Tim