rob.s Posted November 14, 2005 Report Share Posted November 14, 2005 I’m having a problem with a new Exchange agent that I have recently added to our server. At first it appeared to work but after a few days it stopped backing up. Now when trying to select a source the Exchange server is greyed out and apparently not licensed. When I try to select it and use my licence Retrospect crashes with the following error: Assertion failure at “elem.cpp-986” Retrospect runs as is a domain admin and there are emails in this users mailbox. I have also tried creating another user who is a domain admin with mailbox but to no avail (as advised by tech support). This is a big problem because our Exchange server is not being backed up. Can anyone help please?! Link to comment Share on other sites More sharing options...
natew Posted November 15, 2005 Report Share Posted November 15, 2005 Hi It may be corrupt settings files. Close Retrospect and rename the Retrospect settings folder to "retrospect-orig". Then relaunch the program, enter you license codes and try to login the Exchange databases again. Config files are located at system root\documents and settings\all users\application data. Thanks nate Link to comment Share on other sites More sharing options...
rob.s Posted November 16, 2005 Author Report Share Posted November 16, 2005 Thanks Nate, just tried that and it appears to have done the trick! Link to comment Share on other sites More sharing options...
rdb Posted June 6, 2006 Report Share Posted June 6, 2006 Yes, that solves the license problem, but what about the clients, volumes & scripts that were defined in the old config files? Don Link to comment Share on other sites More sharing options...
nekr0phage Posted June 6, 2006 Report Share Posted June 6, 2006 Hi Don, Since all of that information is stored in the configuration files that were damaged, those will need to be redefined and recreated. To guard against this inconvenience in the future, you can make a copy of the configXX.dat file and store it in another directory, or even a new folder in the same directory. Retrospect has a built in guard against having to do this, which is the .bak version of the config file. When you exit Retrospect it exports the .dat to the .bak, unfortunately corruption in the configs is not always caught in time and often exported to the .bak file. Link to comment Share on other sites More sharing options...
rdb Posted June 6, 2006 Report Share Posted June 6, 2006 I'll make a copy as soon as I get finished with this note... I was able to solve my elem.cpp-986 error by removing the client for my Exchange server & recreating it. Once recreated, I was able to reassign my license to the server without Retrospect crashing. Thus, I didn't have to recreate everything... Thanks, Don Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.