Access 2010-使用TreeView (MSComctlLib.TreeCtrl.2) 在windows 安全補丁更新之后, 使用就出現錯誤了

復制 MSCOMCTL.OCX 到 syswow64下再注冊也不行

建議 使用版本:6.1.98.34

相關資料:http://www.microsoft.com/zh-cn/security/pc-security/bulletins/201208.aspx

1.先使用這個方法

regsvr32 /u mscomctl.ocx

regsvr32 mscomctl.ocx

針對 Windows 7 or 2008 - 運行 cmd.exe "使用管理員身份"

for 32bit Windows systems: regsvr32 c:/windows/system32/mscomctl.ocx

for 64bit Windows systems: regsvr32 c:/windows/syswow64/mscomctl.ocx

2. 國外的解決辦法如下: (大部分情況下可行)

reg delete hkcr/typelib/{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}/2.0 /f

if exist %systemroot%/SysWOW64/cscript.exe goto 64

%systemroot%/system32/regsvr32 /u mscomctl.ocx

%systemroot%/system32/regsvr32 mscomctl.ocx

exit

:64

%systemroot%/sysWOW64/regsvr32 /u mscomctl.ocx

%systemroot%/sysWOW64

/regsvr32 mscomctl.ocxexit

3. 微軟官方的解決辦法

http://support.microsoft.com/kb/2597986解決微軟安全補丁更新后的問題

http://go.microsoft.com/fwlink/?LinkId=263512下載這個文件來修復

或 下載 : http://www.microsoft.com/zh-cn/download/details.aspx?id=36841

. 它會下載 mscomctlocx2010-kb2687503-fullfile-x86-glb.exe

運行這個程序將會自動修復這個問題,并且不需要重啟

如果你的Mscomctl.ocx控件的版本是 6.1.98.33 或6.1.98.34 才需要運行它

相關鏈接:http://support.microsoft.com/kb/2748410

附加信息:

Microsoft 發布了一個針對 Microsoft Office 2010 32 位版本 的更新。此更新提供 Microsoft Office 2010 32 位版本 的最新修復。此外，此更新包含穩定性和性能改進。

