Session Recording Can Crash on Launch with Improper Permissions

Follow

Date: April 1, 2015
Revision: 1.1

Problem:

When trying to launch an application where session recording is enabled, the session recording portion crashes immediately. The diagnostic logs on the session recorder host, typically found at C:\ProgramData\Lieberman\SessionRecording.SessionR ecording_Expression4_CLI\Version 1.x\Diagnostics, has the following information:

Code:
717 [1] INFO (null) - Note: Config file location for SessionRecorder module is: c:\Program Files (x86)\Lieberman\Roulette\LaunchApp\SessionRecordingEx\SessionRecording_Expression4_CLI.dll.config
1513 [1] DEBUG (null) - Logging recording start to web service - https://server-name/ERPMWebService/WebLauncherBackendService.svc
7441 [1] DEBUG (null) - Specified session data parameter - m_oDataOutputSettings.m_sOutputDirectory: C:\Program Files (x86)\Lieberman\Roulette\LaunchApp\Transcoders\Source
21701 [1] INFO (null) - Note: Posted WM_QUIT message to thread 4292
21701 [1] INFO (null) - Failed to post WM_QUIT message to thread 6704; error: 1444
21701 [1] INFO (null) - Failed to post WM_QUIT message to thread 4464; error: 1444
21701 [1] INFO (null) - Failed to post WM_QUIT message to thread 9920; error: 1444
21701 [1] INFO (null) - Failed to post WM_QUIT message to thread 8796; error: 1444
21701 [1] INFO (null) - Failed to post WM_QUIT message to thread 5880; error: 1444
21701 [1] INFO (null) - Failed to post WM_QUIT message to thread 1980; error: 1444
21701 [1] INFO (null) - Failed to post WM_QUIT message to thread 5404; error: 1444
81716 [1] WARN (null) - Warning: Could not close CLI sub-process within timeout; closing forcefully to avoid lingering. This may cause incomplete saved data.
81716 [1] DEBUG (null) - Logging recording stop failed to web service - https://server-name/ERPMWebService/WebLauncherBackendService.svc

The ERPM connection account may or may not be an administrator on the jump server where session recording is occurring.

Cause:

The cause of the crash is that the session recorder does not have the proper permissions to write to the target directory noted in the log as m_oDataOutputSettings.m_sOutputDirectory. In the example above, the path is: C:\Program Files (x86)\Lieberman\Roulette\LaunchApp\Transcoders\Sou rce.

This may occur even if the connection account is in the administrators group when the jump server has UAC enabled.

Resolution:

Find the target path mentioned above and grant the connection account Modify or Full Control over the directory.

The connection account can be determined by opening the ERPM console and going to Settings | Manage Web App | Application Launch >> Jump Servers tab. Edit the server and note the connection account. This account is used to connect to the jump server. This account must have permissions to the target directory on the jump server.

Even if the account is part of the administrators group, UAC will remove the administrator's token from the login token. Thus explicit permissions should be granted.

Applies To:

Enterprise Random Password Manager (ERPM)

Was this article helpful?
2 out of 2 found this helpful

Comments

  • Avatar
    Carlos Nunes

    This was very useful.

    Edited by Carlos Nunes
Powered by Zendesk