DATAPAGE 3.33 (Database System Error -127) HELP ME PLEASE...

[jaymunday]

As of yesterday at the end of a program where the results update into the Datapage database I get a error. ( Database System Error -127 Database files do not exist in selected directory.) I switched databases and same issue. I deleted my program and loaded a backup and same issue. I tried another program witch has ran for months and that program aslo has the same error. That told me its a datapage issue not my program. So I unlocked the databases and did all that and nothing worked. Then I uninstalled Datapage and reinstalled it. That did not work. Then I uninstalled, saved my database file in another folder reinstalled and created new databases. Still same issue. I dont know what else to do. Can anyone help. Also, at the end of the program when its generating the info to go to datapage in ususally will sat the name of the program and the specified database. But instead it gets stug generating and skips from database to database and even skips programs.

[Matthew D. Hoedeman]

XSTATS11.TMP file has BAD DATA in it, directed to a database that does not exist. Delete the file. Problem solved.

[Matthew D. Hoedeman]

As a side note, all 'good' data that has been sent to the XSTATS11.TMP file will still end up in Datapage, and when the good data is sent, it is removed from the file, however, any data with a database target location that does not exist, that will stay in there so you can open the file, fix the path, then update (from DPEditor) and recover the data. With all you've done, you are at the point where you can just delete the file. Deleting it does no harm since it will get re-created when you next send data to datapage.

[jaymunday]

Thanks I got it.

[goosefraba]

That works perfectly.

[SAmerica]

I have the same issue. So if I delete this file I will lose all of my good data? I guess I understand but I'm really paranoid because I can't lose this data I have. Is there any way to repair the directory error without deleting the file.

[SABarber]

you can edit the xstats11.tmp file via NotePad to edit the correct database path.

[Keren McComas]

XSTATS11.TMP file has BAD DATA in it, directed to a database that does not exist. Delete the file. Problem solved.

So matt are you saying to delete the xstats11.tmp file, the whole thing?

[Matthew D. Hoedeman]

So matt are you saying to delete the xstats11.tmp file, the whole thing?

Any and all data in the XSTATS11.TMP file that has a GOOD database will be updated to Datapage, any data with a BAD database will NOT get updated to Datapage and it just stays in there and will cause the error every time you try to update Datapage. I just delete the whole file. If it does not exist, Pcdmis creates it. When Datapage is updated, all the GOOD data is removed from the file, so if there are no -127 errors, if you look at the file, it will be empty. I have a quick-pick macro that just deletes this file. I do this when I have to interrupt and stop a program that is saving stats because it saves what it has already dimensioned, and I don't want duplicate data in the database, so when I do have to interrupt/stop a program, the first thing I do is click that quick-pick that deletes the file.

[Keren McComas]

ok Matt I did that now I get "unableto access database for write operation, when I hit ok I get "cannot lock database"

[Matthew D. Hoedeman]

in teh database directory, there are the following files:
VISTA.TAF and LOCKMGR.DBL.

You can either move them or delete them, then open Datapage and let it re-make those files.

[Keren McComas]

We have done that too. I am out of here till Wed. of next week, if they don't get it fixed tomorrow, I will get back with you then. Have a blessed CHRISTmas.

[SABarber]

all 'good' data that has been sent to the XSTATS11.TMP file will still end up in Datapage

Just a note about this statement. Depends on what "good data' means. Since you are getting a '-127' database path not found message ALL information trying to go to that database will NOT be sent since there is no database to send the data. The stats file will then be appened to with any new pcdmis data. If that data points to a valid database you will still get the -127 on the first invalid path but any data associated with a valid database will be updated. So if you need the data that is associated with the invalid database edit the stats file to point to the database directory you want it to go to. The next update will put this data in the database.