Author Topic: arspdoci trace information  (Read 2535 times)

jw

  • Guest
arspdoci trace information
« on: October 04, 2013, 10:44:44 AM »
Hi,
I am currently using 8.5.0.5 and I have a problem with a PDF when using PDF indexer.

So, I tried to use arspdoci with the tracedd=filen.trace parameter.

the syntax was:

arspdoci parmdd=filen.parms inputdd=filen.pdf outputdd=filen.out indexdd=filen.ind tracedd=filen.trace


and I am getting the following in the file filen.trace

^A^A^D?^C?^F6.1^PARSPDOCI^N8.5.0.5^A^H^A,RN?RRN?T^N/|^An^B??^A^E^A  arspdoc.C^RArspSearchDocPages^EL^C^H^A^^ArspSearchDocPages loop failed^F
bufArcChar.Expected a dict object.^F^EszBuf^R536936462




I am expecting something like the following:


COORDINATES=IN
ARSPDOCI completed code get_keyword <------------------
ARSPDOCI completed code get_keyword 003 ------------------>
TRIGGER1=UL(7.00,0.25),LR(7.70,0.57),*,'Page:'
ARSPDOCI completed code get_keyword <------------------
ARSPDOCI completed code get_keyword 003 ------------------>
ARSPDOCI completed code parse_trigger <----------------
ARSPDOCI completed code parse_quoted_parm <----------------
ARSPDOCI completed code parse_quoted_parm 001 ---------------->
ARSPDOCI completed code parse_trigger 001 ---------------->
FIELD1=UL(7.00,0.48),LR(7.90,0.77),0,(TRIGGER=1,BASE=0)
ARSPDOCI completed code get_keyword <------------------
ARSPDOCI completed code get_keyword 003 ------------------>
ARSPDOCI completed code parse_field <----------------
ARSPDOCI completed code parse_subfields <----------------
ARSPDOCI completed code get_keyword <------------------
ARSPDOCI completed code get_keyword 003 ------------------>
ARSPDOCI completed code get_keyword <------------------
ARSPDOCI completed code get_keyword 003 ------------------>
ARSPDOCI completed code parse_subfields 001 ---------------->
ARSPDOCI completed code parse_field 001 ---------------->
FIELD2=UL(6.11,1.39),LR(7.15,1.57),0,(TRIGGER=1,BASE=0)
ARSPDOCI completed code get_keyword <------------------
ARSPDOCI completed code get_keyword 003 ------------------>
ARSPDOCI completed code parse_field <----------------
ARSPDOCI completed code parse_subfields <----------------
ARSPDOCI completed code get_keyword <------------------


Does anyone know what I have done wrong?

Thanks in advance for your help.

-jw


Frederick Tybalt

  • Full Member
  • ***
  • Posts: 124
    • Personal Website
Re: arspdoci trace information
« Reply #1 on: October 07, 2013, 07:42:14 AM »
Did you try arstfmt -i <trace.log>
rIcK
======------------------======
www.rick.co.in | www.tekbytz.com

jw

  • Guest
Re: arspdoci trace information
« Reply #2 on: October 07, 2013, 09:12:34 AM »
Rick,

Thank you very much.  This is what I missed.

-jw

CMOD-user

  • Jr. Member
  • **
  • Posts: 15
arspdoci trace information
« Reply #3 on: March 21, 2021, 12:46:51 AM »
I used the arstfmt option to trace and got the below in the CLI.

ARS1122E Unable to open the  to UCS-2 icu converter
fatal error 'invalid document structure' at line: 1

What am I missing?
icu dlls are in place as below with the size in bytes.
       988,080 icucnv40.dll
       95,080 icudt40.dll
       3,072 icudt58.dll
       393,728 icuhb58.dll
       2,115,584 icuin58.dll
       53,760 icuio58.dll
       1,512,448 icuuc58.dll

I am in 10.5.0.1 in Windows 2019 server, with an error on arsload, that works in CMOD 9.0. Did not change the PDF indexer parameters. PDF indexer 10.5 is installed.
Acrobat  Reader DC is installed.

How do we resolve the UCS-2 converter issue?

Thank you