Jump to content

Determine Ways to Clean Up Orphaned OWAScratchPad and StoreEvents

  • PrintPrint

Information

As per MS ExRAP report, need to do cleanup of multiple orphaned OWAScratchPad and StoreEvents objects that exist in Exchange organization.
Since Public Folders are very critical data in Exchange organization and many of the scratchpad items are referring to Public Folder, need to determine way to isolate OWAScratchPad related to Public Folder and only do a cleanup of Orphaned OWAScratchPad.

Details

What are OWAScratchPad and StoreEvents by the way in Exchange ?
OWAScratchPad
Posts have to start out somewhere to have attachments, and for public store logons, that place is the Outlook Web Access scratch pad. Because Distributed Authoring and Versioning (DAV) does not cross MDB operations, user needs a point on every mailbox where one can always write posts to, so that user can support adding attachments. The posts are staged in the OWAScratchPad until all attachments are added, or they are saved.
Exchange creates the OWAScratchPad{GUID} folder when an OWA user adds an attachment to a public folder post. Exchange will recreate this folder when it needs. So user could safely delete it.
\NON_IPM_SUBTREE\OWAScratchPad - Introduced in Exchange 2000 SP1 – for more information, please refer the below links:
Understanding EXOLEDB Default Folders
Click here to access the above mentioned article at http://technet.microsoft.com/en-us/library/aa996197(EXCHG.65).aspx.
NOTE: The above-mentioned URL will take you to a non-HP Web site. HP does not control and is not responsible for information outside of the HP Web site.
XCCC: Adding Attachments to Public Folder Posts in OWA
Click here to access the above mentioned article at http://support.microsoft.com/kb/319143.
NOTE: The above-mentioned URL will take you to a non-HP Web site. HP does not control and is not responsible for information outside of the HP Web site.
StoreEvents
All store event folders described in the following list have been present since Exchange 2000 Server:
  • \NON_IPM_SUBTREE\StoreEvents\
  • \NON_IPM_SUBTREE\StoreEvents\GlobalEvents
  • \NON_IPM_SUBTREE\StoreEvents\Internal
StoreEvents{GUID} is used to hold the Event Sinks which are registered to Information Store in the Exchange Server. If user deletes it, all the Event Sinks registered previously would not work. However, if user did not use.
Event Sink on the Exchange Server, user can feel free to delete them. Also, when user registers a new Event Sink on server, this folder will also be created automatically.
This is the event binding folder, where EXOLEDB stores information on events built to a specific MDB. At startup, EXOLEDB must enumerate the events here, which can lead to long store startup times with large event sink numbers. Exchange Server 2003 performance in this area is greatly improved, but time to mount an MDB is still affected by the number of rows. Each binding is validated for class, having a valid event method, such as onsave or ontimer, valid clsid, and sink parameters. Events with a match class of ANY can only be registered in the GlobalEvents subfolder.
After creating the schema folders and starting the event bindings system, EXOLEDB creates the Outlook Web Access scratch pad.
All store event folders have been present since Exchange 2000 RTM.
  • \NON_IPM_SUBTREE\StoreEvents\
  • \NON_IPM_SUBTREE\StoreEvents\GlobalEvents
  • \NON_IPM_SUBTREE\StoreEvents\Internal
Additional Information :
Understanding Public Folders and System Folders
Click here to access the above mentioned article at http://technet.microsoft.com/en-us/library/bb124189(EXCHG.65).aspx.
NOTE: The above-mentioned URL will take you to a non-HP Web site. HP does not control and is not responsible for information outside of the HP Web site.
Understanding Exoledb’s default folders
Click here to access the above mentioned article at http://technet.microsoft.com/en-us/library/aa996197(EXCHG.65).aspx.
NOTE: The above-mentioned URL will take you to a non-HP Web site. HP does not control and is not responsible for information outside of the HP Web site.
RESOLUTION
The good way to check if the system objects are associated to any PF or not one can use the guid2obj.exe , which is part of Windows 2000 resource kit.
NOTE: The above-mentioned URL will take you to a non-HP Web site. HP does not control and is not responsible for information outside of the HP Web site.
Guid2obj Examples (Have taken from MSKB:927229 for quick reference
The following are all valid command lines for GUID2Obj.
guid2obj {6501886d-9a84-11d2-bc7c-00c04f82fe9d}guid2obj 6501886d-9a84-11d2-bc7c-00c04f82fe9dguid2obj /server:microsoftdc2 {6501886d-9a84-11d2-bc7c-00c04f82fe9d}guid2obj /site:Default-First-Site-Name {6501886d-9a84-11d2-bc7c-00c04f82fe9d}
This command-line produces the following output:
c:\>guid2obj {6501886d-9a84-11d2-bc7c-00c04f82fe9d}CN=Administrator,CN=Users,DC=microsoft,DC=com
For the GUID’s user cannot resolve user can safely delete by hitting Delete button from Exchange 2007 Exchange Management Console using Public Folder Management Console.

HP Support forums

Find solutions and collaborate with others on the HP Support Forum
HP.comHP on FacebookHP on TwitterHP on YouTubeHP on Linked InHP on FlickrHP on Google+