mlandau248 Posted March 10, 2010 Report Share Posted March 10, 2010 I have been tasked with coming up with a new backup solution for both my internal IT and my companys customers. At first glanz Retrospect 7.7 with exchange looked promising but every backup of mailboxes fails with "Assertion Failure at "tstring.cpp-374"". This is installed on SBS 2003 R2. I will have to give up on testing for recommendation if there is no resolution to this. Thank you. Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 10, 2010 Report Share Posted March 10, 2010 Please call tech support. We may be able to provide you with a pre-release version that contains some bug fixes with exchange backup Quote Link to comment Share on other sites More sharing options...
allisong Posted March 11, 2010 Report Share Posted March 11, 2010 I have the same issue on the production version see post made earlier, I have had to downgrade to get around the issue, using 7.7 clients on 7.6 software! If there is a version fixing exchange backups I would be grateful! See post: http://forums.dantz.com/showtopic.php?tid/33438/ Geoff Quote Link to comment Share on other sites More sharing options...
mlandau248 Posted March 12, 2010 Author Report Share Posted March 12, 2010 (edited) Will keep you posted if I can. Thanks. Marc Edited March 12, 2010 by Guest Quote Link to comment Share on other sites More sharing options...
mlandau248 Posted March 12, 2010 Author Report Share Posted March 12, 2010 Robin - Thank you for your reply but I'm afraid things have in my opinion gone from bad to worse. I called your tech support department and listened to ringing for over 5 minutes before I even got an auto attendant. Really, just ringing. I design enterprise call centers, please let me know if you need help over there. 15 more minutes of music on hold before a live answer took my information and opened a ticket. Transfer to an engineer took another 5 minutes. After just a short while on the phone with the engineer, he had me change some settings, reproduce the error and send him the log files via e-mail. I did and awaited a reply. The reply came 5 hours later in a single sentence "Un license exchange server, exit retrospect, re license exchange server, then run the backup again.". Ok, I'll bite. Made the changes, tried a backup again, same results. I sent another set of logs. That e-mail was sent over 11 hours ago with no reply. Ticket number is 100311-00610. As I stated in my first sentence, bad to worse. Marc Quote Link to comment Share on other sites More sharing options...
Mayoff Posted March 12, 2010 Report Share Posted March 12, 2010 This error is fixed in the next scheduled release. Our tech support can provide you with a beta version to try. Do you know if you were working with our european call center or the US? Quote Link to comment Share on other sites More sharing options...
allisong Posted March 18, 2010 Report Share Posted March 18, 2010 Please let us KNOW when the next scheduled release is expected, thanks! Quote Link to comment Share on other sites More sharing options...
allisong Posted March 29, 2010 Report Share Posted March 29, 2010 Fixed in 7.7.325! Well done. 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.