![]()
Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
|
|
||
Product |
Prinergy Connect 2.0 | |
Platform |
||
Operating system |
||
|
|
||
Error |
W 24Jan02 19:15:10.140-GMT-3 [3912.5068] YCS273-146 ARAXI PArchRetJTP.Medium Retrieve Thread: 5068 SEQM_Araxi10TapeFormat.cpp(1159): Archive header has wrong magic number: 192120118 E 24Jan02 19:15:10.140-GMT-3 [3912.5068] YCS273-146 ARAXI PArchRetJTP.Medium Retrieve Thread: 5068 SEQM_SequentialMediaIO.cpp(690): Verify of save set header failed. Device = \\.\Tape1, Archive ID = 1f73a60f-fb4a-4f7b-8c9c-80f828fc88ee. Error = 11 E 24Jan02 19:15:10.140-GMT-3 [3912.5068] YCS273-146 ARAXI PArchRetJTP.Medium Retrieve Thread: 5068 NTMS_RemovableMedium.cpp(1147): Open of archive failed. Status = 11Medium ID = 4e9d37d7-42f5-4f4f-88ae-45bcb6710f73 Medium name = Offline_Janeiro2002_2 NTMS logical medium ID = 274d175e-4714-468e-ac42-f0392ee2c2e2 E 24Jan02 19:15:10.156-GMT-3 [3912.5068] YCS273-146 ARAXI PArchRetJTP.Medium Retrieve Thread: 5068 AMDM_Medium.cpp(575): Open of archive failed. Status = 11 W 24Jan02 19:15:10.156-GMT-3 [3912.5068] YCS273-146 ARAXI PArchRetJTP.Medium Retrieve Thread: 5068 AJTP_MediumRetrieve.cpp(138): Save set header is invalid. Will attempt to continue. W 24Jan02 19:15:33.171-GMT-3 [3912.5068] YCS273-146 ARAXI PArchRetJTP.Medium Retrieve Thread: 5068 SEQM_Araxi10TapeFormat.cpp(1236): File header has wrong magic number: 2892347612 E 24Jan02 19:15:33.171-GMT-3 [3912.5068] YCS273-146 ARAXI PArchRetJTP.Medium Retrieve Thread: 5068 SEQM_SequentialMediaIO.cpp(1086): Failed to get file from tape. Device = \\.\Tape1, file = \\YCS273-146\AraxiVolume_YCS273-146_G\Jobs\Col_Congresso_2002_vol_01\UserDefinedFolders\Input PDF\000I_0XVIII.pdf. Error = 11 |
|
|
|
||
Symptoms |
Prinergy Archiver may incorrectly overwrite saved sets of archives of a newly allocated tape. The status of the tape is not changed (internally within Prinergy) from new to allocated when multiple tasks are trying to use a new tape at the same time. Retrieve fails with the error message, "Archiver header has wrong magic number:...." |
|
|
|
||
Cause |
When Prinergy allocates a new tape, it flags that tape as new. This means that the first task that writes an archive to the tape will put a new header on the tape, identifying it as a Prinergy tape. In minor updates 2.0.5.13 and 2.0.7.13, we do not correctly change the status of the tape (internally within Prinergy) from new to allocated when multiple tasks are trying to use a new tape at the same time. | |
|
|
||
Solution |
Apply patch 2.0.7.15 or 2.0.5.14. Below workaround applies to all 2.0 systems proir to 2.0.7.15, even those without 2.0.5.13, 2.0.7.13, or 2.0.7.14, as it is safer to perform the registry update in case someone installs 2.0.5.13 or 2.0.7.13 accidentally. Preferred method: Update the registry to allow Archiver to only archive to one task at a time. This method allows the customer to keep all benefits of minor update 2.0.5.13 or 2.0.7.14, including the fix for purge processing, and to load minor update 2.0.5.14/2.0.7.14. 1. Change the value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Creo\Araxi\2.0.4.bld69\Default\AMDM\TotalDriveScalingFactor. 2. Stop and restart the ParchRet.JTP. Note: The registry value depends on how many drives are connected to the sytem; if the customer has a library, you must determine how many drives are inside the library, including the drive for backup. i) If there is one drive, set the value to 10. ii) If there are 2 drives, set the value to 5. iii) If there are 3-4 drives, set the value to 4. iv) If there are 5-6 drives, set the value to 2. This is a drive scaling factor, measured in tenths, that indicates the percentage of available drives to allocate for Prinergy tasks. IMPORTANT NOTE: If you apply patch 2.0.7.15 or 2.0.5.14, the registry value will change it back to 10. Alternate method: Uninstall 2.0.5.13/2.0.7.13. For a customer who cannot live with processing only one task at a time, another option is to uninstall the offending minor update, although this is not recommended. If a customer chooses this option, they should be vigilant about checking that archives to all selected pools have completed successfully before purging a job. Permanent fix: Prinergy 2.0 |
|
|
|
||
See also |
||
|
|
||
Keywords |
archiver, archiver - retrieve |
|
|
|
||
Technical contact(s) |
Amy Chan |
|
Submitted by |
Amy Chan |
|
Date submitted |
25 Jan 2002 |
|