pdf_icon Download contentACCESS Manual as PDF

  1. Introduction to contentACCESS
    1. Services provided by contentACCESS
    2. Software requirements
  2. Installation of contentACCESS
  3. contentACCESS Tools
    1. Installing Virtual drive
    2. Installing the Proxy server (contentACCESSWS)
    3. Installing the Proxy web services
    4. Installing Outlook forms
    5. Legacy email archive connectors
    6. Legacy archive connector for Metalogix Archive Manager Exchange Edition (MAM EE)
    7. Legacy archive connector for Email Lifecycle Manager (ELM)
    8. Installing TECH-ARROW’s WinShortcutter
  4. contentACCESS Central Administration
    1. Central administration login
    2. contentACCESS Central Administration user interface
  5. Tenants in contentACCESS
    1. How to create a new tenant
    2. Tenant limitations
    3. How to provide access to a tenant (adding new tenant administrators)
    4. Tenant administrator invitation types
  6. General system configurations
    1. Connection
    2. User interface
    3. Users — role types, creating new users, adding user logins
    4. How to activate your license key
    5. How to create user logins to an already existing user?
    6. System administrators
    7. Login providers
    8. System
    9. Licensing
    10. Notifications
    11. Monitoring — how to find out possible misconfigurations / reasons of potential system/job failures
    12. Distributed environment in contentACCESS — Clusters
    13. Statistics
    14. How to create/configure databases — All databases
  7. Common features
    1. Databases
    2. Schedules
    3. Retentions
    4. Storages
    5. Exchange connections
    6. Importing contentACCESS configurations from files
  8. Creating new jobs in contentACCESS
  9. Jobs’ page, jobs’ context menu
  10. File Archive
    1. Introduction to File system archive
    2. File Archive settings
    3. File archive Databases
    4. File archive System settings
    5. File archive Retentions
    6. File archive Storages
    7. Root folders
    8. Aliases
    9. File archive Schedules
    10. Provisioning settings and managing access to contentWEB
    11. Configuring aliases
    12. Configuration of jobs available in contentACCESS File Archive
    13. Configuration of File system archive job
    14. Configuration of a File system restore job
    15. Configuration of File system recovery job
    16. Configuration of Remote shortcutting job
    17. Active/inactive documents in File system archive
  11. Email Archive
    1. Important settings before creating an Email Archive job
    2. Database settings
    3. Email archive System settings
    4. Provisioning settings
    5. Retention settings
    6. Shortcuts in email archiving
    7. Storing of archived emails
    8. Creating email archive schedulers
    9. User experience
    10. Exchange 2013: Mail app in OWA 2013 or on MS Outlook 2013 desktop version
    11. Exchange 2010: OWA 2010 integration
    12. Address book objects
    13. Granting access rights for mailbox users and explicit users to view the mailbox archive?
    14. Creating contentWEB users (option 1)
    15. Manage access to a mailbox archive (option 2)
    16. How the end user should log in to contentWEB (archive) over Internet?
    17. Database and store assignment in email archiving
    18. How to assign database and storage to an Exchange group?
    19. How to assign database and storage to a mailbox?
    20. How to move data from source database/storage into a second (target) database/storage?
    21. Creating Email archive jobs: archive, restore, recovery, mailbox move
    22. Email archive job
    23. Email restore job
    24. Email recovery job
    25. Mailbox move job
  12. Custom plugins
  13. Email management job configuration
  14. SharePoint archive plugin
  15. Storage replication plugin
  16. Sharing plugin
  17. Datengut plugin
  18. Email synchronizer plugin
  19. contentWEB
  20. officeGATE
  21. accessGATE Mobile
  22. Virtual drive
  23. Terms of use
  24. FAQ

6.11.Monitoring — how to find out possible misconfigurations / reasons of potential system/job failures

Navigate to System ⇒ Services ⇒ Documentation122.1 Monitoring button.

Documentation123

The monitoring feature enables to check the currently running or in the past run system or job related events very easily. The user can check here all desired system events such as system updates, shutdowns, startups, system component updates, or possible system errors etc. In monitoring feature, the user also has the chance to check all possible failure details that might happen during the running of the jobs, so it makes the troubleshooting easier.

If you first open monitoring, you can see the following basic parts on the interface: Runs of the jobs or system on the left side (red frame); system and job events on the right side (green frame). With clicking on the Refresh button (purple arrow) you can also check the real-time running jobs. With this button it is possible to reload the current runs/event from the database. With a single click on the collapse all/expand all buttons (indicated with blue arrows) you can expand or collapse all sessions for all jobs. It is also enabled to list among the events at the bottom of the monitoring page (orange frame).

Documentation124



Sorting in monitoring: sorting option is enabled both in the Runs and Events tables. Click on the particular column name (Start date, End date by the runs, Date, Title, Description, Job by the events), and the items will be displayed in the reverse order.

Documentation125



