If a non-transacted framed mode replication temporarily loses its network connection, the file that was being replicated during the connection loss may get corrupted. If this occurs, the publishing service will place a lock on the file, which will remain until the service has been stopped. The corruption will appear in the form of null characters that start at the location of the frame that was being transmitted at the time of the lost connection and continue to the end of the file.

Back to the top

To resolve this problem, apply the latest Site Server 3.0 service pack.

To work around this problem, disable framing and/or enable transactions. However, disabling framing is only recommended if your network connections are good and only rarely experience failures (that is rebooting routers, and so on).

Back to the top

Microsoft has confirmed this to be a problem in Site Server version 3.0. This problem was corrected in the latest Microsoft Site Server version 3.0 U.S. Service Pack. For information on obtaining the service pack, query on the following word in the Microsoft Knowledge Base (without the spaces):

Back to the top

This condition only occurs when you use the combination of framing and no transactions. You can determine if you are using framing by reviewing the status of the "Turn off framing for local deployment" option on the Advanced tab of the Project Properties page ON THE ORIGINATING SERVER. If the box is unchecked, you are running with framing enabled.

To check if you are running without transactions, view the "Enable rollback and transaction" option on the Advanced tab of your Server Properties page ON THE SERVER WITH THE CORRUPTION. If this is unchecked, then you are running with transactions disabled.

Back to the top