Schedule Refresh

[Fercast19]

Hello, I wish you could help me with this problem. I have a report in power BI web and it is programmed by a schedule to update the information, when performing the update on certain days it works well but on other days it does not work, that is, it marks an error as the following:

{"error": {"code": "DM_GWPipeline_Gateway_MashupDataAccessError", "pbi.error": {"code": "DM_GWPipeline_Gateway_MashupDataAccessError", "parameters": {}, "details": [{"code": "DM_Errortail "detail": {"type": 1, "value": "- 2147467259"}}, {"code": "DM_ErrorDetailNameCode_UnderlyingErrorMessage", "detail": {"type": 1, "value": "Microsoft Db2 Client : Non-negative number required. \ R \ nParameter name: count SQLSTATE = HY000 SQLCODE = -343 "}}, {" code ":" DM_ErrorDetailNameCode_UnderlyingHResult "," detail ": {" type ": 1," value ":" -2147467259 "}}, {" code ":" Microsoft.Data.Mashup.ValueError.Reason "," detail ": {" type ": 1," value ":" DataSource.Error "}}]," exceptionCulprit " : 1}}} Table: Mexico Receivable Accounts.

As I tell you, this error only happens certain days at the most that I have seen two days skipped or the other days it works well, if you update the information.

my question is why is this error, if it has a solution or is it necessary to make the report again, the data source we use is from DB2.

Thank you

[Greg_Deckler]

@Fercast19 - It's odd, it seems like a negative number is being passed in as a parameter and apparently it doesn't like it. Non-negative number required. \ R \ nParameter name: count SQLSTATE = HY000 SQLCODE = -343

You could check the Issues forum here:

https://community.powerbi.com/t5/Issues/idb-p/Issues

And if it is not there, then you could post it.

If you have Pro account you could try to open a support ticket. If you have a Pro account it is free. Go to https://support.powerbi.com. Scroll down and click "CREATE SUPPORT TICKET".

[Fercast19]

alright then i will post the problem at https://community.powerbi.com/t5/Issues/idb-p/Issues/tab/most-kudoed

And as you mentioned, it is a rare error because on certain days the schedule does not fail me, it runs correctly, I will see what ideas you can give me.

Thank you

[edhans]

When it fails, you should open the report in the Power BI Desktop and do a manual refresh and see if it returns the same error. You can then drill down into the tables themselves in Power Query and see if you can find the source of the error.

That is only valid if the error is in the data itself and not in the connection.