Troubleshooting

This list provides some general debugging information.

  1. When you start the Marvel Run Portal be sure that you direct the output into a local log file where you can examine it. The log file often contains useful information. Examine it when you have a problem, and be prepared to answer questions about it when you talk to a support person.

  2. If the Marvel Run Portal appears to have started correctly (which you can determine from the log file), try running lmstat ‐a and lmdiag to see if that program has the same problem as your application.
  3. If your application is version 1.0, you can use the Marvel_DIAGNOSTICS environment variable. Set Marvel_DIAGNOSTICS to 1, 2, or 3. A setting of 3 gives more information than 2, 2 gives more information than 1 (in particular, the feature name that was denied).

  4. When you talk to a support person, be prepared with answers to the following questions:

    • What kind of system is your license server running on?

    • What version of the operating system?

    • What system and operating system is the application running on?

    • What version of Marvel Run Portal is in use?

    • What error or warning messages appear in the log file?

    • Did the server start correctly? Look for a message such as: server xyz started for: feature1 feature2

    • What is the output from running lmstat ‐a?

    • Are you using a combined license file or separate license files?

    • Are you using three-server redundancy (i.e., there are multiple SERVER lines in your license file)?