alexracheck Posted February 7, 2013 Report Share Posted February 7, 2013 Hello! In the last two weeks I have been gettings this error 1111 (locked range conflict) on several people's backup when it is trying to copy their pst files from Outlook. Any ideas? Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted February 7, 2013 Report Share Posted February 7, 2013 Have them exit Outlook when the backup runs or buy the "Open File Backup" Add-On. Quote Link to comment Share on other sites More sharing options...
johnnymacgo Posted February 8, 2013 Report Share Posted February 8, 2013 There is an option called "Force Backup of Microsoft Outlook data" that will let Retrospect close Outlook to backup its data files. It's located under Windows -> Outlook and might be worth a try. Quote Link to comment Share on other sites More sharing options...
alexracheck Posted February 12, 2013 Author Report Share Posted February 12, 2013 We do have a license for Open File Backup and I have checked the box to Force Backup of Microsoft Outlook. Not sure what else could be causing this error. Is file size an issue? Quote Link to comment Share on other sites More sharing options...
Lennart_T Posted February 13, 2013 Report Share Posted February 13, 2013 That's puzzling. It works just fine for us on Retrospect 7.6. Some .pst files are 2-3GB. I have no solution for you. Sorry. Quote Link to comment Share on other sites More sharing options...
alexracheck Posted February 13, 2013 Author Report Share Posted February 13, 2013 Hello and thank you for you feedback. We are having this error message on Proactive Backups and Managed Scripts. Here are my setttings for the Proactives for Laptop's only: Options for Backop Execution as Thorough Verification (Should I change this to Media, then it won't have to communicate back to the laptop as much?) Not really sure of difference between Thorough and Media 5,000 ms for Disk Inactivity Threshold 10 minutes for Retry Timeout Your thoughts? Quote Link to comment Share on other sites More sharing options...
alexracheck Posted February 20, 2013 Author Report Share Posted February 20, 2013 I found the issue was only with Windows 7 and not our XP systems. Upon further investigation I realized since Microsoft now redirects My Documents to Documents was the cause for my error. Removing my docs from the source and only using documents resolved the issue. 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.