Not solved! New "An error occured on the server" issue affecting all PowerApps

[davidstone]

Getting this error affecting all our PowerApps intermittently on submit and read of data.

Also on opening an app in web editor we get:-

WebAuthoring abnormal termination.

errorNumber: -2147024882

errorMessage: Not enough storage is available to complete this operation.

callStack: Error: Not enough storage is available to complete this operation.

[Delid4ve]

Seems to have just sorted itself out..
No server errors and app loading time gone from 4 minutes down to 20 seconds

[Delid4ve]

@Audrie-MSFT could you please update us on the situation / resolution on this since it does not show in the admin portal/health

[davidstone]

@Audrie-MSFT It would be really good if we could get some word from MS on what happened, and the likelihood of reocurrence.

As noted, this is the second time in recent memory where we've had a whole-service issue for around a 24hr period.

Really what I'm after is some assurance from MS that I can in turn offer to my customer base, that this won't keep happening.

Thanks.

[JRaasumaa]

---

@davidstone wrote:

@Audrie-MSFT It would be really good if we could get some word from MS on what happened, and the likelihood of reocurrence.

As noted, this is the second time in recent memory where we've had a whole-service issue for around a 24hr period.

Really what I'm after is some assurance from MS that I can in turn offer to my customer base, that this won't keep happening.

Thanks.

---

Unfortunately we get absolute silence regarding all errors and outages. It's making it very hard to convince management that we can move forward with projects if we have no idea what the status of the services are when something doesn't work as it normally did. Very frustrating!

[Anonymous]

Screw this Microsoft team that is learning DevOps and Microservices.

Getting this "Error Occcured on Server" and my manager is screaming at me saying when she can send email to QA to test it out.

Going mad that some controls have this idiotic error and publishing/republishing has no effect.

You make a form on a list using powerapps in DEV and You have no way to move it QA or PROD.

Sucks no. Who in this whole world ever imagined that MICROSOFT would became a joke of a company.

Azure and all bull **bleep**. A company with a too called Virto which was used earlier for designing to do SharePoint Forms is 10 times better than this **bleep** call POWER APPS.

Don't believe me:

Try renmaing a Form and if You get NaN error then tell me.

[JRaasumaa]

---

@Anonymouswrote:

Screw this Microsoft team that is learning DevOps and Microservices.

Getting this "Error Occcured on Server" and my manager is screaming at me saying when she can send email to QA to test it out.

Going mad that some controls have this idiotic error and publishing/republishing has no effect.

You make a form on a list using powerapps in DEV and You have no way to move it QA or PROD.

Sucks no. Who in this whole world ever imagined that MICROSOFT would became a joke of a company.

Azure and all bull **bleep**. A company with a too called Virto which was used earlier for designing to do SharePoint Forms is 10 times better than this **bleep** call POWER APPS.

Don't believe me:

Try renmaing a Form and if You get NaN error then tell me.

---

The whole development, testing, production process just doesn't work currently. There needs to be a staging area or a way to allow certain users access to a testing version of the app when launching so we can try things out before going live with them (not just in the editor, on an actual mobile device).

Very frustrating.

[Anonymous]

We have been advising to launch the app from a browser on mobile. Not ideal , but it works. 

Any update on long-term resolution?

[Meneghino]

As always, these glitches are linked with major new releases.

We now have version 3.18032.0 of PowerApps, does anybody know what is new?

[Anonymous]

I know this error still persists on Android devices... 

[Anonymous]

This keeps coming depending on if the PowerApps product team pushes any new release to the environment.

And if they do that on a friday afternoon then your weekend is gone.

And there is nothing that you can do about it. Just wait as it would get resolved on it's own when the Service Fabric deployment is over and Your node is up and running...