• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

Wrong related files showing - Error: Access to "_notes/dwsync.xml was denied

Contributor ,
May 25, 2020 May 25, 2020

Copy link to clipboard

Copied

Hello, thanks for your time.

 

I'm experiencing another bout of a very troubling issue with the "related files" panel in Dreamweaver 20.

 

Any time I create more than a single "site" the related files get mixed up. If I nuke all of the site prefs (even manually) then rebuild my sites (set up local & server from scratch) every site will show related files from the first site I set up. In other words, if I set up 2 sites from scratch then open up a page within site #2 I will see the css, js etc... related files from site #1. 

 

When I hover over the file names in the related files panel I can see the wrong location.

 

The file viewer in dreamweaver shows the CORRECT files in both the local & remote view. The problem is isolated to the "related files" panel. This happened several times with Dreamweaver 19 as well & was very difficult to fix. The automated process to nuke the prefs did not fix it. Even manually deleting the site prefs file did not fix it. I had to manually delete the whole folder as well as all of the "_notes" folders in every site & rebuild all of the "sites" in Dreamweaver to fix it.

 

Unfortunately the problem reoccurs basically every time I set up a new "site" in Dreamweaver. This time nuking the prefs is not fixing it.

 

I'm getting a new error this time when I open files from an effected site:

"Access to Macintosh

HD:Users/username/path-to-site.../_notes:dwsync.xml was denied"

 

I've deleted these files and the _notes folders many times but it's not fixing the problem.

 

In my previous fix I was able to see the errant file locations written into the "Site Prefs" file. This time all of the file paths in that file look correct but I'm still getting the error. It makes it impossible to have more than 1 site configured at a time and creates potential disasters for the wrong files to be shown.

 

I'm running out of ideas.

 

** ADDITIONAL INFO **

 

Durring the intial opening of a page, while dreamweaver is working to "put dependent files" to the server etc. The "related files" panel will show the CORRECT files. It is durring this process that the "Access to..." error about the dwsync.xml files appears several times. Once these operations are complete the contents of the "related files" changes and shows the WRONG files. specifically it is showing the files from a different site. This is the same problem I was having before. All sites were showing the related files from 1 particualr site instead of the correct files for each page.

 

** MORE ADDITIONAL INFO **

 

The wrong related files are only shown when live view or split live/code view is active. If I view the pages in code view or split code/design view the correct files are shown. It seems to only effect related files that have the same name as files from other sites. For example, if more than 1 site has a file called "page.css" or "nav.css" (or both, or several), all sites will show the files from whichever site was created first. files with completely unique names that do not exist in any other sites seem to display fine.

 

Views

866

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 26, 2020 May 26, 2020

Copy link to clipboard

Copied

  • Which operating system?
  • Is your local site folder stored on your primary hard drive?
  • Does your computer user profile have full administrative permissions? 
  • Have you tried creating a new computer user profile?

 

Nancy O'Shea— Product User, Community Expert & Moderator

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
May 26, 2020 May 26, 2020

Copy link to clipboard

Copied

Hello Nancy. Thanks for looking.

 

I'm running Dreamweaver 20.1 on Mac OS 10.14.6.

All sites are in their own directory on the internal HD.

My user profile has admin permissions. 

 

Creating a new user account on the computer seems like a very troublesome solution to a problem with a single feature of a single app. Can you tell me why you think that might help?

 

This problem sems like a caching problem of some sort. It is intermittent and seems to worsen over time. It happened before with Dreamweaver 19, got worse over time until Dreamweaver was basically unusable. 

 

it seems to begin as soon as I create more than one Dreamweaver "site". It seems related to an issue where the "related files" panel often shows remote related when it should be showing local. Sometimes it shows both... definitely not right.

 

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 26, 2020 May 26, 2020

Copy link to clipboard

Copied

I cannot reproduce your problems which leads me to believe this may have more to do with your computer permissions than it does with DW 20.1.  I suggested creating a new Mac user profile to rule out a corrupted profile.  

 

If you're unwilling to try it,  then go to plan B.  Run the Adobe Cleaner tools to remove old program files followed by a re-installation of Creative Cloud and Dreamweaver.

https://helpx.adobe.com/creative-cloud/kb/cc-cleaner-tool-installation-problems.html

 

Nancy O'Shea— Product User, Community Expert & Moderator

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
May 26, 2020 May 26, 2020

Copy link to clipboard

Copied

Thanks Nancy,

 

When you say "rule out a corrupted file" what file exactly do you mean? Is there a single file somewhere that controls filer permissions? Maybe you're suggesting that because of what I said about the dwsync files?

 

The issue with the dwsync.xml files erroring only lasted a short time & did not occur in the previous bout with this issue. I could tell that the files were locked when the access denied error occurred. I unlocked them manually and the error no longer appeared but it did not resolve the issue.

 

Any idea why the "related files" panel would be showing the remote files rather than the local?

 

Any idea where exactly the data to poulate the "related files" panel comes from?

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Community Expert ,
May 26, 2020 May 26, 2020

Copy link to clipboard

Copied

LATEST

I'm neither techinical support nor a DW engineer.  As a fellow product user,  I have never experienced what you describe.  And I don't pretend to understand why your installation is acting as it does.  

 

Occasionally computer user profiles become corrupted.  And the only way to know for sure is to create a new OS user profile to see if that clears up the problems.  

 

A clean re-install is another solution that works for the majority of users. 

 

Or, feel free to reach out directly to Adobe technical support via online chat.

https://helpx.adobe.com/contact.html

 

================
NOTE: The pandemic is still effecting many sectors. There are fewer available support agents and wait times may be longer than normal.  Please be patient.

 

Nancy O'Shea— Product User, Community Expert & Moderator

Votes

Translate

Translate

Report

Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines