Capture App Error: The application could not be loaded. Please see log for details

Support - Assistance technique
, ,
1

i was upgrading an instance from v2.31.9 to v2.40.7 (major upgrades sequencial), but the capture app can not be loaded, even though i upgraded it to the latest app;

If there is anyone who has the solution somewhere, please guide/ direct me there. Thank you in advance!

The application could not be loaded. Please see log for details.

Mar 26 16:57:03 inpatient tomcat9[6562]: * INFO  2025-03-26T16:57:03,979 Scheduled job: JobConfiguration{uid='uwWCT2BMmlq', name='Remove expired or used reserved values', jobType=REMOVE_USED_OR_EXPIRED_RESERVED_VALUES, cronExpression='0 0 2 ? * *', delay='null', jobParameters=null, enabled=true, inMemoryJob=false, lastRuntimeExecution='null', userUid='null', leaderOnlyJob=false, jobStatus=SCHEDULED, nextExecutionTime=null, lastExecutedStatus=NOT_STARTED, lastExecuted=null} (DefaultSchedulingManager.java [main])
Mar 26 16:57:04 inpatient tomcat9[6562]: * INFO  2025-03-26T16:57:04,099 Scheduling job: JobConfiguration{uid='pd6O228pqr0', name='File resource clean up', jobType=FILE_RESOURCE_CLEANUP, cronExpression='0 0 2 ? * *', delay='null', jobParameters=null, enabled=true, inMemoryJob=false, lastRuntimeExecution='00:00:00.091', userUid='null', leaderOnlyJob=false, jobStatus=SCHEDULED, nextExecutionTime=Tue Mar 25 02:00:00 WAT 2025, lastExecutedStatus=FAILED, lastExecuted=2025-03-24 02:00:00.092} (DefaultSchedulingManager.java [main])
Mar 26 16:57:04 inpatient tomcat9[6562]: * INFO  2025-03-26T16:57:04,101 Job pd6O228pqr0 of type FILE_RESOURCE_CLEANUP has been added to the schedule (DefaultSchedulingManager.java [main])
Mar 26 16:57:04 inpatient tomcat9[6562]: * INFO  2025-03-26T16:57:04,102 Scheduled job: JobConfiguration{uid='pd6O228pqr0', name='File resource clean up', jobType=FILE_RESOURCE_CLEANUP, cronExpression='0 0 2 ? * *', delay='null', jobParameters=null, enabled=true, inMemoryJob=false, lastRuntimeExecution='00:00:00.091', userUid='null', leaderOnlyJob=false, jobStatus=SCHEDULED, nextExecutionTime=Tue Mar 25 02:00:00 WAT 2025, lastExecutedStatus=FAILED, lastExecuted=2025-03-24 02:00:00.092} (DefaultSchedulingManager.java [main])
Mar 26 16:57:04 inpatient tomcat9[6562]: * INFO  2025-03-26T16:57:04,157 Scheduling job: JobConfiguration{uid='Ny1B8gQjDv9', name='Resource table', jobType=RESOURCE_TABLE, cronExpression='0 0 23 * * ?', delay='null', jobParameters=null, enabled=true, inMemoryJob=false, lastRuntimeExecution='00:00:12.562', userUid='null', leaderOnlyJob=false, jobStatus=SCHEDULED, nextExecutionTime=Mon Mar 24 23:00:00 WAT 2025, lastExecutedStatus=COMPLETED, lastExecuted=2025-03-23 23:00:12.563} (DefaultSchedulingManager.java [main])
Mar 26 16:57:04 inpatient tomcat9[6562]: * INFO  2025-03-26T16:57:04,158 Job Ny1B8gQjDv9 of type RESOURCE_TABLE has been added to the schedule (DefaultSchedulingManager.java [main])
Mar 26 16:57:04 inpatient tomcat9[6562]: * INFO  2025-03-26T16:57:04,159 Scheduled job: JobConfiguration{uid='Ny1B8gQjDv9', name='Resource table', jobType=RESOURCE_TABLE, cronExpression='0 0 23 * * ?', delay='null', jobParameters=null, enabled=true, inMemoryJob=false, lastRuntimeExecution='00:00:12.562', userUid='null', leaderOnlyJob=false, jobStatus=SCHEDULED, nextExecutionTime=Mon Mar 24 23:00:00 WAT 2025, lastExecutedStatus=COMPLETED, lastExecuted=2025-03-23 23:00:12.563} (DefaultSchedulingManager.java [main])
Mar 26 16:57:04 inpatient tomcat9[6562]: * WARN  2025-03-26T16:57:04,602 Scheduler started with one or more unexecuted jobs:
Mar 26 16:57:04 inpatient tomcat9[6562]: Job [P9MuptoZyIL, Analytics] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 00:00:00 WAT 2025
Mar 26 16:57:04 inpatient tomcat9[6562]: Job [sHMedQF7VYa, Credentials expiry alert] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 02:00:00 WAT 2025
Mar 26 16:57:04 inpatient tomcat9[6562]: Job [YvAwAmrqAtN, Dataset notification] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 02:00:00 WAT 2025
Mar 26 16:57:04 inpatient tomcat9[6562]: Job [BFa3jDsbtdO, Data statistics] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 02:00:00 WAT 2025
Mar 26 16:57:04 inpatient tomcat9[6562]: Job [pd6O228pqr0, File resource clean up] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 02:00:00 WAT 2025
Mar 26 16:57:04 inpatient tomcat9[6562]: Job [Ny1B8gQjDv9, Resource table] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Mon Mar 24 23:00:00 WAT 2025 (SchedulerStart.java [main])
Mar 26 16:57:04 inpatient tomcat9[6562]: * INFO  2025-03-26T16:57:04,606 All startup routines done (DefaultStartupRoutineExecutor.java [main])
Mar 26 16:57:16 inpatient tomcat9[6562]: Deployment of web application directory [/var/lib/tomcat9/webapps/inpatient] has finished in [526,434] ms
Mar 26 16:57:16 inpatient tomcat9[6562]: Starting ProtocolHandler ["http-nio-8080"]
Mar 26 16:57:16 inpatient tomcat9[6562]: Server startup in [536739] milliseconds
Mar 26 18:54:11 inpatient tomcat9[6562]: * INFO  2025-03-26T18:54:11,717 Authentication event: AuthenticationSuccessEvent; username: Jones_Likoro; ip: 105.232.176.31; sessionId: d2adb478742bff2a9f3db1b30a43c854dfb024033be611de25349b43c2753f79 (AuthenticationLoggerListener.java [tomcat-http-6])

