Skip to main content
N
nigel_long
Known Participant
September 6, 2012
Question

FRAMEMAKER10 CLIENT .DLLs - 'NOT INITIALISED 'MESSAGE

  • September 6, 2012
  • 1 reply
  • 750 views

Hi -

Thanks to assist from Markus and Russ a little while back, I was able to re-compile some old API clients that were developed using Frame 7.1 / Visual Studio 6 in a Frame10 / VS2010 environment.

However, when I passed my dlls to a colleague to test on his PC, he started getting the old generic 'cannot initialise client [path] check for errors in the APIclient...etc' message. The dlls seem to work ok on my PC. These are both XP machines.

I also created a WIN7 virtual desktop (since we are gearing up to migrate from XP to WIN7) and installed Frame10 - I got the message again. I wondered if it is anything to do with security settings - presumably VS2010 is a lot more sophisticated than the 20yr old VS 6 we were using? 

Is there anything additional I need to 'switch on' in VS2010 when I'm compiling? Do I need to set it to 'publish' or allow it to run on a machine or network other than my own PC? Is it failing to run because of Microsoft security settings or policies? Any ideas?

Thanks, Nigel

    This topic has been closed for replies.

    1 reply

    R
    Russ Ward
    Legend
    September 7, 2012

    Hi Nigel,

    I don't have any additional ideas other than what we discussed before. But just to reiterate (and emphasize), the two important things that I had to do to stop the crashes:

    - Change the preprocessor definition from _DEBUG to NDEBUG and remove _USRDLL

    - Always use the same versions of the FDK and FM. It is said that earlier versions of the FDK should work with later versions of FM, but I know for sure that vice-versa will invite much crashing. After all the problems I had, I take no chances any more... if it is FMxyz, I use FDKxyz.

    Your problems are so reminiscent of mine, where everything runs great on the dev machine, but then crashes immediately on somebody else's. Once I did the two things above, that stopped. I really hope you can figure this out, because corny as it sounds, I feel your pain. This situation is very frustrating and sometimes feels a bit hopeless.

    Russ

    N
    nigel_longAuthor
    Known Participant
    September 12, 2012

    Hi Russ - many thanks for your suggestions and kind words of encouragement - much appreciated.

    I'm pretty sure I tweaked it to do _DEBUG to NDEBUG and remove _USRDLL

    But will re-check. Also pretty sure my FDK / FM set-ups are in-line, but will also double-check.

    Yep, running fine on a Dev machine, but not another XP machine or a WIN7 test-rig.

    I did add a Windows SDK to my own Dev machine, which won't be on my colleague's machine, so may try putting that on his PC or another test machine... maybe there is some library / dll stuff that's required by the VS2010 set-up I used to compile...

    Thanks! Nigel

    N
    nigel_longAuthor
    Known Participant
    September 12, 2012

    Double-checked all of the above and it looked fine.

    Out of interest, I have just 'built' a new Frame10 installation on another XP box in our department and my APIs run fine, like they do on my own PC; I'm forced to the conclusion that my colleague - who works in another area - has some sort of local config difference on his PC or different permissions (though we checked te security sid eof things).

    So, I've proved I can port my Frame10 environment to other XP PCs (though not his!) and I'm fine with that. :-)

    Nigel

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