StanGen
asked on
Retrospect failing to start - "Launch failed with error code -2857"
Yesterday I went to restart backups on our Mac OS X Restrospect server, which had gotten stuck, and found that I could not get Retrospect to start, either from the Dock or double clicking on it in the Applications folder. When I look at the console and try this, I see the error message: "Launch failed with error code -2857".
Searching around on the web I find that this is a Code Fragment Manager error, but the advice from Apple seems to pertain to developers running from command line and not to people just trying to run applications the usual way. Other people reporting similar problems turned up by googling don't seem to get any conclusive replies that apply to my case which would explain how to solve it. The number is not even on the Error Codes lists that go around from Apple's support site.
The Retrospect support site didn't mention the problem, and a search of their mailing list archive did not turn up the error code in any postings. I have tried repairing permissions, and a couple of restarts. I also tried removing the Configuration file for Retrospect just in case this was a corruption problem in that file, an issue that was pointed at as a startup problem for the OS 9 version. I opened the Retrospect log with a text editor to see if there were any hints there and it seemed to show that it had started to run a script at the beginning there, perhaps when I first woke it, just before I shut it down from the time stamp, but none of the subsequent attempts to start Retrospect up show up. I tried starting up Retrospect without the Maxtor firewire hard drives we back up to turned on just to remove that variable, but no effect.
I am not adverse to doing something at command line to fix it but I don't know what. If it takes a reinstallation of either Retrospect or the OS I'd like to know which one before just guessing.
This is Mac OS 10.3.9 and Retrospect server 5, not a great match, the Retrospect is a bit old and needs a version update, but it has worked, mostly, with the 10.3 series for a long time now. The machine has a very vanilla conifguration, serving simply as a Retrospect server.
Searching around on the web I find that this is a Code Fragment Manager error, but the advice from Apple seems to pertain to developers running from command line and not to people just trying to run applications the usual way. Other people reporting similar problems turned up by googling don't seem to get any conclusive replies that apply to my case which would explain how to solve it. The number is not even on the Error Codes lists that go around from Apple's support site.
The Retrospect support site didn't mention the problem, and a search of their mailing list archive did not turn up the error code in any postings. I have tried repairing permissions, and a couple of restarts. I also tried removing the Configuration file for Retrospect just in case this was a corruption problem in that file, an issue that was pointed at as a startup problem for the OS 9 version. I opened the Retrospect log with a text editor to see if there were any hints there and it seemed to show that it had started to run a script at the beginning there, perhaps when I first woke it, just before I shut it down from the time stamp, but none of the subsequent attempts to start Retrospect up show up. I tried starting up Retrospect without the Maxtor firewire hard drives we back up to turned on just to remove that variable, but no effect.
I am not adverse to doing something at command line to fix it but I don't know what. If it takes a reinstallation of either Retrospect or the OS I'd like to know which one before just guessing.
This is Mac OS 10.3.9 and Retrospect server 5, not a great match, the Retrospect is a bit old and needs a version update, but it has worked, mostly, with the 10.3 series for a long time now. The machine has a very vanilla conifguration, serving simply as a Retrospect server.
If you've already tried removing Library/Preferences/Retros
Hi StanGen,
The frist thing that I would do is refresh all of your retrospect preferences, which will include .plist files. Create a temporary folder and place all of your retrospect preferences and plist files in their. Now try to start retrospect, this will recreate all of those files (or should). If it opens then you know that you had a corrupted preferences file.
On the error above, this explains more what it is, and how to work around it, but I think what I have alread said is what you really want to do.
http://developer.apple.com/carbon/tipsandtricks.html#CFMLaunchError
If you decide to not wait anymore on responses then what you should do is reinstall Retrospect, it is unlikely that you need to reinstall the OS, but that would be a last case scenario.
Another thing that you may do if you do not have it already is upgrade to the latest version that you can
http://www.dantz.com/en/support/updates.dtml
Have you installed or upgraded anything on your server recently, and I mean anything?
Thanks,
Steven Stuart
The frist thing that I would do is refresh all of your retrospect preferences, which will include .plist files. Create a temporary folder and place all of your retrospect preferences and plist files in their. Now try to start retrospect, this will recreate all of those files (or should). If it opens then you know that you had a corrupted preferences file.
On the error above, this explains more what it is, and how to work around it, but I think what I have alread said is what you really want to do.
http://developer.apple.com/carbon/tipsandtricks.html#CFMLaunchError
If you decide to not wait anymore on responses then what you should do is reinstall Retrospect, it is unlikely that you need to reinstall the OS, but that would be a last case scenario.
Another thing that you may do if you do not have it already is upgrade to the latest version that you can
http://www.dantz.com/en/support/updates.dtml
Have you installed or upgraded anything on your server recently, and I mean anything?
Thanks,
Steven Stuart
ASKER
mazur:
Yes, I mentioned having tried repairing permissions. I am considering reinstalling Retrospect but will wait a bit more to see if anybody is directly familiar with this error.
sgstuart:
I'll go look for .plist files that might be involved. That Apple developer article is the one I was referring to. It is talking about a case of a developer launching the app from the terminal and hitting the same error message, which is why I don't think it applies except in a general informational sense.
As far as updates, yes, 10.3.9 itself was a recent update and there have been a few other updates recently from Apple via Software Update. It is possible that one of these has generated a new conflict. It is possible that I may have to purchase the next Retrospect version to resolve such a conflict.
Yes, I mentioned having tried repairing permissions. I am considering reinstalling Retrospect but will wait a bit more to see if anybody is directly familiar with this error.
sgstuart:
I'll go look for .plist files that might be involved. That Apple developer article is the one I was referring to. It is talking about a case of a developer launching the app from the terminal and hitting the same error message, which is why I don't think it applies except in a general informational sense.
As far as updates, yes, 10.3.9 itself was a recent update and there have been a few other updates recently from Apple via Software Update. It is possible that one of these has generated a new conflict. It is possible that I may have to purchase the next Retrospect version to resolve such a conflict.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
OK, the problem is solved now.
It turns out it was hard drive corruption with the Retrospect file crosslinked with a Receipt file for an iPhoto update.
I tried the verify and repair using Disk Utility which identified it as a problem of Overlapped File Extents and some other issues, but did not fix them, though it repeatedly claimed to have repaired the disk each time. A google search on "Overlapped File Extents" turned up some good advice on how to repair that. The two inodes that were identified as overlapped files included Retrospect and the iPhoto receipt file. Deleting them followed by another pass of fsck via Disk Utility sorted out the hard drive, and then I reinstalled Retrospect, put back the Retrospect Config file I had earlier removed, and started a backup.
Thanks.
It turns out it was hard drive corruption with the Retrospect file crosslinked with a Receipt file for an iPhoto update.
I tried the verify and repair using Disk Utility which identified it as a problem of Overlapped File Extents and some other issues, but did not fix them, though it repeatedly claimed to have repaired the disk each time. A google search on "Overlapped File Extents" turned up some good advice on how to repair that. The two inodes that were identified as overlapped files included Retrospect and the iPhoto receipt file. Deleting them followed by another pass of fsck via Disk Utility sorted out the hard drive, and then I reinstalled Retrospect, put back the Retrospect Config file I had earlier removed, and started a backup.
Thanks.
Hi StanGen,
I am glad that you got it working. It is also a good thing to know in case others run into this problem. I am sorry that I was unable to help you here, but at least you got it.
Thanks,
Steven Stuart
I am glad that you got it working. It is also a good thing to know in case others run into this problem. I am sorry that I was unable to help you here, but at least you got it.
Thanks,
Steven Stuart
good to hear your problem was solved - rock on!