Solved: Json error while refreshing semantic model

luukjedlix · ‎05-01-2025

Hi guys,

I'm getting the following (not very descriptive) error while refreshing my semantic model in fabric PBI:

Data source error: We found an unexpected character in the JSON input.. The exception was raised by the IDataReader interface. Please review the error message and provider documentation for further information and corrective action. Table: Web Site Data.
Cluster URI: WABI-EUROPE-NORTH-B-redirect.analysis.windows.net
Activity ID: eb32293c-4bc5-41a5-9980-7a28bc630e16
Request ID: c3de247d-980b-4f79-2e53-9cc75b832ec8
Time: 2025-04-30 15:03:41Z

I'm not very experienced with PBI and there were no recent changes in this model, so I have no idea where to look... Any directions?

Cheers,

Luuk

Anonymous · ‎05-01-2025

Hi @luukjedlix ,
Thank you for reaching out to us!

You may check this by going into Power Query Editor and looking at the source step for that table.

Try copying the URL used in the query and pasting it into a browser or a tool like Postman. If the response doesn’t look like structured JSON , that is might causing the issue.\
If you’re able to see the JSON, kindly check if it is valid.\
Even if you haven’t changed anything recently, the web source itself might have. For example, the data format could have changed, the source might now require a login or different authentication, or the URL could be redirecting or returning an error message instead of the expected data. One way to handle this is by adding error-handling in Power Query using a try...otherwise statement(for example: try Json.Document(Web.Contents("https://...")) otherwise null)
If you're using a data gateway for refreshes, double-check that it’s running and up to date.

Hope this resolve your query.If so,consider accepting it as solution.

Regards,
Pallavi.

View solution in original post

Anonymous · ‎05-12-2025

Hi @luukjedlix ,

As we have not received a response from you yet, I would like to confirm whether you have successfully resolved the issue or if you require further assistance. If the issue has been resolved, please mark the helpful reply as a "solution" to indicate that the question has been answered and to assist others in the community.
Thank you for your cooperation. Have a great day.

Anonymous · ‎05-09-2025

Hi @luukjedlix ,
Has the issue been resolved on your end? If so, please share your solution and mark it as "Accept as Solution." This will assist others in the community who are dealing with similar problems and help them find a solution more quickly.
Thank you.

Anonymous · ‎05-05-2025

Hi @luukjedlix ,
I wanted to check in on your situation regarding the issue. Have you resolved it? If you have, please consider marking the reply that helped you or sharing your solution. It would be greatly appreciated by others in the community who may have the same question.
Thank you.

Anonymous · ‎05-01-2025

Hi @luukjedlix ,
Thank you for reaching out to us!

You may check this by going into Power Query Editor and looking at the source step for that table.

Try copying the URL used in the query and pasting it into a browser or a tool like Postman. If the response doesn’t look like structured JSON , that is might causing the issue.\
If you’re able to see the JSON, kindly check if it is valid.\
Even if you haven’t changed anything recently, the web source itself might have. For example, the data format could have changed, the source might now require a login or different authentication, or the URL could be redirecting or returning an error message instead of the expected data. One way to handle this is by adding error-handling in Power Query using a try...otherwise statement(for example: try Json.Document(Web.Contents("https://...")) otherwise null)
If you're using a data gateway for refreshes, double-check that it’s running and up to date.

Hope this resolve your query.If so,consider accepting it as solution.

Regards,
Pallavi.