Though thankfully a relatively rare event, Captivate projects have been known to suffer corruption. If damage is severe enough, a corrupted file will simply refuse to open in Captivate and then you need to resort to one of the methods suggested in this section to recover it.
If you are unable to recover the project, and you didn’t take the extra precaution of doing daily backups, then you are in all likelihood going to lose all your work on that file.
Why Captivate projects sometimes corrupt
It’s important to remember that Adobe Captivate is actually a very complex application. Any software developer knows that the more complex an application becomes, the more likely it is to contain annoying bugs, and the more likely that you will at times encounter a condition from which the application cannot recover, resulting in a ‘crash’. Some Captivate versions (and updates) have certainly had ‘teething problems’ and critical stability issues, which Adobe usually addresses quite quickly. (By contrast Adobe is far less likely to address other equally annoying usability issues because these do not cause the app to crash and lose work.)
The more recent versions of the app and its file format seem to have be very stable. In my personal experience, when Captivate is properly set up on the developer’s system, and used in accord with best practices, it is extremely stable
Here are some of the reasons for the occasional instability issues that some Captivate users experience:
- The nature of the CPTX file format – A CPTX project file is actually a zip archive in disguise and may contain hundreds or even thousands of smaller files relating to the myriad of objects, images, and actions contained in your e-learning course. Each of these tiny files must be flawlessly saved back to the default location of the Captivate project cache folder every time you perform a save action. If for any reason this save action does not occur as planned, corruption may result. This is a key reason why Captivate developers are told NOT to directly open CPTX project files residing on a network or cloud drive and NEVER to save changes directly back to the same network or cloud location. See the next item…
- Working on project files over a network – Another big cause of project file corruption in Captivate is the ill-advised practice of storing project files on a network drive and using Cp to directly access and work on these files over the network. All it takes is the smallest glitch in network traffic at the same moment your file is being saved to render it beyond repair. This is why Captivate authors are repeatedly advised to maintain all currently active project files in a folder on your PC hard drive rather than on a LAN.
- The project file is not corrupt, but some objects within it may be – We just mentioned that a Captivate project file is actually a collection of scores, hundreds, or even thousands of objects. Sometimes one or more objects conflict with others and this manifests itself similarly to project corruption. One way this can sometimes occur is due to developers doing too many copy / paste actions from one project to another. Captivate will normally rename any objects being copied, so as to avoid the possibility of two objects ending up with the same unique ID. But it’s still best not to tempt fate. Image files (e.g. SVGs) and fonts are two areas that often turn out to be corrupted. Any third-party components such as OAM files should also be considered as possible sources of corruption, especially if they were not created by compatible apps made by Adobe.
- The current IT love affair with virtualization technologies – In recent years we are seeing a growing trend for corporations to employ new technologies known as virtualization. This approach is designed to make it easier to maintain the company’s valuable information assets by ensuring they are all located on central servers rather than being spread all over the landscape on individual PC drives. This means that user profiles, desktops, and My Documents folders are now often stored on servers to facilitate easier management and backups. Unfortunately for Captivate users, this innovative IT management approach has some major downsides, one of which is that it requires files be remotely stored and not locally on the developer’s own local drive. As stated earlier, this can sometimes cause Captivate to become unstable and crash, which can then result in project file corruption. If you work in a corporate environment where virtualization and roaming user profiles are the order of the day, you need to explain to your IT people that working from anywhere other than the hard drive is a known cause of file corruption and ruined projects with Adobe Captivate. Hopefully they will do a quick search on the Adobe Captivate Forums to verify your story. They should be able to locate large numbers of users complaining about lost projects due to working over a LAN instead of locally.
Unable to open a specific Captivate project file
One day you try to open a Captivate project file you’ve been working on, and all you get is some kind of cryptic error message. Here are the most likely reasons:
Project lock file still present in folder
When you open a project file for editing, Captivate creates another hidden file with the same name, but with a cptx_lock file ending. This file locks your project to prevent any other user from attempting to edit the same file while you have it open.
This file is normally deleted to unlock the project when you save and close. However, if Captivate crashes or the lock file is not deleted on closing the project, then you project may remain locked from the previous editing session.
Browse to the file location and see if there is a file with the same name but with a cptx_lock file ending as shown above. (The lock file is a hidden file. So you need to Show Hidden Files and Folders in Windows folder settings.) If you find the lock file, delete it and try to open the project again from within Captivate.
Project file has become corrupted
If you still cannot open the project file, it may have become corrupted during the last editing session, or when you saved it. You may be looking at a case of corruption if you see any of the following symptoms:
- Captivate opens without issue but crashes as soon as you open the project file. (You can prove this must be due to the project file itself rather than Captivate because it opened initially and other similar projects open without issue.)
- The project crashes or throws error messages when you attempt to publish out.
- After publishing, some part of the project fails to work or shows blank slides.
- Captivate refuses to open the project file at all, even though the same project worked perfectly the last time you opened it.
The most common reason for project file corruption is NOT following the rule to ONLY work on projects stored on your local hard drive. In mild cases, you can often use a process of elimination to locate and remove corrupt slides, objects, or actions thereby restoring the project to full functionality. In worst-case scenarios, you may need to restore an entire project to an earlier point in time in order to resurrect it. That’s only possible via backups or by using the cache.
If you obey the instructions on this website about setting the Captivate Project Preference to Generate Project Backup, then all you need to do is go to the folder containing the project file, delete the .bak file ending from the backup file, and open it in Captivate. All you will lose this way is any work performed since you last saved and closed the project file.
If you have not as yet cleared your Project Cache, then you can often resurrect a project all the way up to the last Save action by converting the cache files back into a CPTX file. see the instructions in the heading below about how to recover a project file from the cache.
Locate and remove corrupted elements from a project
Corruption is usually limited to one or more slides. Sometimes the issue can be caused by a single object on one of the slides. If you can locate and remove the corrupting elements, you can usually restore your project to full functionality. If fortune smiles and you can still open and navigate the project, try using a process of elimination to locate the offending slide or object and remove it.
- Hide all slides in the first half of your project and try to publish again.
- If you still cannot publish, hide all slides in the last half of the project and try to publish.
- If you are able to identify the half of the project where the corruption exists, use the same slide hiding process to progressively narrow down where the problem slide is.
- Once you identify the issue, remove the object or slide and try publishing again.
The good news is that even if your Captivate project file does turn out to be completely corrupted, if you followed all the suggestions in the section of this document about setting up for Captivate development, you still have at least two options left.
Recover a project from backup
If you implement the suggestion to Generate Project Backup in Preferences, then you will start seeing duplicates of your project files appear in the same folder with .cptx.bak file endings. This is really just a copy of your current project file that contains all changes up until the last time you saved and closed your project.
- Just rename or delete your corrupted project file (so that you’ll know which one it was) and move it out of the way somewhere.
- Next, remove the .bak ending from the backup file and try to open it in Captivate. If your backup file predates the moment when corruption afflicted your project, then it should open properly and you’re back in business. You will of course lose all work performed after that file was lasted saved and closed, but at least you’ll still have a working project file.
Recover a project from cache
Your backup file can only ever contain changes you made up until the last time you successfully saved and closed down your project. If you want to try and recover all changes to the current state of your project, you can try restoring from the cache. This is a special folder where temporary working files are stored as you edit a Captivate project file. The default location is usually in My Documents > Adobe Captivate Cached Projects. However, on corporate networks user profiles are often virtualized, which means the user’s My Documents folder is not located on their local hard drive but resides on a network or cloud server somewhere. So, I usually advise Captivate developers to set up a special folder near the root level of their local C: drive so that the project cache has no chance of being corrupted.
To change the Project Cache folder location, open Edit > Preferences > General Settings > Default Locations > Project Cache and use the Browse button to navigate to the special folder you set up for this purpose. As you can see from my example below, the folder I set up is right at the root level of my C drive.
If you’ve been working on quite a few project files your cache will likely contain a large number of folders with names that consist of seemingly random letters and numbers. These folders contain all the files necessary to recreate each separate project file you’ve worked on since the last time the cache was cleared. The contents of the cache folder are updated each time you hit Save for that particular project. This means, if you know what to do, you can sometimes resurrect a project file that steadfastly refuses to open via any other method. This is great news for Captivate developers!
But it’s not all good. Since the folders all have this cryptic naming convention, it’s impossible to tell from just looking at the names which specific project each one contains. If you run into project corruption issues during a particular session, you can sort the project folders by date modified and that should shorten the odds somewhat. The most recently modified folder is probably the one for your project.
Using the Dcache application
However, what if you are trying to resurrect a project file from last week or last month? By now you may have opened and worked on dozens of projects and finding the right one in the cache is like finding a needle in a digital haystack.
Adobe realized this would be the case and created a special AIR application called Dcache. You can download the free Dcache utility from here. This application enables you to browse those cryptic cache folders and see which one relates to a given project. However, be warned that AIR apps are actually encapsulated Flash files programmed in ActionScript 3. So, it’s very possible that your system may no longer allow you to install or use these files due to the much advertised “Death of Flash” at the end of 2020.
Assuming you still can use the Dcache AIR app, once you locate the correct cache folder for your problematic project, just browse to that folder in windows explorer and open the single db folder it contains to see the files and folders shown in the screenshot below. Now you’re ready to recover the project as per the following instructions.
To recover a project from within the cache db folder:
- Select all files and folders EXCEPT any called already_in_use.lock or backup_data. (Including these files would prevent Captivate from opening the recovered project once you convert it back to a CPTX.)
- Right click on the selected group of files and choose Winzip > Add to db.zip from the context menu. (This assumes you’re one of the 99% of users that have Winzip or some similar compression app.)
- Save this zip file to another location (usually where you store your project files) and change the file extension from .zip to .cptx.
- No try to open the .cptx file in Adobe Captivate. Be warned that you will need to use the same version of Captivate that was last used to edit the project file, or a Captivate version that was released AFTER that version. (Captivate is backward compatible but not forward compatible.)
If the project file opens successfully, you will see all saved changes up to the point the development session was closed or Captivate became unresponsive and crashed. If the recovered project file will NOT open, you may yet be able to find an older cached version of it that is still recoverable. However, if you’ve already cleaned out your cache, those versions will not exist anymore.
So, all things considered, Adobe has tried to support you by providing a backup file option in Preferences, cached project versions you can use as a last resort to restore the project, and even a free utility to browse the cache and identify specific projects you may want to recover. But, in some cases none of this is going to be enough and you will in the end lose work due to corrupted projects.
Life wasn’t meant to be easy…