I deleted the agent from the settings, but it is still displayed in the google coloud projects list, and when I delete it with a command from google cloud, it is not deleted because the preemptive point is set.
Related
I was running a python program to fetch data from Azure Data Explorer, process it and write. The way I authenticate is:
import os
os.system("az login")
#browser pops up, I click on the relevant microsoft account and login.
I can now go back to my IDE and continue with my program. After finishing coding my programs, I restarted the kernel and ran it again for testing. This time, on the browser, I accidently clicked on the wrong micrsoft azure account and the login succeeded (because it was a valid login), but I knew it was wrong so I immediately restarted my kernel again. But ever since then I've been stuck at an error when I actually run a query:
'Caller is not authorized to perform this action', '#type': 'Kusto.DataNode.Exceptions.UnauthorizedDatabaseAccessException',
I tried cleaning the cache with az
az cache purge
#no output on console
I tried going to a different browser, closing everything and restarting. I also tried to find kusto or azure-data-explorer folders under AppData in the windows system and manually deleting the cache, but didn't find any such folders. Note: I haven't restarted the system yet, it's an ec2 instance and I have a lot of work open.
I am able to run the same program normally on a different windows machine succesfully. How can I fix this in an easy way in the future? I normally don't use windows or Azure for development work.
The az logoutcommand should do the work and let you logout from the current active accounts.
But as your tests this don't work for you so a second alternative is to use az logout with all specific accounts az logout --username -Doc
I have a standard Azure build -- one web role, one worker role. After the latest merge, it has decided that the roles are invalid. When I double click on the web role or worker role, or when I right click and choose "Properties", I get a grey screen saying "Invalid service definition or service configuration. Please see the Error List for more details". However, there is nothing at all in the Error List.
I have cross-compared the Settings elements and tried commenting out sections of the csdef and cscfg files, but nothing seems to bring the roles back to life. I have wasted half a day on this already. My question is not so much "What is wrong" -- more like, how on Earth are you supposed to find out what the error is when no information is given and successive blanking out of code draws a comprehensive blank?
I've run across this a couple of times (VS 2015 Enterprise). Simply closing and re-opening the solution resolved the issue.
In this case, nothing was wrong with the csdef and cscfg files. It was the way the wadcfgx files were linked to the roles.
I'm on a branch that is using Azure 2.5; the other branch is on a previous version of Azure, that uses the older version of diagnostics. By deleting the existing wadcfgx files and re-generating them, I was able to make the roles visible and editable again. Having different versions on different branches does, of course, open a very large can of worms, but we're stuck with that difficult situation for the time being.
Check if the VM Size specified in the configuration is Small or Extra Small as it doesn't support more than that on local emulator. In my case it was defaulted to Standard Size VM. I changed the size to Extra Small and it started working fine!
I just ran into this after adding a new Worker Role project to an existing cloud service with a few existing Worker Roles.
In my ServiceConfiguration.Cloud.cscfg, I had a <NetworkConfiguration> tag in between the old roles and the new role. This was the problem. I simply moved the <NetworkConfiguration> tag to the bottom as it was before (this tag is not in my ServiceConfiguration.Local.cscfg file, which might've been the problem).
Probably not the most common cause of this problem, but figured I'd post on the off chance someone has similar settings.
I have a 2013 SharePoint hosted app. I made some changes and went through the update process (changed the app version, kept the id the same, uploaded the package to the app catalog and updated the app immediately through the site contents of the site collection). Everything worked fine. However, when I go through the same process again with an even higher version, the app says that it's updating and after completion everything is the same. In fact, the app even shows that a new version is available. If I click "Get It", it says that it's updating for about 5 to 10 minutes and then nothing changes, same old app, same old files, same old version number, still says that a newer version is available. I get no error messages.
Any help or pointers are greatly appreciated, of course. Thank you.
UPDATE: In Central Admin. I started to monitor the app and found that there were failed upgrades with an error message of "There was a problem accessing the file system on the server."
I have created a website using mvc4, everything working fine in the dev environment.
The site was running for about 6 hours (luckily only a few people had registered) and then the database reverted to the state it would be when the site was first published.
I had made a few changed to the site since it had gone live (just to the views) and those changes persisted, had the site somehow re-published itself, those changes wouldn't have stayed.
The changes I made as to how the db seeds were all from this post; http://kevin-junghans.blogspot.ie/2013/01/seeding-customizing-aspnet-mvc.html .
Any help would be great, I can't pin down the problem and don't want to put the site live again until I know that user accounts won't be deleted.
If there is any more specific information that would be useful for identifying the problem let me know.
I ended up publishing the project including the database, than removing reference to initDb and recreating the database, then re-publishing.. And so far the issue hasn't happened again.
I've installed Gmail Meter script in Google Documents and launched it. It demanded many permissions and access to many google account elements. Script works quite slowly and meanwhile I decided to take back those permissions because they were too wide. An hour later I got mail notification about error, script cannot work without permissions.
I tried to turn off this working script but didn't find the way so I deleted (permanently) the file in which I installed the script. Since then I get every day 3 error notifications. I can turn off them (there is a link in a mail) but I'm more interested in terminating the script? What should I do?
Indeed the triggers should be terminated once the spreadsheet has been moved to trash. This is a known issue:
Issue 143: Spreadsheets with time triggered scripts should no longer trigger when spreadsheet is deleted
You can star this issue and turn the triggers off via the link in the email.
You can access all your script projects by opening the script editor and selecting Resources > All your triggers. Find the triggers you want to delete and click the 'x' icon next to them.
You should delete the triggers ...