Mar 26 16:57:04 inpatient tomcat9[6562]: Job [sHMedQF7VYa, Credentials expiry alert] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 02:00:00 WAT 2025
Mar 26 16:57:04 inpatient tomcat9[6562]: Job [YvAwAmrqAtN, Dataset notification] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 02:00:00 WAT 2025
Mar 26 16:57:04 inpatient tomcat9[6562]: Job [BFa3jDsbtdO, Data statistics] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 02:00:00 WAT 2025
Mar 26 16:57:04 inpatient tomcat9[6562]: Job [pd6O228pqr0, File resource clean up] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 02:00:00 WAT 2025
Mar 26 16:57:04 inpatient tomcat9[6562]: Job [Ny1B8gQjDv9, Resource table] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Mon Mar 24 23:00:00 WAT 2025 (SchedulerStart.java [main])
Mar 26 16:57:04 inpatient tomcat9[6562]: * INFO  2025-03-26T16:57:04,606 All startup routines done (DefaultStartupRoutineExecutor.java [main])
Mar 26 16:57:16 inpatient tomcat9[6562]: Deployment of web application directory [/var/lib/tomcat9/webapps/inpatient] has finished in [526,434] ms
Mar 26 16:57:16 inpatient tomcat9[6562]: Starting ProtocolHandler ["http-nio-8080"]
Mar 26 16:57:16 inpatient tomcat9[6562]: Server startup in [536739] milliseconds
Mar 26 18:54:11 inpatient tomcat9[6562]: * INFO  2025-03-26T18:54:11,717 Authentication event: AuthenticationSuccessEvent; username: Jones_Likoro; ip: 105.232.176.31; sessionId: d2adb478742bff2a9f3db1b30a43c854dfb024033be611de25349b43c2753f79 (AuthenticationLoggerListener.java [tomcat-http-6])

