Author Topic: Graphical Indexer  (Read 64 times)

Steve Lance

  • Jr. Member
  • **
  • Posts: 27
    • View Profile
Graphical Indexer
« on: August 31, 2020, 04:36:42 PM »
We have upgraded our Windows server to 2016 servers for PDF/Indexer.  We have a graphical indexer file that keeps failing.  The name is RUBY2-V01.WR687P01-V01.WR687R01.pdf.08312020.094751.ARD.  We are receiving the error:

2020-08-31 17:06:34.358032: ARS4315I Processing file >f:\TLoad44\IDP-V02.BI610P01-V08.318483.2020.08.30.ARD<
2020-08-31 17:06:34.358032: ARS4334I Load Version <10.5.0.0>  Operating System <Windows 64> <10.0.14393.2430>  OS Userid <ADMIN>  Install Location <F:\Program Files\IBM\OnDemand\V10.5\>
2020-08-31 17:06:34.358032: ARS4335I Server Version <10.5.0.0>  Operating System <z/OS> <04.26.00>  Database <DB2> <12.01.0005>
2020-08-31 17:06:34.367029: ARS4339I Application Group >IDP-V02<
2020-08-31 17:06:34.367029: ARS4340I Application >BI610P01-V08<
2020-08-31 17:06:34.367029: ARS4341I Storage Set >SGTEST01.MCRDTST<
2020-08-31 17:06:34.367029: ARS4342I Storage Node >TOD.V7.SGTEST01.MCRDTST<
2020-08-31 17:06:34.367029: ARS4347I Encryption >None<
2020-08-31 17:06:34.369154: ARS4302I Indexing started, 2227128 bytes to process
                          : 'F:\Program' is not recognized as an internal or external command,
                          : operable program or batch file.
2020-08-31 17:06:34.548111: ARS4309E Indexing failed
2020-08-31 17:06:34.548111: ARS4324E File >f:\TLoad44\IDP-V02.BI610P01-V08.318483.2020.08.30.ARD< renamed to >f:\TLoad44\IDP-V02.BI610P01-V08.318483.2020.08.30.ARD.Failed<.  Correct problems and resubmit file.
2020-08-31 17:06:34.548111: ARS4318E Processing failed for file >f:\TLoad44\IDP-V02.BI610P01-V08.318483.2020.08.30.ARD<

We think we have fixed this error but now receiving:
2020-08-31 18:36:08.047423: ARS4315I Processing file >F:\TLoad44\IDP-V02.BI610P01-V08.318483.2020.08.30.ARD<
2020-08-31 18:36:08.047423: ARS4334I Load Version <10.5.0.0>  Operating System <Windows 64> <10.0.14393.2430>  OS Userid <ADMIN>  Install Location <F:\Program Files\IBM\OnDemand\V10.5\>
2020-08-31 18:36:08.047423: ARS4335I Server Version <10.5.0.0>  Operating System <z/OS> <04.26.00>  Database <DB2> <12.01.0005>
2020-08-31 18:36:08.047423: ARS1110E The application group >2020< does not exist or user >ADMIN< does not have permission to access the application group
2020-08-31 18:36:08.047423: ARS4324E File >F:\TLoad44\IDP-V02.BI610P01-V08.318483.2020.08.30.ARD< renamed to >F:\TLoad44\IDP-V02.BI610P01-V08.318483.2020.08.30.ARD.Failed<.  Correct problems and resubmit file.
2020-08-31 18:36:08.047423: ARS4318E Processing failed for file >F:\TLoad44\IDP-V02.BI610P01-V08.318483.2020.08.30.ARD<

Any ideas?

Thank you

Steve Lance

  • Jr. Member
  • **
  • Posts: 27
    • View Profile
Re: Graphical Indexer
« Reply #1 on: August 31, 2020, 04:40:41 PM »
Also, we are upgrading from 10.1 to 10.5.

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 1903
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Graphical Indexer
« Reply #2 on: September 01, 2020, 06:41:50 AM »
Can you provide the actual arsload command you're running?  Or is arsload running as a daemon?

Both errors seem like they might be related to problems with having spaces in file paths or AG names.

-JD.
IBM CMOD Professional Services: http://TenaciousConsulting.com
Call:  +1-866-533-7742  or  eMail:  jd@justinderrick.com
IBM CMOD Wiki:  https://CMOD.wiki/
FREE IBM CMOD Education & Webinars:  https://CMOD.Training/

Interests: #AIX #Linux #Multiplatforms #DB2 #TSM #SP #Performance #Security #Audits #Customizing #Availability #HA #DR

spond

  • Newbie
  • *
  • Posts: 7
    • View Profile
Re: Graphical Indexer
« Reply #3 on: September 02, 2020, 05:50:36 AM »
This issue looks it may be remedied by enabling short names on the Windows 2016 server. - applicable when there are embedded spaces in the installation path. You can find details here:

https://www.ibm.com/support/pages/content-manager-ondemand-installation-considerations-windows