Article ID: 837214 - Last Review: April 7, 2006 - Revision: 2.1 FIX: When you define a custom security zone in Internet Explorer and you try to use the custom zone, the .NET Framework 1.1 may failSYMPTOMSWhen you define a custom security zone in Microsoft Internet Explorer and you try to use the custom zone, the Microsoft .NET Framework 1.1 may fail. You receive the following error message: Illegal security permission zone specified RESOLUTIONA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next hotfix that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: http://support.microsoft.com/contactus/?ws=support
(http://support.microsoft.com/contactus/?ws=support)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.The English version of this fix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel. Date Time Version Size File name -------------------------------------------------------------- 27-Feb-2004 00:16 1.1.4322.1005 77,824 Corperfmonext.dll 27-Feb-2004 00:15 1.1.4322.1005 282,624 Fusion.dll 27-Feb-2004 17:57 1.1.4322.1005 86,016 Mscorie.dll 27-Feb-2004 00:15 1.1.4322.1005 311,296 Mscorjit.dll 27-Feb-2004 00:16 1.1.4322.1005 102,400 Mscorld.dll 27-Feb-2004 00:15 1.1.4322.1005 2,093,056 Mscorlib.dll 27-Feb-2004 00:15 1.1.4322.1005 2,498,560 Mscorsvr.dll 27-Feb-2004 00:15 1.1.4322.1005 2,490,368 Mscorwks.dll 18-Jan-2004 05:55 1.0.3705.0 106,496 Netfxupdate.exe 18-Jan-2004 05:55 1.1.4322.573 102,400 Setregni.exe 18-Jan-2004 05:55 1.1.4322.573 118,784 Togac.exe STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. REFERENCES
For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684
(http://support.microsoft.com/kb/824684/
)
Description of the standard terminology that is used to describe Microsoft software updates
| Article Translations
|
Back to the top
