Microsoft KB Archive/818464

= &quot;Setup Cannot Copy the File &quot; Error Messages Occur When You Perform an In-Place Upgrade of Windows Server 2003 =

Article ID: 818464

Article Last Modified on 12/3/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Small Business Server 2003 Standard Edition
 * Microsoft Windows Small Business Server 2003 Premium Edition

-



,



SYMPTOMS
When you perform an in-place upgrade of Windows Server 2003, you receive the following error messages during the Graphical User Interface (GUI)-mode portion of Setup:

Setup cannot copy the file

You receive this error message for each file that Setup cannot copy. The following file names may be referenced in this error message:

Cmprops.dl_

Licwmi.dl_

Mmfutil.dl_

Servereps.dl_

Additionally, when you view the Scesetup.log file in the %Windir%\Security folder on the hard disk, you may receive the following error messages:

Error 1208: An extended error has occurred.

Error opening \Security\Database\secedit.sdb.

-and-

Error 1208: An extended error has occurred.

Errors occurred.

-and-

Error 1208: An extended error has occurred.

Error creating database.



CAUSE
This problem occurs because the security database, Secedit.sdb, is damaged. The security database may be damaged in situations where the computer is shut down incorrectly.



RESOLUTION
To resolve this problem, use the Esentutl.exe command-line utility to repair the database, and then run Windows Server 2003 Setup. To repair the database by using Esentutl.exe:  Click Start, and then click Run. In the Open box, type the following line, and then press ENTER:

esentutl /p %windir%\security\database\secedit.sdb

 Click Start, and then click Run. In the Open box, type the following line, and then press ENTER:

%windir%\security

 Right-click the Edb.log file and the Edb0000 .log file, and then click Delete. Click OK when you are prompted to confirm the deletion.</li></ol>

Note When you perform this procedure, some data loss may result. For example, cached local security policy settings may be lost.

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Keywords: kbprb KB818464

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.