Menu
I'm using Yodlee SOAP API endpoints and in my error logs I'm getting Site Refresh Status as LOGIN_FAILURE with error code 0 (which as I understand is not an error according to Yodlee docs). I was wondering what could be the cause of this? Is it an expected behavior? I'm assuming this is not a successful login.
Here is the returned xml:
<?xml version='1.0' encoding='utf-8'?>
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/">
<soapenv:Body>
<ns21:getSiteRefreshInfoResponse xmlns:ns21="http://refresh.refresh.core.soap.yodlee.com">
<getSiteRefreshInfoReturn><siteRefreshStatus>LOGIN_FAILURE</siteRefreshStatus>
<siteRefreshMode>NORMAL_REFRESH_MODE</siteRefreshMode>
<code>0</code>
</getSiteRefreshInfoReturn>
</ns21:getSiteRefreshInfoResponse>
</soapenv:Body></soapenv:Envelope>
Thanks,
436
Windows Installation Error Code 0X0 Memory Leak - This type of memory leak causes Windows Installer to keep using increasing amounts of memory, bringing down the total system performance. Potential triggers may be endless looping, which causes the program operation to run over and over again.
To clarify, AADSTS stands for Azure Active Directory (Azure AD) security token service (STS). In other words, Azure's security token service failed to authenticate your connection request. Some AADSTS errors seem to affect Microsoft Teams more frequently than others.
The correlation ID is not an error number or code. Simply, it's a GUID (globally unique identifier) that's automatically generated for every request that the SharePoint server receives. It's unique to each request, not each error.
I contacted Yodlee Support and I got the answer that it is expected behaviour and users need to login again to get the instant refresh and refreshing sites should work again.
63
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
