Microsoft KB Archive/842765

= FIX: When a new user logs on to a server, the Security.Config.cch file is not copied, and the logon may fail in the .NET Framework 1.0 =

Article ID: 842765

Article Last Modified on 6/1/2006

-

APPLIES TO


 * Microsoft .NET Framework 1.0

-





SYMPTOMS
When a new user logs on to a server that is running Microsoft Windows and that has the Microsoft .NET Framework 1.0 installed, the logon may fail. The user may receive an error message that is similar to the following:

Windows cannot copy file ...Documents and Settings\Default User\Application Data\Microsoft\CLR Security Config\v1.0.3705\security.config.cch.XXXX-XXX



RESOLUTION
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, 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

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 ---  10-Jun-2004  19:08  1.0.3705.508      200,704  Aspnet_isapi.dll 10-Jun-2004 19:08  1.0.3705.508       24,576  Aspnet_regiis.exe 10-Jun-2004 19:08  1.0.3705.508       28,672  Aspnet_wp.exe 10-Jun-2004 18:27  1.0.3705.508       69,632  Corperfmonext.dll 10-Jun-2004 18:26  1.0.3705.508      299,008  Mscorjit.dll 12-Jun-2004 00:26  1.0.3705.508    1,953,792  Mscorlib.dll 10-Jun-2004 18:27  1.0.3705.508    2,199,552  Mscorsvr.dll 10-Jun-2004 18:26  1.0.3705.508    2,265,088  Mscorwks.dll 10-Jun-2004 19:06  1.0.3705.508       20,480  Perfcounter.dll 12-Jun-2004 00:26  1.0.3705.508    1,179,648  System.data.dll 12-Jun-2004 00:26  1.0.3705.508    1,695,744  System.design.dll 12-Jun-2004 00:26  1.0.3705.508    1,175,552  System.dll 12-Jun-2004 00:26  1.0.3705.508      241,664  System.messaging.dll 12-Jun-2004 00:26  1.0.3705.508      311,296  System.runtime.remoting.dll 12-Jun-2004 00:26  1.0.3705.508      131,072  System.runtime.serialization.formatters.soap.dll 12-Jun-2004 00:26  1.0.3705.508    1,200,128  System.web.dll 12-Jun-2004 00:26  1.0.3705.508      507,904  System.web.services.dll 12-Jun-2004 00:26  1.0.3705.508    1,994,752  System.windows.forms.dll 10-Jun-2004 19:09  1.0.3705.508       57,344  System.windows.forms.tlb 12-Jun-2004 00:26  1.0.3705.508    1,302,528  System.xml.dll 12-Jun-2004 00:26  1.0.3705.508       32,768  Tlbimp.exe 12-Jun-2004 00:26  1.0.3705.508       65,536  Wsdl.exe



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

