Question

Mobile Error Log Errors when committing task

  • 2 February 2022
  • 1 reply
  • 86 views

Userlevel 2
Badge +5
  • Do Gooder (Customer)
  • 5 replies

Hi!

 

We’re seeing alot of these errors on our newly updated environment:
 

EXCEPTION Message: Følgende systemnivå unntak ble generert av programmet: Cannot create a Key when the same column is listed more than once: 'task_id'
Kontakt systemadministratoren for å få hjelp. Serverlogg eller hendelsesloggen kan inneholde flere detaljer om feilen. ... Stack Trace:    at Metrix.Global.Exceptions.ExceptionManager.HandleException(Exception e)
   at Metrix.BusinessServer.BusinessPolicyInterface.SelectBuilder.ProcessSelectRequest(XmlElement root, UserSession session, Dictionary`2 attachments, Boolean checkForSqlInjection, Boolean bypassTableAccessCheck, Boolean& responseIsException)
   at Metrix.BusinessServer.BusinessPolicyInterface.SelectBuilder.ProcessSelectRequest(XmlElement root, UserSession session, Dictionary`2 attachments, Boolean checkForSqlInjection)
   at Metrix.BusinessServer.BusinessPolicies.SharedTablesComponent.MobileManager.ResolveRelationInfoQuery(XElement message, String tableName, mm_process_defRow processDef, XElement messageToDevice, String personId)
   at Metrix.BusinessServer.BusinessPolicies.SharedTablesComponent.MobileManager.ProcessInsertMessageToMobile(XElement message, String tableName, mm_process_defRow processDef, MetrixDataRow[] activeDevices, List`1& personIdList)
   at Metrix.BusinessServer.BusinessPolicies.SharedTablesComponent.MobileManager.ProcessMessageToMobile(String xml)”

 

These seem to occur each and every time a task is manually committed to a mobile user.
However it does not occur when an admin does the same.

Is there a setting on the role which can create this error?
FSM6 u13


This topic has been closed for comments

1 reply

Userlevel 5
Badge +15

I would guess this is due to bad custom metadata.  Do you have custom metadata on the TASK table?  Or TASK extension metadata?  If so, backup your current configuration, then delete it all, refresh cache, and try again.  If that resolves the problem, then you’ll need step by step review of all the previous configuration to identify what was wrong.