This article is about an infrequent issue I see with Windows Exchange servers that causes a complete outage. It is really hard to figure out what is wrong. Normally, you will see this when you restore an Exchange server to new hardware or a new virtual platform. But I’ve also seen it occur spontaneously with existing servers.
Windows 2008 R2 Server (normally)
Exchange 2007 or Exchange 2010 or Exchange 2013
Exchange Information Store service is “starting”, will not start
Services does not display and/or blank for a long time
Server manager information does not display or very slow
Network properties , NIC settings, does not come up
Control Panel does not display
- Rebooting does not work (and the server normally will not shutdown gracefully)
- You can ping the server and ping from it, but remote desktop does not work.
- (Often) The server has recently been restored from backup
- (Often) The server is running in a virtual environment
- (Often) Task manager shows low CPU activity
Exchange is trying to use a network adapter (NIC) that doesn’t exist anymore.
This normally happens when you restore to new hardware. For example, your server may have had one network card: “Network Connection 1”.
When you turn on Windows with new hardware, “Network Connection 1” is hidden and you will see “Network Connection 2” (or potentially a new “Network Connection 1”).
Most Windows servers handle this just fine, but with Exchange, the Information Store service is still trying to use the hidden network card. This locks up the Network Connections window, Control Panel, Services, and other administrative panels. The Information store stays “starting” during this process.
How to fix:
You need to remove the hidden network adapter from your server’s Device Manager.
- Click Start, click Run, type cmd.exe, and then press ENTER.
- Type set devmgr_show_nonpresent_devices=1 and then press ENTER.
- Open device manager (run devmgmt.msc or Right-click My Computer > Manage)
- Type Start DEVMGMT.MSC, and then press ENTER.
- From the top menu, click View, and then click Show Hidden Devices.
- Expand Network Adapters.
- Right-click the hidden network adapter, and then click Uninstall. If in doubt, I’d remove everything that looks like a network adapter. The server will re-install the live ones during reboot.
- Give it a reboot.
- You may need to re-configure your IP address on the existing NIC.
- At this point your information store should start properly and your server will begin responding normally.
What to do if Device Manager won’t open?
If you can’t manage your server because none of the admin windows will open, you need to get the Exchange Information Store service stopped and disabled. Once you get the Information Store out of status “starting”, your network properties, device manager, control panel, etc, will open.
Here are some ideas to try.
- If you are using a virtual server (VMWare, KVM, or HyperV), remove all virtual network adapters from the server. Reboot the Exchange server afterward. You should be able to get to Services now.
- Try using Computer Management from another computer to access the server (I don’t remember if this works).
- Try using command prompt to stop and disable the Information Store service (I don’t remember if this works).
sc config "store" start= disabled
sc stop "store"
- Try booting into safe mode to stop and disable the Information Store Service.
- If you are using a physical server, and nothing else is working, try removing the physical network adapter.
Helpful reference material (for this and other related errors):
I hope that works for you! If it does, or does not, please leave a comment to help others!
If you need a senior escalation point for Exchange, VMware, or Netapp technologies, consider Kieri Solutions. You can find more about me and my company in the menu above.