FAILED_WITH_ERROR Results not generated

Question

FAILED_WITH_ERROR Results not generated

Mahesh Nalluri 40

I have small pipeline and my source and target are Snowflake .. In my Pipeline there are 2 dataflows, 1 is running fine and 2nd is failing with : "Status of the query associated with result set is FAILED_WITH_ERROR.Results not generated". I compared my Pipeline target columns with Snowflake table there is no mismatch and there were no nulls in my data, Can someone please advise me what went wrong here. Thanks !!!

Subashri Vasudevan 11,226 Reputation points

2023-10-09T05:01:48.0333333+00:00

Hi Mahesh, are you able to do a data preview in second data flow? in source\sink and the transformations in between? And are there any transformations \ expressions used in between source and sink
Harishga 6,000 Reputation points Microsoft External Staff

2023-10-09T14:03:04.7133333+00:00
Hi@Mahesh Nalluri ,
Welcome to Microsoft Q&A platform and thanks for posting your question here.

As per my understanding that you are facing an issue with one of your data flows failing with the error message "Status of the query associated with result set is FAILED_WITH_ERROR.Results not generated".

please try the below troubleshooting options to resolve the issue and see if it works:

Check the credentials: Ensure that the credentials used to connect to Snowflake are correct in the linked service used in the sink dataset.

Check the network connectivity: Check the firewall settings between Azure Data Factory and Snowflake are not blocked.

Reimport the projection: Try reimporting the projections from the source.

Ensure that there is no datatype mismatch: Check if all my datatypes in the sink are the same as the destination database.

Follow the given best practices to avoid this issue:

Clean up duplicate columns as often as possible after performing certain transforms

Import your schema projection at the source level every time there are major/minor schema changes.

Make sure there is no mismatch between source and sink schema.

I hope this information helps you. Let me know if you have any further questions or concerns.
Harishga 6,000 Reputation points Microsoft External Staff

2023-10-10T13:00:37.6033333+00:00

Hi@Mahesh Nalluri ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Harishga 6,000 Reputation points Microsoft External Staff

2023-10-11T13:09:48.0766667+00:00

Hi@Mahesh Nalluri ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Your answer

Subashri Vasudevan 11,226 Reputation points

2023-10-09T05:01:48.0333333+00:00

Hi Mahesh, are you able to do a data preview in second data flow? in source\sink and the transformations in between? And are there any transformations \ expressions used in between source and sink
Harishga 6,000 Reputation points Microsoft External Staff

2023-10-09T14:03:04.7133333+00:00

Hi@Mahesh Nalluri ,
Welcome to Microsoft Q&A platform and thanks for posting your question here.

As per my understanding that you are facing an issue with one of your data flows failing with the error message "Status of the query associated with result set is FAILED_WITH_ERROR.Results not generated".

please try the below troubleshooting options to resolve the issue and see if it works:

Check the credentials: Ensure that the credentials used to connect to Snowflake are correct in the linked service used in the sink dataset.

Check the network connectivity: Check the firewall settings between Azure Data Factory and Snowflake are not blocked.

Reimport the projection: Try reimporting the projections from the source.

Ensure that there is no datatype mismatch: Check if all my datatypes in the sink are the same as the destination database.

Follow the given best practices to avoid this issue:

Clean up duplicate columns as often as possible after performing certain transforms

Import your schema projection at the source level every time there are major/minor schema changes.

Make sure there is no mismatch between source and sink schema.

I hope this information helps you. Let me know if you have any further questions or concerns.
Harishga 6,000 Reputation points Microsoft External Staff

2023-10-10T13:00:37.6033333+00:00

Hi@Mahesh Nalluri ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.
Harishga 6,000 Reputation points Microsoft External Staff

2023-10-11T13:09:48.0766667+00:00

Hi@Mahesh Nalluri ,
We haven’t heard from you on the last response and was just checking back to see if you have a resolution yet. In case if you have any resolution, please do share that same with the community as it can be helpful to others. Otherwise, will respond with more details and we will try to help.

Share via

FAILED_WITH_ERROR Results not generated

Your answer