MS Outlook is quite useful among professionals and more organizations are embracing the email platform due to its simplified user platform and other friendly features. Microsoft who is trying everyday to improve the Outlook and is focusing on improving its services, wants to remove all the bugs faced by the user while using the email platform.
There are the numbers of issues faced by the professionals while using the email platform, but the most notorious issue comes to play while exchange of the emails from the exchange server. This error message is not difficult to recognize. You must have seen the following messages in the dialog box.
-Task “Microsoft Exchange Server – Sending” reported error (0x8004060c): ‘The message store has reached its maximum size. To reduce the amount of data in this message store select some items that you no longer need and permanently delete them.’
-Task “Email Address- Sending and Receiving” reported error (0x8004060c): ‘Unknown Error 0x8004060c.’
-Task “Microsoft Exchange Server- Receiving” reported error (0x8004060c): ‘Unknown Error 0x8004060c.’
To deal with such error user must be either be qualified one to sort it by own or the user must be ready to take the assistance from an external software. It could be a third-party software that can sort out the issues within minutes without involving any algorithmic approach directly over the screen.
Before counting on any software for the rescue to the problem, user must understand the reason for occurrence of such error. Many professionals suggests following reasons for the occurrence of error (0x8004060c):
So it can be clearly inferred that no clear majority claims a single reason to be responsible for the occurrence of error (0x8004060c). Thus, before moving to the resolution users must know how to technically handle the situation.
To resolve the error (0x8004060c) manually there are certain fundamentals that must be known. It includes the knowledge of location of registry files, methods to reduce the OST and PST file size and file size limitations.
The issues related to Outlook (0x8004060c) error can be resolved in following ways:
These solutions are explained as follows:
To enhance the Outlook message capacity the Windows registry limits must be enhanced. To do so user has to perform the following steps:
Before entering into compaction of OST/PST files, user must check the Outlook version they are using. For Outlook 2007 users, open the Tools menu, while Outlook 2010 users must open the File Tab on the ribbon click Info and Choose the Account Settings.
To recreate OST files user has to follow these steps:
Note: Users can also try recreating the .ost file in case of corruptions by deleting the file from its location (find it through Account Settings in Outlook or directly go to C:\Users\Username\AppData\Local\Microsoft\Outlook) and then restart the Outlook application with configured Exchange Server account to create a fresh updated .ost file.
This is the best way to reduce the OST size and eliminate the unwanted mailbox entries.
Also, try archiving the old .ost emails based on time filter using the Archive option in the Cleanup Tools feature in the Outlook application to a desired saving path location. There is a separate AutoArchive feature in the Outlook options using which you can decide the archiving frequency, old items saving destination, deleting actions on old items (delete on every –time or permanently delete old items, etc.
There are many chances that the file error ‘0x8004060c While Trying to Send/Receive Email from Outlook’ may get resolve with such resolutions; however, if we consider 1% chance of failure then we even have the solution for such issue. In such cases user is recommended to take assistance from a reliable third-party tool like OST to PST Tool. To evaluate the performance of the tool, the trail version can be tried that exactly works like the licensed version with varied success rate. Upon satisfaction with its performance user can purchase the licensed version without any delay. Just try once before entering into technical complications.