Microsoft KB Archive/321936

= A roaming user profile does not upload successfully, and Event ID 1000 is logged in the application log in Windows 2000 =

Article ID: 321936

Article Last Modified on 2/20/2007

-

APPLIES TO


 * Microsoft Windows 2000 Server
 * Microsoft Windows 2000 Professional Edition
 * Microsoft Windows 2000 Advanced Server
 * Microsoft Windows 2000 Datacenter Server

-



This article was previously published under Q321936





SYMPTOMS
When a client logs off from a Microsoft Windows 2000-based server, a roaming user profile may not upload successfully, and event 1000 may be logged in the application log. When you view the log by using Event Viewer, you may see an event that is similar to the following: Source: Userenv

Category: None

Type: Error

Event ID: 1000

Windows cannot copy file C:\Documents and Settings\TestUser\Favorites\Travel Planning\Traffic.url to location \\PROFILESERVER\Userdata\TestUser\Profile\Favorites\Travel Planning\Traffic.url. Contact your network administrator. DETAIL - The process cannot access the file because it is being used by another process.

If you have turned on Userenv logging, when this problem occurs, text that is similar to the following is logged in the Userenv log:

USERENV(9010.8bc8) 13:16:22:346 ReconcileFile: Failed to rename file <\\PROFILESERVER\Userdata\TestUser\Profile\Favorites\Travel Planning\prf146.tmp> to <\\PROFILESERVER\Userdata\TestUser\Profile\Favorites\Travel Planning\Traffic.url> with error = 32



CAUSE
This problem occurs because when the memory management system tries to rename the temporary file on the profile server to its intended name, a sharing violation occurs.

For caching and increased performance, the operating system may temporarily retain memory sections that describe a file. The redirector does not send a close operation to the target server until memory sections that describe the file are closed. In this scenario, a rename operation is issued against a file while the operating system is still caching section objects for the file. Because the close operation has not yet been sent, the file is still in use, and a sharing violation occurs.



Hotfix information
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.

Prerequisites
No prerequisites are required.

Restart requirement
You must restart your computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other hotfixes.

File information
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 -  09-Apr-2004  18:05   5.0.2195.6923   408,752   Mrxsmb.sys 09-Apr-2004 18:05   5.0.2195.6923   169,936   Rdbss.sys After this hotfix is applied, when the scenario that is described in the &quot;Cause&quot; section occurs, the redirector forcibly closes all memory sections that describe the problem file and then retries the operation. However, a related hotfix covers the case where a memory section is never closed because of a unique combination of low pool resources. Therefore, to resolve this possible cause of the problem, also apply the hotfix that is described in the following Microsoft Knowledge Base article:

839919 A logon stops responding in Windows Server 2000



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



MORE INFORMATION
Sometimes, the destination file server shows that the profile is still in use until the Terminal server is restarted. You can check to see if this is the case by typing the following command at a command prompt:

net files

The hotfix that is described in the &quot;Resolution&quot; section addresses the sharing violation that is mentioned in the &quot;Cause&quot; section. However, there are many other causes of roaming profile upload/download errors. For additional information about the profile copy process and about the problems that may occur when profiles are copied, click the following article number to view the article in the Microsoft Knowledge Base:

328607 Roaming profile accumulates extra .tmp files

