Troubleshoot

At a glance:

This is a conceptual topic, explaining an aspect or feature of VTScada.

Find this in VTScada:

This is a navigational node within the documentation.

Related topics and things to know before reading this include:

Before calling support, it is helpful to ensure that you have collected as much information as possible about the cause of a problem.

Be sure that you know your serial number (see: Installation & Activation)

For serious problems, it may be helpful to capture diagnostics using a crash dump (Generate a Crash Dump from the Source Debugger).

Where to go from here:

Please refer to the links provided in this topic.

VTScada provides a set of utilities to assist with troubleshooting, analysis, and debugging. In general, the diagnostic utilities are useful to:

  • Programmers when writing VTScada script code.
  • Customers when directed to use a tool by VTScada support staff, in order to diagnose a problem.

These tools are designed to be functional, rather than user-friendly. Most utilities are not listed in the VAM by default, but can be added using the Find Existing option of the Add Application Wizard. The most versatile and powerful of VTScada's diagnostic utilities is the Source Debugger. Start here when attempting to diagnose performance issues or debug code.

For a complete list of messages that can be written to the Windows Event Log, refer to Event Log Messages - Event ID 1001

A lack of memory or disk space can cause many problems including slow performance, difficult or failure to log, difficulty or failure to distribute updates.
Check the available space on every server on a regular basis. If the percentage available is becoming small, consider options to clear space or (if this is an Historian server) to install a larger drive.

Tips and Techniques
A collection of troubleshooting tips, optimization techniques, and assorted helpful suggestions.

Coordinates Application
Small window showing the coordinates of the cursor within any VTScada window.

Debugger Utility
Early version of the Source Debugger. Rarely used now.

Instance Count Application
Counts the number of instances of all modules in all running applications.

Memory Tracer Application
Can be used to trace high memory usage to specific modules.

RPC Timing Utility
Monitor the time required by server-to-server messages.

Test Framework Application
Use to run tests that you have created to prove that your script code is working properly.

Thread List Application
Shows a list of all threads in use by VTScada.

Trace Viewer Application
Monitor inter-server communications, device driver communication, or SOAP messages.

Trace VTScada Actions Application
Monitor actions of selected VTScada services.