Jump to: navigation, search

Known Issues and Recommendations

Genesys SR Service

The Known Issues and Recommendations section is a cumulative list for all 8.5.x releases of Genesys SR Service. This section provides the latest information on known issues and recommendations associated with this product. It includes information on when individual items were found and, if applicable, corrected. The Resolved Issues section for each release describes the corrections and may list additional issues that were corrected without first being documented as Known Issues.




When the Screen Recording Service (SRS) is configured with primary and peer Interaction Recording Web Services (RWS) sites, and if the primary RWS site is down, then SRS will not attempt to upload error logs to the peer RWS site.

ID: GIR-13495 Found In: 8.5.345.24 Fixed In: 8.5.355.61

If a screen recording session is in progress, and the agent logs out from the operating system before logging out from Workspace Web Edition (WWE), it might cause a corrupted video.

Workaround: Ensure that the agent is fully logged out before logging out of the operating system.

ID: GIR-6633 Found In: 8.5.320.64 Fixed In: 

The SR Service parameter certificate does not take effect. As a result, the page "Select Certificate Validation Option" in the SR Service Installation Wizard does not produce the expected result.

ID: GIR-6615 Found In: 8.5.302.14 Fixed In: 8.5.350.65

If the RWS has CSRF enabled, the SR Service may not function properly due to handling the CSRF tokens.

Workaround: Disable CSRF on the RWS side.

ID: GIR-6539 Found In: 8.5.320.64 Fixed In: 

After the agent clicks the Pause button in WWE, there might be some latency and additional seconds of the screen may be recorded.

ID: GIR-6529 Found In: 8.5.311.13 Fixed In: 

If the agent starts a screen recording session and switches the primary monitor to the secondary monitor on the fly, the SR Service will not be able to properly capture the screen recording on the secondary monitor.

Workaround: Do not switch the display while a recording session is in progress.

ID: GIR-6468 Found In: 8.5.311.13 Fixed In: 

If the agent logs into WWE simultaneously on different browsers at the same time on the same machine, the screen recording session might not work properly.

Workaround: Login to only one session of WWE at a time.

ID: GIR-6451 Found In: 8.5.311.13 Fixed In: 

If the RWS is running behind NGINX and an unexpected close/refresh of the WWE browser occurs, it might cause some stale connection be reported by RWS.

Workaround: Ensure that the agent manually logs in and logs out from WWE to reset the connection status.

ID: GIR-6428 Found In: 8.5.311.13 Fixed In: 

If the agent logs in to multiple machines at the same time and starts screen recording sessions, the VLC.exe might not stop and will became a zombie process when the call ends.

Workaround: Ensure that the agent logs in to only one machine at a time.

ID: GIR-6426 Found In: 8.5.311.13 Fixed In: 

The SR Service might not be uninstalled if the CANCEL button is clicked during the maintenance upgrade.

ID: GIR-6408 Found In: 8.5.311.13 Fixed In: 

Screen Recording might be overlooked by the system when VLC fails to start the recording.

ID: GIR-6259 Found In: 8.5.311.13 Fixed In: 

VLC allows the user to override the default vlcPortBegin and vlcPortEnd value. If the set range is too small, an infinite loop might occur.

Workaround: Configure a large vlcPortBegin and vlcPortEnd range.

ID: GIR-6118 Found In: 8.5.311.13 Fixed In: 

If the SR Service (SRS) contains screen recording files in the agent's local directory, and the SRS is restarted, the recordings are not uploaded to GWS.

ID: GIR-6064 Found In: 8.5.311.13 Fixed In: 8.5.355.61

If Internet Explorer is used in Citrix environment, processing HTTP requests may be delayed due to socket timeout handling in the Screen Recording Service (SRS) because SRS is single-threaded by design.

ID: GIR-6035 Found In: 8.5.302.10 Fixed In: 

If the vlcLog parameter is set to true in the Screen Recording Service (SRS) configuration, the VLC log may not be generated if the user does not have the right permissions.

ID: GIR-6034 Found In: 8.5.310.77 Fixed In: 8.5.355.61

The SR Service (SRS) prevents the installation of an older SRS version if a newer version is already installed in the system. To perform a full downgrade, uninstall the existing (newer) version of SRS before installing an older SRS version.

