This is a staging forum for AgileBits, not an official support forum. Visit http://discussions.agilebits.com instead.

Knox 2.0 crashes after restore

OSXfan
OSXfan Junior Member
edited December 1969 in Knox
Hi! I'm a new Knox user with a small problem. I can back up Knox vaults just fine, but restores are problematic. The restores appear to work, but Knox quits and must be manually relaunched when vaults (1 or more) are restored. This is happening with Knox 2.0 in OS X 10.5.8 on a PPC iBook during restores from backups on a USB flash drive and my Mac's Desktop.



Also, while the restored vaults can be opened in Knox, their filenames retain the date and time information from the backup, and have the ."sparsebundle" extension. When I open these vaults in Knox, this extraneous info disappears, and my filenames go back to normal (eg. "MyVault 2010-6-11 12.12.sparsebundle" goes back to "MyVault" in both Knox's menu and in the Finder). Any chance this extra filename info is there because the restore hasn't quite completed?



Thanks for any help!

Comments

  • thightower
    thightower "T-Dog" Agile's Mascot Community Moderator
    edited December 1969
    In re to the file name thats because the vault / bundle is associated with diskimagemounter and once you open it with knox, knox reclaims the vault as its own. This would be perfectly normal at least in my experience. Especially if you have set knox as the default app for such file types. Which would be the case since its a knox created backup you are restoring.



    As for the issue about knox quitting, someone else may need to chime in on that.



    Edit wheres my manners welcome to the forums :)
  • OSXfan
    OSXfan Junior Member
    edited December 1969
    Thanks for the info and welcome!



    Unfortunately, Knox still crashes for me after any restore. The same thing happens running 10.6.3 on my Core2Duo iMac. Can't imagine what could be happening. Knox is running from the Applications folder on both machines, I'm an admin user on each, and both OS X installs are standard––no crazy haxies running or anything like that. Strange that only one part of Knox's functions would go screwy like this. If anyone has any ideas of what to try, I'd welcome 'em!
  • MikeT
    MikeT Agile Samurai
    edited December 1969
    Can you post any errors from Knox or System in Console.app?



    You might want to reinstall Knox and delete the preference files with it, you might have a corrupted preference file, so delete that as well. It's located at ~/Library/Preferences/ with the name, com.knoxformac.knox.plist.
  • jpgoldberg
    jpgoldberg Agile Customer Care
    edited June 2010
    Hi OSX fan,



    Another user has reported the identical problem, and we have been working on this. Can you confirm that despite the crash, the restored vaults are perfectly fine? That is what the other user reporting this said.



    Could you please send the crash report to [email]support@agile.ws[/email]. You can send us the crash report clicking "Report" in the crash window, but instead of sending the report to Apple, copy and paste the crash log into an email to us. Alternatively, you can find the Crash logs in this folder:



    Home > Library > Logs > CrashReporter



    "Home" is your own account's main folder. In the Finder's sidebar it's represented by an icon of a house with your account's name beside it.



    If you find the crash log in there, you can drag and drop it onto your email.



    Also, there could be errors in your Console so I'll need to see those too. You can get these logs as follows:



    1. Launch Console, found in the /Applications/Utilities folder.

    2. Click the "Clear Display" button on the toolbar.

    3. Do your restore and let it fail; wait 15 seconds to let the Console refresh.

    4. Press CMD-A to select all the logs and CMD-C to copy them to your clipboard.

    5. After starting your email to [email]support@agile.ws[/email] press CMD-V to paste the logs.



    I know that Chad, who has been looking at the other case I've mentioned, will appreciate the logs and crash reports.



    Thanks for your help in this. We hope to have this problem identified and fixed shortly.



    Cheers,



    -j