Troubleshooting and Logging

Introduction

The troubleshooting guide offers detailed instructions for addressing errors that may occur during the installation of the Rundown Broker.

Pre-Troubleshooting Checks

Setup Log File

By default, the https://davidsystems.atlassian.net/wiki/x/CYDpNw doesn't write log files. Use the following procedure to create a setup log file:

• Open a console window with elevated rights: Press Windows+R, type cmd, press Ctrl+Shift+Enter.

• Change to the directory where the RundownBrokerSetup.exe file is located: Type cd /d "<Full path to the RundownBrokerSetup.exe>" and press Enter.

• Type the following command into the console window: RundownBrokerSetup.exe /L*V setup.log and press Enter.

This procedure creates the file setup.log in the current directory while the Rundown Broker setup is running. This log file is a great help when it comes to finding the reason for failure.

The https://davidsystems.atlassian.net/wiki/x/BIBxO already contains this line in batch file. This means the Rundown Broker Setup log file setup.log is already written to the setup folder.

The https://davidsystems.atlassian.net/wiki/x/D4B4O generates a log file too, which is saved in the TEMP folder ${env:temp}\RundownBrokersetup.log. The installation by PowerShell writes useful information about the progress of the installation and errors to the console output as well.

Reading the log

If there was an error during the installation, open the log file, search for the first “return value 3” occurrence and/or the last “Error” in the log file to find the reason why the installation has failed.

Service Log File

The setup also could fail in case the Rundown Broker can not be started.

The reason for not starting Rundown Broker is written to the most recent service log file located in <Rundown Brokert Installation folder>\Log\<Configuration Name> directory.

Common Issues and Solutions

Contact Support

E-Mail: support@davidsystems.com