Home | Contact Us | Submit Troubleshooting Info | Search | Help
Output | Software Solutions | Proofing | Color, Screening and Calibration | Scanning | Digital Photography | Consumables | POS
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 |
Intel |
|
Operating system |
Windows 2000 Server |
|
|
|
||
Error |
||
|
|
||
Symptoms |
Archiver fails with the error :assertion failed: (nBytes == TotalFileSize) E 22May01 20:54:24.093-PDT [924.4520] YCS634-301 ARAXI PArchRetJTP.Medium Archive Thread: 4520 SEQM_Araxi10TapeFormat.cpp(857): assertion failed: (nBytes == totalFileSize) at line 857 in file SEQM_Araxi10TapeFormat.cpp i 22May01 20:54:26.562-PDT [3572.2376] YCS634-301 ARAXI PDeviceAndServiceD.XCON_Callback DASS_DatabaseMgr.cpp(431): The 'Archive' service has stopped. Z 22May01 20:54:26.640-PDT [3548.920] YCS634-301 ARAXI PTaskD.XCON_Callback TAKS_JobSub.cpp(1302): Archive:Archive: Message from Extreme: JTP used by an active process has disconnected from the coordinator: Archive:Archive/Retrieve. |
|
|
|
||
Cause |
Archiver will fail to archive a file that contains a SPARSE_BLOCK in it. This problem is happening with particular files (or better streams in them) that we do not see very often here; however, at one site, it happens more often apparently because of the way how they handle the file. It occurs on the NTFS5, which was introduced with W2K and NT4.0 SP4, so we might see it more often now. A SPARSE_BLOCK was one of the streams in the file. The problem with reproducing this bug is that the file cannot be copied, additional streams after SPARSE_BLOCK in the file are dropped when copied. |
|
|
|
||
Solution |
The only workaround is to make another copy of the file and back that up. The new file shouldn't have a sparse stream. The only problem is in identifying which files have sparse streams. In the mean time, try doing a selective archive of the files and when you hit the file with the sparse stream, the archive will fail. Another way to get around this would be to copy the entire job to another folder then rename the folder to the job name. This way you wouldn't have to worry about which files were bad. You should be able to archive the job in one shot. Permanent fix: Prinergy 2.0 |
|
|
|
||
See also |
||
|
|
||
Keywords |
archiver |
|
|
|
||
Technical contact(s) |
Amy Chan |
|
Submitted by |
Amy Chan |
|
Date submitted |
||