How to solve the message "Microsoft Visual Basic: "Automation error: Unspecified error (440)" with MS Office Excel?

It can happen that an export of data to Microsoft Office Excel shows the notification "Microsoft Visual Basic: Automationerror: Unspecified error (440)". Also opening Microsoft Excel itself will displays this notificiation. After a recent Microsoft update the notification will occuur with Microsoft Office.

The notification can be solved by registering the file MSCOMCTL.OCX again.

  • Check if the machine is 32 of 64 bits.
  • Go to [Start-run] on the workstation/server.
  • If it's a 32 bits machine type the following: regsvr32 C:\windows\System32\MSCOMCTL.OCX 
  • If it's a 64 bits machine type the following: regsvr32 C:\windows\SysWOW64\MSCOMCTL.OCX 

After doing this a notification will come that the file is correctly registered. If this is not the case and you get for instance the following notification 
"'MSCOMCTL.OCX' is loaded but the call to DllRegisterServer failed with error code 0x80004005.", this could be due to security issues on the workstation / server.

If this is the case make sure the Windows "Dos Prompt / Command Prompt" is opened with "run as administrator". To do this go to [Start-all programs-accessoires] and click with right mouse on the "Command Prompt" and choose to run as administrator.

In the Command Prompt screen you can type the line (regsvr32 C:\windows\System32\MSCOMCTL.OCX or regsvr32 C:\windows\SysWOW64\MSCOMCTL.OCX) and press enter.

After the file is correctly registered opening Microsoft Excel will not show the notification anymore and exports out of Exact Globe will also work correctly.

For more information about the Microsoft updates which cause this notification use the following links:


 Main: Support Product Know How
 Cat: FAQ
 Sub: Functional
 Assort: Exact Globe
 Doc Type: *FAQ-Functional
 Doc ID: 23.821.335
 Date: 26-09-2012



Despite the continued efforts of Exact to ensure that the information in this document is as complete and up-to-date as possible, Exact can not be held accountable for the correctness and/or completeness and/or specific applicability of the published and/or requested information in this document. Exact shall not be liable for any direct, indirect, incidental, special or consequential damages, lost profits or for business interruption arising out of the use of this document. The extraction and use of information from this document remains at all times completely within the user's own risk.


No tags added
One moment please...