On Thu, Mar 05, 2009 at 03:58:52PM -0600, Jewel wrote:
> I am running Dspace version 1.5.1 on a Windows 2003 box. We have loaded
> very little into our collection. I can't make out what the error means.
> Below is the error I receive after running: dsrun
> org.dspace.app.mediafilter.MediaFilterManager
> /
> E:\dspace\bin>dsrun org.dspace.app.mediafilter.MediaFilterManager
> Using DSpace installation in: E:\dspace
> ERROR filtering, skipping bitstream:
>
> Item Handle: 10425/53
> Bundle Name: ORIGINAL
> File Size: 11301578
> Checksum: 4a6333832dc9b7ee8704b2c0ec735bbe (MD5)
> Asset Store: 0
> java.io.IOException: Invalid header signature; read 3759996809423114277,
> expected -2226271756974174256
> java.io.IOException: Invalid header signature; read 3759996809423114277,
> expected -2226271756974174256
> at
> org.apache.poi.poifs.storage.HeaderBlockReader.<init>(HeaderBlockReader.java:88)
It sure would be nice if the message indicated which bitstream had the
problem, no? It appears that one of the bitstreams attached to item
53 is either a corrupt MS Office document, or is not an MS Office
document at all but DSpace believes it is one. (POI is the library
that DSpace uses to extract text from MS Word documents.)
If there is only one Office document attached to item 53, that is the
culprit. If there are more than one, examine each until you find the
problematic one. If there are no bitstreams that should be treated as
Office documents, check the associated format of each bitstream to see
if it matches the content type you would expect.
--
Mark H. Wood, Lead System Programmer mw...@IUPUI.Edu
Friends don't let friends publish revisable-form documents.