New installation - msexports_ExecuteETL fails #1516
Replies: 4 comments 5 replies
-
I see there is .9 will try that |
Beta Was this translation helpful? Give feedback.
-
Upgraded to .9 today and reran an export from Cost Management and Billing. The data factory pipeline msexports_ExecuteETL was triggered and promptly failed with the same error. Operation on target For Each Blob failed: Activity failed because an inner activity failed; Inner activity name: Execute, Error: Operation on target Get Existing Parquet Files failed: ADLS Gen2 operation failed for: Operation returned an invalid status code 'NotFound'. Account: 'mystorage'. FileSystem: 'ingestion'. Path: 'Recommendations/2025/04/providers/microsoft.billing/billingaccounts/mybilling account/billingprofiles/firstpartofbillingprofileid682bxxx-fin-ops-daily-disk-reservation-recommendations'. ErrorCode: 'PathNotFound'. Message: 'The specified path does not exist.'. RequestId: '67215082-401f-006a-06ea-ae2cd3000000'. TimeStamp: 'Wed, 16 Apr 2025 16:12:32 GMT'. |
Beta Was this translation helpful? Give feedback.
-
Thanks for looking into this Michael @flanakin . Will try and provide all the information and validations below. Information format for Cost Management and Billing exports: what is being exported (frequency) -> target container (format/compression)
Waited for my Data Factory pipelines to run today. I have the following errors related to teh msexports_ExecuteETL pipeline. I am not calling out any of the msexports_ETL_ingestion errors as I feel they are dependent on the msexports_ExecuteETL errors. All other msexports_ExecuteETL run successfully. First One:
Second
Third
Upon review I am wondering if these pipelines are failing because there is no data to actually move. If you could validate that I would appreciated it. |
Beta Was this translation helpful? Give feedback.
-
Sorry for not getting back sooner @flanakin - FinOps is not my only gig :) The three msexport_ETL_ingestion errors are associated with 'The specified path does not exist. for the msexport runs of:
The activity name that each run fails on is "Get existing Parquet files" -> "Get Metadata". During the creation of these msexports there is no option to select Parquet - they are all .csv Other reservation exports are successful, like AppService Reservation recommendations, which is in csv format does work. The other activities that these runs fail on is Convert to Parquet and Convert to .csv As for re-running an msexports_ExecuteETL on a run that failed - nothing different
I did not rerun the msexport prior to the re-run. Looking in the msexport container there is data entry for today as a manifest.json and a part0.csv in the expected folder: msexports\billingProfiles\xxxxxid\fin-ops-daily-disk-reservation-recommendations\xxxxotherid. Looking in the container target for, there is no container called xxxxxbilliningIDfin-ops-daily-disk-reservation-recommendations |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
I have a new installation of the finops-toolkit .8. I am a MCA customer and have Cost Management & Billing exports setup to go to a storage account. Data Factory connects to the storage account without issues.
I get multiple failures for the msexports_ExecuteETL pipeline, but feel if I fix one the others will get fixed as well. Some msexports_ExecuteETL jobs work - the ones around recommendations are the ones that are failing.
I am new to Data Factory and the toolkit and have tried to go through the troubleshooting guide and common errors, but no luck. I also searched this forum without success.
Problem:
The error I have is:
Operation on target For Each Blob failed: Activity failed because an inner activity failed; Inner activity name: Execute, Error: Operation on target Get Existing Parquet Files failed: ADLS Gen2 operation failed for: Operation returned an invalid status code 'NotFound'. Account: mystorageaccount'. FileSystem: 'ingestion'. Path: 'Recommendations/2025/04/providers/microsoft.billing/billingaccounts/mybillingaccountid/billingprofiles/mybillingprofileID'. ErrorCode: 'PathNotFound'. Message: 'The specified path does not exist.'. RequestId: 'myrequestID#'. TimeStamp: 'Tue, 15 Apr 2025 18:29:29 GMT'.
I can tell you that the storage account does have an ingestion container, but does not have a Recommendations folder.
The msexports_ExecuteETL is configured (I think) to look at the msexports container - but I think that is where I have gone wrong. So this is how msexports_ExectueETL has for settings:
The source dataset for manifest has the linked service of my storage account which I can do a successful Test Connection.

However, the File Path for this connection is:
File Path [blank box]/@{dataset().folderPath}/@{dataset().fileName}
There is a browse button this page and I can browse to the desired folder. But doing a preview data fails.
Not sure I have explained this sufficiently. But any guidance anyone could provide would be appreciated.
Beta Was this translation helpful? Give feedback.
All reactions