Author Topic: Opening PDFs using thick Client 32-bit Error  (Read 778 times)

JMichael

  • Jr. Member
  • **
  • Posts: 22
    • View Profile
Opening PDFs using thick Client 32-bit Error
« on: June 07, 2024, 09:13:27 AM »
Hello everyone,
When Opening PDFs using thick Client 32-bit, I now get the error below.  Please note that, I recently had the Client & Admin reinstalled onto my workstation.  Any reason or where I should check to resolve this issue?

" \plug_ins\ARSPDF32.API could not be loaded "

Justin Derrick

  • IBM Content Manager OnDemand Consultant
  • Administrator
  • Hero Member
  • *****
  • Posts: 2234
  • CMOD Guru for hire...
    • View Profile
    • Tenacious Consulting
Re: Opening PDFs using thick Client 32-bit Error
« Reply #1 on: June 09, 2024, 04:15:41 PM »
Sounds like the new version didn't include the requisite APIs/DLLs/Plugins.
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

Ed_Arnold

  • Hero Member
  • *****
  • Posts: 1213
    • View Profile
Re: Opening PDFs using thick Client 32-bit Error
« Reply #2 on: June 11, 2024, 10:38:50 AM »
JMichael - take a look at this:

Unable to create new Content Manager OnDemand application groups for PDF documents either manually or automatically from the Report Wizard in the OnDemand Administrator client

https://www.ibm.com/support/pages/node/6997647

Especially the section about which is installed first, Adobe or the CMOD client.

Ed

#zOS #ODF

JMichael

  • Jr. Member
  • **
  • Posts: 22
    • View Profile
Re: Opening PDFs using thick Client 32-bit Error
« Reply #3 on: June 14, 2024, 09:57:54 AM »
Will try this, thanks.

JMichael

  • Jr. Member
  • **
  • Posts: 22
    • View Profile
Re: Opening PDFs using thick Client 32-bit Error
« Reply #4 on: June 14, 2024, 10:37:21 AM »
Hi Ed,
Those procedures resolved the issue.  Thanks!