Permission Denied

Why am I all of a sudden getting the following errors when recompiling my scss files.

Errno::EACCES: Permission denied - ./.sass-cache/6056a8ba603079aa18252308259713634aad1317/members.scssc Use --trace for backtrace.

Errno::EACCES: Permission denied - ./.sass-cache/6056a8ba603079aa18252308259713634aad1317/_colors.scssc Use --trace for backtrace.

I searched for sass-cache and deleted all the folders and recompiled fine and all is well.

I had the same issue. FYI for future travelers, my .sass-cache location was

C:\Users\[UserName]\AppData\Local\VirtualStore\Windows\SysWOW64\.sass-cache

I must have messed something up good - it was still giving me access errors after deleting .sass-cache and restarting Visual Studio. I restarted VS again in admin mode and it kicked back up again.

I suspect the original issue was triggered by my backup software.

For yet other future travelers, I had the same issue. And I found my drive littered with those .sass-cache files. I found one in C:\Users\MyUser\Pictures, one in C:\Windows, one in C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\, one in C:\Windows\SysWOW64. Not sure what all these are for, but nuking all of them solved my problem.

would someone from mindscape please answer someone here. i can't so any work because of the same error and this is AFTER teh 12-3-2012 nightly build and AFTER we paid for five licenses. compass sass have their act together, mindscape does not

rick f.

Hi Rick,

It sounds like you may be running into the same permissions issues as above. There is an option in the Web Workbench options dialog which allows you to set a custom path where the sass cache files will be emitted to which you can then direct to a location where the user has full permissions.

If you look under Tools / Options / Web Workbench, then look under the Sass category you will see a "Location of Sass Cache" property. Set this to folder where you want the Sass Cache to be stored. e.g. C:\Temp\SassCache and this will be passed on to the Sass compiler.

e.g.

Jeremy

Apparently, you need to escape the string path. Eg. "C:\\tmp\\sass-cache\\" But this still doesn't solve my problem.

Still throwing

/* System.ComponentModel.Win32Exception (0x80004005): Access is denied
   at System.Diagnostics.Process.StartWithCreateProcess(ProcessStartInfo startInfo)
   at System.Diagnostics.Process.Start()
   at Mindscape.VisualSass.Integration.CustomTool.ExternalCommandBase.Execute(String customToolFolder)
   at Mindscape.VisualSass.Integration.Compilation.ScssCompiler.CompileCore(String scss, String sourceFilePath, String rootPath, IEnumerable`1 additionalPaths, ICompilationSettings settings, ICompilerContext context, CompilationResult result)
   at Mindscape.VisualSass.Integration.Compilation.CompilerWithMinification.Compile(String text, String sourceFilePath, String rootPath, IEnumerable`1 additionalPaths, ICompilationSettings settings, ICompilerContext context, CompilationResult result) */

The only fix that does it is running it as Administrator

I have the same issue - I can only now compile if I run as admin.

Error: Errno::EACCES: Permission denied - ./.sass-cache/43b7e49e10e8fd3cdf1235bbe25fe6ffcd11e956/style.scssc Use --trace for backtrace.

My cache is here (xxxx = user): C:\Users\xxxx\AppData\Local\VirtualStore\Program Files (x86)\Microsoft Visual Studio 12.0\Common7\IDE

Should I repoint the cache?

What other solutions have been provided?

Yes, try repointing the cache to a folder you have created under your user account.

As per above: There is an option in the Web Workbench options dialog which allows you to set a custom path where the sass cache files will be emitted to which you can then direct to a location where the user has full permissions.

If you look under Tools / Options / Web Workbench, then look under the Sass category you will see a "Location of Sass Cache" property. Set this to folder where you want the Sass Cache to be stored. e.g. C:\Temp\SassCache and this will be passed on to the Sass compiler.

Jeremy

Thanks Jeremy, I had already repointed the cache and yes, it seems to work fine now. I'm just not sure what changed to cause the permissions issue.