Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Get certified in Microsoft Fabric—for free! For a limited time, the Microsoft Fabric Community team will be offering free DP-600 exam vouchers. Prepare now

Reply
LogicoCR
Regular Visitor

Publishing succeeded, but Power BI needs credentials for the data source

Hello!

 

Systems and applications related: Power BI, Dynamics 365 FO, Connection Gateway.

 

Issue: I have created the gateway. It shows online. I added the DataSource and it shows Online. Yet, when I try to publish the report I received a "Publishing succeeded, but Power BI needs credentials for the data source".

If I go and check the report and dataset have been published but I am not able to run the report in Power BI.

The report does works on Desktop and it is using a local database in one of our sandbox VMs.

Any idea of what can I do or check?

1 ACCEPTED SOLUTION

I'm sure someone more knowledgeable can correct me if I'm wrong, but by understanding is that the data source will choose a gateway based on the name of the server and the name of the database. In your screenshot I assume that you've deleted the name of the server out of security concerns when posting on the the internet.

 

Ensure that you're using the actual server name, and not "localhost" or an IP address in the report.

 

 

View solution in original post

8 REPLIES 8
v-huizhn-msft
Microsoft Employee
Microsoft Employee

Hi @LogicoCR,

In Power Bi service, please right the dataset->schedule refresh->Data source credentials, and check Data source credentials is connect successfully as @Ormesome said.

Best Regards,
Angelia

Thank you for your reply Angelia!

I am not sure if I am doing this as you said, but in powerbi.com I went to the Dataset, Schedule Refresh but there are no Data Source Credentials in there.

See attachment.

errorPBI.png

Ormesome
Helper II
Helper II

I would check first that the server and database name in your connection string in Power BI Desktop match those in the gateway.

Then I would check that the account specified in the gateway has the same database permissions as the account you're using locally.

Thank you for your reply Ormesome!

The database and server are the same. The users were not. I checked and the user I was using on the gateway did not have the correct permissions to the database.

So I corrected that (I can now connect with that user/pass to the Database using SQL Server Management) and also from Power BI Desktop, I changed the Source Settings of the report so they'll be using the same username/pass as the one I am using at the gateway. 

After I changed those permissions I was able to Refresh the report in Power BI Desktop but I am still getting the same message when trying to publish it.

Any other ideas?

I think I am missing something.

Do I have to tell the report to use a specific gateway? If so, where or how do I do that?

The error message now it is this one

errorPBI2.png

 

But I have a Gateway configured using same user/pass and server/database.

 

errorPBI3.png

I'm sure someone more knowledgeable can correct me if I'm wrong, but by understanding is that the data source will choose a gateway based on the name of the server and the name of the database. In your screenshot I assume that you've deleted the name of the server out of security concerns when posting on the the internet.

 

Ensure that you're using the actual server name, and not "localhost" or an IP address in the report.

 

 

It worked!!!

Thank you! 🙂

Thanks Ormesome.

I am using localhost in both ends. I will set the real server name in both and check.

Will let you know.

Helpful resources

Announcements
OCT PBI Update Carousel

Power BI Monthly Update - October 2024

Check out the October 2024 Power BI update to learn about new features.

September Hackathon Carousel

Microsoft Fabric & AI Learning Hackathon

Learn from experts, get hands-on experience, and win awesome prizes.

October NL Carousel

Fabric Community Update - October 2024

Find out what's new and trending in the Fabric Community.