This Knowledge Base article provides information about how to retrieve the logs and other information required for troubleshooting. The logs will commonly be requested by SolarWinds Support when submitting a Support Request and should contain the relevant log information related to a Support Request.
VBS files: Do not send files with a
extension, as they will be blocked by the SolarWinds mail system. If a VBS script is attached to a Support email, the email will not be delivered to the SolarWinds Support Team.
BAT files (such as stop/start scripts): Please rename from .bat to .txt before attaching to email. If a batch script is attached to a Support email, the mail will not be delivered to the SolarWinds Support Team.
How to Use the Orion Failover Engine Log Collector
- Download the correct version of the Orion Failover Engine Log Collector.
Note: This might not be necessary, as the Orion Failover Engine Log Collector is also available as part of the Orion Failover Engine Kit.
- Extract the .zip file to an appropriate location on the server.
- Run the LogCollector.exe .
- Follow the on screen prompts.
Collect logs from the location specified on screen by the Log Collector. This is typically:
- For Windows 2003 server installations: C:\Documents and Settings\All Users\Application Data\SolarWinds\OrionFailoverEngine\Log_%DateAndTimeRun%\*.zip
- For Windows 2008 server installations: C:\ProgramData\ SolarWinds\OrionFailoverEngine\Log_%DateAndTimeRun%\*.zip
Email the .zip file to the person addressing your Support Request. If you already have a Support Request reference number, this should be included in the Subject line of the email. For example, Subject: SR 1000 - Company Name.
Note: If the Log Collector is used to gather logs, the following section can be disregarded or used for information only. If you would like to gather information manually, this section contains details of which logs are required and how to gather them.
Exceptions: Windows Server 2008
When running on the Windows Server 2008 platform, the LogCollector might experience problems while collecting the logs from the passive server. To workaround the issue:
Run the LogCollector separately on each server and collect the logs locally following these steps:
- Open a command prompt and navigate to LogCollector folder.
- Type LogCollector -remote and press the Enter key.
SolarWinds Support Requires the Following Information When a Support Request is opened.
- Information collected by default using the Orion Failover Engine Log Collector, or
If the Log Collector is not used then the following information should be gathered:
All NF values in the registry:
- Installation logs from the new setup.exe .
- Collect: %installdir%\R2\bin\*.xml
- Collect: %installdir%\R2\logs\*.*
- Collect: %systemroot%\nfinstalltemp\*.*
- Collect: %installdir%\R2\Support\*.*
- Collect: Orion Failover Engine Diagnostics Logs in default locations, %systemroot%\Documents and Settings\USER\ApplicationData\SolarWinds Orion Failover Engine Diagnostics
- Collect: %systemroot%\hs_err_pid*.*
- Collect: %systemroot%\system32\hs_err_pid*.*
- Collect: %systemroot%\Documents and Settings\*\nfsetupauditlog.txt
- The Windows Event Viewer Application and System logs exported to .CSV format files. See below for instructions on how to gather these.
- With the Data Collector service installed, collect all the logs from the directory specified by Settings -> Output Files in the SolarWinds Orion Failover Engine Diagnostics MMC snap-in.
How to Gather Information in the Correct Format:
- The Windows Event Viewer Application and System logs exported to . csv format files. You can do this by opening Windows Event Viewer, selecting Action , Save log file as and then changing the save as type option to CSV (Comma Delimited) .csv .
- Any SolarWinds Orion Failover Engine Diagnostics information held on the servers.
Retrieving Logs from the Passive Server in case LogCollector fails to do it automatically
This section details how to retrieve Orion Failover Engine logs from the passive server when there are no management (backdoor) IP addresses configured. This need only be done when the logs have been requested by support.
Note: If you do not know the Channel IP address currently being used, you can check this via the SolarWinds Orion Failover Manager configuration screen.
Follow these steps:
At the console of the active server run the following commands, substituting the relevant directories where appropriate.
C:\net use \\passive.channel.ip.address /user:administrator
copy \\passive.channel.ip.address\SystemRootDrive$\Documents and Settings\All Users\Application Data\SolarWinds\OrionFailoverEngine\Log_%DateAndTimeRun%\*.zip c:\temp\OrionFailoverEngine \passive
copy \\passive.channel.ip.address\SystemRootDrive$\ProgramData\SolarWinds\OrionFailoverEngine\Log_%DateAndTimeRun%\*.zip c:\temp\OrionFailoverEngine\passive
for Windows 2008\*.*
When a management (backdoor) IP address exists on the passive server, the logs can be simply copied from the passive server to a remote client via explorer.
- Other useful information to collect.
Current Configuration can be obtained by:
cd c:\%Orion Failover Engine install folder%\r2\bin\ and run exportconfig.exe c:\temp\OrionFailoverEngine\config.xml
Registry Information including current File Filters can be obtained by:
reg export HKLM\Software\JavaSoft\Prefs\neverfail\current\/Interceptor\/Filters c:\temp\OrionFailoverEngine\file-filters.txt and email file-filters.txt to support.
- To list all folders on a drive:
dir /a:d /b /s >>c:\temp\OrionFailoverEngin \folders.txt
- This should be completed for each drive
- Sending the information to Support
Run the following commands from a command prompt on either server with Solar Winds Orion Failover Engine installed:
As before, the information gathered should be zipped and labeled clearly as primary or secondary.
All the above information must be supplied in order for Support Team to provide support effectively.
LogCollector V2.1 and later