Re: Permissions and Auditing
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Mon, 11 Jun 2007 11:46:52 -0500
"steve" <stevesemple@xxxxxxxxx> wrote in message
news:1181577317.227064.9700@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a file that someone cant open becasue of some permission issue.
The file is an excel file.
I was wondering if I can use auditing to track down the problem. (I
have used effective permissions but it looks good to me.)
You can try but it isn't likely to tell you anything you don't already know.
You already know there is a permission (denied) problem so that is
pretty much what the auditing will say too.
I wondered if I could use the auditing to see what failures are
occuring when the user trys to open the file.
It might show that the file is being opened for FC, Write, etc when
all you need is READ, but other than that it is just going to show
what you already know: permission was denied.
(right click file/ click properties/click security /click advanced /
click auditing.)
I did this but Im not sure where to see the results or if the results
Event Viewer.
will tell me what I need. The file is on a share on a 2003 server but
the link to it is on an xp computer.
File or rather "Object Auditing" requires TWO different settings however;
you must set it on the FILE PROPERTIES as you describe but also must
enable the general Object Auditing in the Local Security of the Server
or through Group Policy.
1. Where will I see the results
Event viewer, Security Logs.
2. Will they be usefull to see what is causing a falure to open a
file.
Probably not. You seem to already know which file is the problem.
If you don't know WHICH program etc is attempting to open the file
there is a FileWatch program (free) at SysInternals.com which will
show both, along with the failures which might be more useful but usually
this is only needed for the most difficult permission issues.
You might want to just POST the output from the command line XCalcs.exe
or Calcs.exe if you already know which file is the problem.
Are you sure that it isn't due to having the file OPEN by two different
programs/processes? This is not really a "permission" (i.e., security)
problem.
If one program has the file open for "exclusive read" then no other
program can open it even for "read".
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- Follow-Ups:
- Re: Permissions and Auditing
- From: steve
- Re: Permissions and Auditing
- References:
- Permissions and Auditing
- From: steve
- Permissions and Auditing
- Prev by Date: Re: Server 2003 users loosing home drive mappings
- Next by Date: Methodology for File Server migration/consolidation
- Previous by thread: Permissions and Auditing
- Next by thread: Re: Permissions and Auditing
- Index(es):
Relevant Pages
|