Troubleshoot the Splunk App for Microsoft Exchange

Is the Splunk App for Microsoft Exchange deployment correctly configured?

The first thing to check when Splunk App for Microsoft Exchange data is incomplete or incorrect is to confirm that the central Splunk instance is properly configured and receives data.

1. Confirm that every indexer in the deployment has been configured to receive data. See Install and configure a Splunk Enterprise indexer for instructions.
2. Confirm that every search head in the deployment has been configured to search all indexers. Search heads must search all available indexers to get all indexed data. See Configure distributed search in Distributed Search for specific instructions on configuring search heads and search peers (indexers).
3. Confirm that you have installed and configured all of the pieces properly. Indexes that the Splunk App for Microsoft Exchange requires must be present on all indexers.
   
• msexchange for Exchange events.
• msad: for AD health metrics.
• winevents: for Directory Service, Replication Service, DNS server event logs.
• perfmon: for performance metrics.
4. Confirm that the Splunk App for Microsoft Exchange resides on all indexers and search heads in the deployment.
5. Confirm that the Splunk Supporting Add-on for Active Directory (SA-ldapsearch) has been configured properly. See Configure the Splunk Supporting Add-on for Active Directory.
6. Confirm that the Splunk Supporting Add-on for Active Directory resides on all search heads in the deployment. See "Troubleshoot issues with SA-LDAPsearch."
7. Confirm that eventtypes.conf (in %SPLUNK_HOME%\etc\apps\splunk_app_microsoft_exchange\local) has been configured with the proper indexes for the defined event types. Check for typos in the configuration file.
8. Confirm that the Splunk App for Microsoft Exchange lookup tables have been properly created. From the "Tools and Settings" menu, select "Build lookups".
9. Confirm that PowerShell is available on all domain controllers and DNS Server hosts. See Configure PowerShell execution in Active Directory.
10. Confirm that Group Policy objects to change audit policy are in place to enable local script execution. See "Configure Active Directory Audit Policy."

Troubleshoot issues with SA-LDAPsearch

To troubleshoot problems with the Splunk App for Microsoft Exchange and the Splunk Supporting Add-on for Active Directory version 3.0.0, see, see Troubleshoot the Splunk Supporting Add-on for Active Directory in the Splunk Supporting Add-on for Active Directory documentation.

To troubleshoot problems with version 3.0.0 see Troubleshoot the Splunk Supporting Add-on for Active Directory for version 3.0.0.

Windows event log or performance events from universal forwarders go to the 'main' index

When you install a universal forwarder on your Exchange server, do not select any options in the Enable Inputs screen of the installer. Doing so enables the scripted inputs that come with the forwarder by default. Those inputs send data to the "default" index as specified in their configuration files, which, on a standard Splunk Enterprise installation, is main.

After you install the universal forwarder onto your exchange server, deploy the appropriate add-ons for Windows, Active Directory, Windows DNS, or Exchange to ensure that the data those add-ons collect goes to the correct index.

If you're using TA-Windows version 6.0.0 or later, you don't need TA_AD and TA_DNS. TA_AD and TA_DNS are merged with TA-Windows version 6.0.0.

No data types found after upgrade

If you experience a problem where the first-time run process detects no data after an upgrade, make sure that you add the exchange-admin role to the user that runs the app.

1. From Splunk Web, click Settings.
2. In the window that pops up, under "Users and Authentication", click Access Controls. Splunk Enterprise loads the "Access Controls" page.
3. Click Users. Splunk Enterprise loads the "Users" page.
4. In the Username column, click the name of the user that runs the Splunk App for Microsoft Exchange. Splunk Enterprise loads the settings page for that user.
5. Scroll down to Assign to roles.
6. Add the exchange-admin role to the Selected roles pane by clicking on its entry in the Available roles pane.
7. Click Save. Splunk Enterprise saves the changes and returns you to the Users page.

Dashboards do not populate due to errors with PowerShell modules

If you run Exchange Server 2010 with Service Pack 2, you might experience an issue where dashboards do not populate because of errors with PowerShell. This owes to a bug that occurs when you apply Exchange Server 2010 SP2. This is a problem with Exchange Server and not with the Splunk software.

To fix the problem, follow the instructions at "Microsoft.Exchange.Management.PowerShell.E2010 is not installed on this machine" on MS TechNet Blogs.

Dashboards fail to load after upgrading the app or Splunk Enterprise

If you experience a problem where some dashboard panels or menus fail to load after you upgrade either Splunk Enterprise or the Splunk App for Microsoft Exchange, clear your web browser cache, log out of Splunk Enterprise, then log back in.

The Service Analyzer page displays errors after an upgrade

