Select the product you need help with
- Internet Explorer
- Windows Phone
- More products
The functionality of an add-in, an ActiveX control, or a COM add-in is reduced, or the functionality is blocked after you install Office 2003 Service Pack 3
Article ID: 938814 - View products that this article applies to.
Important This article contains information that shows you how to help lower security settings or how to turn off security features on a computer. You can make these changes to work around a specific problem. Before you make these changes, we recommend that you evaluate the risks that are associated with implementing this workaround in your particular environment. If you implement this workaround, take any appropriate additional steps to help protect the computer.
You install Microsoft Office 2003 Service Pack 3 (SP3). When you start an Office 2003 program, the functionality of an add-in, an ActiveX control, or a COM add-in is reduced. Or, the functionality is blocked in some scenarios.
The behavior of add-ins, ActiveX controls, and COM add-ins was changed in some scenarios in Office 2003 SP3 to improve the security of Office 2003 files.
Office 2003 SP3 performs a test for poorly written COM components that use the QueryInterface() method when an Office 2003 program is started. Most COM components will pass the test successfully. However, if a COM component fails the test, the functionality of some add-ins, ActiveX controls, or COM add-ins may be reduced. Or, the functionality may be blocked. The COM components may fail the test in scenarios in which the component provides an incorrect response to the QueryInterface() method.
To determine whether the behavior that you experience is because of this change in Office 2003 SP3, follow these steps:
To resolve this behavior in Office 2003 SP3, contact the provider of the add-in, the ActiveX control, or the COM add-in. The component provider should update the component so that implementations of the QueryInterface() method return only interface pointers for interfaces that are implemented by the component.
Warning This workaround may make a computer or a network more vulnerable to attack by malicious users or by malicious software such as viruses. We do not recommend this workaround but are providing this information so that you can implement this workaround at your own discretion. Use this workaround at your own risk.
Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/322756/ )How to back up and restore the registry in Windows
To work around this behavior in Office 2003 SP3 when a policy is used, an administrator can disable the feature completely. Or, an administrator can disable the feature for a specific CLSID.
To do this in the registry, use one of the following methods.
Note The values that are set in the following methods may affect other versions of Microsoft Office that are installed on the computer.
Method 1: Disable this feature completely
Method 2: Disable this feature for a specific CLSID
For more information about CLSID, visit the following Microsoft Web site:
http://msdn2.microsoft.com/en-us/library/ms691424.aspxFor more information about how to obtain the latest Office 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/870924/ )How to obtain the latest service pack for Office 2003
Article ID: 938814 - Last Review: October 31, 2007 - Revision: 1.8