Missing password or incomplete logon data is registered in Qlik Sense reload task script logs.
When Data Connection is edited, and credentials are updated while app is opened on a specific RIM node, the issue is fixed. However, the problem starts to occur on another Engine node that did not exhibit the issue. If fixing the issue on the next RIM node, problem will re-occur on the previous node.
Example with SAP connection:...
2019-11-22 16:55:51 0112 LIB CONNECT TO [SAP(user)]
2019-11-22 16:55:52 Connected.
2019-11-22 16:55:52 0115 Table:
2019-11-22 16:55:52 0116 LOAD dim1, dim2
2019-11-22 16:55:52 0117 SELECT field1. read
2019-11-22 16:55:52 0118 FROM dim1
2019-11-22 16:55:53 Error: Connector reply error: RfcLogonException:Incomplete logon data.
2019-11-22 16:55:53 ---> RfcAbapRuntimeException:Incomplete logon data.
2019-11-22 16:55:53 Execution Failed
- Qlik Sense Enterprise April 2018
Root cause has not been determined at the time of writing of this article.
Correct the password issue on the Central Node, and reinstall the RIM node(s) where issue occurs.Workaround(s):
- Stop the Scheduler service on the specific RIM node to prevent scheduled reloads or triggered by QMC to be assigned to that node. However this will not prevent the Engine on the specific node from loading the app when accessed via Hub. A reload from Hub will fail when app is opened on the specific RIM node.
- If reloads are performed only via Hub, the app can be forced to be opened only by node(s) that do not present the issue. See Load Balancing Rules: Have only specified streams/apps to be available on a dedicated node