Google Workspace Drive - creating documents issue "Something went wrong" - google-chrome

I have a problem with my new Google Workspace. When I am creating a new document or sheet, there is always only message "Something went wrong. Reload":
After reload, there is next page with message:
Under the same Chrome browser I am using two profiles, personal and business.
In personal Drive, everything works properly. The problem is only with Google Workspace profile.
I already tried to clean all Chrome data (history, cookies, setting...) but nothing solve this issue.
Do you have any idea where the problem is?

Finally after about 20 hours Google Drive under workspace starts work poperly.
I seems that, there was some issue on some Google servers.

Related

Google Apps scripts called from Google sites now (suddenly) returning 404 error

I have a Google site (https://sites.google.com/site/kitchenergaffers/) which has many pages where scripts are launched. This morning (18 August 2020 EDT) I see that none of the script pages are working and the script seems to be reporting a 404 error of some sort.
The scripts interact with a series of Google sheets
Here is an example of one such page
https://sites.google.com/site/kitchenergaffers/home/general-gaffers-information/publish/directory-of-results?display=directory
=============
404. That's an error.
The requested URL /accounts was not found on this server. That's all we know.
There are many pages that run the same script, and some pages that have different scripts.
All scripts are set to run Anonymously, anyone can execute
Nothing on the site or within the scripts code or Sheets has changed to create this issue.
UPDATE: Although the error comes up using Chrome browser when logged into the creator account, or my personal account if I open an incognito window they run correctly!
UPDATE2: My PC suffered a Windows update yesterday that may be related however, my Chromebook shows the same problem. This problem does not happen if I use Edge browser.
UPDATE3: If I log out of all my accounts, and only sign in to one of them, the problem does not happen. Once I log into an additional account, the problem recurs. Signing out of all, then back into one only is then necessary.
as of 15:00EDT 20 August the issue seems to be resolved. I am not sure if it was something I did experimentally or what, but it has gone.
As it seemed to be related to my account and using Chrome I turned off sync, cleared cookies (also disabling Chrome extensions and bookmarks it seems) then "repaired" or reenabled extensions, resync'd to get the bookmarks from the Chromebook or phone and tried again.
The issue seems to have been resolved - maybe by these actions :)

Google Colaboratory and Google Drive integration fails

I am not able to save a new notebook in my Google Drive environment.
Google Colaboratory works with predefined notebooks such as Hello, Colaboratory, but I am not able to save any into my Drive folder.
I have the Colaboratory app allowed in the Google Drive settings and really dont know how to solve it. Colaboratory communicates with Drive - it even creates the notebook files in the Google Drives folder, but when loading any notebook file it always report following Notebook loading error
There was an error loading this notebook. Ensure that the file is accessible and try again.
Neither the details of the error help much:
Failed to fetch TypeError: Failed to fetch
I was playing with the access rights of both the file and the folder and could not find any solution.
Update: Chrome 64.0.3282.167 (64 bit); Windows 10 1709. I use two users on the Chrome. Creating Notebooks works normally on different computers with my username.
This is the output from console:
Chrome Console Output
On Google Chrome, I was seeing this issue randomly and it mentioned not being able to load the file /some/google/path/thats/gone/because/this/fixed/it/client.js. I tried clearing my cache and hard reloading, and sure enough, Colab starting working again.
As with standard cookies, third-party cookies are placed so that a site can remember something about you at a later time. Both are typically used to store surfing and personalization preferences and tracking information.
Google's colaboratory uses third party cookies and your browser most likely has them disabled.
Navigate to your browser settings, search for cookies and enable third party cookies. This should hopefully fix your problem.
I had the same problem, and I just disabled AdBlock on google Colab in everything works perfectly.
try to close/pause AdBlock and reload the page, it works for me.

Google Drive Page Not Found - Sorry, unable to open the file at this time

