Scheduled job with ID 'conversionLoader' failed due to binary incompatibilities
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
While uploading the attachment in the newly installed Confluence, it gives an error message.
The following errors when trying to load the package upon the last startup of Confluence appears in the {{atlassian-confluence.log}}
2019-05-02 15:36:45,794 ERROR [Caesium-1-2] [atlassian.scheduler.core.JobLauncher] launchAndBuildResponse Scheduled job with ID 'conversionLoader' failed due to binary incompatibilities
-- referer: http://localhost:8099/setup/setupdata-start.action | url: /setup/setupdata.action | traceId: 8576b486aef5fb20 | userName: anonymous | action: setupdata
java.lang.ExceptionInInitializerError
Caused by: class com.aspose.slides.exceptions.ArgumentException: Culture Name: en-HK is not a supported culture
java.lang.Thread.run(Thread.java:748)
at com.aspose.slides.internal.ep.if.if(Unknown Source)
at com.aspose.slides.internal.ep.if.<init>(Unknown Source)
at com.aspose.slides.internal.ep.if.do(Unknown Source)
at com.aspose.slides.internal.e0.try.try(Unknown Source)
at com.aspose.slides.internal.du.break.<clinit>(Unknown Source)
... 30 moreDiagnosis
Check the configuration in Confluence UI by doing the following:
- Navigate to General Configuration > System Information
- Look for the following and check if it is set as {{user.language=zh}} and {{user.country=HK}}:
Cause
The 'System Locale' were not configured properly. From the above error, it seems like the settings are configured as:
-Duser.language=en
-Duser.country=HKResolution
The correct language localization should be zh-HK as per stated in this Oracle documentation
In order to change the locale settings the recommended way is to add the additional arguments user.language and user.country to the JVM parameters. The details steps for adding the parameters is explained in this article - Configuring System Properties
Example parameter for the above error:
-Duser.language=zh -Duser.country=HK