@microsoft/azure-data-factory-utilities fails with downloaded main.js

Question

@microsoft/azure-data-factory-utilities fails with downloaded main.js

Bánhidy Attila 20

Hi,

I've found a similar problem here: https://learn.microsoft.com/en-us/answers/questions/1483654/@microsoft-azure-data-factory-utilities-fails-to-d.

My company's network is highly restricted, so the pipeline is not able to download the main.js file.

What I did:

Downloaded the file manually from: https://adf.azure.com/assets/cmd-api/main.js

Added it to the pipeline repository.

My package.json looks like this because I can only download the utility package from our Nexus repository:

JSON

{
 "scripts": {
 "build": "node node_modules/@microsoft/azure-data-factory-utilities/lib/index"
 },
 "dependencies": {
 "@microsoft/azure-data-factory-utilities": "^1.0.0"
 }
}

The installed version is 1.0.3.

The installed Node version is: 20.11.0

The utility package is installed locally, not globally.

I also patched bundle.manager.js:

JSON

set -euo pipefail

BUNDLE_FILE="$(Build.SourcesDirectory)/node_modules/@microsoft/azure-data-factory-utilities/lib/bundle.manager.js"

sed -i "s|if (!fs.existsSync(BundleManager.defaultBundleDir)) {|this._runCommand('$(Build.SourcesDirectory)/_scripts/AdfPublishTool/main.js', args); return;\\
if (!fs.existsSync(BundleManager.defaultBundleDir)) {|g" "$BUNDLE_FILE"

grep -n "_scripts/AdfPublishTool/main.js" "$BUNDLE_FILE"

I also tried using the --path option to specify the location of my downloaded main.js file. However, when NOT using --path, the process still attempts to download main.js, which is not possible in our environment. If I use the --path flag, the setting going to be duplicated in the command.

At this point I am quite confused about what the correct solution should be. I have already spent several days trying to solve this issue, but I still have not managed to get it working.

...to be honest, the main question would be: how can I solve, without any patch or package related file modification, that process not try to download main.js file, instead use mine downloaded main.js file... If I added --path flag to npm run build (or start) command after it, tried to download the main.js file...what is not possible...

The error what I get:

Error: Command failed: node /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js validate /home/agent/azp/_work/1/s/Datafactory /subscriptions/xxx-xxx-xxx/resourceGroups/az-rg/providers/Microsoft.DataFactory/factories/yyyy  /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js:1

If you need any additional information and it is not sensitive, I will gladly provide it.

Any help would be greatly appreciated.

Thanks!

SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-26T09:39:08.8933333+00:00
Hi @Bánhidy Attila

Welcome to Microsoft Q&A platform and thanks for posting your question.

From the error provided, I can see that the utility is already executing the local main.js file:

node /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js validate …

This suggests that the local bundle is being picked up successfully, and the failure may not be related to downloading main.js.

At this point, the error output is incomplete and only shows the first line of the exception. Could you please share:

The complete error output (including all lines after main.js:1)

The exact command being executed

The package.json script used to invoke the utility

Based on the information currently available, I cannot confirm that the utility is failing because it is attempting to download main.js, as the logs indicate that the local bundle is already being invoked.

Once you share the complete error details, we can further investigate the root cause.
Bánhidy Attila 20 Reputation points

2026-08-26T11:34:45.3233333+00:00

Dear @SIVASANKAR YEDDULA !

I do not know why, but I can not answer and share the requestetd informations.

In all cases my answer has been deleted :(
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Bánhidy Attila 20 Reputation points

2026-08-26T11:49:32.3533333+00:00

I got a new error:

RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stderr maxBuffer length exceeded

Execution finished...

Bánhidy Attila 20

npm run build -- --path /path/to/my/downloaded/main.js validate /source/of/DF /subscription/atur/info

npm run build -- --path /path/to/my/downloaded/main.js export/source/of/DF /subscription/atur/info OutPutFolder

...and you can find my package.json in my main question

Bánhidy Attila 20 Reputation points

2026-08-26T11:52:23.02+00:00

Dear @SIVASANKAR YEDDULA !

I am very sorry that I've answered to you in this way...but many times my answer has been deleted...except the last 2

I hope it helps you and provide more information.

Thanks,

Attila

Bánhidy Attila 20

Dear @SIVASANKAR YEDDULA !

I can not send the whole error result...

Meanwhile I could solve the previous problem...now I get back the main problem: Error: Command failed: node /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js validate /home/agent/azp/_work/1/s/Datafactory /subscriptions/xxx-xxx-xxx/resourceGroups/rgrp/providers/Microsoft.DataFactory/factories/yyyyyy

/home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js:1
<content of main.js>

/home/agent/azp/_work/1/s/node_modules/@microsoft/azure-data-factory-utilities/lib/bundle.manager.js:69

 /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js validate /home/agent/azp/_work/1/s/Datafactory /subscriptions/xxx-xxx-xxx/resourceGroups/rgrp/providers/Microsoft.DataFactory/factories/yyyyyy 

/home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js:1
<content of main.js>

/home/agent/azp/_work/1/s/node_modules/@microsoft/azure-data-factory-utilities/lib/bundle.manager.js:69
                throw "Execution failed with exit code: ".concat(exitCode);

                ^Execution failed with exit code: 1

(Use node --trace-uncaught ... to show where the exception was thrown)

Node.js v20.11.0

##[error]Bash exited with code '1'.

SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-27T11:38:42.5166667+00:00

Hi @Bánhidy Attila ,

Thank you for the update and for sharing the latest error details.

Based on the logs provided, I can confirm that the --path parameter is working correctly and that the utility is successfully executing your local main.js bundle:

node /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js validate …

This indicates that the original issue related to downloading the bundle has been resolved, and the utility is no longer attempting to retrieve main.js from the internet. This is consistent with the documented behavior of the --path option for restricted network environments. Automated publishing for continuous integration and delivery - Azure Data Factory.

The current error:

Execution failed with exit code: 1

is a generic error returned by the validation process running inside main.js. The stack trace shows only that the execution failed, but it does not expose the actual validation exception that caused the failure.

At this stage, we can conclude:

The local main.js bundle is being invoked successfully.

The --path option is functioning as expected.

The failure is occurring during the ADF validation/export operation executed by main.js.

The logs shared so far do not contain the underlying validation error needed to determine the exact root cause.

I recommend removing any custom modifications made to bundle.manager.js, as they are no longer necessary and may complicate troubleshooting.

As the next step, please run the bundle directly, outside of the npm wrapper:

node --trace-uncaught /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js validate If the complete output cannot be shared publicly, please provide:

The first validation error reported

The last 20-30 lines before the process exits

Any messages referencing pipelines, datasets, linked services, triggers, or data flows

At this point, I would not focus further on internet access, bundle downloads, or the --path configuration, as those appear to be working correctly. The remaining task is to capture the actual validation exception generated by main.js, which should reveal the root cause of the failure.

Once that exception is available, we can investigate the specific ADF validation issue further.

Bánhidy Attila 20

Dear @SIVASANKAR YEDDULA !

Thank you for your answer, and I hope, now my answer will not be deleted :)

I've removed all steps what do any changed in MS ralted utilities package, like bundle.manager.js.

Changed the validation command to this:

node --trace-uncaught $(Build.SourcesDirectory)/_scripts/AdfPublishTool/main.js validate $(Build.SourcesDirectory)/Datafactory "/subscriptions/xxx-xxx-xxx/resourceGroups/rgrp/providers/Microsoft.DataFactory/factories/dfac"

And the result is:

node -v
v20.11.0
npm -v
10.2.4
mkdir /home/agent/azp/_work/1/s/ArmTemplateOutput
node --trace-uncaught /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js validate /home/agent/azp/_work/1/s/Datafactory /subscriptions/xxx-xxx-xxx/resourceGroups/rgrp/providers/Microsoft.DataFactory/factories/dfac
/home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js:1
<here is the minimized main.js with full content>
(()=>{var e={39052(e,t,n){"use strict";var o;n.d(t,{J:()=>o}),func...
    at wrapSafe (node:internal/modules/cjs/loader:1288:20) 
    at Module._compile (node:internal/modules/cjs/loader:1340:27) 
    at Module._extensions..js (node:internal/modules/cjs/loader:1435:10) 
    at Module.load (node:internal/modules/cjs/loader:1207:32) 
    at Module._load (node:internal/modules/cjs/loader:1023:12) 
    at executeUserEntryPoint (node:internal/modules/run_main:135:12) 
    at node:internal/main/run_main_module:28:49 
Node.js v20.11.0 
##[error]Bash exited with code '1'.

I hope it could help. I also continue the investigation

Thanks,

Attila

SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-28T17:50:58.8133333+00:00
Hi @Bánhidy Attila ,

Thank you for sharing the additional details.

Based on the log provided, the failure occurs before the Azure Data Factory validation process starts. The main.js file is being invoked successfully, but Node.js fails while loading or compiling the script:

/home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js:1

…

at wrapSafe (node:internal/modules/cjs/loader:1288:20)

at Module._compile (node:internal/modules/cjs/loader:1340:27)

…

Node.js v20.11.0

This indicates that the failure occurs within the ADF Publish Tool bundle itself and not during validation of the Data Factory resources.

Based on the information provided, the most likely causes are:

The main.js bundle is corrupted, incomplete, or modified during download/extraction.

The version of the ADF Publish Tool being used may have a compatibility issue with Node.js v20.11.0. The package contents may differ from the original Microsoft-distributed package.

As a troubleshooting step, I recommend:

Remove the existing package and reinstall the latest Azure Data Factory utilities package. Verify that the downloaded main.js file is complete and has not been replaced by an HTML login page, proxy response, or other unexpected content. Test with a supported LTS Node.js version (for example, Node.js 18.x) to determine whether the issue is runtime-version related. If possible, test the same package on another build agent to verify whether the behavior is environment-specific.

However, the key detail still missing is the actual exception message that appears immediately after main.js:1. The current log only shows the stack trace and does not include the underlying error (for example, SyntaxError, Unexpected token, ReferenceError, etc.).

Could you please share:

The complete error output immediately following main.js:1. The version of the Azure Data Factory Publish Tool package being used. Whether the same package works successfully on another build agent or with a different Node.js version.

Once we have the complete exception text, we will be able to identify the exact root cause and recommend the appropriate resolution.Thank you for sharing the additional details.

Based on the log provided, the failure occurs before the Azure Data Factory validation process starts. The main.js file is being invoked successfully, but Node.js fails while loading or compiling the script:

/home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js:1

…

at wrapSafe (node:internal/modules/cjs/loader:1288:20)

at Module._compile (node:internal/modules/cjs/loader:1340:27)

…

Node.js v20.11.0

This indicates that the failure occurs within the ADF Publish Tool bundle itself and not during validation of the Data Factory resources.

Based on the information provided, the most likely causes are:

The main.js bundle is corrupted, incomplete, or modified during download/extraction.

The version of the ADF Publish Tool being used may have a compatibility issue with Node.js v20.11.0.

The package contents may differ from the original Microsoft-distributed package.

As a troubleshooting step, I recommend:

Remove the existing package and reinstall the latest Azure Data Factory utilities package.

Verify that the downloaded main.js file is complete and has not been replaced by an HTML login page, proxy response, or other unexpected content.

Test with a supported LTS Node.js version (for example, Node.js 18.x) to determine whether the issue is runtime-version related.

If possible, test the same package on another build agent to verify whether the behavior is environment-specific.

However, the key detail still missing is the actual exception message that appears immediately after main.js:1. The current log only shows the stack trace and does not include the underlying error (for example, SyntaxError, Unexpected token, ReferenceError, etc.).

Could you please share:

The complete error output immediately following main.js:1.

The version of the Azure Data Factory Publish Tool package being used.

Whether the same package works successfully on another build agent or with a different Node.js version.

Once we have the complete exception text, we will be able to identify the exact root cause and recommend the appropriate resolution.

Bánhidy Attila 20

Dear @SIVASANKAR YEDDULA !

Thank you for your answer!

Here is what I did:

I've changed the version of node to 24.20.0:

=== Node version === 
v24.20.0

Version of npm

=== npm version ===
11.19.0

ADF UTilities version

=== ADF utilities version ===
s@ /home/agent/azp/_work/1/s
`-- @microsoft/azure-data-factory-utilities@1.0.3

package.json

=== ADF utilities package.json ===
+ node -p 'require('\''./node_modules/@microsoft/azure-data-factory-utilities/package.json'\'')'
{
  name: '@microsoft/azure-data-factory-utilities',
  description: 'Azure Data Factory utilities library',
  version: '1.0.3',
  license: 'MIT',
  scripts: {
    build: 'node node_modules/typescript/bin/tsc',
    start: 'node ./lib/index.js',
    'start-preview': 'node ./lib/index.js --preview'
  },
  main: 'index.js',
  dependencies: { commander: '6.2.0' },
  devDependencies: {
    '@types/node': '^12.20.46',
    minimist: '^1.2.6',
    'ts-node': '~10.9.1',
    tsutils: '~1.6.0',
    typescript: '^4.9.5'
  },
  keywords: [ 'AzureDataFactory', 'ArmTemplate', 'Validation', 'Microsoft' ] 
}

command:

node --trace-uncaught /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js validate /home/agent/azp/_work/1/s/Datafactory /subscriptions/xxx-xx-xxxx/resourceGroups/rgrp/providers/Microsoft.DataFactory/factories/dfac

...but nothing changed...

Actual exception still not available, not displayed :(

Further information: unfortunately I can not change agent pool...

Thanks,

Attila

Bánhidy Attila 20 Reputation points

2026-08-29T06:18:40.2666667+00:00

...with Node.js v18.20.8 I got the same result
Bánhidy Attila 20 Reputation points

2026-08-30T06:20:11.24+00:00
Dear @SIVASANKAR YEDDULA !

I have a good news: finally I've successfully run MS utilities tool and I was able to create ARM Temaplates :)

This issue kept bothering me, so I tried to figure out what might be causing it. On my personal machine, where I have WSL installed and there is no proxy or firewall, I created three Dockerfiles with different Node.js versions installed: Node v18, Node v20, and Node v24.

With the help of AI, I generated a dummy Data Factory source project and then ran the validate and export commands against it...

In my pipeline, at the company, I've installed MS utilities package locally, I mean that was not global installation. On private project, the installation was globally, so I've changed it in my pipeline from local to global installation.

Also changed the node_module path in the package.js

Finally the command what is currently working:
# Validate ADF source parameters.adfRg }}/providers/Microsoft.DataFactory/factories/${{ parameters.adfName }} node --trace-uncaught $(Build.SourcesDirectory)/_scripts/AdfPublishTool/main.js validate $(Build.SourcesDirectory)/Datafactory "/subscriptions/${{ parameters.subscriptionId }}/resourceGroups/${{ parameters.adfRg }}/providers/Microsoft.DataFactory/factories/${{ parameters.adfName }}" # Generate ARM Tempaltes parameters.adfRg }}/providers/Microsoft.DataFactory/factories/${{ parameters.adfName }} ArmTemplateOutput node --trace-uncaught $(Build.SourcesDirectory)/_scripts/AdfPublishTool/main.js export $(Build.SourcesDirectory)/Datafactory "/subscriptions/${{ parameters.subscriptionId }}/resourceGroups/${{ parameters.adfRg }}/providers/Microsoft.DataFactory/factories/${{ parameters.adfName }}" ArmTemplateOutput

...and finally it worked! ...but think in this case the --trace-uncaught not need! Am I right?

Copilot said:

I almost forgot to mention that I also replaced the main.js file with the one that was downloaded by the utilities themselves in my private environment. The previous main.js had been downloaded through a browser in the corporate environment, because I had no other option at the time.

It's possible that the issue was caused by the combination of the browser-downloaded file and the non-global installation.

Overall, I would like thanks for you, for your help and support. I think we can close this question now.

If I will face again with any error regarding to the MS utilities package, I will open a new one.

Thanks a lot,

Attila
Bánhidy Attila 20 Reputation points

2026-08-30T06:24:35.48+00:00
Dear @SIVASANKAR YEDDULA !

I have a good news: it is working!

This issue kept bothering me, so I tried to figure out what might be causing it. On my personal machine, where I have WSL installed and there is no proxy or firewall, I created three Dockerfiles with different Node.js versions installed: Node v18, Node v20, and Node v24.

With the help of AI, I generated a dummy Data Factory source project and then ran the validate and export commands against it...

What I did:

changed the utilities installation type form local to global

I replaced the browser-downloaded main.js with a version downloaded using curl.

Overall, I would like to thanks for you, your help and support, I think now we can close this question. If I will have any error in the future with MS utilities package, I will open a new one.

Thanks a lot,

Attila
Allan Solomon Mejia 7,585 Reputation points

2026-08-30T16:22:45.1266667+00:00

Hi @Bánhidy Attila

Help make this community better for everyone: if this answer resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution.
SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-31T00:38:25.36+00:00

Hi @Bánhidy Attila ,

I hope the information provided has been helpful. If you have any further questions or need additional assistance, please let us know in the comments, and we will be glad to help. If this answer helps, please consider clicking Accept Answer so that other community members with similar questions can benefit as well.
Bánhidy Attila 20 Reputation points

2026-08-31T05:10:21.86+00:00
Hi @Allan Solomon Mejia !

To be honest non of above or under answers did not include the soultion, however all comments helped me, to not give up and find a solution.

I do not know what was the real problem:

DO NOT download the main.js via browser what it looks like make some errors in the main.js. Of course, this is just a assuption.

install MS utilities package global not local

Anyway...the fact is, that it is working now, and I am gratefull for you and @SIVASANKAR YEDDULA to helped me and answer to my questions and try to find the probelm and a solution.

Could you help me how I can close this conversation? I just find a button: "Yes, accept answer" under your comment.

Thanks,

Attila
SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-31T10:13:58.1033333+00:00

Hi @Bánhidy Attila ,

hope the information provided has been helpful. If you have any further questions or need additional assistance, please let us know in the comments, and we will be glad to help. If this answer helps, please consider clicking Accept Answer so that other community members with similar questions can benefit as well.

Answer accepted by question author

Allan Solomon Mejia 7,585

Hello @Bánhidy Attila

Based on the latest error, the --path option is working correctly.

Your log shows:

node /home/agent/.../_scripts/AdfPublishTool/main.js validate ...

So @microsoft/azure-data-factory-utilities is executing your local main.js rather than failing because it cannot download the bundle.

Microsoft documents --path specifically for this scenario: when the build environment cannot download the bundle because of network/proxy restrictions, you can provide an existing downloaded bundle directly.

The command should therefore remain in this form:

npm run build -- --path "/path/to/main.js" validate \
  "/path/to/Datafactory" \
  "/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.DataFactory/factories/<factoryName>"

and for export:

npm run build -- --path "/path/to/main.js" export \
  "/path/to/Datafactory" \
  "/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.DataFactory/factories/<factoryName>" \
  "ArmTemplateOutput"

I would remove the bundle.manager.js modification completely. Patching files under node_modules isn't necessary when using the supported --path option and makes troubleshooting harder.

The remaining:

Execution failed with exit code: 1 is now a different issue. Unfortunately, the useful error from main.js isn't visible in the output you've posted.

The earlier ERR_CHILD_PROCESS_STDIO_MAXBUFFER is also important because it indicates the child process generated more stderr output than the wrapper could retain. That may be hiding the actual ADF validation error.

As the next test, run the downloaded bundle directly, bypassing the npm utility wrapper:

node --trace-uncaught "/path/to/main.js" validate \
  "/path/to/Datafactory" \
  "/subscriptions/<subscriptionId>/resourceGroups/<resourceGroup>/providers/Microsoft.DataFactory/factories/<factoryName>"

This should expose the actual validation exception rather than only bundle.manager.js

Execution failed with exit code: 1

Also verify that the manually downloaded file is actually JavaScript and wasn't replaced by a proxy/authentication/error page:

file "/path/to/main.js"

head -c 100 "/path/to/main.js"

wc -c "/path/to/main.js"

So at this stage, I wouldn't troubleshoot Internet access anymore. Your local bundle is being selected successfully. The next objective is to capture the actual exception generated by main.js during validation.

Sharing this reference with you:

Automated publishing for Azure Data Factory CI/CD

If the direct node --trace-uncaught main.js validate ... command returns an error, please post the final exception/stack trace (with subscription/resource details redacted). That should identify the actual remaining problem.

0 comments

3 additional answers

Your answer

SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-26T09:39:08.8933333+00:00

Hi @Bánhidy Attila

Welcome to Microsoft Q&A platform and thanks for posting your question.

From the error provided, I can see that the utility is already executing the local main.js file:

node /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js validate …

This suggests that the local bundle is being picked up successfully, and the failure may not be related to downloading main.js.

At this point, the error output is incomplete and only shows the first line of the exception. Could you please share:

The complete error output (including all lines after main.js:1)

The exact command being executed

The package.json script used to invoke the utility

Based on the information currently available, I cannot confirm that the utility is failing because it is attempting to download main.js, as the logs indicate that the local bundle is already being invoked.

Once you share the complete error details, we can further investigate the root cause.
Bánhidy Attila 20 Reputation points

2026-08-26T11:34:45.3233333+00:00

Dear @SIVASANKAR YEDDULA !

I do not know why, but I can not answer and share the requestetd informations.

In all cases my answer has been deleted :(
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Bánhidy Attila 20 Reputation points

2026-08-26T11:49:32.3533333+00:00

I got a new error:

RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stderr maxBuffer length exceeded

Execution finished...
Bánhidy Attila 20 Reputation points

2026-08-26T11:51:19.2966667+00:00

npm run build -- --path /path/to/my/downloaded/main.js validate /source/of/DF /subscription/atur/info npm run build -- --path /path/to/my/downloaded/main.js export/source/of/DF /subscription/atur/info OutPutFolder

...and you can find my package.json in my main question
Bánhidy Attila 20 Reputation points

2026-08-26T11:52:23.02+00:00

Dear @SIVASANKAR YEDDULA !

I am very sorry that I've answered to you in this way...but many times my answer has been deleted...except the last 2

I hope it helps you and provide more information.

Thanks,

Attila
Bánhidy Attila 20 Reputation points

2026-08-26T19:19:43.87+00:00

Dear @SIVASANKAR YEDDULA !

I can not send the whole error result...

Meanwhile I could solve the previous problem...now I get back the main problem: Error: Command failed: node /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js validate /home/agent/azp/_work/1/s/Datafactory /subscriptions/xxx-xxx-xxx/resourceGroups/rgrp/providers/Microsoft.DataFactory/factories/yyyyyy

/home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js:1
<content of main.js>

/home/agent/azp/_work/1/s/node_modules/@microsoft/azure-data-factory-utilities/lib/bundle.manager.js:69

/home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js validate /home/agent/azp/_work/1/s/Datafactory /subscriptions/xxx-xxx-xxx/resourceGroups/rgrp/providers/Microsoft.DataFactory/factories/yyyyyy /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js:1 <content of main.js> /home/agent/azp/_work/1/s/node_modules/@microsoft/azure-data-factory-utilities/lib/bundle.manager.js:69 throw "Execution failed with exit code: ".concat(exitCode); ^Execution failed with exit code: 1 (Use node --trace-uncaught ... to show where the exception was thrown) Node.js v20.11.0 ##[error]Bash exited with code '1'.
Bánhidy Attila 20 Reputation points

2026-08-28T13:28:17.8533333+00:00

Dear @SIVASANKAR YEDDULA !

Thank you for your answer, and I hope, now my answer will not be deleted :)

I've removed all steps what do any changed in MS ralted utilities package, like bundle.manager.js.

Changed the validation command to this:

node --trace-uncaught $(Build.SourcesDirectory)/_scripts/AdfPublishTool/main.js validate $(Build.SourcesDirectory)/Datafactory "/subscriptions/xxx-xxx-xxx/resourceGroups/rgrp/providers/Microsoft.DataFactory/factories/dfac"

And the result is:

node -v v20.11.0 npm -v 10.2.4 mkdir /home/agent/azp/_work/1/s/ArmTemplateOutput node --trace-uncaught /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js validate /home/agent/azp/_work/1/s/Datafactory /subscriptions/xxx-xxx-xxx/resourceGroups/rgrp/providers/Microsoft.DataFactory/factories/dfac /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js:1 <here is the minimized main.js with full content> (()=>{var e={39052(e,t,n){"use strict";var o;n.d(t,{J:()=>o}),func... at wrapSafe (node:internal/modules/cjs/loader:1288:20) at Module._compile (node:internal/modules/cjs/loader:1340:27) at Module._extensions..js (node:internal/modules/cjs/loader:1435:10) at Module.load (node:internal/modules/cjs/loader:1207:32) at Module._load (node:internal/modules/cjs/loader:1023:12) at executeUserEntryPoint (node:internal/modules/run_main:135:12) at node:internal/main/run_main_module:28:49 Node.js v20.11.0 ##[error]Bash exited with code '1'.

I hope it could help. I also continue the investigation

Thanks,

Attila
Bánhidy Attila 20 Reputation points

2026-08-29T06:15:04.64+00:00

Dear @SIVASANKAR YEDDULA !

Thank you for your answer!

Here is what I did:

I've changed the version of node to 24.20.0:

=== Node version === v24.20.0

Version of npm

=== npm version === 11.19.0

ADF UTilities version

=== ADF utilities version === s@ /home/agent/azp/_work/1/s `-- @microsoft/azure-data-factory-utilities@1.0.3

package.json

=== ADF utilities package.json === + node -p 'require('\''./node_modules/@microsoft/azure-data-factory-utilities/package.json'\'')' { name: '@microsoft/azure-data-factory-utilities', description: 'Azure Data Factory utilities library', version: '1.0.3', license: 'MIT', scripts: { build: 'node node_modules/typescript/bin/tsc', start: 'node ./lib/index.js', 'start-preview': 'node ./lib/index.js --preview' }, main: 'index.js', dependencies: { commander: '6.2.0' }, devDependencies: { '@types/node': '^12.20.46', minimist: '^1.2.6', 'ts-node': '~10.9.1', tsutils: '~1.6.0', typescript: '^4.9.5' }, keywords: [ 'AzureDataFactory', 'ArmTemplate', 'Validation', 'Microsoft' ] }

command:

node --trace-uncaught /home/agent/azp/_work/1/s/_scripts/AdfPublishTool/main.js validate /home/agent/azp/_work/1/s/Datafactory /subscriptions/xxx-xx-xxxx/resourceGroups/rgrp/providers/Microsoft.DataFactory/factories/dfac

...but nothing changed...

Actual exception still not available, not displayed :(

Further information: unfortunately I can not change agent pool...

Thanks,

Attila
Bánhidy Attila 20 Reputation points

2026-08-29T06:18:40.2666667+00:00

...with Node.js v18.20.8 I got the same result
Bánhidy Attila 20 Reputation points

2026-08-30T06:24:35.48+00:00

Dear @SIVASANKAR YEDDULA !

I have a good news: it is working!

This issue kept bothering me, so I tried to figure out what might be causing it. On my personal machine, where I have WSL installed and there is no proxy or firewall, I created three Dockerfiles with different Node.js versions installed: Node v18, Node v20, and Node v24.

With the help of AI, I generated a dummy Data Factory source project and then ran the validate and export commands against it...

What I did:

changed the utilities installation type form local to global

I replaced the browser-downloaded main.js with a version downloaded using curl.

Overall, I would like to thanks for you, your help and support, I think now we can close this question. If I will have any error in the future with MS utilities package, I will open a new one.

Thanks a lot,

Attila
Allan Solomon Mejia 7,585 Reputation points

2026-08-30T16:22:45.1266667+00:00

Hi @Bánhidy Attila

Help make this community better for everyone: if this answer resolved your issue, please accept it or upvote it. If not, share more details in a comment so we can continue the discussion and find the right solution.
SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-31T00:38:25.36+00:00

Hi @Bánhidy Attila ,

I hope the information provided has been helpful. If you have any further questions or need additional assistance, please let us know in the comments, and we will be glad to help. If this answer helps, please consider clicking Accept Answer so that other community members with similar questions can benefit as well.
Bánhidy Attila 20 Reputation points

2026-08-31T05:10:21.86+00:00

Hi @Allan Solomon Mejia !

To be honest non of above or under answers did not include the soultion, however all comments helped me, to not give up and find a solution.

I do not know what was the real problem:

DO NOT download the main.js via browser what it looks like make some errors in the main.js. Of course, this is just a assuption.

install MS utilities package global not local

Anyway...the fact is, that it is working now, and I am gratefull for you and @SIVASANKAR YEDDULA to helped me and answer to my questions and try to find the probelm and a solution.

Could you help me how I can close this conversation? I just find a button: "Yes, accept answer" under your comment.

Thanks,

Attila
SIVASANKAR YEDDULA 150 Reputation points Microsoft External Staff Moderator

2026-08-31T10:13:58.1033333+00:00

Hi @Bánhidy Attila ,

hope the information provided has been helpful. If you have any further questions or need additional assistance, please let us know in the comments, and we will be glad to help. If this answer helps, please consider clicking Accept Answer so that other community members with similar questions can benefit as well.

Answer 1

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 2

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Answer 3

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

@microsoft/azure-data-factory-utilities fails with downloaded main.js

Copilot said:

3 additional answers

Your answer