search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.28k stars 21.45k forks source link

OperationErrorMessages JSON Property of the ETL error response is empty #119996

Closed syedjalalt closed 8 months ago

syedjalalt commented 8 months ago

[Enter feedback here] The OperationErrorMessages JSON Property of the ETL error response is empty. The ETL is not relaying the error message back to ADF. Due to which the said property is empty. I am not sure why the ETL isnt throwing the error for ADF to catch. Could you please elaborate? Or at least include it in the documentation at https://learn.microsoft.com/en-us/azure/data-factory/ssis-integration-runtime-ssis-activity-faq

Thanks

Document Details

⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

syedjalalt commented 8 months ago

Could this be due to the compute resources of SSISDB Catalog connected to the IR of ADF. For example, our SSISDB Catalog has "Standard 01" compute power. It does not require a lot to run and runs without issues almost always.

AjayBathini-MSFT commented 8 months ago

@syedjalalt Thanks for your feedback! We will investigate and update as appropriate.

syedjalalt commented 8 months ago

Update:

The functionality seems to be completely broken now. I have extensively tested sending all kinds of errors (HTTP (400, 401, 503, etc) and otherwise) from ETL (deployed in SSISDB Catalog) to ADF. None of the errors reach ADF. And the OperationErrorMessages property is always empty.

This used to work before. For example, the last time we receieved an error from ETL into ADF in the said property was in December 2023. Since then, no ETL error has been caught by ADF.

I will be happy to provide more information if required. Request you to please look into this.

Thanks

syedjalalt commented 8 months ago

Update:

Upon Checking the SSISDB Catalog, the error message is being captured as message_type = 120 in Catalog.Operation_messages table. The timestamp shows that the message is captured well before the error is thrown in ADF. That means, ADF should receieve the error message in the OperationErrorMessages property since logging of message is happening during the execution of the package itself.

RamanathanChinnappan-MSFT commented 8 months ago

@syedjalalt You are experiencing issues with the OperationErrorMessages property not being populated with error messages from your ETL. Based on the information you have provided, it seems that the error messages are being captured in the SSISDB Catalog, but are not being relayed back to ADF. This could be due to a number of reasons, such as network connectivity issues or configuration issues with your SSIS Integration Runtime.

I would recommend checking the following:

  1. Ensure that your SSIS Integration Runtime is properly configured and connected to your SSISDB Catalog.
  2. Check the network connectivity between your SSIS Integration Runtime and your SSISDB Catalog.
  3. Verify that the error messages are being captured in the SSISDB Catalog and that they are associated with the correct package execution.
  4. Check the logs and error messages in ADF to see if there are any clues as to why the OperationErrorMessages property is not being populated.

If you are still unable to resolve the issue, I would recommend reaching out to the Azure support ticket since the support team will be able to respond much more quickly and have a conversation with you to figure out what could be going on for further assistance. They will be able to provide more detailed guidance and help you troubleshoot the issue.