If you experience errors in the Service Analyzer after upgrading the Splunk App for Microsoft Exchange, confirm that the new data model has built successfully.

Check data model build progress

To check the status of the new Microsoft Exchange data model, follow this procedure:

1. Log into Splunk Enterprise on a search head in the deployment.
2. In the system bar, click Settings > Data Model. Splunk Enterprise loads the "Data Models" page.
3. In the entry for Microsoft Exchange click the caret to the left of the title.
4. Review the status under Acceleration. The status says "100% complete" when it has finished. Otherwise, it says "Building."
5. Wait until the status says "100% complete" before using the app. After an upgrade, this process could take a while.

Disable Transport Handling and Mailbox components in Service Analyzer for Exchange Server 2007 and Server 2010 environments

Fix an issue where tiles in the Service Analyzer and Service Health pages spuriously appear as red when the Splunk App for Microsoft Exchange monitors an Exchange Server 2007 or Exchange Server 2010 environment.

Symptoms

When you visit the Service Analyzer page, the "Mailbox" and "Transport Handling" tiles appear red/in a "Critical/Error" state, even though no data is present that warrants the services appear in such a state.

Cause

In Exchange Server 2007 and 2010, the Mailbox and Hub Transport roles were separate and had their own set of exclusive Windows services. In Exchange Server 2013, the Hub transport role was merged with the Mailbox role.

By default, Service Analyzer shows all of the components for both roles in the Hub Transport and Mailbox services. This means that if you have an Exchange Server 2007 or Exchange Server 2010 environment, you will see red components for those services.

Workaround

To fix this, use the configure components page to disable the following components for your Exchange Server 2007 and 2010 hosts:

Transport Handling role	Mailboxes role
Information Store Mail Submission Service Mailbox Assistants Replication Service RPC Client Access Service Search Service Backup Extension System Attendant Service Throttling Service	Anti-Spam Service Edge Sync Service Protected ServiceHost Transport Service

This problem only appears on Windows systems.

Exchange app installed on same search head as the Splunk App for Windows Infrastructure

Your deployment receives the following error.

Configuration file settings may be duplicated in multiple apps: stanza="ActiveDirectory: Create Computer Lookup" file="savedsearches" apps="splunk_app_microsoft_exchange,splunk_app_windows_infrastructure"

This error happens when the Splunk App for Windows Infrastructure and the Splunk App for Microsoft Exchange are installed on the same search head. The Splunk App for Windows Infrastructure and the Splunk App for Microsoft Exchange contain identical knowledge objects that cause a conflict when installed on the same search head deployment.

Removing either the Splunk App for Windows Infrastructure or the Splunk App for Microsoft Exchange will resolve this issue.

Lookup errors on all searches for WinEventLog:System:IAS and source:::Security' If running splunk_app_microsoft_exchange v3.5.0 with Splunk_TA_windows 4.8.4.

This section is for troubleshooting lookup errors on all searches for WinEventLog:System:IAS and source:::Security.

If you experience the following search errors on UI while running splunk_app_microsoft_exchange v3.5.0 with the Splunk_TA_windows 4.8.4, then remove windows_apps lookup and its transforms definition from Splunk App for Microsoft Exchange.

Error 'Could not find all of the specified lookup fields in the lookup table.' for conf 'source::*:Security' and lookup table 'windows_app_lookup'.

Remove windows_apps.csv lookup from main app.

1. Remove windows_apps lookup from /etc/shcluster/apps/splunk_app_microsoft_exchange/lookups on the searchhead deployer (In case of standalone searchhead, remove it from /etc/apps/splunk_app_microsoft_exchange/lookups).
2. Remove following windows_apps lookup definition from /etc/shcluster/apps/splunk_app_microsoft_exchange/default/transforms.conf on the searchhead deployer (In case of standalone searchhead, remove it from /etc/apps/splunk_app_microsoft_exchange/default/transforms.conf).

[windows_app_lookup]
filename = windows_apps.csv

[windows_apps]
filename=windows_apps.csv
max_matches=1

3. Push bundle from deployer to SHs.
4. *In case of standalone searchhead, restart Splunk on SH.

Troubleshoot Splunk App for Microsoft Exchange performance issues

If you run into performance issues with the Splunk app for Microsoft Exchange, add maxDataSize and maxHotBuckets under all the stanzas in indexes.conf. For exaple:

[msexchange]
homePath = $SPLUNK_DB/msexchange/db
coldPath = $SPLUNK_DB/msexchange/colddb
thawedPath = $SPLUNK_DB/msexchange/thaweddb
maxDataSize = 10000
maxHotBuckets = 10
repFactor = auto