After installing the 2/28/06 update (DBA Classic) I'm receiving the following errors in WO-A:
 
1) A record was not found in fileloc for file - ISLOG.B02 - 4
2) An error message record was not found in the ERRMSG.B file. 405
3) An error message record was not found in the ERRMSG.B file. 405
4) The field you are trying to use is unallocated.  It may belong to a file that hasn't been opened yet, or was an array that was removed from memory - IS.LOG.WHAT
 
When trying to recreate the ddf files, I get the message:
BTRIEVE error - c:\DBAMFG\FILE.DDF - 5
 
I've re-run setup numerous times, and receive no errors during the dictionary conversion routine, but I receive an information error "Internal Err-Mismatching FDs" always at the Evo-ERP Update routine, file BKDCCFG.B, the numerous warning errors "*** DEMO VERSION *** There are more than 100 records in this file. You must initilize it before it can be opened again in this version! - File: C:\dbamfg\oldloc.b", same for olddict.b, and a few other files, then numerous nformation messages like  "could not delete temp loc file" and "could not delete temp dict file", and finally a "FATAL ERR - File:NZLICE.LIB Line: 70 You have tried to access a file that has not been previously opened, or the file number value (fnum) passed was 0."
 
Help?

Lynn,
 
I have reinstalled 2-28-06 three times and I receive a Btrieve error -W:\DBAMFG\ISLOG.B - 3
 
I rebooted the server before applying the patches to ensure that no files were either in use or locked.
 
I have applied all of the supplemental patched listed on the website.  Any ideas?
 
John
 
 

Lynn, Doug,
 
this sound kind of like an issue I was having.  Is there any chance that the path on the server and the mapped drive on the workstations are different?
 
i.e. on the server that path is "c:\program files\DBAMFG\"  but the map point is at DBAMFG so your mount point is "D:\DBAMFG\"?  If it is, make sure your mount point for your map and your server point are  the same and your error will probably go away.  I have sent Allen info on part of this issue and I saw the same thing when doing the update from my server.  I had to do it from the workstation as that is were the correct mappings are (Along with the path being under the DBAMFG path!).
 
Hope it helps,
 
Tim