Configuring an RLM Server/Debugging problems with RLM



Release:

4.6  •  5.0  •  5.1  •  5.2  •  5.3  •  5.4  •  6.0  •  6.1


If you experience a problem with the RLM license server that requires debugging or help from tech support, your first step should be to generate RLM diagnostic files. The server-side diagnostic file gives a view into what is happening in the server, and the client-side diagnostic file gives a view into what is happening as far as communication with the RLM server and license acquisition from the Analytica (the client) side.

If you think the problem is with the license or if it happens while activating the license, you should also see the page "Solving problems during managed license activation", which chronicles problems that have been experienced and solved by others.

Generating the Server-side diagnostic file

  1. Log into your RLM admin panel.
    If you are logged into your RLM server, you would get there by pointing your browser to http://localhost:5054.
  2. Press the [Diagnostics] button on the left.
  3. Proceed through, and copy path to the diag file that is written


First, review this file yourself (often, something obvious jumps out). If you request help from Lumina or Reprise tech support, please attach this file, as well as the client log, to your email.

Generating the Client-side diagnostic file

  1. Run CMD (Command prompt)
    To do this, from the Windows start menu, type: CMD
    Command Prompt is shown as a suggestion. Click on it.
  2. From the command prompt, type:
    1. C:
    2. CD "\Program Files\Lumina\Analytica 6.1"
      Adjust this line to be the install directory of the actual release that you are running
    3. Analytica.exe /rlmDiag:"C:\Temp\clientDiag.log"
      Adjust the path, c:\Temp, to be an existing writable folder on your computer"
    4. After Analytica launches (even if it is showing a license error), make a copy of this clientDiag.log file, because if you change things on the license information dialog, or in some cases attempt to obtain an optimizer add-on license later during model evaluation, this file will be replaced with a new log of those attempts. In most cases, you will be debugging the first attempt, so you want to copy the log for the first attempt.

Again, review the clientDiag.log file to see if something jumps out, and then, if requesting tech support help from either Lumina or Reprise, also include this diagnostic file as an attachment to your email request.

See also

Comments


You are not allowed to post comments.