Thursday, February 16, 2012

Troubleshooting Outlook OST Error 'Errors have been detected In the File Outlook.ost'

For a real time collaborative messaging environment Microsoft Exchange Servers are deployed by end number of business enterprises all over the map. What Exchange administrators realize is that any sort of malfunction or Exchange Server failure can result in downtime that can prove to be disastrous for the organization. Even at the time of maintenance or upgrading the server to a higher version would require the Exchange to be brought down making all the user data inaccessible for the time being.

For a business enterprise it can be critical and lead to a great loss. Fortunately, Exchange OST files (Offline Storage Table) are available that can allow the Exchange users to work in the offline mode and serve as the replicas of user mailboxes stored on the local machine. This makes it possible for the Exchange administrators to bring down the server for maintenance or any other purpose without disabling all the access to the user's mailbox data. Once the Exchange Server is back online, the OST files synchronize with it and whatever work has been done offline gets updated onto the server mailboxes.

A banal error message encountered at the time when the Exchange OST file is accessed is:

“Errors have been detected In the File Outlook.ost”

Once you come across the aforementioned error message you loose access to emails, attachments, appointments, calendar entries, notes, tasks and journals. The appearance of this error clearly means that the Exchange OST file has become corrupt and no matter how many attempts are made to access the file, it would remain futile leading to cardinal data loss.


OST file corruption can result due to multifarious factors such as a virus attack, oversized OST, OS malfunction, hardware and software issues. Whenever a user is struck by the bolt of OST file corruption, the primary resolve turns out to be OST Recovery using the inbuilt utility Inbox Repair Tool (Scanost). Scanost.exe is the free utility by Microsoft that scans and repairs the corrupt OST file by completely restructuring the file and removing all the corrupt or unreadable items. This sometimes removes vital data from the OST file. Additionally, Scanost is not able to repair the OST file under severe cases of corruption.

The best resolve for OST file corruption is to devoir a professional third party OST Recovery Software that can successfully recover all the user data from the severely corrupt or damaged OST by using adavanced scans and mechanisms. One such powerful tool is “OST to PST Converter”. This adroit software recovers user mailbox data such as emails, attachments, calendar, contacts, notes, tasks, To-do lists and journals from the corrupt OST file by Converting OST to PST. The software is built with an interactive interface and comes with a step by step user guide that both regular and savvy Exchange users can operate easily. This preeminent OST Recovery Software is compatible with MS Outlook 2010, 2007, 2003, 2002 and 2000.

Wednesday, February 8, 2012

Resolving Outlook OST accessibility issues owing to RPC Connectivity

Microsoft Exchange Server creates OST files in the cached mode that are the exact replicas of server mailboxes but are stored on a user's local computer. These OST files need to synchronize with the Exchange Server in order to reflect all the work done in the offline mode on the actual server mailboxes. Sometimes when the OST file is tried to be accessed it returns the following error message:

The name could not be resolved. The Microsoft Exchange address book was unable to logon to the Microsoft Exchange Server computer.

Root of the problem:

The aforestated error is the result of one or more missing/corrupt RPC registry entries. RPCs (Remote Procedure Call) protocol registry keys are deployed by Microsoft Outlook to make calls to the network. RPCs permit users to send calls to many different protocol stacks, the most common one being TCP/IP. If one or more of these registry keys are missing, Outlook fails to establish a connection with the Exchange Server. Moreover, in the absence of required RPC entries Exchange Services are not registered to respond to client requests.


To identify and troubleshoot the RPC issues RPC Dump can be used. The three most essential RPC components required by Outlook to connect successfully are:

1.The endpoint mapper
2.Exchange Information Store service with the Universal Unique Identifier (UUID) of a4f1db00-ca47-1067-b31e-00dd010662da.
3.The Name Service Provider Interface (NSPI) with the UUID of f5cc5a18-4264-101a-8c59-08002b2f8426.

RPC Dump should be run through the following command prompts:

rpcdump.exe /i > rpcdump.txt
rpcdump.exe /p > rpcdump.txt

In order to restore the missing RPC registry values follow these steps:

1.Verify registry entries
2.Verify the version of the DLL file
3.Remove and reinstall TCP/IP

If this is still not able to resolve the issue, then the OST file has become corrupt and needs to be recovered by OST to PST Conversion. Myriad OST errors are encountered owing to corrupt or orphaned Outlook OST files. The only way for efficacious Outlook OST Recovery is through reliable third party tools. One such sought after tool is “Stellar Phoenix OST to PST Converter”.

Stellar is a leading name in the world of data recovery and this powerful utility can recover all the Outlook OST file data into an importable PST file for MS Outlook 2010, 2007, 2003, 2002 and 2000. The demo version of the software is available for free download and offers a clear preview of the recoverable items in a three view structure. This is an adroit tool that can recover vital user mailbox data by successful conversion from OST to PST.