4. 微軟針對這個Treeview(Mscomctl.ocx)的官方解決辦法(http://support.microsoft.com/kb/2687441)

基于 Windows Common Control 的嵌入式 ActiveX 控件可能無法在預先存在的 Office 文檔中、第三方加載項中，以及當您在開發人員模式下插入新控件時加載。

推薦的解決方案

現在可下載安裝控件并修復控件注冊的修復程序。 我們建議您安裝此修復程序來解決問題。您可以在此下載修復程序。

注意

在安裝此修復程序來解決問題之前，您不必安裝安全更新 2687441。

注意

如果您不安裝該修復程序并選擇了其他分辨率，則當您為 Office 安裝在 MS12-060 之后發布的更新時可能還會遇到相同的問題。

其他解決方案

如果愿意，您可以使用“Fix it”解決方案來讓我們為您解決此問題。 為此，請轉到“Fix it for me”部分。

解決方法

Regsvr32

要解決此問題，您可以使用注冊表編輯器刪除相關注冊表項。 然后使用命令注冊 Mscomctl.ocx 文件。 您也可以創建批處理文件使其自動化。

手動刪除相關注冊表項

重要說明

此部分、方法或任務包含有關如何修改注冊表的步驟。但是，注冊表修改不當可能會出現嚴重問題。因此，請一定嚴格按照下列步驟操作。為了獲得進一步保護，請在修改注冊表之前對其進行備份。這樣就可以在出現問題時還原注冊表。有關如何備份和還原注冊表的更多信息，請單擊下面的文章編號，以查看 Microsoft 知識庫中相應的文章：

322756如何在 Windows 中備份和還原注冊表

要刪除此注冊表項，請執行下列步驟：

依次單擊“開始”、“運行”，在“打開”框中鍵入regedit，然后單擊“確定”。

找到并單擊注冊表中的以下子項：

HKEY_CLASSES_ROOT/TypeLib/{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}/2.0

在“編輯”菜單上，單擊“刪除”，然后單擊“是”。

退出注冊表編輯器，然后重新啟動計算機。

手動注冊 Mscomctl.ocx 文件

注意

您必須使用管理員權限從提升的命令提示符處運行命令。為此，請執行下列步驟：

cmd

單擊“開始”，鍵入。

右鍵單擊“cmd”圖標，然后單擊“以管理員身份運行”。

根據您使用的操作系統，鍵入下面的一個命令，然后按 Enter：

對于 64 位操作系統，請鍵入以下命令：

Regsvr32 "C:/Windows/SysWOW64/MSCOMCTL.OCX"

對于 32 位操作系統，請鍵入以下命令：

Regsvr32 "C:/Windows/System32/MSCOMCTL.OCX"

創建批處理文件以刪除相關注冊表項，并注冊 Mscomctl.ocx 文件

您可以創建批處理文件以刪除注冊表項，并注冊 Mscomctl.ocx 文件。要創建批處理文件，請將以下文本復制到文本文件中，然后使用文件擴展名“.bat”保存該文本文件。(下例檢測操作系統是 32 位還是 64 位，然后根據檢測結果運行相應的命令。)

reg delete hkcr/typelib/{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}/2.0 /f

if exist %systemroot%/SysWOW64/cscript.exe goto 64

%systemroot%/system32/regsvr32 /u mscomctl.ocx

%systemroot%/system32/regsvr32 mscomctl.ocx

exit

:64

%systemroot%/sysWOW64/regsvr32 /u mscomctl.ocx

%systemroot%/sysWOW64/regsvr32 mscomctl.ocx

exit

regsvr32

要自動運行命令，請將命令行開關添加到前一個示例中的每個命令。例如：

%systemroot%/system32/regsvr32 /u mscomctl.ocx /s

注意

您必須以管理員身份運行批處理文件：

要在 Windows Vista、Windows Server 2008、Windows 7 或 Windows Server 2008 R2 中執行此操作，請右鍵單擊批處理文件，然后單擊“以管理員身份運行”。

以管理員身份運行

要在 Windows XP 或 Windows Server 2003 中執行此操作，請按住 Shift 鍵，右鍵單擊批處理文件，然后單擊

有關如何以管理員身份啟動程序的更多信息，請轉到以下 Microsoft 網頁：

http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/windows_security_runas.mspx?mfr=true

有關如何注冊 ActiveX 控件的詳細信息，請單擊下面的文章編號，以查看 Microsoft 知識庫中相應的文章：

2746232(頁面可能為英文) 如何手動注冊 ActiveX 控件 (.ocx)

7.FMS提供的解決辦法 原文: http://www.fmsinc.com/MicrosoftAccess/Controls/mscomctl/?goback=%2Egde_937037_member_154050465#%21

修復 Microsoft Windows Common Control Library (MSCOMCTL.OCX) 安裝更新導致的問題

Microsoft Office 的新的安全更新

在2012年8月14日,微軟發布了一個安裝更新補丁,里面包含了Windows Common Control MSCOMCTL.OCX的更新:

注意這個控件的日期是6月份,但它是包含在這個8月份的安全補丁包中.

微軟針對這個補丁的相關知識庫(KB)

KB2597986- for Office 2010

KB2687441- for Office 2007

KB2687323- for Office 2003

微軟版本

以下版本:

Windows XP, Vista, Windows 7 (32/64 bit)

Windows Server 2003, 2008, 2008 R2

使用這個更新可能導致的問題

After installing the update, the Windows Common Control Library does not work. The issue seems to stem around a defective installation or registration of the OCX file. This update causes problems with existing Microsoft Access, VB6 and other applications using common controls such as the Treeview and Listbox controls.

The symptoms are rather odd. It's not as if the control is completely missing or not registered. The control exists but does not behave correctly as events are not firing correctly. For instance, the Treeview control don't issue NodeClick events, so any code that expects the expansion of a node to display or load more data fails. It took us a while to discover that a change in this control caused this problem.

In other cases, users are reporting that Microsoft Access locks up and crashes. People are also reporting problems with this in Visual Basic 6 (VB6) applications. Here are additional reports ofissuesassociated with this patch.

Impact on Total Access Analyzer

This impacts our Total Access Analyzer product which displays the results of your Microsoft Access database documentation with the Treeview control. This error appears:

Error 459 - Object or class does not support the set of events, Procedure clsFrmExplorer_TAA.InitForm

If your PC received the security update and you're using the Microsoft Access 2010, 2007, 2003, 2002, or 2000 version of Total Access Analyzer, the Treeview control in our Database Explorer view no longer functions properly.

Known Issues as Reported by Microsoft

Microsoft has acknowledged problems with their security update that is causing these problems. The issue is caused by a registration of the updated MSCOMCTL.OCX file. Microsoft has released a Knowledgebase article 2687441 addressing this problem entitled:MS12-060: Description of the security update for 2007 Office system: August 14, 2012.

In that article, they mention the known issues with the security update:

Windows Common Control-based embedded ActiveX controls may fail to load within pre-existing office documents, within third-party applications, and when you insert new controls in developer mode. For example, depending on your operating system, you can type the either of the following commands at an elevated command prompt, and then press Enter:

For 64-bit operating systems, type the following: Regsvr32 "C:/Windows/SysWOW64/MSCOMCTL.OCX"

For 32-bit operating systems, type the following: Regsvr32 "C:/Windows/System32/MSCOMCTL.OCX"

The article goes into details about unregistering the control and re-registering it using a batch file calling REGEDIT.EXE.

Microsoft's Suggested Solution Fails

In our internal testing, we've discovered that the recommended steps don't work in most cases. Just unregistering and re-registering the control doesn't solve the problem. We tried adding a reboot between steps, but that didn't help either. The steps below work consistently. An technical explanation why is given at the end.

Our Steps for Fixing the Registration of the Windows Common Control

While there seems to be nothing physically wrong with the new OCX, we need to register another version to reset it. Here are the steps we discovered to manually repair this issue reliably and consistently:

Unregister the new MSCOMCTL.OCX and make a backup of it

Install and register an old (legacy) version of the MSCOMCTL.OCX file

Replace the legacy control with the new one

Re-register the new control

#FormatImgID_0#Windows Command Prompt and Security Permissions

You need Administrator rights to make registry changes. Depending on your operating system and Windows login rights, you may not be allowed to do this.

From your Windows Start button under, All Programs, Accessories, launch the Command Prompt by right clicking on it and choosing "Run as administrator".

You can then copy the Regsvr32.exe command lines described below into the dialog.

32 Bit Windows

Unregister the new OCX file. Open an instance of the Windows Command Prompt, paste the following command, and press : Regsvr32.exe /u C:/Windows/System32/MSCOMCTL.OCX

Make a backup of the OCX file C:/Windows/System32/MSCOMCTL.OCX to C:/Windows/System32/MSCOMCTL.bak

Copy a legacy version of the MSCOMCTL.OCX file to your C:/Windows/System32 folder. For your convenience, a zipped copy from 2011 ishere.

Register this legacy OCX file with the following command: Regsvr32.exe C:/Windows/System32/MSCOMCTL.OCX

Unregister this legacy version of the OCX file: Regsvr32.exe /u C:/Windows/System32/MSCOMCTL.OCX

Delete the legacy OCX file: C:/Windows/System32/MSCOMCTL.OCX

Rename the new OCX file we renamed in step 2, back to its original name: C:/Windows/System32/MSCOMCTL.bak to C:/Windows/System32/MSCOMCTL.OCX

Re-register the new version of the OCX file. Paste the following command and press : Regsvr32.exe C:/Windows/System32/MSCOMCTL.OCX

Reboot the computer.

Open Microsoft Access and then retest the control. It should be working at this point.

64 bit Windows

The 64-bit steps are identical to the 32 bit version except the folder is SYSWOW64 rather than SYSTEM32:

Unregister the new OCX file. Open an instance of the Windows Command Prompt, paste the following command, and press : Regsvr32.exe /u C:/Windows/SYSWOW64/MSCOMCTL.OCX

Make a backup of the OCX file C:/Windows/SYSWOW64/MSCOMCTL.OCX to C:/Windows/SYSWOW64/MSCOMCTL.bak

Copy a legacy version of the MSCOMCTL.OCX file to your C:/Windows/SYSWOW64 folder. For your convenience, a zipped copy from 2011 ishere.

Register this legacy OCX file with the following command: Regsvr32.exe C:/Windows/SYSWOW64/MSCOMCTL.OCX

Unregister this legacy version of the OCX file: Regsvr32.exe /u C:/Windows/SYSWOW64/MSCOMCTL.OCX

Delete the legacy OCX file: C:/Windows/SYSWOW64/MSCOMCTL.OCX

Rename the new OCX file we renamed in step 2, back to its original name: C:/Windows/SYSWOW64/MSCOMCTL.bak to C:/Windows/SYSWOW64/MSCOMCTL.OCX

Re-register the new version of the OCX file. Paste the following command and press : Regsvr32.exe C:/Windows/SYSWOW64/MSCOMCTL.OCX

Reboot the computer.

Open Microsoft Access and then retest the control. It should be working at this point.

Why This Solution Works

The reason why Microsoft's recommendation to un-register and re-register the new MSCOMCTL.OCX Common Control fails is because it doesn't overwrite the legacy control's registry on the machine. Industry colleague, Andrew Rohm provides this nice explanation:

The problem is that the update leaves some old 2.0 Version entries in the Registry. The previous MSCOMCTL.OCX carried the version number 2.0 (the *File* Version is 6.something but in the registry it's known as Version 2.0).

The new file version is 6.1.98.34 but Version 2.1 in the registry. Here we are talking about registry entry: HKEY_CLASSES_ROOT/TypeLib/{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}

The patch installs the new version but leaves a part of the old registry settings.

By installing and uninstalling the legacy control, it cleans up the 2.0 registry so the new version is installed properly. The offending registry that needs to be deleted is:

HKEY_CLASSES_ROOT/TypeLib/{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}/2.0

We have the same problem. In our Add-In, we were able to trace the problem to a declaration of a variable as Excel.Application. The reference to this object is in the Excel.exe file, so it is very unclear as to which files got messed up.

The machines that have this problem were all updated early this morning (15 Aug 2012) with the following updates (sorry for not posting links, as a new user, I'm limited to only two per post):

Security Update for Microsoft Office 2007 suites (KB2596615)

Security Update for Microsoft Office 2007 suites (KB2596754)

Security Update for Microsoft Office 2007 suites (KB2596856)

Security Update for Microsoft Office 2007 suites (KB2687441)

Update for Microsoft Office Outlook 2007 Junk Email Filter (KB2687400)

Windows Malicious Software Removal Tool x64 - August 2012 (KB890830)

At present, we have not found any information on the MSDN site that could clear this up. We're still trying to isolate this down further.

Same issue here today after performing the update for Office 2007 Excel. Oddly, one system had no issues despite the update - the newest system. So after some inspection, I noticed this trouble-free system had different version of MSCOMCTL.OCX in windows/sysWOW64 then others. Here are the details of this activeX Size: 1,070,152 bytes created: 6/3/2012 modified: 6/6/2012 product version: 6.01.9834 So I copied this to the trouble one and it did the trick.

Also, you might want to check if these application extensions are present in windows/sysWOW64 or windows/system32 for 32-bit system FM20.DLL (Modified Date: 7/7/2011, version 12.0.6604.1000, 1.13MB) FM20ENU.DLL (Modified Date: 10/24/2008, version 12.0.6413.1000, 32.3KB) Not sure where you can download these. I cannibalized them from other systems. 5. 另一個有效的解決辦法

This article applies toWord, Access, Excel and PowerPoint. MS12-060 is a security update that was released Tuesday, August 14, 2012. This update replaced MS12-027. You may now be seeing one of the following errors:

"Unspecified Automation Error" when running or compiling your Microsoft Office VBA code after installing MS12-060;

or

"Errors were detected while saving 'filename.xlsm'. Microsoft Office Excel may be able to save the file by removing or repairing some features. To make the repairs in a new file, click Continue. To cancel saving the file, click Cancel."

clicking continue you will see "Document failed to save" or similar error.

Update - 9/26/2012. Seethis blog postfor the latest update.

Fixit Available

There is a fixit available for this problem:

Office 2010 w SP1 -http://support.microsoft.com/kb/2597986

Office 2007 w SP2 or SP3 -http://support.microsoft.com/kb/2687441

Office 2003 w SP3 or Office 2003 Web Components w SP3 -http://support.microsoft.com/kb/2687323

Steps to fix the problem manually

Alternatively, the manual fix for this problem is to re-register MSCOMCTL.OCX. To do this, follow these steps:

1. Open anadministrative-level command prompt. The command prompt MUST be on the administrative level for this to work. Click START, and type RUN in the run command line. On Windows Vista and Windows 7 you will see CMD.EXE appear in the quick searchlist. Right click CMD.EXE and left click Run As Administrator. A black command prompt opens. On Windows XP, there is no built-in run-as-admin, but you can use the run as menu option (or runas command line) to execute an admin command from a Limited User Account.

2. If on a 64-bit machine, type the following:

regsvr32.exe /u C:/Windows/SysWOW64/MSCOMCTL.OCX Hit ENTER

then type

regsvr32.exe C:/Windows/SysWOW64/MSCOMCTL.OCX

If on a 32-bit machine, type the following:

regsvr32.exe /u C:/Windows/System32/MSCOMCTL.OCX

hit ENTER

then type

regsvr32.exe C:/Windows/System32/MSCOMCTL.OCX

Your Office program should work again after doing this.

(Updated) 3. NOTE: The following step is done at your own risk. Microsoft doesn't know about any side effects to deleting this registry key. In cases where the re-registration doesn't work and you still get the error, you will need to open the registry editor (START > RUN > REGEDIT) and find andDELETE the following registry key:

HKEY_CLASSES_ROOT/TypeLib/{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}/2.0

to

HKEY_CLASSES_ROOT/TypeLib/{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}/2.0OLD

We've heard reports that renaming the key doesn't work. The key has to be deleted.

Afterward, follow steps 1 and 2 to unregister and re-register MSCOMCTL.OCX

Automating a Solution for Multiple Machines

You can also include the unregistration and re-registration in a batch file that is pushed out to multiple machines. Here is a sample script which should do the job:

reg delete hkcr/typelib/{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}/2.0 /f

if exist %systemroot%/SysWOW64/cscript.exe goto 64

%systemroot%/system32/regsvr32 /u mscomctl.ocx %systemroot%/system32/regsvr32 mscomctl.ocx exit

:64 %systemroot%/sysWOW64/regsvr32 /u mscomctl.ocx %systemroot%/sysWOW64/regsvr32 mscomctl.ocx exit

If you require a batch file that runssilently, use the following:

reg delete hkcr/typelib/{831FDD16-0C5C-11D2-A9FC-0000F8754DA1}/2.0 /f

if exist %systemroot%/SysWOW64/cscript.exe goto 64 %systemroot%/system32/regsvr32 /u mscomctl.ocx /s %systemroot%/system32/regsvr32 mscomctl.ocx /s exit

:64 %systemroot%/sysWOW64/regsvr32 /u mscomctl.ocx /s %systemroot%/sysWOW64/regsvr32 mscomctl.ocx /s exit

Alternate Solution

See

http://blogs.technet.com/b/office_sustained_engineering/archive/2012/08/24/ms12-060-not-initiating-with-certain-controls.aspx