Hi Emile,
I'm afraid we will need to know the steps you did to get to this situation.
Presuming you are trying to achieve something that is covered on this page and thus using WS-Security...
I might be totally wrong with my assumptions, but...if you were using automation tools to convert your old code and make it ACE v13 compatible, then most probably you should have that BizagiPartyManagementServicesLIB library referenced from the BizagiCreateParty-5.2.5 Application. If something failed during conversion and you ended up with no link between the two, try adding it manually in ACE Toolkit.
Another option is to take the original code and step-by-step rework into ACE v13 Application without shared libraries. Then try build and deploy the Application. If it works compare (manually or using AI) the resulting code with the code provided by automation tool. Then manually externalise the reusable pieces of code into BizagiPartyManagementServicesLIB and deploy again. If this version works, compare it with automated code.
If my suggestions look too complex or not relevant, please provide more details about the code you currently have and how you got (I assume from the code that worked before) to the currently observed error message.
------------------------------
Jevgenijs Jefimovs
------------------------------
Original Message:
Sent: Fri April 10, 2026 07:17 AM
From: Emile Kearns
Subject: TADataCollector V13.0.6.0 on Linux - multiple IIB42 errors
Thanks.
How do I , and can I bypass the below error? I am aware that we have not moved to shared libraries but still used static libraries.
BIP1239E: Application 'BizagiCreateParty-5.2.5' references shared library 'BizagiPartyManagementServicesLIB', which is not deployed to the integration server.
------------------------------
Emile Kearns
------------------------------
Original Message:
Sent: Fri April 10, 2026 03:57 AM
From: Jevgenijs Jefimovs
Subject: TADataCollector V13.0.6.0 on Linux - multiple IIB42 errors
Hi Emile,
I'd suggest to use the latest ACE v13 version and consider this page for more information on changes introduced in v13.0.7.0 related to WS-Security.
This should help with most of the WS-Security issues that you see on v13.0.6.0.
If you are sure Security (any kind) is disabled, please share screenshots for us to confirm that.
------------------------------
Jevgenijs Jefimovs