Application Center 2000 may replicate unexpected files and directories

This article was previously published under Q304385
This article has been archived. It is offered "as is" and will no longer be updated.
Microsoft Application Center 2000 may replicate content that was not intended to be replicated. If the unintended content includes files that cannot be replicated for any reason, you may receive the following error message:

Event ID: 5064
Source: Application Center
Description: Could not send file
Event Type: Error

Synchronization could not send the file Path to the target server RemoteServer during the session ReplicationID and job ReplicationJobID. Status is Status StatusMessage.
Note Replace Path with a file that you intend to replicate.

For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
288626 Event ID: 5064 Replication Session SendFileFailed
Application Center 2000 tries to replicate the folders that are specified as a local path for all Web sites and virtual directories. If a Web site or a virtual directory is set to redirect, the local path will remain in the Microsoft Internet Information Services metabase and Application Center 2000 may replicate the contents that are located at the local path.
This problem was first corrected in Application Center 2000 Service Pack 2.
To resolve this problem, obtain the latest service pack for Application Center 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
815034 Application Center 2000 Service Pack 2 fix list
To work around this problem, change the local path of the Web site or the virtual directory to a local path that you can replicate.

You can identify and repair this problem with a metabase utility like Mdutil.exe. Mdutil.exe is located in the Support folder on the Application Center 2000 CD. Dump the metabase to a text file. This is an example command line command:
Note Replace DumpFilePath with the path of the text file that you want the metabase dumped into. You can search the text file for "VrPath", and then verify that the associated value is a folder that should be replicated.
More information

Steps to reproduce the behavior

  1. Create a new virtual directory that points to a valid folder on the hard disk like as C:\.
  2. Change the virtual directory to redirect to a URL. This action hides the original local path.
  3. Attempt a synchronization or a deployment in Application Center. Notice that Application Center tries to replicate the contents of the C:\ disk drive.
The metabase entry for a virtual directory may look similar to the following:
[/w3svc/1/Root/Sample] AccessPerm         : [IF]  (DWORD)  0x201={Read Script} DirectoryBrowsing  : [IF]  (DWORD)  0x4000003e={Date Time Size Extension LongDate LoadDefault} Win32Error         : [IS]  (DWORD)  0x0={0} AppIsolated        : [IW]  (DWORD)  0x2={2} KeyType            : [S]   (STRING) "IIsWebVirtualDir" VrPath             : [IF]  (STRING) "c:\" AppRoot            : [IF]  (STRING) "/LM/W3SVC/1/Root/Sample" 2102               : [IW]  (STRING) "Sample" HttpRedirect       : [IF]  (STRING) ""					
Note The VrPath property is the path that is recognized by Application Center as a path to replicate.

Article ID: 304385 - Last Review: 10/26/2013 09:45:00 - Revision: 2.0

  • Microsoft Application Center 2000 Standard Edition
  • kbnosurvey kbarchive kbprb KB304385