The null-IV migration for application_link_client processed 100 rows with 0 errors.

[Vox]

Hi,

Just upgraded from 8.13.1 to 9.0.6 and looking at the system activity logs I am seeing the following for every 5 minute cron run:

The null-IV migration for application_link_client processed 100 rows with 0 errors.

Any idea what this is?

[K n K Web Services]

Yeah, that's normal — nothing wrong on your end.

WHMCS tightened up their encryption in 9.0, and part of that is fixing some older data (application_link_client — your cPanel/WHM SSO tokens) that was encrypted with a static/null IV instead of a proper random one. Not great practice, so they're fixing it.

Instead of doing it all at once during the upgrade and risking locking things up, they just run it in the background — 100 rows every cron cycle until it's all converted. Once it's done, the log entry stops showing up.

Check System Health (Configuration > System Health) if you want to see the actual progress/status of it. But otherwise just let it run, it'll finish on its own.

[WHMCS Ricardo]

21 hours ago, Vox said:

The null-IV migration for application_link_client processed 100 rows with 0 errors.

Hey Vox

I can confirm the issue.

The case WHMCS-27325 is open with our developers in order to have this reviewed for future releases.

Whilst the technical support team cannot provide an estimated time for completion for this, once we resolve cases and push features, they are available in our change log at https://changelog.whmcs.com/

I apologize for the inconvenience, and appreciate your patience as we work to resolve this.

Thanks again for taking the time to report your findings.

[Vox]

@K n K Web Services and @WHMCS Ricardo,

Thanks for the update guys, much appreciated.

[pRieStaKos]

@Vox Fix is included in v. 9.0.7 (maintenance), that was released today.

Edited August 25 by pRieStaKos

[Vox]

@pRieStaKos 

Thanks for the update.

Kind Regards

[websolutionzoneUAE]

Yes, that behavior can be expected after upgrading to WHMCS 9.x. The background migration approach is actually a sensible way to handle older encrypted data without making the upgrade process unnecessarily disruptive.

If the conversion is processing a limited number of records on each cron run, I’d let the scheduled cron jobs complete rather than trying to manually modify the data. Checking Configuration → System Health is also a good way to confirm that the migration is progressing normally.

It’s also worth making sure WHMCS cron is running reliably. If the conversion appears stuck for an unusually long time, then checking the cron logs and WHMCS activity logs would be the next step.