• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer

SuperTekBoy

Practical Help for Exchange & Office 365

  • Exchange
    • News
    • Tutorials
    • Solve a Problem
    • Videos & Podcasts
  • Office 365
    • News
    • Tutorials
    • Solve a Problem
    • Videos & Podcasts
  • Outlook
    • Tutorials
    • Solve a Problem
    • Videos & Podcasts
  • Windows
    • News
    • Tutorials
    • Solve a Problem
    • Videos & Podcasts
  • Quick Links…
    • Generate or Renew SSL Certs for Exchange
    • Connect PowerShell to Exchange Online
    • Connect PowerShell to Office 365
    • Extend Schema for Exchange
    • Exchange Schema & Build Numbers
  • More…
    • Kemp Load Balancers
    • Other tech…
    • About SuperTekBoy
    • Contact Us

Exchange Solutions

Web Management Service (WMSvc) could not be started: 2147483640

July 5, 2018 By Gareth Gudger 10 Comments

14 Shares
Share
Tweet
Share
Reddit
Print

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.
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.
Windows could not start the Web Management Service on Local Computer 2147483640

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
Web Management Service terminated with the following service-specified error unspecified error
[Read more…] about Web Management Service (WMSvc) could not be started: 2147483640

Filed Under: Exchange Solutions

​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​Nullable object must have a value (when migrating mailboxes)

June 16, 2018 By Gareth Gudger 1 Comment

18 Shares
Share
Tweet
Share
Reddit
Print

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.

​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​Nullable object must have a value

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.

[Read more…] about ​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​​Nullable object must have a value (when migrating mailboxes)

Filed Under: Exchange Solutions

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

May 18, 2018 By Gareth Gudger Leave a Comment

18 Shares
Share
Tweet
Share
Reddit
Print

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.

Outlook Web App - There was a problem loading your options
[Read more…] about Exchange Server – There was a problem loading your options (“add-ins”)

Filed Under: Exchange Solutions

GMail App fails to connect to Exchange – Certificate not valid

February 17, 2018 By Gareth Gudger 1 Comment

26 Shares
Share
Tweet
Share
Reddit
Print

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.
GMail App fails to connect to Exchange - Certificate not valid

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).
GMail App fails to connect to Exchange - Certificate not trusted

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.

[Read more…] about GMail App fails to connect to Exchange – Certificate not valid

Filed Under: Exchange Solutions

Exchange does not have Audit Security Privilege on the domain controller

January 6, 2018 By Gareth Gudger 7 Comments

33 Shares
Share
Tweet
Share
Reddit
Print

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.

[Read more…] about Exchange does not have Audit Security Privilege on the domain controller

Filed Under: Exchange Solutions

Error ‘Cannot stop tmlisten service’ when installing Exchange updates

December 31, 2017 By Gareth Gudger 3 Comments

31 Shares
Share
Tweet
Share
Reddit
Print

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.

Temporarily disabling Trend Micro - tmlisten.exe

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

Trend Micro Disable With Password - tmlisten.exe

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.

Twitter

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.

Filed Under: Exchange Solutions

No account settings were returned from the Autodiscover response

December 30, 2017 By Gareth Gudger 14 Comments

97 Shares
Share
Tweet
Share
Reddit
Print

While attempting to configure an Outlook client with an Exchange mailbox I ran into an issue where the account creation would not complete. Instead, Outlook would stop on “Search for server settings” and prompt me for a username and password. The credentials of my Exchange account did not work and kicked back the login prompt.

When I attempted to test Autodiscover using testconnectivity.microsoft.com I ran into an even stranger error. Autodiscover appeared to work. But I received the error “No account settings were returned from the Autodiscover response”.

No account settings were returned from the Autodiscover response

Examining the Autodiscover response I noticed that the test successfully completed against the root of supertekboy.com. This was odd as supertekboy.com is redirected to the website www.supertekboy.com where no Autodiscover responses should be happening.

No account settings were returned from the Autodiscover response using root domain record

However, when attempting to plug the Autodiscover URL into a web browser I found that something was responding to Autodiscover requests. It was responding with an error of “Autodiscovery must be provided a valid email address”.

Autodiscovery must be provided a valid email address b

This isn’t an Exchange or Office 365 autodiscover response. Instead, this was my web hosting provider responding to my Autodiscover request. Specifically, cPanel. cPanel has its own implementation of autodiscover, which allows Outlook and other email clients to automatically configure themselves for a cPanel mailbox. Unfortunately, this conflicts with autodiscover locating an Exchange or Office 365 mailbox.

[Read more…] about No account settings were returned from the Autodiscover response

Filed Under: Exchange Solutions, Office 365 Solutions

Disabling TLS 1.0 may cause Outlook to crash

November 11, 2017 By Gareth Gudger 1 Comment

244 Shares
Share
Tweet
Share
Reddit
Print

Disabling TLS 1.0 may cause Outlook to crash for some of your clients.

I encountered this recently while upgrading a customer from Exchange 2010 to Exchange 2016. The customer had an existing Kemp Load Balancer they had been using for Exchange 2010. We upgraded the Kemp to the latest firmware and created a new Exchange 2016 VIP using the latest templates from Kemp. When we cut over our DNS to the new VIP some of our Outlook clients started to receive the errors below. Other Outlook clients continued to operate without incident.

For some Outlook clients, we would receive errors when creating a brand new profile in Outlook. Errors such as,“Windows Shell Common DLL has stopped working”

Outlook 2016 - Windows Shell Common DLL has stopped working

Clicking “Close Program” would then be followed by an error reporting that “System resources are critically low”.

Outlook 2016 - System resources are critically low
[Read more…] about Disabling TLS 1.0 may cause Outlook to crash

Filed Under: Exchange Solutions, Kemp Load Balancers

  • « Go to Previous Page
  • Go to page 1
  • Go to page 2
  • Go to page 3
  • Go to page 4
  • Go to page 5
  • Interim pages omitted …
  • Go to page 8
  • Go to Next Page »

Primary Sidebar

Want to stay up to date?

Join thousands of IT professionals and get the latest Exchange & Office 365 tips and tutorials direct to your inbox

My favorite book on all things Office 365! Continually updated with fresh content by MVPs Tony Redmond, Paul Robichaux, Brian Desmond, Ståle Hansen & more! Get the eBook
Office 365 for IT Pros 7th Edition
(affiliate banner)

Free Kemp Loadbalancer 300x300
(affiliate banner)

Passware

(affiliate banner)

DigiCert SSL certificate for Microsoft Exchange

(affiliate banner)

Footer

Site Navigation

  • Subscribe to blog
  • About SuperTekBoy
  • Disclaimer
  • Privacy & Cookies
  • Contact Us

Want to stay up to date?

Join thousands of IT professionals and get the latest Exchange & Office 365 tips and tutorials direct to your inbox

Join the conversation

  • Twitter
  • LinkedIn
  • Facebook
  • YouTube
  • RSS

Copyright © 2021 · SuperTekBoy LLC