Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/170551

From BetaArchive Wiki

Article ID: 170551

Article Last Modified on 10/20/2003



APPLIES TO

  • Microsoft Office 97 Developer Edition
  • Microsoft Access Developer's Toolkit 1.1



This article was previously published under Q170551

Advanced: Requires expert coding, interoperability, and multiuser skills.


SYMPTOMS

When you start Microsoft Replication Manager, you may receive the following error message:

Sharing Violation while attempting to open log file <path to log file> in Deny Write mode.

This is followed by the following error, depending on which version you are using.

In Microsoft Replication Manager 3.5

Microsoft Replication Manager can't start the Synchronizer. Without the Synchronizer running, no synchronization of data can occur.

Do you want to work without the Synchronizer?

Synchronizer could not be initialized.

In Microsoft Replication Manager 3.0

Microsoft Replication Manager can't start the Transporter. Without the Transporter running, no synchronization of data can occur.

Do you want to work without the Transporter?

Transport could not be initialized.

CAUSE

You are trying to run Transporter and Synchronizer at the same time, and both are configured to use the same log file.

RESOLUTION

Reconfigure either Transporter or Synchronizer to use a different log file.

STATUS

Microsoft has confirmed this to be a problem in Microsoft Access Developer's Toolkit 7.0 and Microsoft Office 97 Developer Edition Tools.

MORE INFORMATION

When Synchronizer and Transporter start, they attempt to open their log files for write access, and deny write access to other applications. If Synchronizer and Transporter are configured to use the same log file, the first application started can successfully access the log file for this mode. However, this prevents the second application from accessing the file in the same mode, and an error occurs during startup.

Steps to Reproduce Problem

  1. Start Microsoft Replication Manager 3.0.
  2. On the Tools menu, click Configure Microsoft Replication Manager.
  3. Add a managed folder if one is not in the list, and then click Next. The folder you select does not need to contain any replicas.
  4. Select a shared network folder for indirect synchronizations, and then click Next.
  5. In the "Path to Log File" box, type:

    C:\My Documents\Transporter.log

    Click Finish. Transporter will start on your computer.
  6. On the File menu, click Exit and Stop Transporter.
  7. Start Microsoft Replication Manager 3.5.
  8. On the Tools menu, click Configure Microsoft Replication Manager.
  9. Click Next.
  10. Click to select the Support Indirect Synchronization check box, and then click Next.
  11. Click Next.
  12. Select a shared Network folder for indirect synchronizations, and then click Next.
  13. Click No to indicate that your computer is not an Internet server, and then click Next.
  14. In the "Path to Log File" box, type:

    C:\My Documents\Transporter.log

    Note that this is the same path selected for the log file in step 5.
  15. Click Finish. Synchronizer will start on your computer.
  16. Quit Microsoft Replication Manager 3.5. Do not stop Synchronizer.
  17. Start Microsoft Replication Manager 3.0. Note that you receive the errors described in the "Symptoms" section.


REFERENCES

For more information about the Synchronizer log file, search the Microsoft Replication Manager Help Index for "log, Synchronizer."


Additional query words: can t

Keywords: kbbug kbother KB170551