The issue was, whenever the customer tried to work with smart client, the Object reference not set to an instance of an Object error was popping out intermittently.
This is not happening for a specific functionality or screen. Randomly the error get triggered. Customer only start to face this issue after upgrade the FSM from 12 to 18. Once the error triggered, the user can see the same error message in the other screen as well. After the relogin this issue is not happening for a while, and but some time later again the same error triggered.
Based on the log file investigation, I have found that issue in the authentication session token. So customer is facing this issue only login through the SSO credentials. But they didn’t get this issue whenever using FSM credentials.
What can be the possible solutions to sort out this issue?
The detail error message:-
<message>Object reference not set to an instance of an object.</message>
Sounds like there has been a timeout on the SSO token. Does this only occur after the client is left for some time?
I would first check the client timeout settings within FSM. There may also be a timeout setting on the SSO provider.
Yes, customer is getting error in one case where they opened the smart client and opened any screen to make sure the smart client is not giving error and then they left the system unused for 40-50 mins straight, then error is observed every time.
Thanks & Best Regards,
This is a client timeout issue then. If you require it longer than the 40-50 mins you will need to set the client timeouts longer in FSM and in the SSO.
@Lee Pinchbeck Thank you for your input.