Forum Discussion

Anonymous's avatar
Anonymous
Not applicable
4 years ago
Solved

Power BI Report Server Refresh fails

Hello everyone,

 

for scheduled data refresh on Report server I get Error 404: 

DataSource.Error: Web.Contents failed to get contents from '******' (404): Not Found. DataSourceKind = Web. DataSourcePath = *****. Url = *******. ;Web.Contents failed to get contents from '********' (404): Not Found. The exception was raised by the IDbCommand interface.

 

Could you please advise on the possible reason for that?

 

Thanks in advance!

  • AbhiSSRS's avatar
    AbhiSSRS
    4 years ago

    d_gosbell is right! You would need to contact web-link support team for the logs , its possible that its load balanced in some old mechanism and one of them is failing when your request goes to that.

5 Replies

  • A 404 is a "not found error" so it look like you are using a call to web.contents and the url you are trying to fetch is no longer valid. You will need to update the url to a valid one.

  • Anonymous's avatar
    Anonymous
    Not applicable

    hello d_gosbell , 

     

    thank you a lot for your answer! 

    As I can see from the error notifications --> sometimes the refresh is successful, sometimes - not.

    There are two data resources --> SQL Server and Web-link (Rest API). 

    The problem usually occurs with Web-Link.

     

    Any ideas why the refresh is still successful?

    • d_gosbell's avatar
      d_gosbell
      Super User

      Anonymous wrote:

      sometimes the refresh is successful, sometimes - not.

       

      Any ideas why the refresh is still successful?


      No I have no idea. It sounds like a problem with the web server.

       

      The fact that report server gets a 404 response means it connects to the web server, but the web server is saying that it does not have the resource that is being requested. You may need to contact someone that supports the web server and see if they can tell you why this happens.

    • AbhiSSRS's avatar
      AbhiSSRS
      Solution Sage

      d_gosbell is right! You would need to contact web-link support team for the logs , its possible that its load balanced in some old mechanism and one of them is failing when your request goes to that.