Work orders are not transferring to the mWo application : Unexpected error while calling server method UplinkServices/RegisterUplinkURL
Cannot get a WO transferred to a mobile. Looking through our mobile user logs we can see the following error :
Sending Push Notification: Authenticator Token: '7ec05efd6f2a44e0a9b59c70e6415d8c' is invalid.
Sending Push Notification: Authenticator Token: '{token}' is invalid.
+7
+9According to the error message issue seems to be in the user IFSMOBILITY follow the below steps in order to solve the issue.
Steps to solve the issue:
• Check the IFSMOBITITY user’s status by navigating to oracle user window in IEE
• RMB on the record and click “UNLOCK”
• Log into the TAS web portal.
• Validate and deploy the metadata of the relevant cloud resource.
• Reinitialize the mobile devices.
Steps to solve the issue:
• Check the IFSMOBITITY user’s status by navigating to oracle user window in IEE
• RMB on the record and click “UNLOCK”
• Log into the TAS web portal.
• Validate and deploy the metadata of the relevant cloud resource.
• Reinitialize the mobile devices.
+14This error means the Auth token in the IFS database is invalid compare to what Touch App Server is expecting. Token is used to communicate with TAS in order to send push notifications. If this invalid then you see the error you mentioned in the Mobile Device Logs.
When TAS start-up or when configuration has changed in the system, it update the valid token in IFS database by using the activity UplinkServices/RegisterUplinkURL. But sometimes this could fails. One of the common reason is locked user 'IFSMOBILITY'. If that does not solve the issue, then you can recycle TAS connection pool. By doing that, we force TAS to re-register Uplink URL and token in IFS Database.
You can check the token’s last register time form the table mobile_push_msg_setting_tab.
When TAS start-up or when configuration has changed in the system, it update the valid token in IFS database by using the activity UplinkServices/RegisterUplinkURL. But sometimes this could fails. One of the common reason is locked user 'IFSMOBILITY'. If that does not solve the issue, then you can recycle TAS connection pool. By doing that, we force TAS to re-register Uplink URL and token in IFS Database.
You can check the token’s last register time form the table mobile_push_msg_setting_tab.
+1We´ve got the same problem here. We are using TAS on premise we are receiving the message below:
Error: 0 : Authentication expected token '56f5e6d37f174ad1ae18fa99b9bc5a69'
DateTime=2021-07-06T23:07:35.4241849Z
w3wp.exe Error: 0 : ERROR_UPLINK_AUTHENTICATION:Authenticator Token: '4761b390f5e549dbbda239a581d11395' is invalid.
DateTime=2021-07-06T23:07:35.4241849Z
The token “4761b390f5e549dbbda239a581d11395” is inserted in the field AUTH_TOKEN of the table mobile_push_msg_setting_tab
I guess due that the notification of new orders are not being showed in the mobile devices. They are only appear to them when we force initialization of the mobile devices.
the user IFSMOBILITY is configured properly and is not locked and we followed all steps above in this thread.
Besides that the field ACTIVE is TRUE in the table mobile_push_msg_setting_tab
Is there anything else to do in this case? Thans in advance
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.