![mscomctl ocx error mscomctl ocx error](http://3.bp.blogspot.com/-IvVmjtxbIbg/TjtqP9XW_1I/AAAAAAAAACI/UDUMzt48YJE/s1600/s5.jpg)
Microsoft's Stefan Goßner describes a fix, which is distributed as part of KB 3114508, a patch for SharePoint 2013 that doesn't mention this list view problem.Component 'MSCOMCTL.
![mscomctl ocx error mscomctl ocx error](https://cdn.windowsreport.com/wp-content/uploads/2019/06/PowerShell-admin-2.png)
There was an apparently related problem reported with the SharePoint 2013 list view command. On his blog page, Myher gives detailed instructions for uninstalling the offending KBs.
#Mscomctl ocx error update
On machines w/o this update the Access app works fine.ĭarren Myher has a full description of the problem, which manifests as the error "Object doesn't support this property or method" in Blue Link Elite. It installs the new version of MSCOMCTL.OCX. Examination showed it happens when the progress bar control which resides in Mscomctl.ocx is addressed. quits saying "Error 91: Object variable or With block variable not set".
![mscomctl ocx error mscomctl ocx error](https://windowsjet.com/wp-content/uploads/2021/05/Solve-The-Error-Mscomctl.Ocx-On-Windows.png)
Poster wmenlonman describes a similar situation:Īncient Access 97 app. These additional controls are Microsoft TreeView Control 6.0 (SP6) and Microsoft ImageList Control 6 (SP6). I got the error message "Could not complete the operation due to error 800a0011". I've verified these were causing the problem by creating a blank form and trying to add one on. about the same time the updates occurred… Once past the initial "automation error" message I would get a Compile error: "Object library feature not supported," highlighting lines of codes associated with the additional controls. MSCOMCTL.OCX file version is 6.1.98.46, created & last modified but accessed at 3.33am yesterday (), i.e. Stackoverflow has a similar thread, where poster Thomas Basset says: We have the same issue, 100s of customers with 1000s of users. Why is the new mscomctl.ocx not backwards compatible (again!). Is there a way to make to newly saved addins work on the not up to date machines? The simple answer "update all machines" obviously does not work, because we are not in control of the machines of all our customers (500+). The up-to-date systems do run older Addins, but older systems cannot run the newly saved addins. This is the fourth time that Microsoft has screwed up an mscomctl.ocx update. This means we can never supply our customers with updated versions.
![mscomctl ocx error mscomctl ocx error](https://i.ytimg.com/vi/5dqjCBhxfHA/maxresdefault.jpg)
We have numerous customers that have a slow update policy (IT wants to test every update first for problems). Our systems are up-to-date and when we save our addin, it stops working for our customers. We use Treeviews from mscomctl.ocx and on systems that are not up-to-date, our addin gives errors: "could not load object because it is not available on this machine".
#Mscomctl ocx error software
Last week we received update MS16-004 and this caused problems in our software (VBA). On the Technet forum, poster ronald75 says: Of course, Microsoft hasn't come up with any warnings in the KB articles. It's not clear to me if those same templates throw errors when run on some machines with the new version of MSComctLib.ocx. It looks like the new version,, saves templates that don't work properly on machines with older versions of MSComctLib.ocx. The symptoms are many and varied, but all seem to be due to a problematic new version of the MSComctLib.ocx common control library for VB6 and VBA. The complaints I've seen center on the Office 2010 patch KB 2881029, Office 2013 patch KB 3039794, and Office 2016 patch KB 2920727, all running on Windows 7. 12, and weird Visual Basic 6, VBA, and SharePoint 2013 errors have followed in its wake.