I'm using google scripts to deploy a web app. I've done about 5-10 in the same account. When I try and run the web app/script, I'm now getting: a "Google Drive: Page not found" in the title and the message
Sorry, unable to open the file at this time. Please check the address and try again.
I published it to run as the owner, but accessible to "Anyone, even anonymous".
I then tried creating a new small project with a doGet() method that returns a small static web page, with the same result.
Code.gs:
function doGet(e) {
return HtmlService.createHtmlOutputFromFile('Test');
}
Test.html:
<!DOCTYPE html>
<html>
<head>
<base target="_top">
</head>
<body>
This is a test
</body>
</html>
I tried publishing the same spreadsheet/code above in my personal account and it works fine. Since I already have some web apps deployed with the account that's having the error, is there a quota on the number of web apps per account?
I tried a different browser, a different account, re-publishing, and logging out and back in. Same error message. The "Test your web app with the latest code" link also fails. I can directly call the doGet() method in the IDE and it works fine, and I see output in the logs.
I don't see anything in the logs for the page not found error, which is what I expect with the page not found - not even getting to code execution, thus no logs.
I think you are logged in with two gmail account: That is why (/u/1,/u/0) may have been appended to script address (may be a bug).
So what you have to do is remove /u/0 or whatever is appended.
ForExample:
https://script.google.com/macros/u/1/s/ffffsdds/exec becomes https://script.google.com/macros/s/ffffsdds/exec
I have several Gmail accounts open at once and kept having this problem. I found it helped to close the Drive window, log out of the email account related to it, and then log back into the Gmail account and open Drive again.
You need to add your organization domain to the URL, as in https://script.google.com/a/yourdomain.com/macros/s/ffffsdds/exec - note that a/domain.com has been added. If you're not using a custom domain, use a/gmail.com.
It works when you are logged in to multiple accounts and redirects to
https://script.google.com/macros/s/ffffsdds/exec when you are not logged-in to the particular domain account.
Background info:
https://script.google.com/macros/u/1/s/ffffsdds/exec - does not work if you are logged-in with multiple accounts
In https://script.google.com/macros/s/ffffsdds/exec - "/u/x" has been removed but if you visit that URL, it will still redirect to https://script.google.com/macros/u/1/s/ffffsdds/exec and (1) problem remains when you are logged into multiple accounts (however it works if you are not).
It looks like it's related to this issue: https://issuetracker.google.com/issues/69270374. Authentication is broken for multiple signed-in accounts.
As Google developers suggests, you should:
Signing out of all accounts and using only 1 account: or
Using an incognito tab to sign in
source (comment 292).
What is sad is that, as they said:
The issue originally reported is due to recent improvements in Sheets' ability to handle multiple logged in accounts.
source (comment 11)
So by improving multiple logged in accounts, they also broke it.
Now the "good" news: we can expect this to be fixed in about 1 year I would say.
Our team plans to begin to work on multi-login support for the new Apps Script IDE and container-bound scripts in Q3 ‘21.
source (comment 292)
All the above answers are relevant. But for me, the issue was due to lack of space in Google account. I've used all 15GB space provided by Google and then all my Google Forms started showing the above error.
Solutions are:
Buy extra space from Google, it wont cost much. For 100GB, it costs Rs.130/month or Rs.1300/year
Free up your space. Go through the Google Drive and you may find a lot of unwanted files. Delete it and make some free spaces.

Unable to add new script in Adwords since new update

I've been a passive StackOverflow user for more than a decade now. I don't really think this is the place to ask this but Google Developers Help page referred me here.
Adwords has been updating to a beta version and I'm a heavy user of its Scripts console, but recently, when I want to ad a new script with the big red button, it starts loading and then this message displays: "There was a problem loading the script. Please try again later"
I've already tried with Chrome and Safari, a cookieless browser and with a different account and nothings seems to work. I also Google the error and there is nothing. I don't think I'm the only person experiencing this, do you have any solution?
I couldn't reproduce your problem and was able to create scripts—however, I've noticed quite a lot of bugs in the new web interface (to be fair, they say it's still in beta).
But as a workaround, just use the Return to previous AdWords link in the three dot option menu, which will take you back to the old interface. I could well imagine that you'll be able to add a new script there.

Unmatched app urls when trying to publish to Chrome Store

I'm getting the following error when I try to publish:
This hosted web app has one or more app urls not owned by the developer.
The web_url of this hosted web app is not owned by the developer.
I am getting the green warning box as described in:
https://code.google.com/p/google-apps-script-issues/issues/detail?id=1520
However, I'm hitting the refresh button and no joy in the solving the problem. I've published a lot of apps scripts in the past and never had this issue.
You have to register your url with the Google webmaster tools program and they will give you code to fix this. In case you have already done that, just go and verify again. It happened to me as well and I had to verify the site again. It works!