Chilkat UNLOCK

[skiman]

Hi,

I'm using Chilkat for a lot of stuff. Since the beginning of 2026 we also use it a lot for e-invoicing (peppol) which is the only way to send invoices from now on in Belgium.

I changed the UNLOCK in our application. I've read on Chilkat that you can unlock once in an application and it should remain active. So at the start of ourt application I have now:

Code: Select all

	oGlobal := CreateObject("Chilkat_9_5_0.Global")
	oGlobal:UnlockBundle(CHILKAT_CODE)

This was to prevent to unlock the bundle or a component hundreds time a day.
But now after a month it seems as this isn't working. Suddenly we get the message 'End of trial period' when using different chilkat component without unlocking each time.

Anyone who is unlocking once at the start of his application or is everyone unlocking each time they use a Chilkat component?

[Tom]

We use the unlock mechanism once within every routine that uses Chilkat. Unlocking takes almost no time. You are still using version 9.5.0?

[skiman]

Hi Tom,

Yes, that's what I was doing before and yes we are using 9.5. Since some time we are using it also for payment terminals. There we were getting errors while unlocking at one customer. They have really a lot of payments, so I thought this could be solved by avoiding the unlocking each time.

That payment system is a class, maybe it would work if I unlock in the init() instead of unlocking in each method.

I suppose that unlocking at the start of the application isn't valid when starting functions in another thread.

[Tom]

I suppose that unlocking at the start of the application isn't valid when starting functions in another thread.

I can't confirm this. Whereever I unlocked Chilkat and where-else-ever I call for the unlockStatus, it's not zero.
Seems like it even survives restarting the app.

Edit: This is what the docs say: "This value (the unlockStatus) is intentionally sticky. If a subsequent and redundant call to UnlockBundle happens, it is effectively a No-Op because the library is already unlocked. The UnlockStatus will not change. "

https://www.chilkatsoft.com/refdoc/xChi ... lockStatus

[Piotr D]

Hi,
Are you using Chilkat as reg-free? If not, was the library registered from a local drive?

Piotr

[skiman]

Hi,
Are you using Chilkat as reg-free? If not, was the library registered from a local drive?

Piotr

No, on each station Chilkat is registered. If not available on a station, there is a message to install it with integrated dowload and startup of the install.

[skiman]

Hi,

Today I had an unlockcomponent error.

This is the code where it happened:

Code: Select all

...
oMailServer := CreateObject("Chilkat_9_5_0.MailMan")
if !oMailServer:UnlockComponent(CHILKAT_CODE) = 1
...

This was the error:

Code: Select all

oError:args         :
          -> VALTYPE: U VALUE: NIL
          -> VALTYPE: C VALUE: ABOSVC.CB1xxxxxxxxxxxxxxxxxxxxxml  (This was my valid Chilkat licence key)
oError:canDefault   : N
oError:canRetry     : N
oError:canSubstitute: Y
oError:cargo        : NIL
oError:description  : Receiver of message is not an object.
oError:filename     : 
oError:genCode      :         38
oError:operation    : UnlockComponent
oError:osCode       :          0 
oError:severity     :          2
oError:subCode      :       2266
oError:subSystem    : BASE
oError:thread       :          3
oError:tries        :          0

It looks to me that CreateObject failed and that this fail was the cause of the UnlockComponent error.

[Tom]

I don't find the Method "UnlockComponent" in the docs für "MailMan". However, we only use the Global object for unlocking the bundle.

[Auge_Ohr]

hi,

Code: Select all

...
oMailServer := CreateObject("Chilkat_9_5_0.MailMan")
if !oMailServer:UnlockComponent(CHILKAT_CODE) = 1
...

i would say you have to check if "oMailServer" is <> NIL else you can´t call it´´s Method.

[Tom]

And maybe it's not created because the bundle was locked.