ID: GIR-5972 Found In: 8.5.302.10 Fixed In: 

During the SR Service (SRS) upgrade, if the SRS service is not stopped when the setup.exe is running, the rra files may remain in the SRS installation folder.

Workaround: Reboot the machine to remove the rra files.

ID: GIR-5945 Found In: 8.5.302.14 Fixed In: 

When working with Internet Explorer or Firefox, the SR Service preflight response can take as long as the configured socket timeout. This occurs when an empty request is sent from the browser to the SR Service.

ID: GIR-5893 Found In: 8.5.311.13 Fixed In: 

If the SR Service is restarted while a recording is in progress or when trying to close a recording, an extra vlc.exe process might be left running in the system.

Workaround: Stop any remaining vlc.exe processes in the Task Manager.

ID: GIR-5870 Found In: 8.5.302.14 Fixed In: 

If the vlcCloseTimeout parameter is configured (default 2 seconds), the SR Service will wait for the configured timeout before killing the VLC. During this time, the SR Service will not be able to start a new recording session.

ID: GIR-5997 Found In: 8.5.302.14 Fixed In: 8.5.310.84

The SR Service might sometimes fail to upload. When this occurs, the following error reporting and print exception will appear: An unexpected error has occurred in send_deferred. list index out of range.

ID: GIR-5994 Found In: 8.5.302.14 Fixed In: 8.5.311.13

When RWS has CSRF enabled, the SR Service generates an error when posting the error log to RWS with a 403 Forbidden Issue.

Workaround: Disable the CSRF on the RWS side.

ID: GIR-5870 Found In: 8.5.302.14 Fixed In: 

When a component's maximum log size is reached, that component may stop working until the next service restart.

ID: GIR-5458 Found In: 8.5.230.23 Fixed In: 8.5.302.10

When the maximium recorder log size is reached, the SR Service will fail to start recording.

ID: GIR-5339 Found In: 8.5.230.23 Fixed In: 8.5.302.10

When running auto update with updateWhen set to immediate, the following log error may appear: "Updater: An unexpected error has occurred.(6, 'WaitForSingleObject', 'The handle is invalid.')". This error can be ignored.

ID: GIR-5339 Found In: 8.5.230.23 Fixed In: 8.5.302.10

The update fails when configuring the softwareVersion parameter, using a single digit without a leading zero (for example, 8.5.301.1 instead of 8.5.301.01).

ID: GIR-4892 Found In: 8.5.230.23 Fixed In: 8.5.302.10

Connection errors are not reported back from the SR Service to Web Services and Applications.

ID: GIR-4800 Found In: 8.5.302.10 Fixed In: 

Working with Internet Explorer 11 can sometimes cause the SR Service to crash.

ID: GIR-4635 Found In: 8.5.230.23 Fixed In: 8.5.311.13

When using Firefox and HTTPS, a security warning may appear about an untrusted certificate from 127.0.0.1.

Workaround: 1. Ignore the security warning. 2. Manually import SR Service certificates ( Server.pem & ServerIp6.pem located at <srs_install_dir>\Certificates) into Firefox.

ID: GIR-4621 Found In: 8.5.230.23 Fixed In: 8.5.350.65

When switching Workspace Web Edition in the middle of a session to a Workspace Web Edition that is not in the SR Service allowed list, a logout is triggered in the SR Service.

ID: GIR-4533 Found In: 8.5.230.23 Fixed In: 8.5.302.10

If the /IP6 argument is supplied to the setup.exe during installation and additional arguments also contain the IP6 string (/CERTIFICATEPASSWORDIP6), an incorrect config.json may be written, If additional arguments also contain the "IP6" string.

Update: Command line configuration has been deprecated. Therefore, this issue is no longer relevant.

ID: GIR-4450 Found In: 8.5.230.23 Fixed In: 

If the SR Service is not installed from the local adminstrator account, and HTTPS is enabled on the SR Service, the Workspace Web Edition may not be able to connect to the SR Service successfully, due to an ERR_INSECURE_RESPONSE error.

