Enterprise Vault™ Administrator's Guide
- About this guide
- Managing administrator security
- Roles-based administration
- Working with predefined RBA roles
- Customizing RBA roles
- Day-to-day administration
- About Exchange mailbox archiving reports
- About starting or stopping tasks or services
- Monitoring journal mailboxes
- About monitoring disks
- About maintaining the SQL databases
- Using SQL AlwaysOn availability groups
- About managing vault store groups and sharing
- About managing safety copies
- About managing partition rollover
- About expiry and deletion
- Working with retention categories and retention plans
- Setting up retention folders
- Enabling archiving for new mailboxes
- About moving archives
- How Move Archive works
- About moving mailbox archives within a site
- About moving mailbox archives between sites
- About configuring Move Archive
- Running Move Archive
- Monitoring Move Archive
- PowerShell cmdlets for managing archives
- Using Enterprise Vault for records management
- Setting the default record type for users
- Common configuration scenarios
- Searching archives for items marked as records
- Automatically filtering events
- Managing indexes
- About the indexing wizards
- Managing indexing exclusions
- About the indexing PowerShell cmdlets
- Advanced Domino mailbox and desktop policy settings
- Editing the advanced settings for Domino mailbox and desktop policy
- Domino mailbox policy advanced settings
- Archiving General: Domino mailbox policy
- Archiving General: Domino mailbox policy
- Domino desktop policy advanced settings
- Advanced Exchange mailbox and desktop policy settings
- Editing the advanced Exchange mailbox and desktop settings
- Exchange mailbox policy advanced settings
- Archiving General (Exchange mailbox policy advanced settings)
- Archiving General (Exchange mailbox policy advanced settings)
- Exchange desktop policy advanced settings
- Office Mail App (Exchange desktop policy advanced settings)
- Outlook (Exchange desktop policy advanced settings)
- OWA versions before 2013 (Exchange desktop policy advanced settings)
- Vault Cache (Exchange desktop policy advanced settings)
- Virtual Vault (Exchange desktop policy advanced settings)
- Advanced Exchange journal policy settings
- Archiving General (Exchange journal policy advanced settings)
- Advanced Exchange public folder policy settings
- Archiving General (Exchange public folder policy advanced settings)
- Advanced SMTP policy settings
- Site properties advanced settings
- Editing site properties advanced settings
- Site properties advanced settings
- Content Conversion (site properties advanced settings)
- File System Archiving (site properties advanced settings)
- IMAP (site properties advanced settings)
- Indexing (site properties advanced settings)
- Skype for Business (site properties advanced settings)
- SQL Server (site properties advanced settings)
- SMTP (site properties advanced settings)
- Storage (site properties advanced settings)
- Content Conversion (site properties advanced settings)
- Computer properties advanced settings
- Editing computer properties advanced settings
- Computer properties advanced settings
- Agents (computer properties advanced settings)
- IMAP (computer properties advanced settings)
- Indexing (computer properties advanced settings)
- Storage (computer properties advanced settings)
- Task properties advanced settings
- Advanced Personal Store Management properties
- Classification policy advanced settings
- Managing the Storage queue
- Automatic monitoring
- About monitoring using Enterprise Vault Operations Manager
- About monitoring using MOM
- About monitoring using SCOM
- Managing extension content providers
- Exporting archives
- Enterprise Vault message queues
- Customizations and best practice
- Mailbox archiving strategies
- Notes on archiving based on quota or age and quota
- Notes on archiving items from Exchange Server 2010 managed folders
- About performance tuning
- Mailbox archiving strategies
- Failover in a building blocks configuration
- Appendix A. Ports used by Enterprise Vault
- Appendix B. Useful SQL queries
- Appendix C. Troubleshooting
- Installation problems
- Microsoft SQL Server problems
- Server problems
- Client problems
- Problems enabling or processing mailboxes
- Problems with Vault Cache synchronization
- Identifying and resolving Vault Cache issues on the Enterprise Vault server
- Identifying and resolving Vault Cache issues on an end-user computer
- Problems with Enterprise Vault components
- Troubleshooting: All tasks and services
- Troubleshooting: Directory service
- Troubleshooting: Exchange archiving or Journaling tasks
- Troubleshooting: Storage service
- Troubleshooting: Shopping service
- Troubleshooting: Web Access application
- Troubleshooting: All tasks and services
- Techniques to aid troubleshooting
- How to modify registry settings
- About moving an Indexing service
- Appendix D. Enterprise Vault accounts and permissions
Examining IIS log files
As a final step in diagnosing client synchronization issues, you can examine the IIS log files on an Enterprise Vault server. The files show the interaction between individual client computers and the various web pages that are used during synchronization.
The IIS log files are typically located at C:\inetpub\logs\LogFiles\W3SVC1
.
The following example shows a typical line in the log file:
2012-08-19 09:29:59 10.12.128.42 GET /EnterpriseVault/Slot.aspx ArchiveID=10F4ECDC3CF80D240B591162DC0F122321110000ECTO1-EVSVR-VM.mail2.lab&Timeout=0 80 MAIL2\mike_smith 10.12.128.36 EnterpriseVaultOutlookExt-V10.0.2.658 200 0 0 6474
In the example:
A request was made to
Slot.aspx
at 09:29 A.M. on August 19, 2012.The request included the archive ID, which in this case was the Archive ID of a client attempting to synchronize.
The requesting user was
MAIL2\mike_smith
.The response code was 200 (success).
Table: Web pages used during synchronization shows the web pages that are used during synchronization, with their uses and their possible effect on synchronization. A response code of 200 indicates success.
Table: Web pages used during synchronization
Web page | Use | Notes |
---|---|---|
DeleteArchivedItems.aspx | The client may call this web page, passing it a list of items to be deleted as the result of items being deleted from Virtual Vault. | A response code of 500 indicates an issue. DTrace |
DeleteJob.aspx | Called by the client to indicate that one or more files have been downloaded successfully, so that the Enterprise Vault server can remove the files from the cache location. | A response code of 500 or 501 indicates an issue. DTrace |
DownloadContent.aspx | Used by the BITS component on the client to download completed files from the cache location to the client. | HTTP response codes can indicate issues with the download, as follows:
DTrace |
FullSync.aspx | Performs an index query and returns data to the client to facilitate an initial, full header synchronization. | A response code of 500 indicates an issue, possibly with the underlying index query being performed. DTrace |
GetArchiveFolderHierarchy.aspx | Gets the archive hierarchy (a list of archive folders). Used for header synchronization. | A response code of 500 indicates an issue. DTrace |
GetIncrSlotWithServer.aspx | Used to obtain a slot with the server to perform an incremental build for Content Cache. | A response code of 500 indicates an issue. DTrace |
GetSlotWithServer.aspx | Used to obtain a slot with the server to perform an initial (full) build for Content Cache. | A response code of 500 indicates an issue. DTrace |
GetVaultInformation.aspx | Used during Content Cache synchronization to get information such as the date range of the archive. | A response code of 500 indicates an issue. DTrace |
HasJobBuiltYet.aspx | The client polls the server through calling this web page to determine when a file being built on the server is ready to be downloaded. | A response code of 500 indicates an issue. DTrace |
IncrSync.aspx | Gets the data for incremental header synchronization. | A response code of 500 indicates an issue. DTrace |
ListArchives.aspx | Returns a list of accessible archives to the client before a synchronization. | A response code of 500 indicates an issue. DTrace |
Slot.aspx | Called by the client to obtain a slot to proceed with header synchronization. | Repeated response codes of 500 indicate a potential bottleneck in the number of users attempting to synchronize. |
SyncPoint.aspx | Used by the client to determine the type of synchronization needed (full or incremental). | A response code of 500 indicates an issue. DTrace |
UpdateArchivedItemMetadata.aspx UpdateArchivedFolderHierarchy.aspx | Used to inform the Enterprise Vault server of any user updates that have been performed in Virtual Vault. | A response code of 500 indicates an issue. DTrace |
UploadItem.aspx | Used to upload (that is, to archive) items that have been dragged into Virtual Vault. | A response code of 500 or 520 indicates an issue. DTrace |