Select the product you need help with
Error message when you try to start Outlook on a computer that has the Microsoft Dynamics CRM client for Outlook installed: "An error occured loading Microsoft Dynamics CRM functionality"Article ID: 911384 - View products that this article applies to. On This PageSYMPTOMSSymptom 1When you open the Microsoft Dynamics CRM client for Microsoft Office Outlook, you receive the following error message: An error occurred loading Microsoft CRM functionality, try restarting Outlook. In the event log, error messages that resemble the following are logged. Error message 1 The following information is part of the event: MSCRM Platform Error Report:
Error: Exception from HRESULT: 0x80040220.
Error Message: Exception from HRESULT: 0x80040220.
Error Details: Details on this error have not been provided by the platform.
Source File: Not available
Line Number: Not available
Stack Trace Info: at System.Web.UI.Page.HandleError(Exception e) at System.Web.UI.Page.ProcessRequestMain() at System.Web.UI.Page.ProcessRequest() at System.Web.UI.Page.ProcessRequest(HttpContext context) at System.Web.CallHandlerExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute() at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously).
Error message 2
The description for Event ID ( 16930 ) in Source ( MSCRMAddin ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 80004005, , CAddin::HrActivateAddin, 472.
Error message 3 The description for Event ID ( 5944 ) in Source ( MSCRMAddin ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: 80004005, , CAddin::HrInitializeUI, 137.
Symptom 2When you use Windows Vista with the Microsoft Dynamics CRM 4.0 client for Outlook and when you enable platform tracing, you receive an error message that resembles the following: Client Configuration: [Error] COM registry keys appear to be corrupted. Rerun the CRM Configuration Wizard or contact your Microsoft Dynamics CRM administrator. ---> System.TypeLoadException: Retrieving the COM class factory for component with CLSID {1385B9FE-D8DA-4A39-B990-5C870F8CAAD3} failed due to the following error: 80131522. at System.RuntimeTypeHandle.CreateInstance(RuntimeType type, Boolean publicOnly, Boolean noCheck, Boolean& canBeCached, RuntimeMethodHandle& ctor, Boolean& bNeedSecurityCheck) at System.RuntimeType.CreateInstanceSlow(Boolean publicOnly, Boolean fillCache) at System.RuntimeType.CreateInstanceImpl(Boolean publicOnly, Boolean skipVisibilityChecks, Boolean fillCache) at System.Activator.CreateInstance(Type type, Boolean nonPublic) at Microsoft.Crm.Outlook.Diagnostics.ComponentObjectModelDiagnosticCheck.Execute(BackgroundWorker backgroundWorker)
--- End of inner exception stack trace ---
at Microsoft.Crm.Outlook.Diagnostics.ComponentObjectModelDiagnosticCheck.Execute(BackgroundWorker backgroundWorker) at Microsoft.Crm.Outlook.Diagnostics.DiagnosticCheck.DeepExecute(BackgroundWorker backgroundWorker)
Symptom 3When you try to run the Microsoft Dynamics CRM client for Outlook, you cannot view the Microsoft Dynamics CRM folder structure. Additionally, you receive the following error message:
An error occurred loading Microsoft CRM functionality, try restarting Outlook. The following error messages are logged in the event log: Event Type: Error Event
Source: MSCRMAddin
Event Category: None
Event ID: 16930
Date: Date
Time: Time
User: N/A
Computer: ComputerName
Description: Initialization of the Microsoft CRM UI failed. Try restarting Microsoft Outlook. HR=0x80004005. Context=. Function=CAddin::HrActivateAddin. Line=521.
Additionally, you receive the following error message in the OUTLOOK-YYDDMM.log trace log file:
[Date and Time] Process: OUTLOOK |Thread:0832 |Category: Unmanaged.Platform |User: PlatformUser |Level: Error | HrGetXmlDOM File: c:\bt\643\src\application\outlook\v3caddin\xmlutil.cpp Line: 179 >hr = 0x80004005
Note In this error message, the Date and Time placeholder represents the actual date and the actual time. For example, the actual date and the actual time could be "2007-10-19 17:53:26.138." Symptom 4When you start the Microsoft Dynamics CRM client for Outlook, you receive the following error message:
An error occurred loading Microsoft CRM functionality, try restarting Outlook.
Additionally, Error event 80072f19 is referenced in the Application log:
Event: 16941
A problem occurred initializing the initialization progress toolbar. Restart Microsoft CRM and try again. HR=0x80072f19. Context=. Function=CAddin::HrActivateAddin. Line=322.
Symptom 5When you try to start Microsoft Office Outlook on a computer that has the Microsoft Dynamics CRM 4.0 client for Outlook installed, you receive the following error message: An error occurred loading Microsoft Dynamics CRM functionality.
Try restarting Microsoft Outlook. Contact your system administrator if errors persist. Event Type: Error
Event Source: MSCRMAddin Event Category: None Event ID: 16931 Description: A problem occurred initializing Microsoft CRM COM interop. Restart Microsoft CRM and try again. HR=0x80131700. Context=. Function=CAddin::HrActivateAddin. Line=274. Event Type: Error Event Source: MSCRMAddin Event Category: None Event ID: 5903 Description: The Microsoft CRM Outlook add-in could not be initialized correctly. Restart Microsoft Outlook and try again. HR=0x80070057. Context=. Function=CAddin::OnConnection. Line=196. CAUSECause 1This problem occurs because the role that is assigned to the user account does not have Read access to the Saved View entity in Microsoft Dynamics CRM. See Resolution 1. Cause 2This problem occurs because the NetBIOS over TCP/IP (NetBT) layer returns an incorrect code. This code does not trigger a DFS failover in the DFS client engine. See Resolution 2. Cause 3The Disable Folder Home Page configuration is enabled through Group Policy. The Disable Folder Home Page configuration is a Microsoft Office 2003 Administrative Template (OUTLK11.adm) configuration. If this setting is enabled, Office 2003 cannot load the Microsoft Dynamics CRM folder structure. See Resolution 3. Cause 4This problem occurs if IIS is missing the mappings for the .srf extensions that point to the CRMisapi.dll file. See Resolution 4. Cause 5This problem occurs because the check for server certificate revocation is enabled. See Resolution 5. Cause 6This problem occurs because the Outlook.exe.config file exists in the Microsoft Office installation folder. This file is used in troubleshooting instances for the Microsoft Outlook CRM 3.0 client for Outlook so that Outlook can use a specific version of the Microsoft .NET Framework. However, this file is not required for the Microsoft Outlook CRM 4.0 client for Outlook. See Resolution 6. RESOLUTIONResolution 1To correctly start the Microsoft Dynamics CRM client for Outlook, the role that is assigned to the user account must have Read access to the Saved View entity. To change the user's access, follow these steps:
Resolution 2For information about how to resolve this problem, click the following article number to view the article in the Microsoft Knowledge Base: 933860
(http://support.microsoft.com/kb/933860/
)
DFS failover does not occur when a client computer that is running Windows Vista tries to connect to a DFS root server that is unavailable, and you receive an error message: "System error 1214 has occurred"
Resolution 3To resolve this problem, change the setting of the Disable Folder Home Page configuration to "disabled" status. To do this, follow these steps for Outlook 2003:
Follow these steps for Outlook 2007:
Resolution 4To resolve this problem, add the .srf mapping to the Microsoft Dynamics CRM Web site. To do this, follow these steps:
Resolution 5To resolve this problem, follow these steps:
Resolution 6To resolve this problem, remove or rename the Outlook.exe.config file, and then restart Outlook. PropertiesArticle ID: 911384 - Last Review: September 11, 2011 - Revision: 11.0 APPLIES TO
| Article Translations
|


Back to the top








