Jump to content

bwgoodkin

Members
  • Content count

    11
  • Joined

  • Last visited

Community Reputation

0 Neutral

About bwgoodkin

  • Rank
    Newbie
  1. Thanks, but that's not really a "fix". :-) The reason that the monitor comes up is that there's a background version running, so, obviously, killing the background task in task manager will "solve" the problem. However, you've just killed your backup task, too, and will have to manually restart it. I'm also not so sure you're not risking corrupting your backup sets by doing such a hard kill. The work around for me is to just have Retrospect launched all of the time. That's not hard for me because I'm backing up my desktop machine, but this wouldn't be a good fix for a server or any other machine that you can't leave "logged in". IMHO, the only fix will be for EMC to figure out how to get this to work the way it used to in Windows XP, where the background task would show in the task bar, and you could launch the full program from there without seeing the monitor.
  2. bwgoodkin

    Starting Retrospect brings up useless window

    See Topic#33739. http://forums.dantz.com/showtopic.php?tid/33739/ I'm seeing this issue when Retrospect launches from a service and has any kind of hang-up, rather than when I launch Retrospect directly. In XP, with Retrospect 7.6, when I logged in, I'd see Retrospect running in the system tray and I'd be able to launch the GUI and correct anything. Now that I'm running 7.7 in Win7 64-bit, I just get the monitor and have no way of correcting the issue without killing the old session and starting a new one. Just seems like Vista and Windows 7 work differently than XP and EMC hasn't updated their software accordingly.
  3. bwgoodkin

    What is the REAL upgrade Price????

    I paid $29 to upgrade from 7.6 to 7.7 when I upgraded my computer from XP Pro (32bit) to Windows 7 (64 bit). I'm still seeing the "no UI when auto-launched" problem with 7.7. See Topic#33739. http://forums.dantz.com/showtopic.php?tid/33739/ I'm seeing this issue when Retrospect launches from a service and has any kind of hang-up, rather than when I launch Retrospect directly. In XP, with Retrospect 7.6, when I logged in, I'd see Retrospect running in the system tray and I'd be able to launch the GUI and correct anything. Now that I'm running 7.7 in Win7 64-bit, I just get the monitor and have no way of correcting the issue without killing the old session and starting a new one. Just seems like Vista and Windows 7 work differently than XP and EMC hasn't updated their software accordingly.
  4. bwgoodkin

    Retrospect Activity Monitor

    Seems like this is still a problem in Windows 7 (I'm running 64-bit, but I don't think that has much to do with it) and with Retrospect 7.7. See Topic#33739. http://forums.dantz.com/showtopic.php?tid/33739/ I'm seeing this issue when Retrospect launches from a service and has any kind of hang-up, rather than when I launch Retrospect directly. In XP, with Retrospect 7.6, when I logged in, I'd see Retrospect running in the system tray and I'd be able to launch the GUI and correct anything. Now that I'm running 7.7 in Win7 64-bit, I just get the monitor and have no way of correcting the issue without killing the old session and starting a new one.
  5. bwgoodkin

    Retrospect Opens Activity Monitor Not Backup Program

    See Topic#33739. http://forums.dantz.com/showtopic.php?tid/33739/ I'm seeing this issue when Retrospect launches from a service and has any kind of hang-up, rather than when I launch Retrospect directly. In XP, with Retrospect 7.6, when I logged in, I'd see Retrospect running in the system tray and I'd be able to launch the GUI and correct anything. Now that I'm running 7.7 in Win7 64-bit, I just get the monitor and have no way of correcting the issue without killing the old session and starting a new one.
  6. See Topic#33739 http://forums.dantz.com/showtopic.php?tid/33739/ If this is an issue in Vista or Windows 7, I think it's probably due to how Retrospect is running scheduled backups that start when Retrospect isn't already running (i.e. launched via a service).
  7. bwgoodkin

    Wrong and unusable UI on Windows 7

    Here's the "warning" / "error" message from Windows 7:
  8. bwgoodkin

    Wrong and unusable UI on Windows 7

    I, too, am having the same problem with Windows 7, but I'm already using Retrospect 7.7, so that's not going to fix the issue. Here's what I think is going on (Someone please correct me if I'm wrong and provide the "fix". I've already tried uninstalling and reinstalling since this was an upgrade from 7.6.)... Starting with Windows Vista, and continuing with Windows 7, processes started by a service (e.g. Retrospect Launcher) can no longer be seen in a user session - a result of "service hardening" so that a rogue service can't interact with other programs. In Windows XP and earlier versions, if Retrospect Launcher started a backup, you'd see Retrospect in the system tray when you logged in and you'd be able to interact with the GUI just like you started it yourself. Click here for an article about "service hardening" at techrepublic.com IMHO, the fact that the Retrospect GUI was not updated for Vista/Windows 7 so that the functionality is the same as it was for XP really is an indication that Retrospect isn't fully compatible with Vista/7 - it's critical that a backup manager be able to interact with the GUI for things like alerts to change the media, etc., even when the script was started by the service. (In fact, when the background task fails and tries to display a message, you get something to the effect of the following: "A program on this computer is trying to display a message The program might need information from you or you permission to complete a task This problem occurs when a program is not fully compatible with Windows. Please contact the program or device manufacturer(s) for more information." There are a few work-arounds, but I think the only acceptable one is for EMC to update the code: 1) Make sure that the background Retrospect session finishes before trying to access it 2) Rename the "monitor" program so you get a pop-up that allows you to effectively kill the other session. This will stop any running jobs, though, and doesn't stop the job immeadiately. (something like "\Program Files\Retrospect\Retrospect 7.7\monitor\retromonitor.exe") 3) Keep yourself logged in and keep Restrospect running so that background jobs are running in the GUI in your session, rather than getting launched by the service.
  9. bwgoodkin

    Starting Retrospect brings up useless window

    What I'm finding is that Retrospect is running as "SYSTEM" instead of my user account. As a result, I can't actually see the application, even though it's running and I'm the only user on the machine. It's properly bringing up the monitor because there's already a session running. If I rename the monitor app, then I get the pop-up informing me of the other session. I'm going to look into ways of forcing it to use my user - I thought "run as the logged in user" setting would have been good enough. This is really just a symptom - not sure why the session hasn't completed properly in the first place - says it's waiting for media...wish I could see what the real problem is. This problem didn't seem to happen with Retrospect 7.6 in Windows XP Pro, but started for me when I upgraded my computer to Windows 7 64-bit and Retrospect 7.7. I'm also not seeing the "background task" icon in my system icon tray. The problem really seems to be a difference in how Windows XP and Vista/7 seem to treat the sessions run by the launcher. In XP, I could actually see the GUI when it was launched by the service. However, in Windows 7, I can't see the GUI, even though I can see the program in Task Manager. I've tried "allow service to connect to Desktop" and Run as user, but neither solved the problem for me. Searching the web, this issue doesn't seem limited to Retrospect...but it would be good if we could find a solution since there are times that the retrospect process needs user input.
  10. As a follow-up to my previous post re: the "116 error", I've been working with Iomega support and they provided me with copies of Iomega QuikProtect and RetrospectExpress HD 2.5. Both of these products also are having trouble with my network drive. Retrospect 7.6 has been working flawlessly with a different drive for over a week, even when that drive is connected via a network share.
  11. I'm having the 'error -116' issue with an Iomega Home Media Network Hard Drive. I have the issue whether or not I have the drive directly connected to the Retrospect computer or if I have the Iomega "NAS" hooked up through a hub. I've had the issue with two different drives and I've been working the issue with Iomega as a hard drive issue. At the same time, I've have flawless backups for the last week using Retrospect by backing up to a 1TB FireWire-connected WD My Book Home Edition drive. I've also had great success backing up with Retrospect over the LAN using the same 1TB My Book as a shared drive hooked up to my laptop. Also at the same time, I've been able to torture-test my Iomega NAS without any notable issues over the same time period, so I'm quickly getting to the realization that it's an interaction between Retrospect and the Iomega network drive. Hope the previously mentioned Windows update is right around the corner and will contain a fix for this.
×