Jump to content

optotronic

Members
  • Content count

    6
  • Joined

  • Last visited

Community Reputation

0 Neutral

About optotronic

  • Rank
    Occasional Forum Poster
  1. Latest update - backup reports better on mac

    Well, I did get a response, and after ~5 follow-ups and replies, I was told that the problem is a known issue with email servers that don't use SSL for authentication, and that it will be fixed in the March release.
  2. Latest update - backup reports better on mac

    Thanks, David. I submitted a support case. I don't have ASM, so I don't expect a response, but I prefer they know about problems I encounter, especially those that cost me time. I saw that, thanks. I was more interested in seeing whether a new feature in the new version of Retrospect that I purchased would improve my workflow than I was of writing a replacement notification mechanism.
  3. Latest update - backup reports better on mac

    Here's one, sent last night from Retrospect for Windows Desktop Version 12.6.0.157. I tried setting up a header and footer as is supported in 12.6, but it didn't make a difference. I wasn't really surprised, as the email says
  4. This problem recurred several times on various clients. Forgetting and re-adding the client fixed it each time, until the next time the problem arose. I believe the Retrospect (server) preferences were being corrupted by the bug that causes two copies of Retrospect to launch in some cases. To clarify, there is a bug that causes two copies of Retrospect to launch sometimes. I think the corruption occurs when two copies of Retrospect are running. Presumably the code to write the preferences is not designed for multiple access. I worked around this bug by disabling the option to auto launch Retrospect when a script needs to be run. Instead I leave Retrospect running at all times. This is not ideal, but not having the backups is worse. Bill
  5. Has anyone found a real fix or another workaround for this? I just realized today what was happening, but for me it happens when the machine autostarts and automatically logs in, which is the normal situation for the backup. So, MHL's workaround doesn't work for me. Here's a clip from my log file: Retrospect version 6.0.193 automatically launched at 5/20/2004 9:35 PM Retrospect version 6.0.193 automatically launched at 5/20/2004 9:35 PM + Retrospect Driver Update, version 5.3.102 + Retrospect Driver Update, version 5.3.102 + Normal backup using All computers at 5/20/2004 9:35 PM To backup set Backup Set B 5/20/2004 9:35:48 PM: Connected to DELL - 5/20/2004 9:35:37 PM: Copying DRIVE C (C:) on DELL + Normal backup using All computers at 5/20/2004 9:35 PM Can't add to backup set Backup Set B: The catalog is locked. 5/20/2004 9:35:55 PM: Execution incomplete. Shutdown at 5/20/2004 9:36 PM Dantz, have you duplicated this in house yet?
  6. I also encountered this error message when accessing a particular Windows 2000 client while using Retrospect Workgroup 6.0.193. Forgetting and re-adding the client fixed the problem. Bill
×