The information in this article applies to:
IMPORTANT: This article contains information about editing the registry. Before you edit the registry, make sure you understand how to restore it if a problem occurs. For information on how to do this, view the "Restoring the Registry" online Help topic in Regedit.exe or the "Restoring a Registry Key" online Help topic in Regedt32.exe. SYMPTOMS
When you attempt to start an application by opening an associated document,
the application fails to start and you receive the following error message:
This error occurs when there is a System Policy in effect that enables the item marked "Run only allowed Windows applications." This error is expected behavior if your application's executable is not in the List of allowed applications dialog box. However, in this case, the application is restricted even though it is included in this list. CAUSE
The shell restriction implemented by the "Run only allowed Windows
applications" policy does not correctly parse file associations when the
executable path contains a space.
RESOLUTIONUse one or more of the following methods to resolve this problem: Method 1To resolve this problem on computers that have Internet Explorer 4.0 or earlier or that have Internet Explorer 4.01 or later installed but not the Desktop Update Component (Active Desktop), obtain the latest service pack for Windows NT version 4.0.To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, please see the following article in the Microsoft Knowledge Base: Q152734 How to Obtain the Latest Windows NT 4.0 Service Pack NOTE: Internet Explorer 4.0 with the Desktop Update Component, ships with its own version of Shell32.dll. Installing this fix may cause Internet Explorer not to function correctly. Method 2Install Internet Explorer 4.01 SP1 and select the Desktop Update Component.Method 3On systems running the earlier version of Internet Explorer 4.0 or not running Internet Explorer at all, you may be able to work around this problem by either surrounding the entire association executable path with quotes, or by altering the executable path into its equivalent 8.3 format. To do this:
STATUSMicrosoft has confirmed this to be a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Keywords : NT4SP4Fix kbbug4.00 kbfix4.00.sp4 NTSrvWkst |
Last Reviewed: April 10, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |