Inline Posted August 8, 2003 Report Share Posted August 8, 2003 I have quite a few clients running this version of retrospect and having this problem (ie, all my clients running retrospect 5.6). Is there a proper fix (not the temporary workaround in your knowledgebase) anywhere? Also, you can provide a temporary workaround by launching retrospect, turning off autolaunch, exiting retrospect, launching and turning it back on rather than having to reboot a server. Link to comment Share on other sites More sharing options...
natew Posted August 11, 2003 Report Share Posted August 11, 2003 Hi Can you post some more details please? Thanks Nate Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.