You are currently offline, waiting for your internet to reconnect

FIX: Temporary files are not deleted after you connect to a server that is running Windows SharePoint Services or SharePoint Portal Server 2003

Support for Office 2003 has ended

Microsoft ended support for Office 2003 on April 8, 2014. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
When you use Microsoft Windows SharePoint Services or Microsoft Office SharePoint Portal Server 2003 and you connect as an anonymous user or as any account with permissions that are not sufficient, you may notice that many temporary files are created in the %temp% folder and are never deleted. This causes the server to eventually run out of disk space. This may cause performance to decrease.
This is caused by an impersonation problem in the Microsoft .NET Framework 1.1 Code Document Object Model (CodeDOM). SharePoint uses the XML Serializer in the .NET Framework. The XML Serializer internally uses the .NET Framework CodeDOM, and the CodeDOM creates temporary files in the %temp% folder. The CodeDOM uses impersonation to impersonate an account that has sufficient access to create the temporary files. After compilation, CodeDOM reverses the impersonation and then tries to delete the temporary files. When you log on to the SharePoint Portal Server as an anonymous user, this user account does not have access to delete the temporary files.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft .NET Framework 1.1 Service Pack that contains this hotfix.

To resolve this problem immediately, download the hotfix by clicking the download link later in this article or contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: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 following files are available for download from the Microsoft Download Center:
DownloadDownload the 824629 hotfix for Microsoft Windows Server 2003 package now.

DownloadDownload the 824629 hotfix for all other versions of Microsoft Windows package now.
Release Date: September 3, 2003

For additional information about how to download Microsoft Support files, click the following article number to view the article in the Microsoft Knowledge Base:
119591 How to Obtain Microsoft Support Files from Online Services
Microsoft scanned this file for viruses. Microsoft used the most current virus-detection software that was available on the date that the file was posted. The file is stored on security-enhanced servers that help to prevent any unauthorized changes to the file.
The English version of this hotfix has the file attributes (or later) 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                    Platform   ------------------------------------------------------------------------------------   30-Jul-2003  00:52  1.1.4322.929      253,952  Aspnet_isapi.dll             x86   30-Jul-2003  00:52  1.1.4322.929       20,480  Aspnet_regiis.exe            x86   30-Jul-2003  00:52  1.1.4322.929       32,768  Aspnet_wp.exe                x86   28-Apr-1999  01:12            32,768  Installpersistsqlstate.sql   15-May-2003  23:49                     34,150  Installsqlstate.sql   30-Jul-2003  00:07  1.1.4322.929       94,208  Perfcounter.dll              x86   31-Jul-2003  04:33  1.1.4322.929    1,216,512  System.dll                   x86   31-Jul-2003  04:34  1.1.4322.929      323,584  System.runtime.remoting.dll  x86   31-Jul-2003  04:31  1.1.4322.929    1,253,376  System.web.dll               x86   31-Jul-2003  04:33  1.1.4322.929      819,200        x86   31-Jul-2003  04:32  1.1.4322.929      569,344      x86   31-Jul-2003  04:32  1.1.4322.929    1,335,296  System.xml.dll               x86   30-Jul-2003  00:47                     14,472  Webuivalidation.js

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
The symptoms that are described in this article are most frequently associated with Windows SharePoint Services or with SharePoint Portal Server 2003. Any other applications or services that use an account with permissions that are not sufficient and .NET Framework 1.1 XML Serializer may also exhibit this behavior.

When you install this hotfix on a computer that is running Microsoft Windows Server 2003, the IISAdmin service will start. This does not change the default behavior of the service. Therefore, if the IISAdmin service is set to manual, IISAdmin will not restart when the server is reset.

Article ID: 824629 - Last Review: 12/08/2015 03:49:18 - Revision: 4.7

Microsoft Office SharePoint Portal Server 2003, Microsoft .NET Framework 1.1, Microsoft Windows SharePoint Services 2.0

  • kbnosurvey kbarchive kbdownload kbfix KB824629