• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 912
  • Last Modified:

windows 7 professional - unable to write to newly installed disk - file permissions problem ?

I have a new desktop system running Windows 7 Professional. I have just added an additional disk. This is mapped as drive E:   The first disk containing the Windows build is C: and the DVD writer is D:

When using Dreamweaver CC then I can not write files to the E: drive whereas I can do this on the C: drive. Dreamweaver gives the message "An unknown error occured while accessing E:\test.html". Other software such as Notepad can write to the disk with no problem. I can even create new folders within Dreamweaver using the normal editing options.

I have removed the existing partitions from the additional disk and formated the disk from scratch.

I am assuming the problem might be down to the permissions / ownership of the new disk. I have checked the permissions (see screen captures) and these all look sensible. The owner of the disk is SYSTEM and SYSTEM has full permissions.

The Windows 7 Professional PC just has a single user and this user is the administrator.

Any suggestions as to what is wrong ?

Many thanks.
Capture10.JPG
Capture11.JPG
Capture12.JPG
Capture13.JPG
0
tigger44
Asked:
tigger44
  • 4
  • 4
  • 3
  • +1
2 Solutions
 
Thomas GrassiSystems AdministratorCommented:
Is E a network drive or local drive you said it is mapped as E?

Sounds like Dreamweaver does not know what type of drive it is.

If a local drive assigned as E then Dreamweaver should have no issue.

What does disk manger show about the drive?
0
 
tigger44Author Commented:
E is a local drive - the next drive letter available (E:) has just been assigned by Windows 7.

Disk Manger looks normal - I'll attach a screen shot for you to see.
Capture14.JPG
0
 
Thomas GrassiSystems AdministratorCommented:
What happens if you open a file from the E Drive?

Create a simple html page using notepad same it to the E Drive then open it with dreamweaver does it open? if it does then try to save it? Does it save?
0
What Security Threats Are We Predicting for 2018?

Cryptocurrency, IoT botnets, MFA, and more! Hackers are already planning their next big attacks for 2018. Learn what you might face, and how to defend against it with our 2018 security predictions.

 
David Johnson, CD, MVPOwnerCommented:
Users only have READ / Execute give them Full Control
0
 
KorbusCommented:
Based on your tests, I don't know that I would suspect NTFS permissions- but here are my thoughts on that anyway:
Capture 13 Shows the drive is owned by user scotsfir\dave
But capture 12 shows that the \USERS group, which I assume dave belongs to, only has Read & Execute permission.
You mentioned you have only one user, but I also see the scotsfir\administrator account specified.  So, can you confirm that dave is a member of the administrator group?
(I must suggest you NOT run with dave as administrator (major security flaw), rather grant the users group full control to the data folders on/or the entire drive e:)

You can also confirm you you have NTFS permissions to the file in question by opening the folder in windows explorer and make a copy of the file (confirm file read, and directory write permissions).  Then delete the original, confirm write permission.

Since working in notepad, lets check some things other than NTFS
- Test with AV software disabled, or folder/file excluded from scanning.
- (Sanity check) Launch Dreamweaver "As Administrator" (right click it for this option)
- run a check disk command (and reboot if needed) to let it scan & fix and problems (command will be something like - chkdsk e: \f)
0
 
tigger44Author Commented:
Interesting...

I can create the file with Notepad and then open it with DW. I see the content that I created.

If I try and Save then I get the same unknown error message as before....however after a few seconds the file on E: is rewritten with blank content and a TMP file also appears. I have done a screen shot of this.
Capture15.JPG
0
 
Thomas GrassiSystems AdministratorCommented:
Lets try putting LIST permission for Everyone at the Root of Drive E
If that does not help Give Everyone Full Permission at the Root of Drive E
0
 
David Johnson, CD, MVPOwnerCommented:
create a new user in the permissions "Everyone" and give it FULL permissions
0
 
tigger44Author Commented:
I have been working through the various suggestions from the different experts.

First I checked how the permissions were set on the C: drive (which works OK) and these are identical to the E: drive e.g. users only have Read & Execute + List + Read while administrators and SYSTEM have full contol (everything except Special Permissions).

Disabling the anti virus made no difference.

Running DW as Administrator mean that I could save a file with no error message !

Interestingly I have rebooted the system and when I start DW normally (e.g. just clicking the desktop icon) then everything works normally. I don't understand why this would be so - I would have expected the problem to have returned.
0
 
KorbusCommented:
It failed our "sanity check", by working when run as administrator.  In such situation a reboot is always a good idea :)

Was this the first reboot after installation?  Sometimes an installation is not completed until after an initial reboot is done (though nowadays, this is usually due to old/poor installation software).
0
 
tigger44Author Commented:
No I had already done multiple reboots. I have tried both a quick format and a full format of the new disk with reboots after each operation (DW CC was already installed).

This was the first time I had tried "run as administrator" and expected that I would need to use this on each occasion unless of course I changed the permissions. However, this was not needed - as since I did the first "run as administrator" it has worked fine since. Most odd....

Thanks again for your help. I'll allocate the points and accept the solution shortly.
0
 
Thomas GrassiSystems AdministratorCommented:
When making permissions changes on a computers hard drive sometimes those changes require a restart to take effect.

Unusually a logoff and then log back on will work .

Restart never hurts.

If you have the correct permissions you should be ok now.
0
 
KorbusCommented:
Possible cause:

Doing "run as administrator", will also allow the the software to write to particular registry keys, which also have read/write permissions.  I suspect some reg entry needed to be created, and your account only has permission to READ this entry, while the admin has permission to write it.  (Cannot explain why admin GROUP would not have permission, probably just be the way the reg key was created; for an individual user (admin) rather than a group.)
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

  • 4
  • 4
  • 3
  • +1
Tackle projects and never again get stuck behind a technical roadblock.
Join Now