Workaround: Perform any one of the following procedures:

  • Reinstall the SR Service under the the local administrator account.
  • If the SR Service is installed under a different Windows account with an administrator privilege, run the following commands to import the self signed certificate under the SR Service's Certificates\Self-Signed directory:
    certutil -addstore "root" "server.crt"
    certutil -addstore "root" "serverIp6.crt"
    After the change is complete, restart the web browser.
  • Manually import the certificate into the Trusted Root Certificate Authority from Windows Certificate Manager.
ID: GIR-4445 Found In: 8.5.230.23 Fixed In: 8.5.302.10

When using the installation command line to configure the SR Service and the installation folder has an empty configuration file, the config.json file will be invalid and manual editing will be required.
Update: Command line configuration has been deprecated. Therefore, this issue is no longer relevant.

ID: GIR-4427 Found In: 8.5.230.23 Fixed In: 

When using the installation command line to configure the SR Service, allowedHosts can only be configured as a single value and not as a list. The wild card can be used.
Update: Command line configuration has been deprecated. Therefore, this issue is no longer relevant.

ID: GIR-4422 Found In: 8.5.230.21 Fixed In: 

The SR Service supports multiple users, provided that the user name is unique across all tenants / HTCCs.

ID: GIR-4412 Found In: 8.5.230.23 Fixed In: 

The SR Service creates a folder with the name None in the postProcessingSavePath folder..

ID: GIR-4411 Found In: 8.5.230.23 Fixed In: 8.5.302.10

When a proxy is used it may interfere with the SR Service operation. The SR Service runs as an HTTP server and it relies on an incoming socket connection to identify the agent's windows session correctly. If the HTTP requests are forwarded by a proxy, the SR Service may not be able to correctly identify the user session in a multi-user environment. In a single user case, it will fall back to the currently active windows session. When the SR Service is installed on a machine with the proxy as an internal system service (such as, Antivirus\Firewall), it is recommended that the SR Service related processes (SrsProcess.exe and GenesysServiceHandler.exe) be added to the security software exception\white list. To avoid this issue, it is recommended that the localhost (127.0.0.1) connections be excluded.

ID: GIR-4406 Found In: 8.5.230.23 Fixed In: 

The Configuration Update log message may sometimes be logged to the wrong user log file.

ID: GIR-4364 Found In: 8.5.230.23 Fixed In: 8.5.302.10

SR Service auto update may be blocked by the Trend Micro OfficeScan Agent Anti-Virus.

Workaround: Add SR Service processes (GenesysServiceHandler.exe and SrsProcess.exe) to the antivirus exception list.

ID: GIR-4355 Found In: 8.5.230.23 Fixed In: 

If a screen recording file size is larger than ~ 200MB, the recording encryption will fail and the recording will be deleted.

Workaround: Reduce the defined maxDurationMinutes configuration parameter.

ID: GIR-4250 Found In: 8.5.230.23 Fixed In: 

In a Citrix environment, the SR Service only supports a single session per remote PC.

ID: GIR-3964 Found In: 8.5.230.23 Fixed In: 

Passing a configuration file during installation using the /CONFIG CLI command line switch sometimes fails. Update: Command line configuration has been deprecated. Therefore, this issue is no longer relevant.

ID: GIR-3174 Found In: 8.5.220.72 Fixed In: 8.5.302.10

  • When Web Services and Applications is deployed with a self-signed certificate, those certificates must be imported into the Windows Local Computer Trusted Root Certificate Store.
  • If Web Services and Applications is deployed with GoDaddy certificates, HTTPS verification may fail. Please refer to Solution Guide for a workaround and a solution.
ID: GIR-3023 Found In: 8.5.205.00 Fixed In: 

Server TLS certificate validation is disabled by default due to issues with certain Certificate Authority verification.

ID: GIR-3019 Found In: 8.5.220.72 Fixed In: 8.5.230.23

When updating the SR Service using the full setup version, a manual uninstall and install is required. The auto updater does not work correctly.

ID: GIR-2056 Found In: 8.5.205.10 Fixed In: 8.5.220.72


Internationalization Issues

Information in this section is included for international customers.


There are no internationalization issues for this product.


Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on March 12, 2018, at 07:48.