Setting of maximum history count of the runs: With this option it is possible to set, how many job runs the user would like to keep. If the value is set to 10 for example, and a job has run 20 times, then only the last 10 runs can be viewed, remaining 10 will be deleted and the user will not have an access to them. It is recommended to set a higher value here, if a job is running too often, or during the weekends, and the user needs to view the events retroactively.
This value is always inherited from the higher level. There are three levels altogether, where the history counter can be adjusted; the system is the highest level, the next is tenant level and the last one is the level of jobs.

  • System level settings are accessible with right mouse click on a system related job in the column of Runs; here click on Settings, and adjust these settings in the System level monitoring setting dialog.

    Documentation126 Documentation127

  • Tenant level monitoring settings are inherited from the system, i.e. if maximum history count is set on “10” on system level, then the same value will apply for the tenant level monitoring settings, too. Nevertheless it is possible to configure the tenant level settings independently from the system settings. Click on the Settings button and set the required value into the Tenant level monitoring settings dialog. If the tenant level settings are set independently, it can be still adjusted to the system settings with a click on the “inherit from system” option in the Tenant level monitoring settings dialog.

    Documentation128

    Documentation129

  • Job level monitoring settings can be adjusted with clicking on the particular job running in the column of Runs and configuring these settings in the Job level monitoring setting dialog. These settings are inherited from the tenant by default. Nevertheless it is still possible to set another value with a right click on the particular job in the Runs column, select here Settings and set the maximum history count in the dialog. This value can be adjusted to the default value inherited from tenant with clicking on the “inherit from tenant” option in the same dialog.


    Documentation130 Documentation131

Filtration in monitoring: If the user would like to check details of a certain system/job running, then he can also filter among the jobs under Filtration ⇒ Jobs: dropdown list. If it is necessary to check the system/job events that run in a certain period of time, then it is possible to further filter among these items with setting the Start date and the End date under filtering options. Under Event types it is allowed to filter among event types occurred in the actually selected events. An event type filter is also available at the bottom of the Event types dropdown list. Using this filter it is possible to sort out all events which belong to one of the 3 event groups [1. error (Documentation131.1), 2. warning (Documentation131.2) or 3. note (Documentation131.3]. Click on the mark of the particular event group next to “Select”, and the selected events will be displayed. On screenshot below, we sorted out all the notes (with a click on “Documentation131.3” mark).

Documentation134

Note: If the logged in user is a system administrator then he will be allowed to see the system related events, if he has tenant administrator rights, then he will be allowed to check the tenant related events using monitoring feature.



The Export function makes it easy to save the reviewed events into XML, CVS or HTML. The report contains all necessary information (date, job ID, Message, Details) which enable to have a look at the desired information, and also identify possible failures very quickly. This enables a very quick access to the system/job processing information, and also ensures a very quick troubleshooting in case of need.

Documentation133

On the below displayed screenshot we have filtered out Mailbox Provisioning Job and TA_ Email Archive job and set 1st of July 2015 as Start date, and 8th of July as End date. Among event types we have also set All events. This filter will find all the events related to these 2 jobs, which happened in this time interval.

Documentation134

Under Runs section click on the arrow mark next to the job, and the last run times will be opened. In the table of Events at the right side of the screenshot you can see all the events related to these 2 jobs, in time period 1st of July – 8th of July. With a click on the certain run of the job instance (for example with a click on the Mailbox Provisioning job that run at 7/2/2015 at 9:39-9:40) you can open further details about this running. In our case we can see that Mailbox provisioning job has processed in this time 98 mailboxes, of which 25 mailboxes added, 71 mailboxes skipped, 2 mailboxes updated etc. red arrows).

If you check the checkbox next to this job running, then the right hand table will display all events, all event types related to this job running at 9:39-9:40, on 2nd of July.

Documentation135

Note: The exact details of a job/system running can be opened/collapsed with a right click on the particular session and selecting Expand Details/Collapse Details from the context menu.

Documentation136


Note: With a right mouse click on a particular event and selecting Expand Detail/Collapse Detail from the context menu the user can open/close additional details related this selected event.

Documentation137



Now, if you want to visualize only Plugin was finished successfully information even type, then set this filter in the Event types checkbox. This will result, that only this type of event will be displayed in the table of Events.

Documentation138

With the Export function save this report in one of the file types, for example in HTML:

Documentation139

The report will contain all necessary information that might be very useful for a user to identify any failure, or just check the last event(s) of this job at the time period that was filtered out.

Documentation140

How to manually remove system/job runs and system/job related events from monitoring:

  • To delete system/job runs right click on the particular system/job run in column Runs and select Delete from the context menu (Screenshot A).
  • To delete a particular event right click on the particular event and select Delete from the context menu (Screenshot B)


  • Documentation141 Documentation142
    Screenshot A: Deleting system/job runs                                         Screenshot B: Deleting system/job events

    What to do if more space is needed on the monitoring page? If there are too many events and the user would like to have more space on the monitoring page, it’s a good idea to hide the ribbon with clicking on the arrow sign at the right upper corner of the user interface, under the About menu.

    Documentation143
Yes No Suggest edit
Help Guide Powered by Documentor
Suggest Edit