Error validating Execution Restrictions - Bad Execution Restrictions

[Jose_Malan]

AzureBlobStorage.CreateFile failed: { "error": { "code": 400, "message": "Error validating Execution Restrictions - Bad Execution Restrictions", "source": "europe-002.azure-apim.net", "path": "choose[3]\\when[1]\\choose\\when[1]", "policyId": "", "clientRequestId": "9227fcd6-8b6b-4117-9957-3e69cdb6c50b" } }

I deleted the data source and reconnected, but it's not working.

Until April 2nd it was running on version 3.24032.26. From version 3.24034.17 the problem started.

[msc365]

Funny how things seem to work out!?

• One solution is to set "Disable Secure Implicit Connections" to switch On (@Daan9, @kabhinav150)
• The other one to keep "Disable Secure Implicit Connections" to switch Off (like me)

I don't know about others, but this morning everything seems to be working fine again.

My current configurations:

• Authoring version 3.24041.27 
• Feature "Disable Secure Implicit Connections" is switched Off 
  (As it was like before the issue started.)

[roverton]

What finally worked for me was to turn on the Disable secure implicit connection and share the blob storage with the entire org.

 

[roverton]

Well now some of the users are reporting that they can't get access to the SQL or Blob. It is asking them to ask for permission, but I have gave the entire company access to the both.

[manoj741]

I have the same issue but I am not able to change version 3.24032.26 as it is not available this time . 

I can see there are two version only 3.24043.22 and 3.24042.23. Please help me out. 

[msc365]

Hi @roverton, are you using solutions to transfer your app between environments?

If so, I had a similar issue a couple of months ago. Then I noticed that the connections, that are asked for to get permissions, are not the connections available in that environment! You can verify the connection ID in the mail when you click the link "Ask for access".

After some back and forward, I finally discovered that the connection ID, that the message is referring to, is a connection from our dev environment. Somehow this connection is transferred in the solution when exporting it.

When investigate the connection, which was exclusively setup for this app, in the dev environment I came to the conclusion that this connection was shared with a user group. Strange, while you don't need to share a connection when it is used only for the app. In my honest opinion, you only share a connection when others need to use this connection for their solutions as well. That being said, I removed the shares from the connection in the dev environment, then exported it and imported it again in production. Guess what, problem solved.

Somehow the export embeds the connection ID in the solution when it is shared. Not a desired behavior if you ask me. We use connection references to handle connections between environments.

Maybe this will help to get you and other on track.

[roverton]

Yes, thank you. I was able to figure out why it was asking to share the connection. 

[Jenske93]

I tried to get back to a previous version (I only have one available) and also removed the connection with the Azure Blob Storage and add the connection again. Unfortunately this didn't do the trick for me. Since the app is now quite unusable because of all the errors the users are getting, I really need a fix pretty soon because our work is stuck right now😓

By the way, the "Disable secure implicit connections" was already turned off.

@LanceDelano Could you please help me out? ( Shane Young advised me to contact you for this). Many thanks in advance! 

[kenbossy22]

Has anyone seen any improvement with this issue? We have been holding off updates for two weeks now awaiting a fix and our queue is growing by the day. 

[MikeyMole]

Still no fix for this at least with the authoring versions I've tried. Like others I am now in a holding position, unable to deploy any new features to my apps. 

I'm sure MS are working on it but it must be a hard one to fix 😞

[msc365]

Hi @LanceDelano,

Any news form your side? People are trying possible work arounds and some of the suggestions in this topic are introducing new issues. Your response is highly appreciated.