OnDemand User Group

Support Forums => Report Indexing => Topic started by: Justin Derrick on October 02, 2012, 06:36:22 AM

Title: arsload mysteriously exits when loading PDFs...
Post by: Justin Derrick on October 02, 2012, 06:36:22 AM
A customer of mine has a strange issue.  We're trying to load PDF data from windows (Win 7, 64-bit with CMOD 8.5.0.6 + the PDF Indexer) to AIX (AIX 6.1, CMOD 8.5.0.5, DB2 9.7) and arsload fails immediately with no useful diagnostic information - see the attachment for an example.

We've tried re-installing, upgrading CMOD from 8.5.0.5 to 8.5.0.6 on the Windows platform, and nothing seems to get arsload working.  We're able to get the PDF to index (by creating a local copy of the parameter file, running arspdoci on the PDF to be loaded) and then by re-issuing the arsload command, we can get it to load -- but arsload just seems to choke.

Does anyone have any tips or tricks for remote loading of PDFs from Windows to a CMOD server on a UNIX platform?  Is there something we're missing?

Thx.

-JD.

Title: Re: arsload mysteriously exits when loading PDFs...
Post by: iravjani on November 20, 2012, 01:03:36 AM
Hello,

I had the same issue and go it resolved through IBM Tech Support, the issue was I didn't have enough rights on the C:/ drive to run ARSLOAD.

What he did was just gave FULL CONTROL to 'Everyone' to the C Drive or the directory in which the arsload bin command folder.

Try this out hope it resolves your issue...

Best,
Title: Re: arsload mysteriously exits when loading PDFs...
Post by: demaya on November 20, 2012, 09:41:24 AM
Hi,

we had the same with german umlauts (?) and the conversion to the valid version in uppercases (ss) in index files. I think you have to open a PMR, since there are no helpful informations.

Cheers
Title: Re: arsload mysteriously exits when loading PDFs...
Post by: Justin Derrick on November 20, 2012, 06:15:04 PM
Thanks for the replies -- it turns out that we were executing arsload from OUTSIDE the directory where the PDFs were located.  Once we were inside the same directory as the PDF file, loads began working.  So, for future reference, you can't just point to a path where the file is located, you need to run arsload from INSIDE the directory where the files are.

Thanks again folks!

-JD.