Web service error code : 26
Hello Team,
We are getting this error while trying an authentication web call:
19:02:41.378 | http-nio-8181-exec-14 | DEBUG | c.bmc.inapp.reporting.rest.AdminLoginResource | The login result is com.bmc.inapp.reporting.vo.AdminLoginResult@3a9e828b {
userName . . . . . . . . . . . . . . . <null>
userFullName . . . . . . . . . . . . . <null>
success . . . . . . . . . . . . . . . . yes
roles . . . . . . . . . . . . . . . . . [ADMIN]
errorMessage . . . . . . . . . . . . . Error in getting User Token for given user. Web service error code : 26
I made a research and seems like this is a setting on the database:
https://www.yellowfinbi.com/resources/forum/yfforum-web-services-error-codes-thread-112290
We are on oracle do you know exactly what configuration needs to be enabled on DB side?
Regards,
Daniel Marrujo
Hi Daniel,
Thanks for reaching out with the issue you're facing. The setting in question is regarding the LOGINUSERNOPASSWORD web service call. When reviewing that info on the Wiki page, it shows the required configuration:
You can review the 'Configuration' table of the Yellowfin Config DB to verify whether this setting exists. If it does not, inserting the above record should resolve the 26 exception.
Let me know how it goes.
Thanks,
Mike
Hi Daniel,
Thanks for reaching out with the issue you're facing. The setting in question is regarding the LOGINUSERNOPASSWORD web service call. When reviewing that info on the Wiki page, it shows the required configuration:
You can review the 'Configuration' table of the Yellowfin Config DB to verify whether this setting exists. If it does not, inserting the above record should resolve the 26 exception.
Let me know how it goes.
Thanks,
Mike
Hi Daniel,
I just wanted to check in and see how things are going with this.
Regards,
Mike
Hi Daniel,
I just wanted to check in and see how things are going with this.
Regards,
Mike
Thanks this works, please close. :D
Thanks this works, please close. :D
Hi Daniel,
Thanks for confirming. This considered, I'll go ahead and close this case out, but please don't hesitate to reach out with any other questions or concerns.
Regards,
Mike
Hi Daniel,
Thanks for confirming. This considered, I'll go ahead and close this case out, but please don't hesitate to reach out with any other questions or concerns.
Regards,
Mike
Replies have been locked on this page!