Click on the Programs and Features option. Select the Microsoft Office program and click on the Change option. Then select the Repair option and select the Quick Online Repair option to start the online repair and fix issues if available. If still gets the error, try reinstalling the Microsoft Office application on your system.
-->Original KB number: 2785498
- I am experiencing the same problem as Patricia. Mine is a new laptop with Win10 and Office 365 installed. So how do I fix it? My desktop Win 7 started crashing now. Been working great until recently - same time as I began experiencing problems with Win 10. This is really frustrating.
- Hi MT, DataType is not supported. Pretty much explains this mishap. What is the data in the source, is it text, and how large? You need to find the max as perhaps NVARCHAR2 can do (4k chars).
- Summary: In this post, we have explained the causes behind Outlook error 0x80004005 and listed different Outlook messages associated with this error.
Symptoms
Microsoft Outlook does not successfully configure an account automatically. When you use the Test E-mail AutoConfiguration tool, you receive output similar to the following on the Log tab:
- Outlook 2013
Local autodiscover for Contoso.com starting
Local autodiscover for Contoso.com Failed (0x8004005)
- Outlook 2010
Local autodiscover for Contoso.com starting
Local autodiscover for Contoso.com Failed (0x8004010F)
Microsoft Office Error Code 0x80004005
Cause
This issue can occur when the following registry subkey exists and is empty:
HKEY_CURRENT_USERSoftwareMicrosoftOfficex.0OutlookAutoDiscoverBoot
Microsoft Office Error Code 0x80004005
Note
In this subkey, x.0 is 15.0 for Outlook 2013 and 14.0 for Outlook 2010.
Resolution
Important
This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, see How to back up and restore the registry in Windows.
Follow these steps to delete the Boot subkey:
Exit Outlook if it is running.
Select Start, and then select Run. Copy and paste (or type) the regedit command in the Open box, and then press Enter.
Locate the following registry location:
HKEY_CURRENT_USERSoftwareMicrosoftOfficex.0OutlookAutoDiscoverBootNote
In this subkey, x.0 is 15.0 for Outlook 2013 and 14.0 for Outlook 2010.
If the registry key exists, follow these steps to delete it:
Select the following registry subkey:
HKEY_CURRENT_USERSoftwareMicrosoftOfficec.0OutlookAutoDiscoverBootNote
In this subkey, x.0 is 15.0 for Outlook 2013 and 14.0 for Outlook 2010.
On the Edit menu, select Delete.
When you are prompted to confirm the deletion, select Yes.
Exit Registry Editor.
Start Outlook.
More information
Use the Test E-mail AutoConfiguration tool to help determine why AutoDiscover failed in Outlook. To do this, follow these steps:
- Start Outlook.
- Hold down the Ctrl key, right-click the Outlook icon in the notification area, and then select Test E-mail AutoConfiguration.
- Verify that the correct email address is in the E-mail Address box.
- In the Test E-mail AutoConfiguration window, clear the Use Guessmart check box and the Secure Guessmart Authentication check box.
- Select the Use AutoDiscover check box, and then select Test.
Note
In some cases, customers report that AppSense software re-creates the Boot registry subkey under specific conditions. However, this does not necessarily occur. If AppSense software is used in a virtual environment, and if the administrator believes that the software may cause the Boot registry subkey to be re-created, the administrator should contact AppSense for support.
Third-party contact disclaimer
Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information.