getCharts().getAs() linechart error: "Service Spreadsheets failed while accessing document with id" [182701055]

Assigned

Bug

Status Update

No update yet.

Description

iv...@olioex.com

created issue #1

Mar 15, 2021 11:41AM

A short description of the issue:

SpreadsheetApp.getActive().getSheetByName().getCharts().getAs() returns this error: "Service Spreadsheets failed while accessing document with id", but only when the line chart has a right vertical axis. If the line chart has a left vertical axis, the script runs as expected.

A small code sample that reliably reproduces the issue. The sample should run as-is or with minimal setup, without external dependencies.

function getAsBug() {

var sheet = SpreadsheetApp.getActive().getSheetByName('bug'); var chartImage = sheet.getCharts()[0].getAs('image/png'); // Chart 0 should be a line chart with a left vertical axis, no error will be returned. var chartImage = sheet.getCharts()[1].getAs('image/png'); // Chart 1 should be a line chart with a right vertical axis, an error will be returned.

}

What steps will reproduce the problem?

Start a new Google Sheet
Create some dummy data (example sheet)
Use the dummy data to create a line chart with a left vertical axis (example sheet)
Use the dummy data to create a line chart with a right vertical axis (example sheet)
Go to 'tools -> script editor' and create the following script:

function getAsBug() {
  
  var sheet = SpreadsheetApp.getActive().getSheetByName('Sheet1');
  var chartImage = sheet.getCharts()[0].getAs('image/png'); // Chart 0 should be a line chart with a left vertical axis, no error will be returned.
  var chartImage = sheet.getCharts()[1].getAs('image/png'); // Chart 1 should be a line chart with a right vertical axis, an error will be returned.

}

Run the script created in step 5, and observe how it correctly processes the chart with the left vertical axis, and then returns an error for the line chart with the right vertical axis.

What is the expected output? What do you see instead? If you see error messages, please provide them.

I expect chartImage to hold a copy of the chart selected with .getAs(). Instead, I get this error message: "Service Spreadsheets failed while accessing document with id 1WdpJynTfTaWnee49Syd1T9ZcGu7y7zGzFuZbDgkRmLA"

Comments

[Deleted User] <[Deleted User]> #2Mar 16, 2021 03:45AM

a concerning line is:
emulator: WARNING: Host CPU is missing the following feature(s) required for x86 emulation: SSSE3

what is the CPU in your computer?

The new emulator system requirements are posted here:

http://tools.android.com/tech-docs/emulator

Message last modified on Mar 16, 2021 04:02AM

ra...@google.com <ra...@google.com> #3Mar 16, 2021 01:35PM

