Skip to main content
Inspiring
November 9, 2016
Answered

Dreamweaver 2017 Sharing Violation

  • November 9, 2016
  • 5 replies
  • 9453 views

I updated to Dreamweaver CC 2017 two days ago. Since then, at some point during each day, when I open a file, I get a message that says something like this:

Encountered a sharing violation while accessing C:\Users\<myusername>\AppData\Roaming\Adobe\Dreamweaver CC 2017\en_US\Configuration\Temp\DownloadCache\RPH1877.css.

The actual file cited at the end varies, but the path is always the same. I have tried renaming or deleting both the Temp and DownloadCache folders, but it does not solve the problem. I've reviewed several older posts that suggested solutions from not allowing Windows Explorer to index the content of files to turning off Details Pane, but none of these have worked. I have also closed my browser and ensured that no processes were running to make sure that wasn't the issue, as it apparently was for one person in the past.

I'm pretty close to reverting to a previous version of the software. Does anyone have any idea why the software might be doing this?

This topic has been closed for replies.
Correct answer HVOL

Since these are temporary cache files, I deleted the file and allowed Dreamweaver to recreate them. It appears to have resolved the issue.

5 replies

HVOLCorrect answer
Inspiring
February 14, 2018

Since these are temporary cache files, I deleted the file and allowed Dreamweaver to recreate them. It appears to have resolved the issue.

Participating Frequently
December 23, 2017

I have a similar issue, and I'm not actually editing the css file that it complains about.  But I'm using sccs, and it's the automagic compilation of scss to css that creates a sharing violation with the css.  Dreamweaver doesn't like the css file being open for editing and also being occasionally updated when I save my sccs file.  And this is even though I DON'T have the css open as a separate file, but only visible as a dependent (i.e. "related") file. 

So, what seems to fix if for me is clicking on the "filter related files" feature and making sure that the css file does not exist as a file I could view as a tab.  That won't help you, if you need to actually edit css directly. I can only suggest doing the same filter thing, editing your css as a separate file (not a tab alongside your source), and closing that editing session when it complains.

jamieh2os
Known Participant
December 14, 2017

I got the same 'sharing violation' message recently.  I posted the problem and received no solutions prior to searching and finding your post.  I seemed to have resolved my problem.  Which, I believe was caused by a combination of saving and putting files to the server and using FileZilla also to transfer changed files to the same.  I messed around doing both to update files the on server and then reloading the index file in DW; which for now has fixed the problem.  Using the DW 'put' command is slower than updating changed files with a FileZilla transfer; but, I believe the "put" command checks all links each time.  It would be nice to hear more about this issue from experts.....thanks

DaveMorton
Participant
February 12, 2017

I just ran across this exact problem, and what I did to correct it is to have DreamWeaver run as an admin. This may well not be the ideal way to correct the situation, but it worked for me.

Participant
March 26, 2017

I'm getting this issue now but nothing mentioned here has worked for me.

Nancy OShea
Community Expert
Community Expert
March 26, 2017

Not enough information. Can you please elaborate?

  • Version of Dreamweaver
  • Operating system
  • Workflow
  • Error messages
  • Types of files, etc...
Nancy O'Shea— Product User & Community Expert
BenPleysier
Community Expert
Community Expert
November 9, 2016

Go to Event Viewer in Windows. There you can see what causes the clash.

Wappler is the DMXzone-made Dreamweaver replacement and includes the best of their powerful extensions, as well as much more!
Inspiring
November 10, 2016

That actually appears to have no information about this whatsoever. Does anyone else have any ideas? I can't put up with this much longer without bailing on the 2017 version.