Rapid Posted July 1, 2003 Report Share Posted July 1, 2003 We use Windows Retrospect 6 with the latest clients for that version. Regularly Retrospect Service will stop running on a Windows 2000 server. The only way to restart it is by rebooting the server running the client concerned. Several but not all Windows servers on our network suffer a similar problem. Anyone help? Link to comment Share on other sites More sharing options...
Mayoff Posted July 1, 2003 Report Share Posted July 1, 2003 What do you mean by "stop running"? Do you get an error? Is the program crashing? Is if failing to Autolaunch? What happens if you manually launch it? Link to comment Share on other sites More sharing options...
Rapid Posted July 2, 2003 Author Report Share Posted July 2, 2003 What happens is that Retrospect can no longer detect the client "source". As a double check we use WhatsUp to monitor Retrospect's TCP port number (497) on all our servers. When the fault occurs WhatsUp shows that port 497 is no longer operational, trying to restart Retrospect Client within Windows Services Mamager is unsuccessful i.e. a Windows error message says that the service cannot be restarted, and Retrospect shows that the source cannot be detected. At this point the only resolution we have found is to restart the whole server. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.