* INFO  2025-03-26T13:10:41,540 Populated analytics tables: 00:17:44.540 (Clock.java [taskScheduler-25])                                           [1671/1835]
* INFO  2025-03-26T13:10:41,540 Invoking analytics table hooks (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T13:10:41,548 Invoked analytics table hooks: 00:17:44.549 (Clock.java [taskScheduler-25])
* INFO  2025-03-26T13:10:41,549 Applying aggregation levels (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T13:10:41,677 Applied aggregation levels: 00:17:44.678 (Clock.java [taskScheduler-25])
* INFO  2025-03-26T13:10:41,678 Creating indexes (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T13:10:41,694 No of analytics table indexes: 1534 (DefaultAnalyticsTableService.java [taskScheduler-25])
* INFO  2025-03-26T13:30:05,874 Created indexes: 00:37:08.875 (Clock.java [taskScheduler-25])
* INFO  2025-03-26T13:30:05,878 Analyzing analytics tables (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T13:32:31,921 Analyzed tables: 00:39:34.922 (Clock.java [taskScheduler-25])
* INFO  2025-03-26T13:32:31,922 Removing updated and deleted data (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T13:32:31,922 Removed updated and deleted data: 00:39:34.923 (Clock.java [taskScheduler-25])
* INFO  2025-03-26T13:32:31,923 Swapping analytics tables (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,071 Swapping table, master table exists: false, skip master table: false (AbstractJdbcTableManager.java [taskScheduler-25])
* WARN  2025-03-26T13:32:32,392 Validation failed for SQL view 'Vv5W3xUY3hW' with code: 'E4310' and message: 'SQL query contains references to protected table
s' (DefaultSqlViewService.java [taskScheduler-25])
* WARN  2025-03-26T13:32:32,396 Ignoring SQL view which failed validation: Vv5W3xUY3hW, List Users, message: SQL query contains references to protected tables
 (DefaultResourceTableService.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,422 Table update done: analytics_event: 00:39:35.423 (Clock.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,424 Table update done (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,450 Updating tables: VALIDATION_RESULT (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,451 Analytics table update parameters: AnalyticsTableUpdateParams{last years=null, skip resource tables=false, skip table types=[]
, skip programs=[], start time=2025-03-26T12:51:18} (DefaultAnalyticsTableService.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,452 Starting update of type: VALIDATION_RESULT, table name: 'analytics_validationresult', processes: 3: 00:00:00.000 (Clock.java [
taskScheduler-25])
* INFO  2025-03-26T13:32:32,467 No validation results exist, not updating validation result analytics tables (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,468 Updating tables: ENROLLMENT (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,469 Analytics table update parameters: AnalyticsTableUpdateParams{last years=null, skip resource tables=false, skip table types=[]
, skip programs=[], start time=2025-03-26T12:51:18} (DefaultAnalyticsTableService.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,470 Starting update of type: ENROLLMENT, table name: 'analytics_enrollment', processes: 3: 00:00:00.000 (Clock.java [taskScheduler
-25])
* INFO  2025-03-26T13:32:32,670 Table update start: analytics_enrollment, earliest: null, parameters: AnalyticsTableUpdateParams{last years=null, skip resourc
e tables=false, skip table types=[], skip programs=[], start time=2025-03-26T12:51:18}: 00:00:00.199 (Clock.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,671 Performing pre-create table work (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,673 Performed pre-create table work: 00:00:00.202 (Clock.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,674 Dropping temp tables (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,684 Dropped temp tables: 00:00:00.214 (Clock.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,685 Creating analytics tables (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,687 Creating table: analytics_enrollment_temp_t6gt2jwmfu1, columns: 47 (AbstractJdbcTableManager.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,717 Creating table: analytics_enrollment_temp_udkpgbugdau, columns: 37 (AbstractJdbcTableManager.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,743 Creating table: analytics_enrollment_temp_ezezf17f2bx, columns: 37 (AbstractJdbcTableManager.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,770 Created analytics tables: 00:00:00.299 (Clock.java [taskScheduler-25])
* INFO  2025-03-26T13:32:32,773 Populating analytics tables (NotificationLoggerUtil.java [taskScheduler-25])
* INFO  2025-03-26T16:57:03,978 Job uwWCT2BMmlq of type REMOVE_USED_OR_EXPIRED_RESERVED_VALUES has been added to the schedule (DefaultSchedulingManager.java [main])
* INFO  2025-03-26T16:57:03,979 Scheduled job: JobConfiguration{uid='uwWCT2BMmlq', name='Remove expired or used reserved values', jobType=REMOVE_USED_OR_EXPIRED_RESERVED_VALUES, cronExpression='0 0 2 ? * *', delay='null', jobParameters=null, enabled=true, inMemoryJob=false, lastRuntimeExecution='null', userUid='null', leaderOnlyJob=false, jobStatus=SCHEDULED, nextExecutionTime=null, lastExecutedStatus=NOT_STARTED, lastExecuted=null} (DefaultSchedulingManager.java [main])
* INFO  2025-03-26T16:57:04,099 Scheduling job: JobConfiguration{uid='pd6O228pqr0', name='File resource clean up', jobType=FILE_RESOURCE_CLEANUP, cronExpression='0 0 2 ? * *', delay='null', jobParameters=null, enabled=true, inMemoryJob=false, lastRuntimeExecution='00:00:00.091', userUid='null', leaderOnlyJob=false, jobStatus=SCHEDULED, nextExecutionTime=Tue Mar 25 02:00:00 WAT 2025, lastExecutedStatus=FAILED, lastExecuted=2025-03-24 02:00:00.092} (DefaultSchedulingManager.java [main])
* INFO  2025-03-26T16:57:04,101 Job pd6O228pqr0 of type FILE_RESOURCE_CLEANUP has been added to the schedule (DefaultSchedulingManager.java [main])
* INFO  2025-03-26T16:57:04,102 Scheduled job: JobConfiguration{uid='pd6O228pqr0', name='File resource clean up', jobType=FILE_RESOURCE_CLEANUP, cronExpression='0 0 2 ? * *', delay='null', jobParameters=null, enabled=true, inMemoryJob=false, lastRuntimeExecution='00:00:00.091', userUid='null', leaderOnlyJob=false, jobStatus=SCHEDULED, nextExecutionTime=Tue Mar 25 02:00:00 WAT 2025, lastExecutedStatus=FAILED, lastExecuted=2025-03-24 02:00:00.092} (DefaultSchedulingManager.java [main])
* INFO  2025-03-26T16:57:04,157 Scheduling job: JobConfiguration{uid='Ny1B8gQjDv9', name='Resource table', jobType=RESOURCE_TABLE, cronExpression='0 0 23 * * ?', delay='null', jobParameters=null, enabled=true, inMemoryJob=false, lastRuntimeExecution='00:00:12.562', userUid='null', leaderOnlyJob=false, jobStatus=SCHEDULED, nextExecutionTime=Mon Mar 24 23:00:00 WAT 2025, lastExecutedStatus=COMPLETED, lastExecuted=2025-03-23 23:00:12.563} (DefaultSchedulingManager.java [main])
* INFO  2025-03-26T16:57:04,158 Job Ny1B8gQjDv9 of type RESOURCE_TABLE has been added to the schedule (DefaultSchedulingManager.java [main])
* INFO  2025-03-26T16:57:04,159 Scheduled job: JobConfiguration{uid='Ny1B8gQjDv9', name='Resource table', jobType=RESOURCE_TABLE, cronExpression='0 0 23 * * ?', delay='null', jobParameters=null, enabled=true, inMemoryJob=false, lastRuntimeExecution='00:00:12.562', userUid='null', leaderOnlyJob=false, jobStatus=SCHEDULED, nextExecutionTime=Mon Mar 24 23:00:00 WAT 2025, lastExecutedStatus=COMPLETED, lastExecuted=2025-03-23 23:00:12.563} (DefaultSchedulingManager.java [main])
* WARN  2025-03-26T16:57:04,602 Scheduler started with one or more unexecuted jobs:

Job [P9MuptoZyIL, Analytics] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 00:00:00 WAT 2025
Job [sHMedQF7VYa, Credentials expiry alert] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 02:00:00 WAT 2025
Job [YvAwAmrqAtN, Dataset notification] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 02:00:00 WAT 2025
Job [BFa3jDsbtdO, Data statistics] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 02:00:00 WAT 2025
Job [pd6O228pqr0, File resource clean up] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Tue Mar 25 02:00:00 WAT 2025
Job [Ny1B8gQjDv9, Resource table] has status failed or was scheduled in server downtime. Actual execution time was supposed to be: Mon Mar 24 23:00:00 WAT 2025 (SchedulerStart.java [main])
* INFO  2025-03-26T16:57:04,606 All startup routines done (DefaultStartupRoutineExecutor.java [main])
2

HI @joneslikoro,

Is this happening to all the users on the instance, or just you?
Can you make sure you clear the cache completely, including the IndexedDB?

It could likely be caused by this issue - which we will be looking into very soon.

3

@joneslikoro Use any Capture version below 101.33
@Karoline In my case it happened to one user (superuser) in three instances (cache sharing as described in the jira you mentioned) when downgrading the Capture version everything worked.

4

Thanks @mkannan but if cache is cleared thoroughly, downgrading should not need to be necessary. Did the user still have the issue after this? :blush:

1 Like
5

Did the user still have the issue after this?

No, the user have no more issues.

2 Likes
6

good day All,
i never managed to test out the proposed solution yet, i have been busy caught up on something else… will do the test over the weekend and will provide the outcome here, before we close this

7

in my case its not yet done… so lets assume the issue is still on

8

Hi @joneslikoro
Sorry to hear you’re still facing an issue. Would you provide more info by answering the questions:

Thanks!

9

so, the capture app isnt resolved yet… we then restarted the whole upgrade process but stopped at 2.37.10 version, as this version everything works fine.

but immediately if we upgrade to the next version, we face issues after issues. so we are leaving the production here, while we troubleshoot the issues in the development instances.

thank y’all,
Regards,