This project is read-only.

Troubleshooting: what to do when you can't get Zen4Sync to work


Overview

This page gives you hints on what to do when Zen4Sync does not seem to be working.
It presents all the tips that are known to work when trying to resolve Zen4Sync issues.

Troubleshooting

The following sections present ways of solving Zen4Sync issues.

Activate Debug log

All Zen4Sync components (Orchestrator, Test Server and Client) can log what they do in text files so that you can easily find where things start to go wrong.
The log files contain any .NET Exception that occurred while executing a Test Session.

Activate the Debug log is the first step to take when nothing seems to be working.

You can activate the Debug log for all the Zen4Sync components: Orchestrator, Test Server and Client.
The procedure is the same for each component, the only difference lies in the configuration file to edit.
Here is the detailed procedure for the Orchestrator:
  • Open the Orchestrator configuration file located under <Orchestrator Install Directory>\Zen4SyncOrchestratorHost.exe.config
  • Locate the following section in the file:
<appSettings>
    <!--
    Uncomment these two lines to enable debug log.
    Debug log can be useful if your Test Sessions refuse to work.
    -->
    <!--<add key="OrchestratorEnableDebugLog" value="true" />-->
    <!--<add key="OrchestratorDebugLogFilePath" value="Path/To/Logfile.log"/>-->
</appSettings>
  • Uncomment the two lines:
<add key="OrchestratorEnableDebugLog" value="true" />
<add key="OrchestratorDebugLogFilePath" value="Path/To/Logfile.log"/>
  • Make sure OrchestratorEnableDebugLog is set to true
  • Edit the OrchestratorDebugLogFilePath value to point to the log file:
<add key="OrchestratorDebugLogFilePath" value="C:\Zen4SyncOrchestrator\Log\OrchestratorDebugLog.log"/>
  • Note: The directory containing the log file must exists for the debug log to work. If it does not exist, no debug log will occur.
  • Save the configuration file and restart the Orchestrator Windows Service.

To activate the Debug log for the Test Server and the Client, follow the steps described above using the following properties:

Test Server Client
Configuration file <Test Server Install Directory>\Zen4SyncTestServerHost.exe.config <Test Server Install Directory>\Zen4SyncClient\Zen4SyncClient.exe.config
Key to activate the Debug log TestServerEnableDebugLog Zen4SyncClientEnableDebugLog
Key to specify the Debug log file TestServerDebugLogFilePath Zen4SyncClientDebugLogFilePath


Allow huge WCF data transmissions

When you launch Test Sessions involving hundreds of Clients, Zen4Sync Orchestrator needs to pass a large amount of data to the Test Servers involved in the Test Session.

If you don't properly configure WCF communications between Zen4Sync components, WCF will refuse to transmit such amount of data.

So you might need to update the WCF configuration of the Zen4Sync components so that they can transmit large amount of data to each other.

In particular, you might want to modify the value of the following WCF properties:
  • maxItemsInObjectGraph
  • maxReceivedMessageSize
  • maxBufferSize

The configuration files you need to edit are mentionned on the how to configure WCF communications between Zen4Sync components page.

Remember that you'll need to configure both sides of the WCF communication for these properties to take effect.

Last edited Jun 17, 2011 at 1:39 PM by Christophe_, version 8

Comments

No comments yet.