Forum Discussion

Komal_chouhan's avatar
Komal_chouhan
Regular Visitor
10 years ago

remote server returned an error : (404) Not Found

Hi...I am getting below error while publishing the report. Anybody have any idea about this error??    remote server returned an error : (404) Not Found
Anonymous's avatar
Anonymous
Not applicable
10 years ago

Hi Komal_chouhan,

Does the above error message occur when you publish specific PBIX file or publish all PBIX files? Also we need to know what is the data source in the PBIX file.

Thanks,
Lydia Zhang

Komal_chouhan's avatar
Komal_chouhan
Regular Visitor
10 years ago

Hi Lydia,

 

I got this error when i published specific PBIX file and Data Source is Oracle.

  • Anonymous's avatar
    Anonymous
    Not applicable
    10 years ago

    Hi Komal_chouhan,

    How do you connect to Oracle from Power BI Desktop? Via import option or DirectQuery option?

    Would you mind sharing me the PBIX file? I will test it in my enviroment.

    Thanks,
    Lydia Zhang

    • Alkhos's avatar
      Alkhos
      Advocate I
      9 years ago

      Hello,

       

      I have the exact same issue.

      This happens only for one data source.

      In my case data source is SQL server.

      I tried removing the dataset as well as the report on the service; it did not work. Removed the data source from my gateway, did not work.

       

      Even created another pbix with a different name that pulls data from the same source and just had one single simple visual; did not work either.

       

      My other visuals work.

       

      I remember the issue started when I added some navigatioin steps ( like reordering of columns, etc ) in my data queries and also renamed them. Now even reverting seems to not work and we cannot update or create any new report on that source.

       

      Any ideas how to fix this error?

       

      PS: I have PBI pro and enterprise gateway

      • Alkhos's avatar
        Alkhos
        Advocate I
        9 years ago

        To add, I can also see that it happens right after I have changed the credentials to access the database on PBI desktop, as I just did a repro for another sql server source.