Entry Point Not found

[GSC977]

While publishing ADF from Json file we are getting below error.

2023-05-15T15:35:48.4086098Z ##[error]Entry point was not found. 2023-05-15T15:35:48.6191647Z ##[error]There was an error with the service principal used for the deployment.

With the exception of Publish ADF from Json File, the same service principal connection used for other tasks is functional in other deployment tasks.

[dayalus]

We're getting the same error. We were not getting this with 1.27.1315

[GSC977]

We're getting the same error. We were not getting this with 1.27.1315

Any solution .?

[DannyvB]

We are also having this issue, unable to fix it so far

[GSC977]

@NowinskiK can you please check and provide some update or solution on above error/Issue..

[GSC977]

did anyone get solution..? @DannyvB @dayalus .. @NowinskiK can you please guide on this issue

[GSC977]

@NowinskiK Any update..??

[NowinskiK]

Do you use Microsoft (Hosted) Agent or custom DevOps agent? Everything works with Hosted Agent.

Try to use previous version temporally and check if that works:

It's probably due to update of Az.Accounts to ver. 2.12.1 (from )

[GSC977]

We use Hosted Agent for deployment and not Azure agents

[dayalus]

Same with us..

Best Regards, Dayal.

From: GSC977 @.> Sent: Tuesday, May 16, 2023 10:56 AM To: Azure-Player/azure.datafactory.devops @.> Cc: Dayal Sukumaran @.>; Mention @.> Subject: Re: [Azure-Player/azure.datafactory.devops] Entry Point Not found (Issue #137)

We use Hosted Agent for deployment and not Azure agents

- Reply to this email directly, view it on GitHubhttps://github.com/Azure-Player/azure.datafactory.devops/issues/137#issuecomment-1549838186, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A7JXV5CJPSMAKNFFDNY2WM3XGOIQ7ANCNFSM6AAAAAAYCQ7APQ. You are receiving this because you were mentioned.Message ID: @.***>

[GSC977]

how to use specific version in a classic editor pipeline

[govindareddy0]

@NowinskiK , Could you please help oh how to use the previous version in Classic editor pipeline. Currently all our releases are impacted with the issue.

[dayalus]

Same issue with us - classic editor pipeline. We can only view the YAML

[NowinskiK]

I released new version 1.29 which contains 2 upgraded Microsoft Az modules. Hopefully this will resolve the issue. Guys, please confirm whether this fix resolves your case as I can't test it.

[michasacuer]

@NowinskiK We have the same issue with Version : 1.29.1369 as from OP

[govindareddy0]

check az.accounts version in devops agent machine and upgrade it to latest version 2.12.2 through powershell it resolves the issue

[jessehouwing]

For those of you hit by this problem and wondering how to deal with such issues in UI based pipelines, releases and where the older version may have been deleted from the collection by an uninstall/reinstall of the extension in an attempt to fix the issue:

https://jessehouwing.net/azure-pipelines-you-broke-our-pipeline/

check az.accounts version in devops agent machine and upgrade it to latest version 2.12.2 through powershell it resolves the issue

To do that run:

> az upgrade

> pwsh
> Install-Module -Name Az -Repository PSGallery -Force -AllowClobber

As far as I can tell.

[dayalus]

@NowinskiK - we're still having the issue

[NowinskiK]

There is nothing else I can do. Your Agent/VM has incompatible PS modules which must be upgraded (described above).

[jessehouwing]

It might make sense to query the incompatible version and log a meaningful error instead of letting it throw a method not found exception...

[dayalus]

@NowinskiK - thank you! There was an issue with our upgrade. After the upgrade, it now works. Sorry about that!