Hello, From the description, there is a issue with permission. But after one hour, the issue disappeared. So I think other processes was using the resource when you access it. Please checkif replication is normal. Best Regards, Lisa

antivirus is the usual culprit when this sort of thing happens. depeneding on what av you use an update may have changed the list of exclusions. if you are using file level antivirus on your exchange have a look at the sites in the following link, and make sure that everything is still set up correctly. http://blogs.technet.com/b/nawar/archive/2011/02/17/exchange-antivirus-exclusion-lists.aspx

Server 2003 x64 Enterprise SP2 MS Exchange Server 2007 SP3 CCR. Hello I had a strange event with our Incremental backup last night, this Job runs every Monday night and has run without issue for years before. The Job started, and successfully completed on Storage Groups 1, 10 and 11, but when it attempted to move onto Storage Group 12, we had an error in the backuplog below; Backup started on 20/08/2012 at 17:01. The 'Microsoft Information Store' returned 'Access is denied.' from a call to 'HrESEBackupRead()' additional data '-'The 'Microsoft Information Store' returned 'An operation was attempted on something that is not a socket.' from a call to 'HrESEBackupRead()' additional data '-' The operation was ended. Backup completed on 20/08/2012 at 17:02. Directories: 0 Files: 2786 Bytes: 2,920,457,404 Time: 1 minute and 44 seconds Anyone got any ideas? When I re-ran the job about 1hour later, the job ran through again without issue on all Storage Groups. Its as though the DB on SG12 was temporarily unavailable, but we have no errors in any of the logs to indicate this. Thanks

Hello, From the description, there is a issue with permission. But after one hour, the issue disappeared. So I think other processes was using the resource when you access it. Please checkif replication is normal. Best Regards, Lisa

antivirus is the usual culprit when this sort of thing happens. depeneding on what av you use an update may have changed the list of exclusions. if you are using file level antivirus on your exchange have a look at the sites in the following link, and make sure that everything is still set up correctly. http://blogs.technet.com/b/nawar/archive/2011/02/17/exchange-antivirus-exclusion-lists.aspx