If Typefi Writer cannot load certain form controls, the problem is typically rooted in the Microsoft Windows Common Controls (MSCOMCTL.OCX). This issue can be represented by several different errors, including:
- "Could not load an object because it is not available on this machine."
- "Unexpected error 91 - Object variable or With block variable not set." If you updated to the 64-bit edition of Typefi Writer and cannot see the Typefi ribbon in Microsoft Word, follow the troubleshooting steps in this article.
The scope of this issue ranges from Word 2003 to Word 2016 and is typically introduced by an update to Office of Windows. Typefi Writer does not ship, or register, MSCOMCTL.OCX
but relies heavily on it for functionality. The issue is typically caused by an out-of-date version of the file.
Known fixes provided by Microsoft
- Run Microsoft Update on the affected system and be sure to include all updates for Windows and Microsoft Office, or
- Access the latest fix directly from Microsoft, such as https://support.microsoft.com/en-us/kb/2881029. Please note these links will change and may not apply to all installations.
Manual Fix
- Back up your system and create a restore point.
- Back up the current version of
MSCOMCTL.OCX
found inC:\windows\syswow64
orC:\windows\system32
depending on your version of Windows. - Download the most recent version of
MSCOMCTL.OCX
Microsoft, or transfer it from a computer that already has the latest update. - Close Word.
- Right-click → Properties, and unblock the file as it will surely be blocked by Windows security features.
- Copy
MSCOMCTL.OCX
intoC:\windows\syswow64
overwriting the older version if you have a Windows 64-bit system. If the machine is 32-bit, the file is placed inC:\windows\system32
. - Run a
regsvr32 c:\windows\syswow64\mscomctl.ocx
command from the RUN or command line in a 64-bit system. On 32-bit systems the command isregsvr32 c:\windows\system32\mscomctl.ocx
. For additional documentation on using theregsvr
command, see Microsoft's documentation. - Start Word and test.
Other Causes
In rare cases, corrupt registry entries can present the same issues when the files are current. If that is the case, your system administrator should review registry entries and verify if existing entries match the currently installed version of MSCOMCTL.OCX
.
Windows Registry Editor Version 5.00
[HKEY_CLASSES_ROOT\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.2]
@="Microsoft Windows Common Controls 6.0 (SP6)"
[HKEY_CLASSES_ROOT\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.2]
[HKEY_CLASSES_ROOT\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.2\win32]
@="C:\\WINDOWS\\system32\\MSCOMCTL.OCX"
[HKEY_CLASSES_ROOT\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.2\FLAGS]
@="2"
[HKEY_CLASSES_ROOT\TypeLib\{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}\2.2\HELPDIR]
@=""
Attached File
For convenience, we've attached MSCOMCTL.OCX
version 2.2 to this article.
Comments
0 comments
Please sign in to leave a comment.