KB73059324: Color Engine Pilot - Recalibration and history not available in the C&R tool (device manager)

Summary

This article describes how to recover the C&R data when:

• The proof server software is installed on another system (with another hostname).
• The bg_data_cms data is moved to another location.
• When the proof client workflows and the corresponding output device needs to be moved to another proof server.

Symptoms

The recalibration and the history of the C&R tool (device manager) is lost.

Solution

• The proof server software is installed on another system.
  
  1. Enable the VDTL shell (user environment variable = VDTL_SHELL_INIT, value = 7)
  2. Open the Color Engine Pilot and type in the VDTL shell: devicemanager_export. Close Color Engine Pilot.

  3. Go to …\bg_data_cms_v010\w\devicemanagerxml and open the stations.xml file.
     In this file you will see which proofer server was used before:

     <Devicemanager-Archive>
      
       <station>
         <id value="0"/>
         <name value="OCTARINE"/>
       </station>
      
       <station>
         <id value="1"/>
         <name value="SMEAGOL"/>
       </station>
      
     </Devicemanager-Archive>

  4. In above scenario, the Color Engine Pilot knows  that two proof servers: OCTARINE and SMEAGOL. If you moved the proof server software from OCTARINE to GOLLUM, then you need to change the following:

     <Devicemanager-Archive>
      
       <station>
         <id value="0"/>
         <name value="GOLLUM"/>
       </station>
      
       <station>
         <id value="1"/>
         <name value="SMEAGOL"/>
       </station>
      
     </Devicemanager-Archive>

  5. Open the Color Engine Pilot and type in the VDTL shell: devicemanager_import.
• The bg_data_cmsdata was moved to another system (with another hostname).
  1. Make sure that the devicemanager folder and the procref folder are copied along to the new location (or just copy the complete w folder).

• Move one or more devices/ workflows from one proof server to another.

  1. Contact customer support in this case.