Answered

Error when trying to retrieve data from network: Login failed for user ''

(0) Share

Report

Posted on by otanom

I developed an app that is working since May 2022. A few months ago it suddenly started to pop up the following error message only to a couple of users (the app is used by around 400 users, only less than 10 got this error):

Weird thing is that they can display and edit all the data, but each time they do changes they got the error messages anyway.

We use mainly SQL to store the data used in the app, also we connected it to a SharePoint list so we can save files as attachments.

I read there are some limitations with the SharePoint list, but doesn't seem to be over that threshold, currently it has 1131 rows.

I had also checked that the accesses to the SQL database and the SharePoint list are in place.

Would be really great if someone could help me to fix this as I'm getting out of clues.

Categories:

Building Power Apps

I have the same question (0)

All responses (4)

Answers (1)

Verified answer

Michael E. Gernaey 53,433 Super User 2025 Season 2 on at

Like (0)

Report

Hi @otanom

So that is happening (the message), because you do not have any error handling, so the OnError (at the app level) get it and tosses you a Pink error of Doom.

To truly fix this, you would need to run Monitor at the same time this is happening, so it can give you more information. As that error is lame, as are most of them.
Step 1. Close your App (stop it running)
Step 2. Click the Stethoscope in the Top Right

Step 3. On the bottom click Open Monitor

Step 4. Once Monitor is running go back and run your app

Step 5. Cause your issue to happen

Step 6. Close the app

Step 7. Go to the Monitor and Filter (top right) based on Error, or key word. Go to the line or lines that match this
Step 8. Look at the Response Tab and you will have to expand the Body > and the Header >. Then look at the body to see more details on the error
Do this for each line you find

Step 9. On each line, also check the Code being executed on Tab 2

Now I want to add, that you CAN join a Monitor Session that the User is doing. You can setup the session, share a link to them and when they launch the app, you see all the things happening.

Now you cannot read their data, no you aren't hacking their app instance. But you will see when this error happens and you will specifically be able to look at the Response tab to see what triggered it and hopefully that will tell you how to stop it.

If you like my answer, I would really appreciate if you please Mark it as Resolved, and give it a thumbs up, so it can help others

Cheers

Thank You
Michael Gernaey MCT | MCSE | MCP | Self-Contractor| Ex-Microsoft
https://gernaeysoftware.com
LinkedIn: https://www.linkedin.com/in/michaelgernaey

Was this reply helpful? Yes No
otanom 6 on at

Like (1)

Report

Hi @FLMike ,

Thank you so much for taking your time to go through this issue.

It turns that there was an old connection to a table that doesn't exist anymore and by deleting this connection the users stopped having the error message.
Seems that was only a stupid error that somehow I couldn't detect before.
I appreciate a lot your contribution, didn't know about the Monitor functionality which was very helpful to solve this issue.

Thanks again and best regards from Uruguay

Was this reply helpful? Yes No
yo_thescooter 2 on at

Like (0)

Report

Hi,

The step by step explanation was amazing. Now, I need to understand how to tackle the errors I found. Can you help me with that as well?

"Expression \"Account eq null\" is not supported.\r\nclientRequestId: a79ef107-27e7-4c43-a71a-fa5b97fee854"
The main error is this where it takes a few seconds for the app to match the Account to something. But users instantly gets the error until the account is matched.
It would be great if you have a way to fix this as well
Thanks,

Was this reply helpful? Yes No
adskjfh987325hk 5 on at

Like (0)

Report

Hi @otanom,

Your comment helped me solve my problem as well, but with a slightly differently:
In my case the error messages also appeared out of the blue (worked fine before) and I could make them dissappear by loading another table I use to map the users into a collection (instead of using the "plain" table from the SQL database directly).
Once the Office365User table was enriched with data from the collection instead of the SQL table, the errors disapperaed.

Thanks for the help!

Was this reply helpful? Yes No