Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Corrupt files after hard drive problem-Progression 7.6.4

Status
Not open for further replies.

Micaman

Vendor
Feb 16, 2007
5
US
Version Progression (PWE) 7.6.4

I attempted to run the Inventory GL Distribution Report, I received the message ‘Error 002 on file IMDISFIL.BTR – I/O error’.

I attempted to access the file using Crystal Reports, and likewise got an i/o error.


Also, how can we identify other possible corrupt files?

Thanks
 
There was a utility available years ago that actually allowed you to schedule rebuilding of the BTR files on a schedule to try and avoid these types of issues. I have lost track of who created the utility but I do rememeber that when MSSQL became the standard they stopped supporting it. I would not recommend using the rebuild utility in Progression as it often does not fix the problem. I always do the following.
Get everybody out of Progression
Delete all .tmp files in /users directory under the Macola root directory. make not of how many of these there are as these could be the cause of the corruption. More on this later.
make a copy of the BTR file
export the file make not of the number of records
initialize the file
import the fle compare the number of record to the number exported
delete the TXT file that was created during the export

This usually works but sometimes it doesn't I purchased a utility a long time ago that has always been able to rebuild files. You can contact me to discuss if you need to do this.

You really need to try and find out what caused the corruption, this is why I was concerned about the TMP files above. I call these ghost users. The fact that they exist are not the cause of the problem but may be an indication of a problem. They get created when a user logs in to the system, they get created when the user exits gracefully. If they do not exit gracefully but uses the ctl-alt-del method to exit it may cause corruption, another way that these get left is from an inconsistant network connection which may also cause corruption depending on what was happening when the connection was lost. The version of Progression that you are on will automatically clean these files up if you are using the PWE executable so trouble shooting can be a problem.

Good luck



Steve Henley
Trianglepartners.com
Exact Software consulting, sales and implementations.

If the only tool you can use is a hammer then all your problems look like nails.
 
TPLLC,

I would look at I think this is who you were thinking of.

Last time I ran into corrupt files (the old error 002), I used the native Pervasive Utilities. If that does not work, I hope the Micaman has a good backup.
 
Were you in the middle of processing something when you encountered the hardware problem? If you can determine what processes were running, it is likely that those files might be the suspects for corruption, as they may have been open when the system went down. To determine which files should be checked, open the process on a workstation, go to pervasive monitor, and note the open files that process shows in the pervasive monitor. Then try the btrieve maintenance, macola export, or run a report that should access the file to see if you get an error 2.

Another type of file that sits out there when you have a system failure are files that have MM???###.btr, where MM is the module designator, ??? is something related to the process, ### is a numeric designator. I've seen these files in GL and OE commonly, and I believe they are created when a process begins and is updated periodically as records are processed. When a process fails, it allows a rollback using these temporary files. If the process terminates abnormally, these files are left behind and are not removed. I've never seen them prevent the process from restarting later, but it would be a good idea to delete them as part of your cleanup process here.
 
I have done this with wbmanage, a pervasive utility. I do not not have access to a Pervasive install right not so I cannot test this, but the actual program to use varies by version.

What version of Pervasive do you use?

Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
 
This I cannot test. It is no longer supported by Macola or even Pervasive for that matter.

Do you have a program called wbmanage in your pervasive directory?

Why have you not upgraded? To MS SQL I might add?


Software Sales, Training, Implementation and Support for Macola, eSynergy, and Crystal Reports

"If you have a big enough dictionary, just about everything is a word"
--Dave Barry
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top