Solved

Failed Application Message

  • 5 April 2021
  • 7 replies
  • 635 views

Badge +5
  • Sidekick (Customer)
  • 18 replies

Hello,

 

Does anyone know how to find that event and inactivate ?

It is failed and it logs every minutes to Application Messages.

You can see details in attachments.

 

 

Sincerely.

icon

Best answer by anmise 5 April 2021, 13:38

View original

This topic has been closed for comments

7 replies

Userlevel 7

Hello,

 

Does anyone know how to find that event and inactivate ?

It is failed and it logs every minutes to Application Messages.

You can see details in attachments.

 

 

Sincerely.

Is the event perhaps called ITEM_CONNECTED_TO_PKG? Otherwise, go to the Application Configuration Package referenced in the error and then go through them.

It’s most likely one of the events related to Service or Maintenance most likely starting with MAINTENGAPP% and SERVICEENGAPP%. Just remove them from the ACP (sfn_custom_obj_api).

 

Userlevel 6
Badge +7

Hi,

 

Go to ‘ New Custom Event’ in navigator and search for %ITEM_CONNECTED_TO% . I cannot tell you the exact event ID here, as I am not sure if the error displays the action name. You can try giving LU Name, Event Enabled = ‘True’ for search criteria.

Once you found the event, you can uncheck the check box ‘Event Enabled’

 

 

Then save. 

Userlevel 4
Badge +8

Hi Cilik

The message seems to be from a External Integration.  Please check , under IFS Solution Manager » Interfaces » Routing Rules ,   where the Routing Address, is a BIZ API : ManageMobileApplications:CreateAllAppEvents.    If your organization does not use Mobile Applications at all, and if this is not relevant to your solution, you may disable it here.

 

As indicated above, Navigate to IFS Solution Manager» Event Actions  and search for ITEM_CONNECTED_TO_PKG  ,  .  You may disable them, if and if you have not implemented any Mobile solution framework.

 

if these are event messages, coming recently , after an update and or they were working correctly earlier, now they are appearing , it is best if this is reported for analysis, than just disabling the solution.

 

Regards

Vivek

Userlevel 7

Hello,

 

Does anyone know how to find that event and inactivate ?

It is failed and it logs every minutes to Application Messages.

You can see details in attachments.

 

 

Sincerely.

Is the event perhaps called ITEM_CONNECTED_TO_PKG? Otherwise, go to the Application Configuration Package referenced in the error and then go through them.

It’s most likely one of the events related to Service or Maintenance most likely starting with MAINTENGAPP% and SERVICEENGAPP%. Just remove them from the ACP (sfn_custom_obj_api).

 

Thinking about it a bit more, I believe ITEM_CONNECTED_TO_PKG is just the error you receive when events are connected to Application Configuration Packages. 

If any of these events are associated with the ACP, please remove the link to the package:
 

Logical Unit Event ID
MaintMaterialAllocation SERVICEENGAPP_1_9
JtTaskTransaction SERVICEENGAPP_1_8
JtTaskStep SERVICEENGAPP_1_7
JtTaskResource SERVICEENGAPP_1_6
JtTaskDependency SERVICEENGAPP_1_5
JtTaskClocking SERVICEENGAPP_1_4
JtTaskAddress SERVICEENGAPP_1_3
JtTask SERVICEENGAPP_1_2
WorkOrderReturns SERVICEENGAPP_1_16
WorkOrderRequisLine SERVICEENGAPP_1_15
WorkOrderJob SERVICEENGAPP_1_14
TransportTaskLine SERVICEENGAPP_1_13
ResourceActivity SERVICEENGAPP_1_12
MobileWorkOrder SERVICEENGAPP_1_11
MobileMaterialReqLine SERVICEENGAPP_1_10
JtExecutionInstance SERVICEENGAPP_1_1
JtTaskClocking MWORKORDER_4_9
PartWoRequisLine MWORKORDER_4_8
MobileMaterialReqLine MWORKORDER_4_7
MaintMaterialReqLine MWORKORDER_4_6
MaintMaterialAllocation MWORKORDER_4_5
JtTaskStep MWORKORDER_4_4
JtTaskAddress MWORKORDER_4_3
JtTask MWORKORDER_4_2
ScServiceContract MWORKORDER_4_18
PurchaseRequisition MWORKORDER_4_17
PurchaseReqLine MWORKORDER_4_16
WorkOrderReturns MWORKORDER_4_15
MobileWorkOrderPicture MWORKORDER_4_14
MobileWorkOrder MWORKORDER_4_13
JtTaskTransaction MWORKORDER_4_12
MobileTaskSignature MWORKORDER_4_11
JtTaskTransaction MWORKORDER_4_10
JtExecutionInstance MWORKORDER_4_1
MaintMaterialAllocation MAINTENGAPP_1_9
JtTaskTransaction MAINTENGAPP_1_8
JtTaskStep MAINTENGAPP_1_7
JtTaskResource MAINTENGAPP_1_6
JtTaskDependency MAINTENGAPP_1_5
JtTaskClocking MAINTENGAPP_1_4
JtTaskAddress MAINTENGAPP_1_3
JtTask MAINTENGAPP_1_2
WorkOrderReturns MAINTENGAPP_1_16
WorkOrderRequisLine MAINTENGAPP_1_15
WorkOrderJob MAINTENGAPP_1_14
TransportTaskLine MAINTENGAPP_1_13
ResourceActivity MAINTENGAPP_1_12
MobileWorkOrder MAINTENGAPP_1_11
MobileMaterialReqLine MAINTENGAPP_1_10
JtExecutionInstance MAINTENGAPP_1_1

 

Badge +5

Hi,

Thank you all for your helps. 

 

@anmise I have solved the problem with your lead.   Thank you so much.

Sincerely. 

Badge +5

Hello again,

 

I have one more question about the failed application messages.

After i have achieved to stop them failing, i wanted to delete failed messages in the list.

Delete button is inactive in Solution Manager\Integration\IFS Connect\Application Messages.

There is a background job, cleanup of finished messages, but no for failed messages.

I have tried to execute cleanup function for state “Failed”. But it took 60 minutes and locked. 

 

My guess, because of there are so many failed messages. Like almost 8 million.

What can i do for that ? 

 

Sincerely.

 

Userlevel 7

Hello again,

 

I have one more question about the failed application messages.

After i have achieved to stop them failing, i wanted to delete failed messages in the list.

Delete button is inactive in Solution Manager\Integration\IFS Connect\Application Messages.

There is a background job, cleanup of finished messages, but no for failed messages.

I have tried to execute cleanup function for state “Failed”. But it took 60 minutes and locked. 

 

My guess, because of there are so many failed messages. Like almost 8 million.

What can i do for that ? 

 

Sincerely.

 

There’s a scheduled task called ‘Cleanup Application Message Queues’ that you can use. I’d setup the parameters to cut the amount of messages into chunks and run the job multiple times, if you have 8 million failed messages waiting. 

 

Specify the Queue and the status and then run it maybe for a couple of hours at a time and see how long it takes and then increase it.