Article ID: 174872
Article Last Modified on 2/20/2004
APPLIES TO
- Microsoft Commercial Internet System 1.0 Service Pack 2
- Microsoft Site Server 2.0 Standard Edition
This article was previously published under Q174872
SYMPTOMS
Microsoft Content Replication System (CRS) can fail to properly replicate if there is a network error or if the destination file is locked. The Windows NT Application Event Log displays Error ID 15060. The CRS log displays this warning:
TransmitFile failed on file * of size x The network session timed out on
a receive or send operation.
The Windows NT Application Event Log will show an Error Id 15119. The CRS log will show this warning:
Moving *.FIL to *, File *.FIL was found but an error was returned anyway
The process cannot access the file because it is being used by another
process.
This problem only occurs when CRS is configured to use Transaction Mode and the size of the file is less than 64 KB.
WORKAROUND
To work around this problem, do not use Frame Mode. Frame mode was designed for use on unreliable wide area network (WAN) links. If all the servers participating in a project are connected by a local area network (LAN), then you should use the /fastmode flag when creating the project. This can also be done in the Web-based CRS Administration in the Project Options page. You need to select the "Turn off framing for local replications" check box.
STATUS
Microsoft has confirmed this to be a problem in Microsoft Commercial Internet System version 1.0 Service Pack 1 (SP1) and Microsoft Site Server version 2.0. This problem has been corrected in the latest U.S. Service Pack for Microsoft Site Server 2.0. For information on obtaining the Service Pack, query on the following word in the Microsoft Knowledge Base (without the spaces):
S E R V P A C K
Additional query words: sp 1
Keywords: kbbug kbfix kbqfe KB174872
