No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade
Knowledge Base

Screen Recording Failure

Publication Date:  2015-07-01  |   Views:  246  |   Downloads:  0  |   Document ID:  EKB1000081129

Contents

Issue Description

After a call is set up between a VTM and a VTA, an inspector fails to record the VTA's screen. No screen recording is available, so post-event screen inspection cannot be performed.

Handling Process

Step 1 Verify that the NFS client is enabled on the inspector's PC and \\File server IP address\shared directory is accessible.
To enable the NFS client, see Fault Management > Troubleshooting  > Appendix  > Configuring an NFS Client .
Step 2 Verify that the file server has sufficient space.
1. Log in to the file server as the root user.
2. Run the df -k command to check the value of Used%.
If the space usage is too high, run the rm -rffile/folder name command to delete unnecessary files and folders. If space is insufficient, but no files or folders can be deleted, expand the space.
Step 3 Verify that the file server directory for storing screen recordings is not mapped to a drive on the MCC server, and the mapped drive letter configured on the MCC configuration assistant is the same as the one in use.
1. Log in to the MCC server as the Elpis user.
2. Run the cd /D: command to go to the mapped drive on the MCC server.
In the preceding command, D: indicates the mapped drive letter on the MCC server pointing to the file server directory for storing screen recordings.
3. Run the ls -l command to check whether all files in /share/voice on the file server are available in D: on the MCC server.
If yes, the mapping is successful.
If no, the mapping fails, and you must re-configure the directory mapping by referring to Manually Installing the MCC > Configuring Directory Mapping in the eSpace VTM Installation Guide.
4. Log in to the MCC configuration assistant as the admin user and access the File Server Mapping Configuration page. Check whether the value of Local directory for mounting the file server on the application server is the same as the mapped drive letter on the MCC server.
Step 4 Verify that the MCC server time is the same as the current time.

Root Cause

 The NFS client is disabled on the inspector's PC and therefore the PC cannot access the file server.
 The file server has insufficient space.
 The file server directory for storing screen recordings is not mapped to a drive on the MCC server, or the mapped drive letter configured on the MCC configuration assistant is different from the one in use.
 Recorded files are named by date. If the MCC server time is different from the current time, recorded files generated at the current time may be named by a different date.