James,

I created a new archive and performed a capture action of a single folder. The capture completed OK. Next, I ran a Compact action...this failed....a re-index of the archive also failed. Repair of the archive failed too.

The report was sent.

Thanks,

GKG

Just an update...

I performed the Quit and Uninstall and then launched the application again, authenticated, etc.

So far...no issues...

I will keep testing and let you know if I see issues...

Thanks again...

GKG

Ok...I will give it a try...

Thanks

Report sent...

James,

The same odd behavior occurred again this morning. This time, I performed a video screen capture to illustrate what is happening.

As you can see from the video...a verify action is manually launched from the Actions window...the Action window does not change at all...however, you can also see from the log window that the verify is indeed kicked-off. The monitor window never opens either, at it should.

I can continue to launch other actions from the action window with the same effect...they execute...but no Action window status and no monitor window. Also, scheduled event triggers to not work when this occurs ether...actions must be kicked-off manually.

Now, if I reboot...it may work normally or it may exhibit these same symptoms. I have noticed that...if I wait maybe 30 minutes before launching QRecall...the symptom occurs with less frequency. Could this possibly be some type of race condition...where certain QRecall processes are getting started out of order?

Very odd...but I thought I would send the video so you don't think I am hallucinating.

Thanks,

GKG

James,

Ok...I have rebooted my systems several times...and then launched QRecall...

The preferences are now Ok...i.e., they remain as they were set before...and I cannot recreate the oddity from earlier...it seems to be working fine now. Possibly, some issue during the installation of the new beta...I do not know..

If I see any other issues...I will let you know...

Thanks,

GKG

James...


I looked around a bit...and discovered that in the QRecall preferences...the Monitor tab's checkboxes had all been reset to "not" selected. I selected the ones I normally use...rebooted....and now QRecall seems to be working as expected.

Let me see if I can recreate the error.

New Beta 54...running on Lion 10.7.2....
Installed new beta...rebooted system...launched QRecall....opened Action Window...launched a task...Action Window does not change to "Running"...Status monitor shows nothing...but a check of the QRecall log shows the task was submitted...repeated this 3 more times. Kick off a task...the Action window shows nothing is happening...the status monitor also shows nothing....but task is actually submitted.

Report sent...

GKG

Thanks!!!

I guess you ran into more issues?

GKG

Greetings James,

Any timeframe on the new beta release that you mentioned in this thread?

Thanks,

GKG

Yes...absolutely...

I will move the repaired archive back to a local drive for now...

As after the new beta arrives...I will move it back and try it again with the new enhanced logging...

Thanks,

GKG

I guess I spoke too soon...the capture is once again failing...

James,


Thanks for the update. I attempted the same capture again today...and this time it worked....very odd.

The volume does have plenty of space available...so...I think your "more likely" scenario is probably correct.

Thanks,

GKG

James,


I ran into an issue this morning performing a capture to a network share. The capture bombs right at the end...with a "Cannot convert FSRef to path" error.

I I repair the archive...and move it to a local SATA drive...the same capture works fine...it just fails when the archive is located on the SMB share. I have sent a report...

Thanks,

GKG