IFS Cloud22R2 MWO Initializing Issue

logs

Note: This isn’t just for the maintenance app. There are unknown errors from “Notify Me” as well as the service app. We have checked the Permission Sets and other settings multiple times, but can’t get past the errors. The mobile apps initialize, and the data is synced from the server. For example, on the maintenance app, I can see work orders, inventory balances, equipment objects, etc. But as soon as the initialization finishes, the errors are encountered. 

Have you given security grants to your permission sets? You can read about this here: Security Grants and Entity Filters - Technical Documentation For IFS Cloud

Yes, I’ve checked the Permission Sets and have the security grants. Thanks for the response.

I suggest you raise this as a support ticket. Something doesn’t look correct with your environment

Cheers

James

Hi,

This is not from the app data initialization. Initialisation was success and then device try to send few initial transactions to the server and they are falling. Support request will help to troubleshoot the issue in the environment. Things you can check meantime is,

• Does ifsapp-native-executor POD is up and running? Are there any errors in the POD logs? 
• Check ifsapp-Odata POD logs which has the ROOT error. 

I assume this could be related to either POD is down or partially installed java IMPL related artefacts in the environment.

You will need to contact environment Admin to get POD logs.  

Hi @kathlk , 

Yes, I see an error in Odata log not in pod desc. attached to support the case.

The error in odata suggests that there is a problem with class loading for the ManagedJobExecutor class in the org.camunda.bpm.engine.cdi.impl package. The error is specifically related to the absence of the javax.enterprise.concurrent.ManagedExecutorService type, which is expected by the ManagedJobExecutor class.

Thank you 

Camunda indicates that you may have a workflow configuration setup, interfering or causing this issue. Do you have any workflows relates to JtTask/JtExecutionInstance perhaps?

HI,

This may be not relevant for the issue you have in the mobile. Can you post the full log pls? 

Hi @kathlk 

These are the logs from odata and Iam

Looks like native Pods are not up and running or they have some short of issues. So pls send both pod logs for ifsapp-native-executor and ifsapp-native-notification. 

Hi @kathlk  

All the logs are attached to case CS0145417. Any specific log other than above