Exchange Solutions

While upgrading an Exchange 2013 server to the latest cumulative update, I ran into the following error while setup was configuring prerequisites.

Service 'WMSVC' failed to reach status 'Running' on this server.

When attempting to start the service manually via the Services MMC, it refused to start, resulting in the following error.

Windows could not start the Web Management Service on Local Computer. For more information, review the System Event Log. If this is a non-Microsoft service, contact the service vendor, and refer to service-specific error code -217483640.

When reviewing the System Event Log an equally cryptic error was displayed.

The Web Management Service service terminated with the following service-specific error: Unspecified error

When migrating mailboxes between Exchange versions using the Exchange Admin Center you may receive the error:

Nullable object must have a value.

This error will appear when you navigate to the Recipient > Migration tab and click View Details on a migration batch. In the screenshot below we are examining a migration batch named “Test Migration to Exchange 2016” which contains two users. We are attempting to move these two users from Exchange 2013 to Exchange 2016.

From this screenshot, you will notice the Status column reports both users as successfully migrated. However, the Data Migrated and Migration Rate attributes in the right-hand pane are missing values. For an executed migration batch these attributes should contain metrics.

When upgrading to Exchange 2016 you may receive the errors, “There was a problem loading your options” & “Exchange Server doesn’t support the requested version”.

Both of these errors are centered around the add-ins feature.

What are add-ins?

First introduced in Exchange 2013, add-ins are apps that you can globally distribute to all your Outlook clients, whether they be the full Outlook client, Outlook Web App, or, Outlook for iOS and Android.

Add-ins include features such as Bing Maps, which will identify an address in an email and automatically load a web-part displaying a map. Or, simply the ability to identify action items within an email.

Exchange ships with a few add-ins out of the box. Additional add-ins can be downloaded through the Microsoft store or uploaded via a custom XML file.

The real beauty of an add-in is that you can centrally manage it via the Exchange Admin Center. Much easier than deploying Outlook add-ins with traditional endpoint management software. Plus it ensures everyone is always using the latest version of an app.

There was a problem loading your options (“add-ins”)

While in coexistence with an older version of Exchange your users may receive the error “There was a problem loading your options”. They receive this error when trying to manage their add-ins via Outlook Web App. This error prevents users from seeing or managing their add-ins.

Ran into an issue recently where Outlook was working fine, however, Android devices, particularly mobile phones, would throw an error that the certificate was invalid when configuring an Exchange mailbox via the Gmail app. The error was:

Certificate not valid

The Gmail app can't guarantee the security of this email address. Your messages would be at risk.

When clicking Advanced we received more clarification that the certificate was not trusted. However, we could quickly see that the correct certificate was being presented to the Android devices and it clearly wasn’t an issue with the date.

Certificate not trusted

Contact your email provider about this error, or proceed with username (unsafe).

We then tested our certificate with DigiCert’s SSL Certificate Checker. This is a great tool to confirm that the certificate is installed correctly and that the certificate path is valid. You can check any certificate with this tool. It does not have to be a certificate issued by DigiCert. In our case, we were testing our GoDaddy certificate with this tool.

While reviewing the event logs on your Exchange server you could encounter the following error.

Log Name: Application
Source: MSExchange ADAccess
Event ID: 2112
Task Category: Topology

Description:
 Process Microsoft.Exchange.Directory.TopologyService.exe (PID=2700). 
 The Exchange computer dc03.supertekboy.com does not have Audit Security 
 Privilege on the domain controller dc03.supertekboy.com. This domain 
 controller will not be used by Exchange Active Directory Provider.

We ran into this recently at a customer. This was an odd error because the description specified the name of one of our domain controllers as an “Exchange Computer”. That aside, my customer was receiving this error for two of their three domain controllers (dc02 & dc03). The error was also repeated across all their Exchange servers.

To make matters worse if the customer shut down the only domain controller not reported in these errors (dc01) Exchange would become completely unavailable. As the error stated, dc02 and dc03 were definitely not being used by the Exchange Active Directory Provider.

Further analysis of the event logs also revealed informational alert MSExchange ADAccess 2080. In this alert, we could see our three domain controllers with one striking difference.

Log Name: Application
Source: MSExchange ADAccess
Event ID: 2080
Task Category: Topology

Description:
 Exchange Active Directory Provider has discovered the following servers with
 the following characteristics:

 (Server name | Roles | Enabled | Reachability | Synchronized | GC capable |
 PDC |  SACL right  | Critical Data | Netlogon | OS Version)
 In-site:
 dc01.supertekboy.com CDG 1 7 7 1 0  1  1 7 1
 dc02.supertekboy.com CDG 1 7 7 1 0  0  1 7 1
 dc03.supertekboy.com CDG 1 7 7 1 0  0  1 7 1

In the eighth column (highlighted), dc01 was reporting a 1 whereas dc02 and dc03 were reporting a 0. All other column data was identical between the three servers. The words in parenthesis are actually the column headers. They don’t line up very well in event viewer but if we count to the eighth word we see the column is titled “SACL right”. What this means is that the Exchange servers are missing the SACL right on the domain controllers marked with a zero.  Or more specifically, Exchange is missing the right to manage the security and audit logs of those two domain controllers.

When installing an Exchange update you may run into the following error.

Error:
The following error was generated when "$error.Clear(); 
 & $RoleBinPath\ServiceControl.ps1 -Operation:DisableServices -Roles:($RoleRoles.Replace('Role','').Split(',')) -SetupScriptsDirectory:$RoleBinPath;
 & $RoleBinPath\ServiceControl.ps1 Stop $RoleRoles.Replace('Role','').Split(',')
 " was run: "Microsoft.Exchange.Configuration.Tasks.ServiceStopFailureException: 
 Service 'tmlisten' failed to stop due to error:'Cannot stop tmlisten service on computer 
---> System.InvalidOperationException:  Cannot stop tmlisten service on computer 
---> System.ComponentModel.Win32Exception: The requested control is not valid for this service

The tmlisten service is associated with the Trend Micro antivirus product and specifically the Trend Micro Listener service. This service requires a password to stop and can not be disabled via either the services snap-in or command line.

Tip: It’s best practice to temporarily shut down antivirus products during the Exchange install as they have been known to increase install times by several hours. Or, in this case, completely block updates.

The tmlisten workaround

To disable Trend Micro right-click on its icon in the system tray and select Exit Security Agent.

You will be prompted to enter a password to shut down the Trend Micro services. Enter this password and click Ok.

You may need to wait about 60 seconds for the Trend Micro services to stop. Once stopped you can continue your Exchange update past this error.

Have you ever run into this problem? What did you do to fix it? Drop a comment below or come join the conversation on Twitter @SuperTekBoy.