WRShaw Posted March 10, 2008 Report Share Posted March 10, 2008 (edited) Running Retrospect MSVP 7.5.508 & 7.5.13.100 Everything has been running well for over one month, and then this weekend for no explaination you see the situation now depicted in the PDF. The Environment sees the devices, but the status tab doesn't. I have rebooted including POR every device and cannot get this situation to change, including removing,disabling the devices which do appear in the Windows Device Manager. any help would be appreciated. thanks, Bill Windows 2003 on HP DL380... Server has been in place for one year, we have been using Retrospect since 2003. Edited March 10, 2008 by Guest Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 10, 2008 Report Share Posted March 10, 2008 That is strange. Retrospect is loading a driver but the device isn't showing up. What is Ignored on the first ID? What happens if you un-ignore it? Quote Link to comment Share on other sites More sharing options...
WRShaw Posted March 10, 2008 Author Report Share Posted March 10, 2008 The first drive is the CD-rom. In my attempts to diagnose/correct. I disabled it, nothing changed and then attempted to re-enable it. One other cute thing is happening. Retrospect is not stopping. You can exit the application, but it remains in task manager. An attempt to relaunch gives you the running in another session. the only way to clear is to logoff and back on between attempts. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 10, 2008 Report Share Posted March 10, 2008 Have you tried removing the config75.dat file from docs and settings/all users/application data to see if the problem goes away? That may help us identify if this is corrupt prefs. Quote Link to comment Share on other sites More sharing options...
WRShaw Posted March 10, 2008 Author Report Share Posted March 10, 2008 Removing the Config75 files gave me back my drives, but of course lost all my scripts, etc... How do I recover from this? Do you have magic tool to fix the config75 file? thanks, Bill Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 10, 2008 Report Share Posted March 10, 2008 So we know the problem is not hardware or drivers. Corruption to the preferences is the real problem. I would try this: 1) Put the config file back so you get your settings again. 2) Inside Retrospect type ctrl-alt-P-P 3) Go to Device Debugging 4) Check "Clear all device info" 5) Quit and open Retrospect Check your devices Quote Link to comment Share on other sites More sharing options...
WRShaw Posted March 10, 2008 Author Report Share Posted March 10, 2008 (edited) I tried that and it didn't work, so is there something else I can try? Thanks, Bill Details: Clear all devices, logoff. Retrospect hangs nothing happens. Logoff again and restart Retrospect - same condition as before (no devices, Retrospect will not completely shutdown). Second attempt: On restart wait 5 minutes - Retrospect will come up, but the condition hasn't changed. Edited March 10, 2008 by Guest Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 10, 2008 Report Share Posted March 10, 2008 Did this shutdown problem still happen when you removed the preferences? This really does sound like corrupt config file. You can try to restore an old version of this file from your backup, with a modify date before the problem started. You can also try to uninstall and reinstall Retrospect, incase part of it is corrupted. Quote Link to comment Share on other sites More sharing options...
WRShaw Posted March 10, 2008 Author Report Share Posted March 10, 2008 Here is the log in case it helps you figure out what the problem is, I need to restore the last working config75.dat and get my backups running again. Thanks, Bill Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 10, 2008 Report Share Posted March 10, 2008 Thanks, I will ask an engineer to review the log. The fact that removing the config file fixed the problem, really points to a damaged preference file more then a hardware issue. Restoring an old Config file is the best option to try next. Quote Link to comment Share on other sites More sharing options...
WRShaw Posted March 10, 2008 Author Report Share Posted March 10, 2008 We're up and running, but I have lots of manual work to do before we are whole. Thanks for your assistance! Bill 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.