mjbolzan Posted February 8, 2008 Report Share Posted February 8, 2008 Sometimes when i check my macs in the morning, I'll find on the screen the message-- "Can't open the operations log, error -48 (duplicate name). It is already open in another application.". What would be the "OK" button contains 4 A's, each in a square. i think this is from the last resort font? The scheduled backup will not have run. The only unusual thing i have done which might bear on this is--when setting up the macs, i did log in once as root and start retrospect, unchecking the checkbox "require authentication". Mac OS X 10.4.11. Retrospect desktop 6.1.138. I have now seen this error 3 times in a month on 2 different macs. all backups occur via backup server scripts to file sets on firewire drives. restarting and logging back in fixes the error. The error occurred infrequently before but my sense is it is more frequent since the upgrade to 6.1.138. The only relevant posts i could find on the internet pertained to Retrospect Express 5 on Panther and seemed to finger retrorun. quitting it via activity monitor would clear the issue. Any causes and solutions? Quote Link to comment Share on other sites More sharing options...
Mayoff Posted February 8, 2008 Report Share Posted February 8, 2008 Sounds like the operations log could be corrupted. You can delete it from Library>Preferences>Retrospect>Operations Log. Retrospect will create a new one next time you open the software. Quote Link to comment Share on other sites More sharing options...
mjbolzan Posted February 9, 2008 Author Report Share Posted February 9, 2008 Quote: Sounds like the operations log could be corrupted. Thank you for answering. i question if that could be it. the logs are small and the problem goes away on restart. these macs are pretty vanilla. it begs the question--if the logs are corrupted, what's corrupting them? Quote Link to comment Share on other sites More sharing options...
n0mad Posted August 13, 2008 Report Share Posted August 13, 2008 The problem goes away if I just launch retrospect after dismissing that error. Which is annoying since that means its harder to test what the cause is. I can run scheduled backups after I run it, I've tried running 3 backups (took about 10 minutes each run) and after that I assumed it was working fine. 1 week later I get a call - backup hasn't been done again. Unfortunately I never set this up so I don't know if anybody logged in as root and unchecked that box. I'll be running an uninstall (through the installer application they have) and reinstalling it and seeing if that helps. But I doubt that it will since I've manually removed all the files I've found in relation to retrospect... including preferences and log files. Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted August 13, 2008 Report Share Posted August 13, 2008 "Can't open the operations log, error -48 (duplicate name). It is already open in another application." Taking the error message at its word, I'm wondering if this might me a manifestation of the double-auto-launch bug that has plagued some users for years. - Is there an entry in the log for the time that this happens? when setting up the macs, i did log in once as root and start retrospect, unchecking the checkbox "require authentication". Why did you do this? There is nothing in the User's Guide suggesting that you should. Retrospect always runs as root; preference settings you select while logged into the Finder as a normal user will be the same as making those changes logged in as root. Retrospect will run correctly on machines where the root user is never enabled. Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted September 15, 2008 Report Share Posted September 15, 2008 Interesting, I've now seen this error myself a couple of times. Best as I can tell, it's script dependent, as it occurs with a weekly script I have setup, but does not occur with the nightly scripts that run fine. Operations log shows no attempt to even launch Retrospect, so it doesn't look like the double-launch bug (as has been reported). See screen shot Quote Link to comment Share on other sites More sharing options...
Mayoff Posted September 15, 2008 Report Share Posted September 15, 2008 Dave, the screenshot didn't make it. Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted September 15, 2008 Report Share Posted September 15, 2008 AAAA Error Dialog: Quote Link to comment Share on other sites More sharing options...
Mayoff Posted September 16, 2008 Report Share Posted September 16, 2008 very strange screenshot, the button is really messed up. Quote Link to comment Share on other sites More sharing options...
mjbolzan Posted September 20, 2008 Author Report Share Posted September 20, 2008 Why did you do this? There is nothing in the User's Guide suggesting that you should. It's been a few years since i checked it but last time i did this, it allowed Retrospect to run without logging in. Retrospect busts through the login screen. maybe not the best idea.... I'm glad you have now seen this error too. i have a subjective sense that it happens more often on dual processor machines. for one customer running on a dual G5, this happens about once a month. last time it did, i completely nuked the install, including the root preferences and re-did it (kept the configuration file though). i'm about to kill the auto launch entirely and just use cron to launch retrospect. Quote Link to comment Share on other sites More sharing options...
CallMeDave Posted September 20, 2008 Report Share Posted September 20, 2008 last time i did this, it allowed Retrospect to run without logging in. Retrospect runs as a root owed process, always. It doesn't matter _at all_ what the user does with the GUI application in that regard. Retrospect can launch behind the Login Window application when no user is logged into the Finder if a script comes due; attempting to interact with the program at that point will prompt the user for authentication, with "root" pre entered in the name field, but will respond to any valid admin credentials. You don't need to ever log in to the Finder as root in order to use all of Retrospect available functionality. > i have a subjective sense that it happens more often on dual processor machines. Not here; it's an old Power Macintosh G4 733 "Quicksilver" with a single processor. Dave Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.