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

SBS 2003 with file system auditing enabled - store.exe generating multiple events

I am in the process of enabling file system auditing on a SBS 2003 server for a client and I have run into a small problem.  I have created a new group policy that add the audit of success and failure of object access and ensured that it has been applied to the server using RSoP.  I enabled auditing on a test folder and created some files, saved changes to the files and then went to the security log to make sure things were working as expected.  However, what I found was that the Exchange process store.exe was unexpectedly generating a large amount of events as well.  Here is a copy of one of the events I get:

Event Type:	Success Audit
Event Source:	Security
Event Category:	Object Access 
Event ID:	562
Date:		4/1/2011
Time:		9:15:25 AM
Handle Closed:
 	Object Server:	Microsoft Exchange
 	Handle ID:	287640912
 	Process ID:	6652
 	Image File Name:	C:\Program Files\Exchsrvr\bin\store.exe

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Open in new window

There are sometimes about 15 of these generated within a minute.  I suspect that there is a audit ACL on a file/folder that store.exe uses, but the event does not provide any information that I can use to find the file/folder.

  • 2
  • 2
1 Solution

are you doing file system auditing on specific files and folders or the whole server? If you are doing on the complete server then it's obvious that you will receive such events
SterlingMcClungAuthor Commented:
I have only enabled it on a single folder for testing, but it appears that it may have been previously enabled by another tech.  The problem is that I don't know which folder/file these alearts are coming from.

As I read over my question, it is not clear that I am trying to determine which folder/file the store.exe process is interacting with in the event, so that I can reconfigure the auditing on that file/folder.  The event does not provide any details to which file the store.exe process is accessing, just that the handle is closed.
at run prompt run gpresult /verbose  > gpresult.log and try to indentify which gpo it's which has audit policy setting enabled.

Then disable that GP and see if you still get handle event logged in security log
SterlingMcClungAuthor Commented:
Sorry about abandoning this.  I will try this later today and get back to you.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now