The processor is an AMD Phenom II x6 1075T, and it has AMD-V, as required by the new Android emulator in Linux (please see this link for more info on this CPU :

http://www.cpu-world.com/CPUs/K10/AMD-Phenom%20II%20X6%201075T%20-%20HDT75TFBK6DGR.html)

It does not have SSSE3, but I don't see it as a requirement in the Android emulator specs.

iv...@olioex.com <iv...@olioex.com> #4Mar 16, 2021 01:55PM

[Comment deleted]

ra...@google.com <ra...@google.com> #5Mar 16, 2021 02:35PM

The same for me.
I have an AMD Phenom II x6 1090T running Ubuntu 14.04 64 bit, which doesn't support SSSE3. API 22 x86 works. API 23 x86 doesn't work (i.e. emulator starts but its screen keeps black).

[Deleted User] <[Deleted User]> #6Mar 16, 2021 02:54PM

The same for me.
I have an AMD Phenom II X6 1055T running Ubuntu 14.04 64 bit. API 22 x86 works. API 23 x86 doesn't work (i.e. emulator starts but its screen keeps black).

This is happening for Platform N too.

Message last modified on Mar 17, 2021 12:56AM

Tue Mar 16 2021 22:54:07 GMT+0800 (Philippine Standard Time).png

67 KB

View

Download

iv...@olioex.com <iv...@olioex.com> #7Mar 16, 2021 03:26PM

The same for me :(
AMD Phenom(tm) II X4 945 Processor it has no ssse3. Running Arch Linux. API 23 gives a black screen. The arm images do work in a paint drying kind of way. API 23 doesn't work on Genymotion either

Older images work pretty good.

st...@ostec.de <st...@ostec.de> #8Mar 17, 2021 02:19PM

Perhaps similar issue - emulator with blank screen for x86 emulation for all tested apis - 16,21,23
OS: slackware 64 14.1 on AMD Phenom II x6 1090T
Android SDK: 23.0.5, 24.3.4 or 24.4.1 , Note 25.1.3 does not work as it depends from QT5.
From command line I could get screen with text "ANDROID" and that's all.

Last test was "/opt/android/sdk_r24.4.1/tools/emulator64-x86 -avd api21.v501-cpu.x86 -debug-all -noaudio -nocache" and result is similar as first post plus repeating errors:
emulator: Error while connecting to socket '

127.0.0.1:1970': 111 -> Connection refused

[Deleted User] <[Deleted User]> #9Mar 17, 2021 05:48PM

Any news on this issue ? It happens on N as well

ma...@gmail.com <ma...@gmail.com> #10Mar 18, 2021 02:43AM

Same problem.
CPU - Athlon x64 X2 3600+.
RAM: 8GB
OS: Manjaro x64

All x86 images work with same SSSSE3 warning, except API 23.
Just black screen in AVD emulator.

Genymotion API 23 does work here on same computer.

ma...@gmail.com <ma...@gmail.com> #11Mar 18, 2021 12:33PM

Same problem with Quad-Core AMD Opteron(tm) Processor 2354

[Deleted User] <[Deleted User]> #12Mar 18, 2021 11:31PM

Same problem.
CPU: AMD Phenom II X4 955 Processor
RAM: 8 GB
OS: Linux Fedora 24 x86_64

All Android images woks with SSSE3 warning, except API 23 x86 and API 24 x86.
API 22 x86 and below works fine. API 23 x86 and API 24 x86 doesn't work (emulator
starts but it screens keeps black.

cp...@gmail.com <cp...@gmail.com> #13Mar 19, 2021 04:56PM

Same issue with
- AMD Athlon II X2 250 Processor
- Linux Fedora 22 x64
- API 23 and 24

Message last modified on Mar 19, 2021 05:18PM

ma...@gmail.com <ma...@gmail.com> #14Mar 22, 2021 03:11AM

Same problem affecting me in this new year of 2017...
To be specific:
API 22 x86 image works fine.
API 23+ x86 images give black screen.
- AMD Phenom II X4 955 Processor
- RAM: 8GB
- OS: Arch-based (Antergos)

bo...@gmail.com <bo...@gmail.com> #15Mar 24, 2021 12:15AM

I am having the same problem , tried everything nothing seems working
CPU : AMD A4-3330MX APU with Radeon(tm) HD Graphics
OS : Ubuntu 17.04

y-...@grandsight.biz <y-...@grandsight.biz> #16Mar 24, 2021 12:24AM

I am seeing the same problem on an ASUS M5 A88-V EVO with an AMD Phenom II 1045T on 64 bit Ubuntu 17.04. I tried API 22-25 and the only one that actually started was 22. All of the rest brought up the device and skin but the screen stayed black and the emulator never seemed to actually start Android. It was very quick to start and seemed to work well with 22 though.

Android Studio 2.3.3

[Deleted User] <[Deleted User]> #17Mar 24, 2021 02:47AM

Same problem - also with a Phenom II and in an ASUS M5A97 EVO. Message is:

emulator: WARNING: Host CPU is missing the following feature(s) required for x86 emulation: SSSE3

It is certainly true, the Phenom II doesn't support SSSE3. But this wasn't required previously.

Also tried

/usr/local/toolset/android-sdk/tools/emulator -avd 'Nexus_5X_API_26' -no-accel

But that failed to start at all. I might be prepared to buy an AMD FX processor with SSSE3 if that would solve the problem. The only practical solution for now is to use a real phone for testing (AMD emulation is too slow).

is...@sparta.cl <is...@sparta.cl> #18Mar 25, 2021 12:36PM

I have same issue on ubuntu, has this issue been resolved?

[Deleted User] <[Deleted User]> #19Mar 26, 2021 10:18AM

Not an ideal solution, but I can confirm that replacing a Phenom II 1090t CPU with a newer FX-6300 solves the problem. I retained the ASUS M5A97 EVO motherboard - it already had the latest firmware with FX support. No other hardware changes were necessary. At least the FX-6300 is not too expensive these days.

ra...@google.com <ra...@google.com> #20Mar 26, 2021 04:13PM

I'm really glad that you posted that. I actually have an FX 8350 that I bought a couple of months ago and still haven't installed. I'll try that. :)

jc...@solarcasa.energy <jc...@solarcasa.energy> #21Mar 31, 2021 01:24PM

Google please fire the developer to whom the issue is assigned (the site unfortunately shows the mail with dots, so I can't even ping you directly). Because having the issue as simple as removing -mssse3 switch and rebuilding stuff, plus affecting everyone with AMD CPUs (since those support sse4a instead), unsolved for a year is just unacceptable.

xa...@gmail.com <xa...@gmail.com> #22Apr 6, 2021 08:59AM

Yes, please fix this thing please, really annoying....

li...@gmail.com <li...@gmail.com> #23Apr 6, 2021 07:22PM

#19 glad it works for you with newer model of AMD processors: we will try to make sure it keeps working.

for all the other developers that can not run emulator on your current AMD processors: thanks for your patience and for bringing this issue up.
I have talked to the tool chain people and they told me they have to require SSSE3. simply disabling SSSE3 is not doable as the tool chain
is already assuming SSSE3 support. (I tried and it still uses SSSE3 instructions anyway).

what we can do going forward is to make sure we can run emulator on the main line AMD processors on linux at least.
(HAXM only works with intel chips on mac/windows)

Message last modified on Apr 6, 2021 07:25PM

ns...@greenpeace.org <ns...@greenpeace.org> #24Apr 7, 2021 10:26AM

#23 it is easy to find where ssse3 is used in the code. In the worst case you could build it with debug information and then use objdump + grep to find it out. And I'm pretty sure there's more ways. Then you could figure out why exactly ssse3 is still there (e.g. perhaps they're using some gcc builtins), and fix it.

Beforewords, sorry for me being mean, I really don't want to tell you how to do your job. But you're working in damn Google, and this issue is α) far from being a rocket science, and β) hangs on you for a year! Do something!

a....@gmail.com <a....@gmail.com> #25Apr 14, 2021 06:28PM

#24, thanks for the tip,

it sucks that emulator does not work on certain AMD CPUs, for such a long time: many other devs are feeling the same frustration too.

changing android tool-chain is not in my control. but will definitely keep experimenting other options, and any suggestion is always welcomed.

I did talk to someone who knows a few more thing on this topic, we might try to do something else, such as just emulate the SSSE3-no idea how easy/hard that will be,
but will keep you posted.

yg...@caylym.com <yg...@caylym.com> #26Apr 21, 2021 07:33PM

> changing android tool-chain is not in my control. but will definitely keep experimenting other options, and any suggestion is always welcomed.
>
>I did talk to someone who knows a few more thing on this topic, we might try to do something else, such as just emulate the SSSE3-no idea how easy/hard that will be,

Then reassign the issue to ones who are in control of the toolchain. You're sure can go as far as emulating SSSE3, but unless you already have something offhand to make this working, it's a bunch of work, you have to emulate 16 instructions. And this is even more hilarious considering how easy the direct solution — simply don't use SSSE3.

mi...@agilecreatives.net <mi...@agilecreatives.net> #27Apr 29, 2021 02:22PM

#26:
I already got complains from other teams (including toolchain team) that emulator image is holding them back;
The decision to update tool chain is more based on physical hardware, not based on emulator. going forward, emulation
is likely the only solution we have left with.(performance could take a hit on certain CPUs, but restricting SSSE3 usage will slow down
other CPUs that do have SSSE3).
(btw, assign this emulator specific bug to other team will keep it in unresolved longer)

ps...@gmail.com <ps...@gmail.com> #28May 9, 2021 09:35AM

It is not acceptable that SSSE3 is mandatory.
Many tools, emulators and visualization solutions are supporting CPUs without SSSE3. Without performance issues. Please provide a fix.
(You may use SSSE3 when it is supported by a specific CPU)

ml...@e2f.com <ml...@e2f.com> #29May 21, 2021 01:27PM

If Google wants to restrict the required hardware that's up to them.

It would be good if the product supports CPU's in common use over the previous five or so years, but not necessarily those introduced further back than that. The low level of activity on this thread probably reflects the level of interest and priority the problem should be given. At least I know know where things stand.

I do think some official statement on required hardware should be provided on release. Otherwise dev's just waste their time trying to figure out what's going on. Personally this is just a hobby. I could walk away from Android development until I felt comfortable with the way forward, which for me was an easy US$100 CPU upgrade to AMD FX.

I guess if some large customer is interested in this issue they could offer to pay, or scream loudly. Google also might want to consider the goodwill and popularity of the platform amongst relatively impoverish developers tapping away at home on old desktops (who might make recommendations to less impoverished workplaces).

mi...@agilecreatives.net <mi...@agilecreatives.net> #30Jun 11, 2021 12:29PM

#29 I think the primarily reason is that AMD CPUs are more popular among hobbyists (due to their price) rather than offices. And for hobbyists I hardly imagine this being a showstopper to Android development — they'd find this thread, see this is not fixed, and pass by to Geanymotion, which is based on VirtualBox and free for non-commercial use. So I did (well, except that I didn't pass by, but I am just an eccentric person).

> If Google wants to restrict the required hardware that's up to them.

I do agree in general, but I'm annoyed by the fact I don't see in this thread any links to a bugreport which would say that Android Emulator doesn't work on certain CPUs on Windows for the same SSSE3 reason. Just show me one, and be sure, I'd be calmed down.

mu...@google.com <mu...@google.com> #31Jun 17, 2021 10:37AM

Any progress on this? - having the same issue on my Phenom II - this build is required for React Native emulation...

unselect_aggregate.png

25 KB

View

Download

mi...@gmail.com <mi...@gmail.com> #32Jun 17, 2021 10:41AM

This just bit me in the ass today. I wonder what the reasoning behind this "feature" was?

iv...@olioex.com <iv...@olioex.com> #33Jun 17, 2021 10:48AM

Sorry (again). I do apologize for the bad experience.
I do not understand the reasoning of forcing SSSE either. As #26 pointed out, direct way of solving the issue is not to assume SSSE. However, I do remember argument from toolchain team is "Since all x86 hardware android is currently running on has this, we can assume this to reduce maintenance effort". That does not make much sense to me. In real life, android on X86 hardware seems to be rare. And this type of reason can be used in future again and again.
Perhaps as user, you can open a bug to toolchain team asking for their help?
Back to the emulator side, we do not have any update so far. Emulating all these instructions might be a solution but we do not have time to cover this. Whether we should go this way is under discussion. SSSE is SIMD which aims performance gain in certain application. Emulating is slow as we all see in running arm image on x86.

mi...@agilecreatives.net <mi...@agilecreatives.net> #34Jun 17, 2021 11:58AM

Probably, I have the same issue with AMD Athlon 64 x2 3600+.

Message last modified on Jun 17, 2021 11:58AM

fa...@gmail.com <fa...@gmail.com> #35Jun 23, 2021 11:35AM

3 years and still no resolution of this issue?

ar...@pc.partners <ar...@pc.partners> #36Jul 2, 2021 03:17AM

I think it's pretty obvious by now that supporting old processors for desktop android development is not a priority for google. It probably doesn't help that these old CPU's are getting more ancient by the day. Best buy a new PC, or a new CPU if you have a compatible MB socket (AMD FX-6300 for US$70).

ji...@gmail.com <ji...@gmail.com> #37Jul 15, 2021 01:09PM

So, per m....@gmail.com, we have to purchase a compatible MB socket (that is, AMD FX-6300)

jc...@solarcasa.energy <jc...@solarcasa.energy> #38Jul 16, 2021 11:14AM

#37 - No, not a MB socket (MainBoard socket, i.e. the place where the CPU goes), you have to get a more recent CPU / processor that supports SSSE3. AMD introduced SSSE3 support in their FX series desktop CPUs (Bulldozer microarchitecture) in late 2011, e.g. the FX-6300, FX-8150, FX-4100, and a few more. And it's possible that your PC works with one of them without changing anything else but the processor.

The FX series CPUs use socket AM3+ which is to some extends backwards compatible to socket AM3 and that socket was used by some Phenom II era systems / mainboards. Check the (online) CPU compatibility list for your mainboard whether you have CPU upgrade options with your current board. But you can be unlucky and either have an older socket AM2+ board or a board that simply doesn't support FX series processors.

Would also check whether it's even worth upgrading an old 2008 processor to an almost equally old FX processor - it's probably the cheapest option but I would have a general look at used systems or used CPU+mainboard combinations, there are a lot out there that are more recent than the FX6300 and they are not that much more expensive.

br...@gmail.com <br...@gmail.com> #39Jul 20, 2021 09:50AM

The problem is that the forcing of SSSE3 instructions was not highlighted in Android Dev. Docs before it was pushed. And like this was forced over-night on developers, who can say if the next version of emulator requires an even newer set of CPU instructions.

As such, if I buy now a FX-6300 or better AM3+ CPU and find out that with Android Studio 3.4 I need at least Ryzen or only works on Intel ... just because the people responsible with these tools don't care to deprecate it in a version or 2, with actually announcing this at least on the blog or during IO ... what do I do then ? Why are Android Tools devs copying Apple's way of "deprecating" and "improving" the tools we use ?

Message last modified on Jul 20, 2021 10:59AM

re...@gmail.com <re...@gmail.com> #40Jul 30, 2021 07:35PM

I have to correct that it is NOT emulator or Android Studio forced an over-night change. It is Android itself who pushed that change. Things are a bit interesting here. Although system images (Android OS itself) is released together with emulator but it was not within emulator/android studio team's control. The team also has to accept such changes made by OS team. To end users, this might not be important. However, filing bugs to OS team might really solve your issue or the request could be denied as usual.
I have to agree at least we should disclose such kind of information to user.

al...@cazisoft.com <al...@cazisoft.com> #41Aug 22, 2021 02:30PM

Ok. I guess since it's been 3 years now I guess there are very few people willing to change things now.
How can we at this moment get a promise from the OS team that :
1. they will not change things like this (forcing users to upgrade hardware to use generic Android tools) without at least 1-2 years of prior notice
2. publish these kind of changes on Android Docs or Google Android Blog ... or anywhere that users have time to adjust
?

lu...@wetlandssake.com <lu...@wetlandssake.com> #42Jan 17, 2022 09:36PM

"As such, if I buy now a FX-6300 or better AM3+ CPU and find out that with Android Studio 3.4 I need at least Ryzen or only works on Intel ... just because the people responsible with these tools don't care to deprecate it in a version or 2, with actually announcing this at least on the blog or during IO ... what do I do then ? Why are Android Tools devs copying Apple's way of "deprecating" and "improving" the tools we use ?"

It's not like it's a major expense (compared to a new PC).

I can easily see how this could have been overlooked by google and most corporate development shops. How many of them would still be using old AMD CPU's? The problem is probably cropping up now because PC upgrades are far less worthwhile than they were 10 years ago. So many small/sole outfits have probably not bothered upgrading in years.

If these changes are truly driven by improvements to the Android OS, then I don't think the OS team should be overly constrained by having to support really old development hardware. But they should endeavour to signal changes in advance so that poorer development shops can start resourcing the support/funds for new hardware. If would also be good if they were clearer on what is/isn't going to be fixed.

Message last modified on Jan 17, 2022 09:37PM

mi...@agilecreatives.net <mi...@agilecreatives.net> #43Feb 2, 2022 06:57PM

Hi, we're wondering if anyone with this issue is seeing it on both Google APIs images and AOSP images, or only one of the two. Would anyone have time to check?

Message last modified on Feb 2, 2022 06:59PM

2022-02-02_13-42-37.png

9.5 KB

View

Download

2022-02-02_13-46-31.png

9.8 KB

View

Download

a....@gmail.com <a....@gmail.com> #44Apr 4, 2022 02:52PM

#42 Thanks for understanding. I do not know the intension of such changes personally but typically with newer SIMD instructions you can get better memory load/store performance (memcpy) in addition to scientific calculations. The former is interesting since usually people won't associate it with SIMD.

bi...@gmail.com <bi...@gmail.com> #45Apr 18, 2022 12:32AM

I will close the bug. But user can file bug to Android OS asking for removing SSSE3 requirement.

kr...@remerge.io <kr...@remerge.io> #46May 10, 2022 08:50AM

Так и не исправили.

al...@gmail.com <al...@gmail.com> #47May 22, 2022 04:29PM

Not all x86 hardware has SSSE3 CPU features, once I used a Acer x86 based tablet to run OpenSSL and found some open source library assumes SSSE3 existed in all x86 configuration and caused crash problem.

Message last modified on May 22, 2022 04:30PM

[Deleted User] <[Deleted User]> #48Jun 30, 2022 01:03PM

Same Problem here. I think i tried everything i could, but nothing seems to do the job. Could we have an answer or a way to solve this from the google team ?

Message last modified on Jul 6, 2022 07:12AM

ma...@gmail.com <ma...@gmail.com> #49Jul 6, 2022 07:14AM

Comment has been deleted.

Message last modified on Jul 6, 2022 07:14AM

[Deleted User] <[Deleted User]> #50Jul 13, 2022 04:49AM

1. I've been having this issue for 2 years now!
2. Google is doing nothing to resolve the situation.
3. Very often this problem is solved by creating a new file, transferring the source code to it and working with the new file.

For Google employees:
I wonder if your management is not ashamed to do nothing on this issue for several years ?

aa...@caredesk.org <aa...@caredesk.org> #51Aug 17, 2022 07:57PM

onEdit script my team has been using no longer works and provides the same error listed above. Please fix!

ro...@aboitizpower.com <ro...@aboitizpower.com> #52Aug 17, 2022 08:06PM

I'm having problem using .getAs('image/png') for charts, kindly fix this.

mi...@gmail.com <mi...@gmail.com> #53Aug 17, 2022 08:30PM

Good luck. This bug has been in the queue for over two years. Everyone has
the same basic complaint...my stuff suddenly stopped working after it had
worked fine for months or years. It is very clear Google has no appetite to
fix the problem.

On Wed, Aug 17, 2022, 3:57 PM <buganizer-system@google.com> wrote:

- Show quoted text -

mi...@gmail.com <mi...@gmail.com> #54Aug 29, 2022 03:56AM

I don't have a solution, but I was able to implement this workaround

bm...@gmail.com <bm...@gmail.com> #55Aug 31, 2022 02:53PM

This is somewhat distressing.. my script that used to work for over six months has been displaying this exception now. Is there a reason this is not going to be fixed?

ma...@condenast.com <ma...@condenast.com> #56Sep 15, 2022 04:06PM

I experienced this issue while trying to use a Combo Chart. The script presents the error only when using a combo chart.

[Deleted User] <[Deleted User]> #57Sep 30, 2022 07:23AM

I'm now experiencing this issue - code has worked fine for months up until this morning when it failed to complete. No change has been made to the code and trigger ran as expected but just didn't complete. I get the error on my line 5 and I don't know how to fix
function duplicateSheetWithProtections() {
var currentDate = Utilities.formatDate(new Date(), "GMT", "dd/MM/yy"); //format for date
var ss = SpreadsheetApp.getActiveSpreadsheet();
sheet = ss.getSheetByName('EComm VCB Master'); // detailing which sheet to copy
sheet2 = sheet.copyTo(ss).setName(currentDate);

I have this code saved in another sheet that I originally used to create the code so I wasn't messing around in a live document and that one is still working fine

[Deleted User] <[Deleted User]> #58Dec 21, 2022 03:30PM

This might help someone although not related to charts per se: I just ran into a similar problem where all calls regarding sheets under the active spreadsheet would throw this error even though the script had not changed for a long time.

Examples of Apps Script function calls that would throw ”Service Spreadsheets failed while accessing document with id ...”:

SpreadsheetApp.getActiveSpreadsheet().getActiveSheet()
SpreadsheetApp.getActiveSpreadsheet().getSheets()
SpreadsheetApp.getActiveSpreadsheet().getNumSheets()

The fix to this was about as obscure as the error. Tracing back the file's version history, I found out that an XLOOKUP formula was added in one cell. There were no formula errors or anything hinting at this formula causing problems and it produced good output. Still, this one cell was actually making all sheet operations from Apps Script side throw. After clearing this cell the script worked again.

XLOOKUP is a new function that was just added to Google Sheets a few months ago, I'm wondering if it could still have some bugs. Inserting the XLOOKUP formula again reproduces the buggy behavior and I might investigate this a bit more to build a minimal reproducible example sheet that I could share.

ph...@gmail.com <ph...@gmail.com> #59Jan 11, 2023 06:18PM

Hey everyone,

also, similar issue, code was working yesterday and now it's not. I get the feeling that in most cases described here, people worked with charts, in my case the same exception was thrown on the last line of the code fragment below where I'm using setValue(). Anyhoo, my script was binded to a spreadsheet and originally I was using getActiveSpreadsheet and getActiveSheet (lines 2 and 3 of the snip below) . However, once I changed to openByID and getSheetByName (lines 4 and 5), it started working ¯\_(ツ)_/¯.

const insertTableForNewMonth = function(monthName) {
// const ss = SpreadsheetApp.getActiveSpreadsheet() // Not working
// const sheet = ss.getActiveSheet(); // Not working
const ss = SpreadsheetApp.openById('########')
const sheet = ss.getSheetByName('##');
const startColumn = sheet.getLastColumn() + 2;
const monthNameRange = sheet.getRange(1, startColumn, 1, 4);
monthNameRange
.merge()
.setValue(getCurrentMonthName()) // exception was thrown here

Hope this helps someone.
Cheers

[Deleted User] <[Deleted User]> #60Jan 19, 2023 11:16AM

Same issue here with this code

''' var newDataSourceSheetName = year+"_"+ month +"_Data_Source"; var templateSheet = activeSpreadsheet.getSheetByName("Template_Data_Source"); templateSheet.copyTo(activeSpreadsheet).setName(newDataSourceSheetName); var dataSourceNewSheet = activeSpreadsheet.getSheetByName(newDataSourceSheetName); ''' This line explores with the same error. No changes in months and was always working

templateSheet.copyTo(activeSpreadsheet).setName(newDataSourceSheetName);

sa...@melhorenvio.com <sa...@melhorenvio.com> #61May 30, 2023 07:37PM

This issue is already 2 years old and no solution.. I'm having the same problem today.

The solution presented in

comment #13

is a workaround that currently works.

jp...@google.com <jp...@google.com> Jul 13, 2023 02:34AM

Assigned to wo...@google.com.

en...@foundernest.com <en...@foundernest.com> #62Sep 15, 2023 07:45AM

Hi, I'm still facing this same issue :(

kk...@nyle.com <kk...@nyle.com> #63Sep 28, 2023 01:35PM

me too:(

ja...@gmail.com <ja...@gmail.com> #64Oct 16, 2023 07:11PM

Same issue.

la...@gmail.com <la...@gmail.com> #65Oct 17, 2023 04:40PM

I'm also experiencing the same issue. The error is 'Service Documents failed while accessing document with id 1monbg_HQxB_nSOrg7kQUGcD45RkLClcKurbfjhlGIXM.'

sr...@gmail.com <sr...@gmail.com> #66Oct 19, 2023 01:27AM

I am also having this issue. I'm copying cells from one sheet and formatting it in a different sheet in the same workbook. There are only ~200 rows. I have added Utilities.sleep(2000) to my calls so it doesn't overwhelm the API

te...@detechcentral.com <te...@detechcentral.com> #67Oct 21, 2023 03:15PM

I haven't changed anything with the application, and just today, "bam", now I get this error:
ERROR: ScriptError: Exception: Service Spreadsheets failed while accessing document with id:
The data in the google sheets have not changed, and the code has not changed.
So the question really is what did Google change?

cn...@usaid.gov <cn...@usaid.gov> #68Feb 20, 2024 11:58AM

Comment has been deleted.

Message last modified on Feb 20, 2024 11:58AM

ci...@gmail.com <ci...@gmail.com> #69Feb 20, 2024 11:59AM

Exception: Service Spreadsheets failed while accessing document with id 1aIzMeuDLCCeCjW02KbGsgQGgz0reOyv7.

le...@gmail.com <le...@gmail.com> #70Apr 9, 2024 12:06AM

Having the same issue. Spread sheet worked fine. Now it suddenly says:

Exception: Service Slides failed while accessing document with id XXXXXXXXXXXXXXXXX.

ti...@hotmail.com <ti...@hotmail.com> #71Apr 18, 2024 09:23AM

Me too. Has Google ever responded on this issue??

me...@geotab.com <me...@geotab.com> #72Apr 19, 2024 11:34PM

This is not exclusive to Sheets; I get this same error while trying to insert (Page.insertImage(blobSource)) or replace (PageElement.asImage().replace(blobSource)) an image in a Slides document.

It started randomly and only happens in a specific document; I recreated the doc and container-bound script from scratch and the new version has no issue.

In fact, I tried changing the scripts to each edit the other doc (using SlidesApp.openById(id)), and the old script successfully edits the new doc, while the new script fails to edit the old doc. Whatever is causing the issue must be within the doc itself, not the script.

ma...@jlborgo.com.au <ma...@jlborgo.com.au> #73Jun 19, 2024 10:38AM

Same issue here. Occurred out of nowhere after years.

[Deleted User] <[Deleted User]> #74Jul 1, 2024 07:29AM

Comment has been deleted.

Message last modified on Oct 24, 2024 03:31AM

ku...@coefficient.io <ku...@coefficient.io> #75Aug 2, 2024 05:03PM

This is a big issue impacting us. We're trying to use combo charts and it's not working. We can't pull them via API. Regular charts work fine. Please fix

an...@coefficient.io <an...@coefficient.io> #76Aug 2, 2024 05:05PM

Same issue, specifically when calling .getAs("image/png") on a Combo chart. If I switch it to an Area chart there's no issue. Would be great to see this issue addressed. Thanks!

to...@gmail.com <to...@gmail.com> #77Oct 17, 2024 11:51PM

Exactly the same as previous comment, error happens on a Combo chart that has a left and right axis, fine with a Line chart. Charts created using GAS.

ya...@embibe.com <ya...@embibe.com> #78Oct 25, 2024 06:58PM

Same issue faced by me. Any solution for this?

sh...@paypay-corp.co.jp <sh...@paypay-corp.co.jp> #79Feb 3, 2025 07:44PM

Same issue here. I hope this will be fixed...

ma...@schibsted.com <ma...@schibsted.com> #80Feb 13, 2025 05:52PM

Here is a sheet with connected apps script to illustrate the problem for combo charts.

https://docs.google.com/spreadsheets/d/13ZgoU1XledWP_LrMFdMvpjQyOsZ4au1H4J3NQhMqV3I/

The sheet has line, column, area and combo charts, stacked and not stacked, created from scratch from the same data. Some use both axis, some use only left. None of them have checked "Aggregate". The script tries to change the title of the charts.
...
let updatedChart = chart
.modify()
.setOption("title", new_title)
.build()
sheet.updateChart(updatedChart); // throws error

All types of line, area and column charts work.
All of the combo charts throws the error "Service Spreadsheets failed while accessing document with id 13ZgoU1XledWP_LrMFdMvpjQyOsZ4au1H4J3NQhMqV3I"

wa...@gmail.com <wa...@gmail.com> #81Feb 15, 2025 06:36AM

Same issue here
sheet.updateChart(updatedChart);
then throws error "Service Spreadsheets failed while accessing document with id xxx"

ce...@dish.com <ce...@dish.com> #82Mar 17, 2025 08:04PM

I'm seeing OP posted about this on 2021. It is 2025 and the issue is still there.

ma...@gmail.com <ma...@gmail.com> #83Mar 18, 2025 12:50AM

I am also having this issue.

eb...@gmail.com <eb...@gmail.com> #84Mar 31, 2025 12:42PM

Another example of the issue:

https://docs.google.com/spreadsheets/d/1ty4R7uxoYw9H3MqxFioaVz51C1lBbOixxVdcXWSo-vQ/edit?gid=906716897#gid=906716897

Any word on if this is being looked at, or if this is something that will be corrected? 4 Years is a long time to wait for a resolution.

Message last modified on Mar 31, 2025 12:42PM

Issue 182701055

Description

Issue summary

Comments

[Deleted User] <[Deleted User]> #2Mar 16, 2021 03:45AM

ra...@google.com <ra...@google.com> #3Mar 16, 2021 01:35PM

iv...@olioex.com <iv...@olioex.com> #4Mar 16, 2021 01:55PM

ra...@google.com <ra...@google.com> #5Mar 16, 2021 02:35PM

[Deleted User] <[Deleted User]> #6Mar 16, 2021 02:54PM

iv...@olioex.com <iv...@olioex.com> #7Mar 16, 2021 03:26PM

st...@ostec.de <st...@ostec.de> #8Mar 17, 2021 02:19PM

[Deleted User] <[Deleted User]> #9Mar 17, 2021 05:48PM

ma...@gmail.com <ma...@gmail.com> #10Mar 18, 2021 02:43AM

ma...@gmail.com <ma...@gmail.com> #11Mar 18, 2021 12:33PM

[Deleted User] <[Deleted User]> #12Mar 18, 2021 11:31PM

cp...@gmail.com <cp...@gmail.com> #13Mar 19, 2021 04:56PM

ma...@gmail.com <ma...@gmail.com> #14Mar 22, 2021 03:11AM

bo...@gmail.com <bo...@gmail.com> #15Mar 24, 2021 12:15AM

y-...@grandsight.biz <y-...@grandsight.biz> #16Mar 24, 2021 12:24AM

[Deleted User] <[Deleted User]> #17Mar 24, 2021 02:47AM

is...@sparta.cl <is...@sparta.cl> #18Mar 25, 2021 12:36PM

[Deleted User] <[Deleted User]> #19Mar 26, 2021 10:18AM

ra...@google.com <ra...@google.com> #20Mar 26, 2021 04:13PM

jc...@solarcasa.energy <jc...@solarcasa.energy> #21Mar 31, 2021 01:24PM

xa...@gmail.com <xa...@gmail.com> #22Apr 6, 2021 08:59AM

li...@gmail.com <li...@gmail.com> #23Apr 6, 2021 07:22PM

ns...@greenpeace.org <ns...@greenpeace.org> #24Apr 7, 2021 10:26AM

a....@gmail.com <a....@gmail.com> #25Apr 14, 2021 06:28PM

yg...@caylym.com <yg...@caylym.com> #26Apr 21, 2021 07:33PM

mi...@agilecreatives.net <mi...@agilecreatives.net> #27Apr 29, 2021 02:22PM

ps...@gmail.com <ps...@gmail.com> #28May 9, 2021 09:35AM

ml...@e2f.com <ml...@e2f.com> #29May 21, 2021 01:27PM

mi...@agilecreatives.net <mi...@agilecreatives.net> #30Jun 11, 2021 12:29PM

mu...@google.com <mu...@google.com> #31Jun 17, 2021 10:37AM

mi...@gmail.com <mi...@gmail.com> #32Jun 17, 2021 10:41AM

iv...@olioex.com <iv...@olioex.com> #33Jun 17, 2021 10:48AM

mi...@agilecreatives.net <mi...@agilecreatives.net> #34Jun 17, 2021 11:58AM

fa...@gmail.com <fa...@gmail.com> #35Jun 23, 2021 11:35AM

ar...@pc.partners <ar...@pc.partners> #36Jul 2, 2021 03:17AM

ji...@gmail.com <ji...@gmail.com> #37Jul 15, 2021 01:09PM

jc...@solarcasa.energy <jc...@solarcasa.energy> #38Jul 16, 2021 11:14AM

br...@gmail.com <br...@gmail.com> #39Jul 20, 2021 09:50AM

re...@gmail.com <re...@gmail.com> #40Jul 30, 2021 07:35PM

al...@cazisoft.com <al...@cazisoft.com> #41Aug 22, 2021 02:30PM

lu...@wetlandssake.com <lu...@wetlandssake.com> #42Jan 17, 2022 09:36PM

mi...@agilecreatives.net <mi...@agilecreatives.net> #43Feb 2, 2022 06:57PM

a....@gmail.com <a....@gmail.com> #44Apr 4, 2022 02:52PM

bi...@gmail.com <bi...@gmail.com> #45Apr 18, 2022 12:32AM

kr...@remerge.io <kr...@remerge.io> #46May 10, 2022 08:50AM

al...@gmail.com <al...@gmail.com> #47May 22, 2022 04:29PM

[Deleted User] <[Deleted User]> #48Jun 30, 2022 01:03PM

ma...@gmail.com <ma...@gmail.com> #49Jul 6, 2022 07:14AM

[Deleted User] <[Deleted User]> #50Jul 13, 2022 04:49AM

aa...@caredesk.org <aa...@caredesk.org> #51Aug 17, 2022 07:57PM

ro...@aboitizpower.com <ro...@aboitizpower.com> #52Aug 17, 2022 08:06PM

mi...@gmail.com <mi...@gmail.com> #53Aug 17, 2022 08:30PM

mi...@gmail.com <mi...@gmail.com> #54Aug 29, 2022 03:56AM

bm...@gmail.com <bm...@gmail.com> #55Aug 31, 2022 02:53PM

ma...@condenast.com <ma...@condenast.com> #56Sep 15, 2022 04:06PM

[Deleted User] <[Deleted User]> #57Sep 30, 2022 07:23AM

[Deleted User] <[Deleted User]> #58Dec 21, 2022 03:30PM

ph...@gmail.com <ph...@gmail.com> #59Jan 11, 2023 06:18PM

[Deleted User] <[Deleted User]> #60Jan 19, 2023 11:16AM

sa...@melhorenvio.com <sa...@melhorenvio.com> #61May 30, 2023 07:37PM

jp...@google.com <jp...@google.com> Jul 13, 2023 02:34AM

en...@foundernest.com <en...@foundernest.com> #62Sep 15, 2023 07:45AM

kk...@nyle.com <kk...@nyle.com> #63Sep 28, 2023 01:35PM

ja...@gmail.com <ja...@gmail.com> #64Oct 16, 2023 07:11PM

la...@gmail.com <la...@gmail.com> #65Oct 17, 2023 04:40PM

sr...@gmail.com <sr...@gmail.com> #66Oct 19, 2023 01:27AM

te...@detechcentral.com <te...@detechcentral.com> #67Oct 21, 2023 03:15PM

cn...@usaid.gov <cn...@usaid.gov> #68Feb 20, 2024 11:58AM

ci...@gmail.com <ci...@gmail.com> #69Feb 20, 2024 11:59AM

le...@gmail.com <le...@gmail.com> #70Apr 9, 2024 12:06AM

ti...@hotmail.com <ti...@hotmail.com> #71Apr 18, 2024 09:23AM

me...@geotab.com <me...@geotab.com> #72Apr 19, 2024 11:34PM

ma...@jlborgo.com.au <ma...@jlborgo.com.au> #73Jun 19, 2024 10:38AM

[Deleted User] <[Deleted User]> #74Jul 1, 2024 07:29AM

ku...@coefficient.io <ku...@coefficient.io> #75Aug 2, 2024 05:03PM

an...@coefficient.io <an...@coefficient.io> #76Aug 2, 2024 05:05PM