Skip to main content
T
Trevor-Nicholls
Inspiring
December 20, 2024
Question

Missing DLL being reported on XML file load

  • December 20, 2024
  • 2 replies
  • 513 views

Hi

I have FrameMaker 2022 17.0.5.725 installed on my laptop and use it to maintain a structured application which requires XSL transformations on XML load and save. I have a modified maker.ini file which specifies a different path for the SAXON XSL processor rather than the one which us delivered with FrameMaker. Everything is working fine in my environment.

This week I have been inducting a colleague into the FrameMaker world so that they can take over some of the responsibilities for the application. We've installed the identical version of FM, correctly specified the Saxon path for their environment, and gone through loading, editing and saving a number of our documents. So far as we can tell the inputs and outputs are identical, but when their FM runs the import or export XSL transform, their FM console echoes the following line hundreds or thousands of times:

There are two autorec.dll libraries, one is in "Program Files\Adobe\Adobe FrameMaker 2022\Legacy32" and the other is in "Program Files\Adobe\Adobe FrameMaker 2022\filters". Both of us have both of these libraries. I presume it is the DLL in filters that is being accessed (or not), but I cannot for the life of me see why my installation is locating it while my colleague's is not.

It's not a maker.ini problem or a failed installation/upgrade. I'm not sure what else it could be though. The DLL is there, my laptop sees it, theirs does not.

Anything else I could check?

cheers

T

 

    2 replies

    S
    s-onishi
    Inspiring
    January 22, 2025

    https://www.microsoft.com/en-US/download/details.aspx?id=40784

      T
      Trevor-NichollsAuthor
      Inspiring
      January 22, 2025

      Thank you for your suggestion. I don't see the relevance though.

      Despite the transform reporting that it can't find the DLL, both machines have DLLs of the same name in the same locations; one instance of Frame reports an error, the other does not. Neither of us have (or need) Visual Studio.

      Jeff_Coatsworth
      Community Expert
      Jeff_CoatsworthCommunity Expert
      Community Expert
      January 22, 2025

      I'd give the FM folks a ping - see https://helpx.adobe.com/contact/enterprise-support.other.html#framemaker for your Adobe Support options. I'd recommend using the tcssup@adobe.com e-mail address as it reaches a team dedicated to Technical Communication Suite products including FrameMaker.

      Jeff_Coatsworth
      Community Expert
      Jeff_CoatsworthCommunity Expert
      Community Expert
      December 23, 2024

      Has the DLL been installed on your machine? Maybe there's a Registry entry for it on yours that doesn't exist on theirs?

      T
      Trevor-NichollsAuthor
      Inspiring
      December 25, 2024

      There's no DLL of that name in my registry (where I don't get this message). I'll check with my colleague after the holiday break and see if it is found in theirs.

      A thought I have just had is to check if there is a different file association for XML files on their machine, because that might trigger a filter step when loading the document that isn't considered necessary on mine.

      Terms & ConditionsAccessibility statement
      Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices