PC-3000 Forum

Hello,

On two recent cases I've handled, data extractor has ended up in a state where it refuses to close, it just complains that I have to stop all running jobs. Don't exactly remember the chain of events the first time, but the second time (today) this happened after I had mounted and unmounted the drive as a virtual device. I had also powered down the drive. In the end, I had to kill PC3000 to be able to continue.

Now I have the files, but I can't open them in Data Extractor. I can concatenate the files manually and use other tools, because I managed to recover the drive perfectly, but I can't open the case in Data Extractor again, it just hangs forever when I open. I've selected "work with data copy", and disabled all other options to avoid waiting for a HD which isn't there.

I've upgraded from UDMA 4.9 to 5.1, and tried again to open the case, but still no luck.

Any ideas how to recover this case in Data Extractor?

1st method:
1. Install the version this task had been created with.
2. go to task folder and rename task.prm to some other name.
3. set task.bak name to task.prm .
4. Run Data Extractor and launch this task


The other method, that could help, if this method didn't help is next:
1. create a new task with this drive
2. open its folder and take its task.prm file to another task folder you expirience problems.
Agree to replace the file.
3. Run the task and see what will happen.

If you will see any errors displayed within "Log" tab, please copy them to forum.

Thanks. I tried to use task.bak on the first case, but that didn't help, Data Extractor just hangs hard when I try to open this case, and I have to kill it again. Nothing in any log window.

Perhaps I can recreate task.prm myself, or edit it if there is a problem? Do you have a tool that might fix it? If the disk dies and DE crashes, it's too bad if the case is lost...

Hi,

Is there nothing to do for cases like this when the disk is dead?? That's a disaster. Can you make a tool to recreate a clean task.prm, or make sure DE always keeps a copy of "last known working" prm? If I can't rely on DE, I have a problem.

Ketil

I used second method that could help me . Thanks