New Bug Encountered:Data table not accessible due to "Internal Error" with all Office365 apps

AppSheet AppSheet Q&A
1

One of my accounts is getting the same error in two different apps- both using Office365/Excel as a datasource.

2X_5_52ebc6a6d490dc295096967930deafffc285161c.png
2X_5_52ebc6a6d490dc295096967930deafffc285161c.png384×584 28.7 KB

There are many other tables but the error only mentions one being inaccessible. I’ve tried clearing cookies/history, different browser, tablet, etc.

3 Likes
2

One thing to check is if the Expense file is open somewhere; I see you’re using Office365 and with that data source the file can’t be currently being edited by someone when the app tries to access it.

But in cases like this, you should email support@appsheet.com for direct support.

2 Likes
3

Thanks @MultiTech_Visions. I have noticed that as well with Office365 Excel files getting locked. No one else has access to the sheet in this case though.

I’ve emailed support already but thought I would also try here in case others are experiencing issues with Office365 data sources this morning. It’s affecting backup copies of the app under the same account as well.

3 Likes
4

I’m having the same issue this morning.

3 Likes
5

Thanks @Kyle_Richardson. Glad to hear it’s not just me.

2 Likes
6

@Kyle_Richardson,

  1. are all of your apps affected?
  2. are all of your apps using Office365/Excel as a data source?

In my case, the account uses an Office365 login, all data sources are Excel files in that Office365 account, and both apps in that account are getting the same error.

However, I was able to copy a sample app using Office365/Excel as the data source, and everything worked fine.

1 Like
7

I have my current live app and an upgrade to it that I’ve been working on separately that are affected.

All associated Excel files are stored on SharePoint with O365.

8

Same issue here…

1 Like
9

Same issue for me too!

2 Likes
10

Looking into it right now! Sounds like it is Office365 accounts only. Could you confirm please?

2 Likes
11

Sounds like SmartSheets is having a similar connection problem.
https://community.appsheet.com/t/smartsheet-error-apps-not-able-to-load/13440/4

2 Likes
12

I only have one app and it uses O365. Now I am getting a different error that may help:
Error: Dat table ‘Crossings’ is not accessible due to: Error code: DeploymentInvalidEditSession Error message: There were communication or server problems and you are no longer connected…

1 Like
13

It might be an O365 API issue. See https://downdetector.com/status/office-365
We’re continuing to investigate

4 Likes
14

We think it is an Office365 API issue. Our code is (unexpectedly) not getting back any data when reading some of these sheets from the Office365 API. This is causing internal errors in our code, which is what you see reported. The problem started happening around 1AM PST today — no change at that time on our side, but probably some change in Microsoft’s service.

Resolution unclear, but no immediate solution from our side unfortunately.

5 Likes
15

One more update: the problem doesn’t seem to occur for all sheets on Office365. Just for some. For example, for @GreenFlux, the problem is only with one of the sheets in the app (the ‘Expenses’ sheet). There may be something specific going on with some sheets (perhaps a special formula or something) that is causing the Office365 Excel API to break.

2 Likes
16

@Kyle_Richardson in your app, ‘Pour’ and ‘PourDate’ load fine. But there is a problem with ‘ProductionLog’. Is there anything special about that table?

17

@praveen It does contain a couple necessary spreadsheet formulas. They worked fine up until this morning.

18

For me the problem is for only one sheet.
It is a table with many necessary columns.

19

Yes, our logs show that this problem started around 1AM PST today. No change on our side at that time (or over the weekend). This is definitely something (probably an internal bug) on the Office365 side. So now we’re down to trial-and-error to see what might be causing the problem and how to work around it.

We are still looking for workarounds in our code (by finding some alternative API). In the interim, we are also looking for any insight any of you may have about what could be special about the spreadsheets that are failing.

1 Like
20

My app is reporting the issue on 2 of the many sheets in that workbook. Neither of these sheets have any Excel formulas. Here are some of the statistics on those two sheets:
Attachments Excel sheet

  • 11 columns
  • 20657 rows of data
  • no formulas in the Excel sheet
  • Some virtual AppSheet columns for this table (total of 16 AppSheet columns)
  • Some AppSheet formulas like
    LOOKUP([PoleID],“Poles”,“_PoleID”,“Segment”)
    CONCATENATE([Height (ft)],“’ “, [Height (in)],””“”)

Poles Excel sheet

  • 39 columns
  • 6837 rows of data
  • no formulas in the Excel sheet
  • Lots of virtual AppSheet columns for this table (total of 51 AppSheet columns)
  • Some AppSheet formulas like
    IF(COUNT([Related Violations])=0,“None”,“See Violations Section”)
    IF(COUNT(SELECT([Related Violations][Violation Category], [Violation Category]=“Power”))>0,“YES”,“NO”)
    LEFT([Inspected By],FIND(“@”,[Inspected By])-1)