Error in Copy Data activity from Lakehouse to Warehouse: partnerResourceProviderUrl

[asocorrocognex]

Any clues what this can be?

The value of the property 'partnerResourceProviderUrl' is invalid: 'Value cannot be null.
Parameter name: partnerResourceProviderUrl'.

In the Destination tab, i am able to select the data warehouse but the dropdown to choose a table fails with the above error.  Even if I enter the table name by hand, I get errors in the Mapping tab.  So I can't really complete the configuration.

A Lookup activity against the warehouse runs fine--but there too I had to enter the table name manually. 

[asocorrocognex]

Hi, someone suggested to work with the connections in the gateway to make this work.  I created a gateway Cloud connection for my warehouse and through it I was able to configure my pipeline activities.  I suspect the same solution can work for lakehouse and sql endpoint connections.

[V-yubandi-msft]

Thanks for sharing your experience.

[V-yubandi-msft]

Thanks for sharing your inputs, @pianalyst_msi  and @vpertsovsky .

@vpertsovsky, since you’ve already raised a ticket with the Microsoft support team, please share any updates or feedback you receive. It will be helpful for other community members facing the same issue.

@asocorrocognex ,thank you for your patience and for staying engaged with the community.

Regards,
Yugandhar.

[vpertsovsky]

I'm having very similar issues with connecting to lakehouse as sources or destinations in CopyJob.  

Just opened a case with Microsoft

[pianalyst_msi]

I actually found the issue. When creating the connection within the pipeline copy data activity, the connection was defaulting to an on-prem gateway connection type since all of our other connections are through an on-prem gateway. I had to go into the connections manager and manually create the lakehouse connection as a cloud connection and now it displays the tablename correctly. I haven't tried the lookup activity against my lakehouse yet in the pipeline, but I think that should work as well. Another workaround is to connect to the Lakehouse using the SQL endpoint but that's a bit of a clunky workaround. Now what I'm dealing with is permissions on sharing cloud connections between users.

[asocorrocognex]

Excellent, please keep us posted.  I wasn't happy about having to work around the bug/limitation.

[pianalyst_msi]

Hi @asocorrocognex, I'm getting this exact error, however in my case it happenes when Lakehouse is the source in either a copy data activity or lookup activity.

When I try to connect to either a Lakehouse delta table or Files sections, even when using manually enter, I get this same error, "The value of the property 'partnerResourceProviderUrl' is invalid: 'Value cannot be null.",  when trying to preview the source.

I was able to create a copy data activity that reads from an ODBC source and writes to a Lakehouse table just fine, but when reading from a lakehouse it doesn't work.

I want to be able to use the Lookup data activity to run a simple select max date query on my lakehouse table to dynamically update the copy data to pull from the last pull date forward but cannot get that to work because of this error.

Additionally I was trying to test upsert behavior by upserting from one lakehouse table to another but that also ran into this error.

Hoping this is either in the works to get resolved soon, or that there's something I'm missing in the setup of my workspace/lakehouse @V-yubandi-msft .

[V-yubandi-msft]

Thank you for sharing your scenario. While it appears similar, in your situation the issue occurs when Lakehouse is used as the source, which causes both the Copy Data and Lookup activities to fail during preview.

As a workaround, you can try connecting through the SQL Analytics Endpoint instead of selecting the Lakehouse option in the UI. This should help you avoid the partnerResourceProviderUrl error caused by the UI.

Regards,
Yugandhar.

[asocorrocognex]

Hi, I entered the table name manually but in the mapping tab I get errors.  I am an admin in the workspace where both the lakehouse and the warehouse are hosted.  

Please note than I was able to run a Lookup activity against the warehouse—but only because I entered the table name manually.  The dropdown always failed.

After spending much time trying to resolve the problem, I ended up creating a Copy Job, which had no trouble letting me select tables in the source and the destination and where I was able to use the UI to create the mappings.

Cheers,

Adolfo

[V-yubandi-msft]

Thanks for the update, @asocorrocognex . 

Good to hear that the Copy Job option worked smoothly for you. From what you’ve described, it does seem like the issue is limited to the Copy Data activity UI when trying to load table details from the Warehouse.

Since this might be a product side behavior, it would be best to raise a support ticket so the Fabric team can take a closer look.
Create a Fabric and Power BI Support Ticket - Power BI | Microsoft Learn

For now, continuing with Copy Jobs or using the Script view in Copy Data sounds like a solid workaround.

Really appreciate you taking the time to share what you tried.

Regards,
Yugandhar.

[V-yubandi-msft]

Hi @asocorrocognex ,

Could you please confirm if you’ve already raised the support ticket? If not, please go ahead and create one.
Also, once you get any update from the support team, kindly share it here it will be helpful for others facing the same issue.

Thank you.

[V-yubandi-msft]

Hi @asocorrocognex ,

Thanks for posting your query in the Microsoft Fabric Community. This error typically happens when the Copy Data activity UI can’t retrieve table metadata from the target Warehouse, which causes the table dropdown and mapping section to not display correctly, even though your Warehouse connection is working (as shown by your successful Lookup activity).

You can try the following steps to resolve 

1. Manually enter the table name in the destination settings using the schema.table format.
2. Switch to the Script view and set up your column mappings there, which often avoids the UI validation problem.
3. Check permissions and linked services to make sure both Lakehouse and Warehouse connections use the correct workspace and artifact IDs, and that you have Contributor access on both.

If the issue persists after these steps, please let us know so we can assist further.

Helpful Reference:
How to copy data using copy activity - Microsoft Fabric | Microsoft Learn
Configure Lakehouse in a copy activity - Microsoft Fabric | Microsoft Learn

Regards,
Yugandhar.