Inspiring

Question

Cannot initial API client in patched FM 2017

Forum|Forum|9 years ago
May 3, 2017
4 replies
2416 views

I have an FDK client that was developed in FM 12. While I did not test it extensively in the original release of FM 2017, it seemed to work. With the patch installed, it does not initialize (the "Cannot initialize API client ..." alert appears when I launch the patched FM 2017). Other older FDK clients initialize successfully with the patch.

What has changed that would affect some clients but not others? Does this one need to be recompiled?

Scripting

This topic has been closed for replies.

K

ksaini

Adobe Employee

Hi,

Due to Xerces version number update some plugins that were using Xerces may not work.

We suspect these errors are coming because of this change.

Plugins should update to accommodate with new version of xerces, as a workaround please try with placing attached dll to fm_home.

Please try this solution and let us know if issue is still there.( remane .txt to .dll.)

http://ftp://cust-dl:$MPLr65489@sjftp.adobe.com/PPBU/File.zip

Thanks

Kunal

A

ASJonnyBe

Known Participant

Lynne,

I have come across this with our plugins where I had inadvertently put a debug DLL on a system that did not have either of Visual Studio or the FDK installed, or with an incorrect version of a c# managed DLL, used by a plugin.

It would be useful if the actual problem causing the initialization to fail was reported.

Have you looked at the event log? As an example I see some crashes being reported there with the DLL that had the exception listed.

Jon

frameexpert

Community Expert

I noticed the same issue with one of the DLLs that comes with FrameScript. It showed up after I installed the latest FrameMaker 2017 update.

www.frameexpert.com

R

Russ Ward

Legend

Lynne, this error is usually indicative of a more serious problem, not a small change to the interface. The most common reason is that the DLL file is registered in maker.ini but simply doesn't exist. I'm sure you accounted for this possibility, but I'm just mentioning it to be thorough. Other reasons include an incompatibility between libraries, or possible a DLL compiled with dependencies that are not present in the applicable FM version.

What resources do you have at your disposal? Do you have the source code?

Russ

L

Lynne A. PriceAuthor

Inspiring

Rick,

Has the problem been fixed? Is the DLL that no longer works the one used as a custom client to allow FrameScript to be used during SGML/XML import and export? (I ask because the one that no longer works for me is an import/export client.)

--Lynne

frameexpert

Community Expert

Yes, as a matter of fact it does. FrameScript has 2 DLLs and the one that deals with structured import/export won't load with the latest update.

FslStruct=Standard,FrameScript Struct Import/Export,C:\Program Files (x86)\FrameScript6\FslStruct6_130.dll,structured

www.frameexpert.com

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded