New Issue Pushing AL Extension Updates via VS Code

(0) Share

Report

Posted on by Greg Kujawa

562

So yesterday my SaaS sandbox was automatically updated to the latest BC 365 22.1.55890.56216 version. Today I notice a new wrinkle. Never encountered this before. Typically when I modify a custom AL extension package we'd had for awhile, I just deploy the latest package via VS Code. Today that deployment hangs up for about 5 minutes and throws an error:

The request for path /v2.0/Sandbox/dev/apps?SchemaUpdateMode=synchronize&DependencyPublishingOption=default failed with code UnprocessableEntity. Reason: We can't save your changes right now, because the data is being updated in a transaction done by another session. You'll have to wait until the other transaction has completed, which may take a while. Please try again later.

If I go into the web UI and manually install the extension's .app file through Extension Management it works fine. I've looked in the BC 365 tenant admin portal and verified there are no other active sessions. I've restarted the environment via the tenant admin as well. Still run into this same issue.

Anyone else experiencing this?

Categories:

Other

All responses (10)

Answers (1)

DaveCubitt 10 on at

Like (0)

Report

RE: New Issue Pushing AL Extension Updates via VS Code

Mine only started working properly again once the Sandboxes I had deleted actually left the soft delete stage. Don't know if that helps anyone though.....
Greg Kujawa 562 on at

Like (0)

Report

RE: New Issue Pushing AL Extension Updates via VS Code

UPDATE: For me the fix was creating a new sandbox environment. Named it Sandbox2 and deleted "My Company," only leaving the evaluation Cronus company. Once I pointed my VS Code there in the launch.json file I was able to install the extension just fine.
Greg Kujawa 562 on at

Like (0)

Report

RE: New Issue Pushing AL Extension Updates via VS Code

For me it got worse. Now after that issue seems to have gone away I run into this error.

The request for path /v2.0/sandbox/dev/apps?SchemaUpdateMode=synchronize&DependencyPublishingOption=default failed with code UnprocessableEntity. Reason: Your license does not grant you the following permissions on TableData Published Application: IndirectInsert.

What's maddening is that the company referenced that I don't have permissions against is the Cronus sandbox company. I am the primary Azure/365 tenant admin, and spun up the BC 365 SaaS environment as the first super user. I was able to deploy my BC 365 SaaS extension updates without issue using VS Code for the four months. Now I have to manually install it via the web UI's extension management. I have the IWs licensing in place as has been the case for awhile now.

I even went to the lengths of purchasing Dynamics 365 Business Central Essentials licensing. Applied a license to my Azure AD account this past Friday. As of today when I look in BC 365 SaaS under all I see is the IW license. When I click Update users from Office 365 there are no changes. I can't access the license I applied over in the Azure AD portal and cannot even deploy VS Code through AL Go! against the sandbox. Very disheartening.
Webz 10 on at

Like (0)

Report

RE: New Issue Pushing AL Extension Updates via VS Code

Same issue for me. Cancelled all sessions, waited a few min. but still VS code:

The request for path /v2.0/sandbox/dev/apps?SchemaUpdateMode=forcesync&DependencyPublishingOption=default failed with code UnprocessableEntity. Reason: Cannot install extension [Proj name] because another service is currently modifying the state of extensions on tenant...

Update: Next morning it started working again. Must be something gets reset on Azure overnight but we should be able to do it on the fly.
Indira88 876 on at

Like (0)

Report

RE: New Issue Pushing AL Extension Updates via VS Code

Hi,

Created new environment but problem persists.Very slow and almost stopped.
JCRVT 15 on at

Like (0)

Report

RE: New Issue Pushing AL Extension Updates via VS Code

Hello!

Have you found a solution to this? I am receiving this error on all of my clients environments. I am unable to publish any code from VS code.
Greg Kujawa 562 on at

Like (0)

Report

RE: New Issue Pushing AL Extension Updates via VS Code

This latest wave update definitely was an odd one in this regard. After I had successfully installed my extension via Extension Management a few minutes later I got the prompt that an administrator had made changes...blah blah blah. So I logged back in, to find that my extension wasn't visible in the web UI. Although it was still showing in Extension Management.

We had never accessed the Production environment, and only had the one Sandbox environment with no work done really other than developing against and testing out the Cronus company.
DaveCubitt 10 on at

Like (0)

Report

RE: New Issue Pushing AL Extension Updates via VS Code

This is happening to me too. What I have noticed is that the session I'm trying to use to publish the extension on my sandbox is also trying to do something on soft deleted sandboxes as well. Bizarrely when I publish one extension I lose another one which I had previously published.
Suggested answer

Nitin Verma 20,991 Moderator on at

Like (0)

Report

RE: New Issue Pushing AL Extension Updates via VS Code

I would request you wait for some more time, or try to Kill the idle sessions by going to the Admin Center.
Verified answer

YUN ZHU 62,477 Moderator on at

Like (2)

Report

RE: New Issue Pushing AL Extension Updates via VS Code

Hi, I have encountered several times, and I feel that it is caused by the sudden slowdown of the Sandbox environment. Restarting the environment and canceling the session will temporarily solve the problem, but after re-publishing, it will reappear.

Usually it will be resolved automatically the next day.
If it has not been resolved for a long time, you can copy and create another environment. Generally, the new environment does not have this problem.

Hope this helps.

Thanks.

ZHU