Corrupt Remote Control recording file .urc

Products

• CA Client Automation - IT Client Manager
• CA Client Automation

Issue/Introduction

When we try to start a .urc file (Remote Control Recording file), following error appears :

The recording file appears to be corrupt. Corrupted recording files can often be recovered. 
Would you like to attempt to repair it now?

And the repair operation does not work.

Environment

Client Automation - All Versions

Cause

This problem occurs if the size of .urc file exceeds 4 GB (4294967296 bytes).

Example :
The file rc_video.urc has a size of 4342559679 and it could not be opened with RC Replayer :

Resolution

Unfortunately there is no real solution. The workaround is to avoid to generate a recording file with a size greater than 4 GB.

After a long rc session, disconnect to save the recording file and reconnect again to generate a new recording file.

Generally the .urc file is filled with a rate between 10 MB/minute and 100 MB/minute.
This is depending of RC Host screen resolution and what is displayed on it. The rate could be higher if a video in full screen is played on the RC Host during the recording.

So generally the .urc file reaches the limit size of 4 GB between 40 minutes and 6 hours 30 minutes

It could reach the 4 GB size in about 10 minutes if a video in full screen is displayed on RC Host.

Additional Information

Attached file check_urc.zip contains a small tool (check_urc.exe) to check the .urc file

Examples :
- rc_video.urc is corrupted :

 

- rc_video2.urc is OK :

 

- rc_video3.urc has a corrupted chunk (chunk starts at offset 0x4ADAA) :