We ran the "pre-run migration checks" on thuesday and everything was fine. Today the migration report give us "We couldn't check for entities with public access".
After searching around we found nothing about this specific error.
We also successufly migrated 3 projects the week before without any error. Today even those three projetcs shows up with the error when we test the pre-run migration on them.
Anything we are missing?
@René Forgues Did you upgrade the JCMA version between Tuesday and Now?
I was able to fix/workaround the problem by downgrading JCMA from version 1.12.14 to version 1.12.12
.
.
.
I am also having this problem today; I opened a support ticket.
While waiting for support to respond... I'm reading the documentation links Mark - Devoteam provided.
The error appears in the atlassian-jira-migration.log for me:
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'dbo.AO_D9132D_ISSUE_SOURCE'
2024-11-30 10:50:36,478 JCMA-ExecutorService-pool-2-thread-159 ERROR edwin 649x2308x1 186v5ig 10.126.65.139 /rest/migration/latest/plan/details/XXX [jira.migration.preflight.AsyncCheckExecutor] Pre-flight execution error occurred for check type AnonPermission
java.util.concurrent.ExecutionException: com.querydsl.core.QueryException: Caught SQLServerException for select "AO_D9132D_ISSUE_SOURCE"."ID", "AO_D9132D_ISSUE_SOURCE"."CONVERSION_FACTOR", "AO_D9132D_ISSUE_SOURCE"."PLAN_ID", "AO_D9132D_ISSUE_SOURCE"."SOURCE_TYPE", "AO_D9132D_ISSUE_SOURCE"."SOURCE_VALUE" from "dbo"."AO_D9132D_ISSUE_SOURCE" "AO_D9132D_ISSUE_SOURCE" where 1 = 2
at java.util.concurrent.FutureTask.report(FutureTask.java:122)
at java.util.concurrent.FutureTask.get(FutureTask.java:192)
at com.atlassian.jira.migration.preflight.AsyncCheckExecutor$Companion.extractResult(AsyncCheckExecutor.kt:387)
at com.atlassian.jira.migration.preflight.AsyncCheckExecutor$Companion.access$extractResult(AsyncCheckExecutor.kt:376)
at com.atlassian.jira.migration.preflight.AsyncCheckExecutor$persistWhenDone$1.onFailure(AsyncCheckExecutor.kt:259)
at com.google.common.util.concurrent.Futures$6.run(Futures.java:1310)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.querydsl.core.QueryException: Caught SQLServerException for select "AO_D9132D_ISSUE_SOURCE"."ID", "AO_D9132D_ISSUE_SOURCE"."CONVERSION_FACTOR", "AO_D9132D_ISSUE_SOURCE"."PLAN_ID", "AO_D9132D_ISSUE_SOURCE"."SOURCE_TYPE", "AO_D9132D_ISSUE_SOURCE"."SOURCE_VALUE" from "dbo"."AO_D9132D_ISSUE_SOURCE" "AO_D9132D_ISSUE_SOURCE" where 1 = 2
at com.querydsl.sql.DefaultSQLExceptionTranslator.translate(DefaultSQLExceptionTranslator.java:50)
at com.querydsl.sql.Configuration.translate(Configuration.java:459)
at com.querydsl.sql.AbstractSQLQuery.fetch(AbstractSQLQuery.java:502)
at com.atlassian.jira.migration.export.db.advancedroadmaps.IssueSourceDataReader.getAllIssueSourcesForPlans$lambda$8(IssueSourceDataReader.kt:87)
at com.atlassian.pocketknife.internal.querydsl.DatabaseAccessorImpl.lambda$execute$0(DatabaseAccessorImpl.java:69)
at com.atlassian.sal.core.rdbms.DefaultTransactionalExecutor.executeInternal(DefaultTransactionalExecutor.java:86)
at com.atlassian.sal.core.rdbms.DefaultTransactionalExecutor.lambda$execute$0(DefaultTransactionalExecutor.java:42)
at com.atlassian.jira.database.DatabaseAccessorImpl.runInManagedTransaction(DatabaseAccessorImpl.java:125)
at sun.reflect.GeneratedMethodAccessor427.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.plugin.util.ContextClassLoaderSettingInvocationHandler.invoke(ContextClassLoaderSettingInvocationHandler.java:26)
at com.sun.proxy.$Proxy374.runInManagedTransaction(Unknown Source)
at sun.reflect.GeneratedMethodAccessor427.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:136)
at com.sun.proxy.$Proxy374.runInManagedTransaction(Unknown Source)
at com.atlassian.sal.jira.rdbms.JiraHostConnectionAccessor.runInStartedOrExistingTransaction(JiraHostConnectionAccessor.java:130)
at com.atlassian.sal.jira.rdbms.JiraHostConnectionAccessor.execute(JiraHostConnectionAccessor.java:60)
at com.atlassian.sal.core.rdbms.DefaultTransactionalExecutor.execute(DefaultTransactionalExecutor.java:39)
at com.atlassian.pocketknife.internal.querydsl.DatabaseAccessorImpl.execute(DatabaseAccessorImpl.java:67)
at com.atlassian.pocketknife.internal.querydsl.DatabaseAccessorImpl.runInTransaction(DatabaseAccessorImpl.java:43)
at com.atlassian.pocketknife.api.querydsl.DatabaseAccessor.run(DatabaseAccessor.java:201)
at com.atlassian.jira.migration.export.db.advancedroadmaps.IssueSourceDataReader.getAllIssueSourcesForPlans(IssueSourceDataReader.kt:79)
at com.atlassian.jira.migration.export.db.advancedroadmaps.IssueSourceDataReader.getAllExistentIssueSourcesForPlans(IssueSourceDataReader.kt:43)
at com.atlassian.jira.migration.preflight.AnonPermissionPreflightService.getFilterIdsExportedWithAR(AnonPermissionPreflightService.kt:194)
at com.atlassian.jira.migration.preflight.AnonPermissionPreflightService.getAllPublicFilters(AnonPermissionPreflightService.kt:148)
at com.atlassian.jira.migration.preflight.AnonPermissionPreflightService.performCheck(AnonPermissionPreflightService.kt:83)
at com.atlassian.jira.migration.preflight.AnonPermissionPreflightCheck.performCheck(AnonPermissionPreflightCheck.kt:42)
at com.atlassian.jira.migration.preflight.AsyncCheckExecutor.runCheck(AsyncCheckExecutor.kt:334)
at com.atlassian.jira.migration.preflight.AsyncCheckExecutor.access$runCheck(AsyncCheckExecutor.kt:50)
at com.atlassian.jira.migration.preflight.AsyncCheckExecutor$executeChecksListenable$1.invoke$lambda$6$lambda$4(AsyncCheckExecutor.kt:221)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
... 3 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'dbo.AO_D9132D_ISSUE_SOURCE'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:258)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1535)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:467)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:409)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7151)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2478)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:219)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:199)
at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:331)
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:83)
at org.apache.commons.dbcp2.DelegatingPreparedStatement.executeQuery(DelegatingPreparedStatement.java:83)
at com.querydsl.sql.AbstractSQLQuery.fetch(AbstractSQLQuery.java:446)
... 34 more
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I "fixed" it (workaround) by reverting JCMA from version 1.12.14 (Released 11-25) to 1.12.12 (Released 11-13)
The Jira Server version is v7.6.0 -- so it's possible this is an "very old junk" type of problem. Good thing they're successfully (it's running now!) migrating away from it :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We reverted JCMA and it did work after. Thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Welcome to the community.
See documentation on migrate-jira-or-confluence-to-cloud-using-public-apis and jira-cloud-migration-assistant-pre-migration-checks-registry
The might help you further.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.