OST Corruption



Common Reasons Let a Microsoft Exchange OST File Corrupt or Damaged


There are many reasons that will make your Exchange offline folder (.ost) file corrupted or damaged. We classify them into two categories, i.e., hardware reasons and software reasons.

Hardware Reasons:

Whenever your hardware fails in storing or transferring the data of your Exchange OST files, the OST files will likely get corrupted. There are mainly three types:

  • Data Storage Device Failure. For example, if your hard disk has some bad sectors and your Exchange OST file is stored on these sectors. Then maybe you can only read part of the OST file. Or the data you read are incorrect and full of errors.
  • Networking Connection Failure . When you synchronize the OST file with the server through a network connection, if the network interface cards, cables, routers, hubs and any other devices constituting the network connection have problems, then the synchronization process will be aborted and the OST file is likely to get corrupted.
  • Power Failure. If a power failure happens when you are accessing or synchronizing the OST files, that may leave your OST files damaged.

There are many techniques to prevent or minimize the OST file corruption due to hardware problems, for example, UPS can minimize the power failure problems, redundant network can reduce the network problems, and using reliable hardware devices can also reduce the chances of data corruption.

Continue reading “OST Corruption”

Exchange Connectivity Test

For those who ever wanted to test activesync connectivity as well as web connectivity to an exchange here is a great tool that Microsoft has put out there for us.

You can test it but make sure the exchange server you are testing it on is running 2007 or 2010 otherwise you get errors.


Have fun and I’ve been able to use it a couple of times so if you have any questions I’ll be happy to help out with it.  It works really well when you are getting ready to setup smartphones on a network and need to verify settings prior to inputting them and then trying to troubleshoot from the phone.

Outlook Web Access (OWA) 2000 – Logoff Issue

3d postman with envelope and bagI recently was required to setup OWA 2000 for a client which currently has no plans or budget to upgrade to 2003/2007. And during the setup I encountered a problem I vaguely remembered from back in the 2000 era.

Basically, when using the logoff icon within OWA, you receive a http 500 error message. This is typically, although not always caused by creating a separate IIS Virtual Directory instance for OWA.

From within the properties of the Virtual Directory instance, under Home Page, be sure to Create an Application Pool, set “Script Only” access, and set to High Security.

You should be all set, however a word of caution. The OWA 2000 page is simply a page which says “you must close Internet Explorer” to really log off, and simply click this link to close your IE window. However, that’s it. If you don’t really close IE, you can simply go back into OWA without any problems or security. Also, as I recall, OWA never times out either, so by default you can leave OWA open indefinitely without problems.


Powered by WordPress.com.

Up ↑