Skip to main content
Skip table of contents


Following are some troubleshooting tips for various issues you may encounter.

SuperWEB2 Cannot Contact SuperSERVER

Issue: Users are unable to login via SuperWEB2 and there is a message similar to the following in the SuperWEB2 logs:

ERROR: 2023-08-02T10:42:18,438--[http-nio-8080-exec-2]--SuperSERVER was not contactable. Please check: your administrationServerCatalog.xml configuration, network connectivity to SuperSERVER and whether SuperSERVER is running--AuthPlugin

Troubleshooting Steps

  1. Verify that the SuperADMIN Server and SuperSERVER are both running. If they are not running, start the components and try again.
  2. Verify that the relevant ports are open for communication between the components (see Port Usage for more details).
  3. Verify that the relevant instance of SuperSERVER has only been started once. One way to verify this is to run the server command in SuperADMIN. If the server is listed multiple times, then this indicates that the same SuperSERVER instance has been started multiple times.

    If SuperWEB2 has previously connected to SuperSERVER with no issues and nothing else has changed on the environment, then multiple SuperSERVERs is very likely to be the root cause of the problem. 

    If you find that the same SuperSERVER instance has been accidentally started more than once, follow the steps below to resolve the issue.

Multiple SuperSERVERs Running

To resolve this issue:

  1. Stop all instances of SuperSERVER.
  2. Stop the SuperADMIN Server.
  3. Take a backup copy of the SuperADMIN dataServerCatalog.xml file (if you installed to the default location on Windows, this file is found in C:\ProgramData\STR\SuperADMIN\server\data\.repository), and then delete the file from the .repository directory.
  4. Take a backup copy of the SuperSERVER scsa.conf.dat file (if you installed to the default location on Windows, this file is found in C:\ProgramData\STR\SuperSERVER SA), and then delete the file from the SuperSERVER SA directory.
  5. Start SuperADMIN Server.
  6. Start SuperSERVER.
  7. Verify that users can now log in to SuperWEB2.

Configure Crash Dump Location

If SuperSERVER or Production System encounter a serious problem, then they may generate a crash dump that can be provided to the WingArc support team to investigate the issue. By default these files will be generated in the Windows temp directory, but you can configure an alternative location by editing the SuperSERVER and Production System configuration files.

This configuration setting is only available for Windows deployments.

To change the output location:

  1. Open the following files in a text editor:

    • SuperSERVER: tablemanager.config.xml
    • Production System: sa2ps.config.xml

    Both files are located in the SuperSERVER data directory (if you have installed to the default location, C:\ProgramData\STR\SuperSERVER SA).

  2. Locate the following section:

    <KEY name="Diagnostics">
        <KEY name="Windows">
            <STRING name="DumpFolder"></STRING>
            <STRING name="DumpFlags">MiniDumpWithFullMemory</STRING>
  3. Update the value of DumpFolder to the full path to the directory where you want any dump files to be created. For example:

    <KEY name="Diagnostics">
        <KEY name="Windows">
            <STRING name="DumpFolder">C:\Crashdumps</STRING>
            <STRING name="DumpFlags">MiniDumpWithFullMemory</STRING>
  4. Save your changes to the files and restart SuperSERVER/Production System.


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.