This isn't your typical file system access is denied error. I am pretty perplexed by this issue.
I recently started getting errors from my nightly cube backup job.
File system error: The following error occurred during a file operation: Access is denied.
I'm not aware of any recent changes to the permissions and they all seem to be intact.
I tried logging into the servers where the backups are located since. I find that even copying a file into the folder in question gives me an "Access is denied" dialog box.
The kicker is that I only get "Access is denied" when I try to copy the .abf file into the folder.
This also happens with the parent folder. I can copy .bak extensions and other files into the folder just fine. The account that is performing the backup has full permissions to the folder as well.
Why am I getting "Access is denied" errors, but only for .abf extensions?
I disabled the antivirus. Still getting access denied.
-
Is it in use by SSAS? Perhaps still being written to?Erik Reasonable Rates Darling– Erik Reasonable Rates Darling2017年07月31日 18:29:02 +00:00Commented Jul 31, 2017 at 18:29
-
@sp_BlitzErik Sorry my SSAS experience is limited. How can I check to see if it is in use?Geoff Dawdy– Geoff Dawdy2017年07月31日 18:31:33 +00:00Commented Jul 31, 2017 at 18:31
-
I'd start here: learn.microsoft.com/en-us/sql/analysis-services/instances/…Erik Reasonable Rates Darling– Erik Reasonable Rates Darling2017年07月31日 18:34:37 +00:00Commented Jul 31, 2017 at 18:34
-
Could you try to rename a .txt file to .abf and copy that over? Also, what is the size of your .abf file, maybe you are exceeding a disk quota?Tom V– Tom V2017年08月04日 09:26:10 +00:00Commented Aug 4, 2017 at 9:26
-
2For anyone else who finds this question by googling 'Backup-ASDatabase File system error: The following error occurred during a file operation: Access is denied.' Check that the analysis services account has permissions on the folder (not just the account running the backup). That was what solved my issue (but I don't think it would answer the original question).marclancy– marclancy2021年05月06日 16:41:26 +00:00Commented May 6, 2021 at 16:41
1 Answer 1
I fixed similar error message on Windows Server 2016 / SQL Server 2017 by granting an access on backup folder to SQL Server Analysis Services (MSSQLSERVER) service account (NT Service\YourAccountName).
Explore related questions
See similar questions with these tags.