Data source error: Value was not specified..

[precisionandskl]

Hi. My refresh for a report keeps failing and returning this error. It refreshes fine in the desktop and what's more there are other reports published in the Service that use the same data sources and they refresh fine? I've not come across the 'Value was not specified' message before...

Data source error: Value was not specified.. The exception was raised by the IDbCommand interface. Table: Students.
Cluster URI: WABI-UK-SOUTH-B-PRIMARY-redirect.analysis.windows.net
Activity ID: d002d49c-1b75-4c3f-8b8a-ed95ae767ab1
Request ID: a84b3618-7373-471f-9b62-fd2279306abd
Time: 2025-03-05 13:53:25Z

[precisionandskl · Accepted solution]

Ok, I've found the solution. Last month, I enabled the 'New Snowflake connector implementation' feature which is still in preview. The refresh obviously didn't like this! Anyway I've disabled it and all works fine now.

[SUMESHKUMAR22]

Hey @precisionandskl , glad that I found your response. Could you please help me with were I can enable the "new snowflake connection implementation' feature??

Showing me below error when I removed the implementation 2.0 part from PQ :
DataSource.Error: ODBC: ERROR [HY000] [Microsoft][Snowflake] (4)
REST request for URL *** failed: CURLerror (curl_easy_perform() failed) - code=60 msg='SSL peer certificate or SSH remote key was not OK'.

Details:
DataSourceKind=Snowflake
DataSourcePath=uza80192.east-us-2.azure.snowflakecomputing.com;COMPUTE_WH
OdbcErrors=[Table]

Please help!

Thanks in advance!

[precisionandskl]

Hi - so I resolved the issue by removing the 'implementation 2.0' part in PQ like you've done. Then disabling the feature in Options > preview features. The error you get seems to be related to your company's firewall/proxy settings blocking the connection. If you refesh at home it should work ok.

[SUMESHKUMAR22]

@precisionandskl , thanks for the quick support.

[andrewsommer]

The most likely explanation I can think of given your notes you have multiple queries in that model from the same source that are set up differently.  Power BI accepts both (ServerName) and (ServerName:Database) as data source when setting up a data query from SQL Server.  Both setups work the same in power bi desktop i.e. no exceptions. However, the exception of IDbCommand interface will be thrown if there were more than one query and at least one of these queries used different setup to the rest of queries.

[precisionandskl]

What do you mean when you say 'set up differently'? 

For added context, I have 7 active queries from Snowflake. And 5 custom-made ones created with DAX/M (things like date tables, indexes, etc.). Also, after refreshing multiple times I get the same error but the table name changes. Originally it was the students table, but now it's something else. I feel like even if I had one query it would still error out. 

[andrewsommer]

What I meant about the queries being set up differently is that in a sql query you could have a source that is ‘server_name.database’ or you could just use ‘database’. However, within one flow or model if you go to the same source and on one query you use server_name.database and on another you use just database it may error out.

With that said I don’t think that is your problem once you mentioned you have custom-made tables.  Do any of your custom-made tables reference your snowflake queries? 

[precisionandskl]

Ah, right. 

No direct references in the code, no. There is a relationship between one of them and a Snowflake table. But earlier I tested deleting it and then refreshing - same error. I've now deleted all queries but the two most essential ones (both Snowflake) and still the same error. I'm stumped.

[v-menakakota]

Hi @precisionandskl ,

Thank you for reaching out to us on the Microsoft Fabric Community Forum.

As you mentioned the error during refresh in Power BI Service, even though the report refreshes fine in Power BI Desktop and other reports using the same data sources work.Please go through the below steps:

Check Gateway issues ,If you're using an On-Premises Data Gateway, make sure it’s online and up-to-date.
Open Power Query Editor and check if any transformation relies on local parameters or dynamic values that may not be resolving in Service.
And also please go through the below link in which the issue is same:
Solved: Re: Data Refresh Error - Microsoft Fabric Community

If this post was helpful, please give us Kudos and consider marking Accept as solution to assist other members in finding it more easily.

[precisionandskl]

1) Not using an On-Premises Gateway

2) The only transformations are a few conditional columns, which are identical to the transformations in the reports that are refreshing successfully