I am unable to recover deleted projects in Azure DevOps Server 2020 On premsie. Do you have any idea?
You can try visiting this project using InPrivate window or on different browsers. If it worked fine in private mode. It was probably caused by corrupted cache data. Then you need to clear your browser data. Clear cookies and local storage ("developer tools/application/clear storage/clear site data"). See this similar thread for more information.
This error could be caused by some preview features too. If you enabled some preview features. You can try disabling them to see if the error will be gone. See this thread for more information.
Related
I have a GCP project. Then I gave permission to a user A with email A#email. They connected it to Firebase and developed a project there with hosting enabled and verified. Then another user B came and I switched the ownership of the project to them and removed A from this. After ownership change, the hosting verification was re-triggered (as expected). However, since 1 week it only shows
I tried searching for other people who had such an issue and nothing came about. I even wrote a bug report but for more than a week nobody has reached out to me and I am worried because the grace period is 1 month and I my project could go down. Have you heard of similar problems?
Edit from comment:
I can confirm that the error comes in Chrome and incognito (version: 80.0.3987.163 (Official Build) (32-bit)) and in Firefox and incognito (version: 72.0.2 (64-bit)). Opening the console gives error 503 for URLs https://clients6.google.com/siteVerification/v1/webResource?verificationMethod=DNS_TXT&alt=json&key= and https://clients6.google.com/siteVerification/v1/token.
The issue was due to my company's license agreement with Google and the way Firebase Hosting is made. More details below.
Strangely enough, using GCP and Firebase require a GCP license. With this license you can do everything from adding/changing/modifing collections/projects. However, the functionality to 'Verify' your hosting site goes through the Google Console which is not included in the license.
Encountered this same thing. The problem turned out that I was using a Google Workspace account that did not have "Google Search Console" enabled for the domain I was logged in on.
To remedy, I had to login to my Workspace Admin, and go turn it on as shown below.
I want to get the unreal engine source from github. I followed the steps on unreal engine 4 on github, I created an epic games account. After that I need to associate that account with my github account. After step 5 "After opening the Connected Accounts menu, select the Connect button below the GitHub icon", I got this:
The problem is, clicking the "Authorize EpicGames" in the light green part did nothing. I don't know where the problem is and I cannot proceed. Anyone have encountered this?
One reasonable explanation is network problem. I mean if there are some problems with some servers, but I'm not sure.
Now I know the answer.
Github page warns that "Please note that Github no longer supports your web browser".
But I ignored it before.
So using my latest firefox or updating the outdated chrome which I was using to the latest version solved my problem.
https://status.epicgames.com/ reports:
Jul 18, 2018 Matchmaking issues
Resolved - The issues impacting matchmaking have been addressed and we're seeing full recovery. Jul 18, 00:49 UTC
It is possible there are still lingering effects of incidents on epicgames side.
I keep getting this error occasionally. It is really annoying because sometimes it fixes itself, but mostly I just have to close VS and reopen and then it will work again for a while.
It happens when I try to pull from a branch (or any other git network interaction).
Error encountered while fetching: An error occurred while sending the request.
Inner Exception:
The remote name could not be resolved: 'github.com'
Sometimes it fixes itself after an unknown period of time.
Sometimes I do nothing during that period of time.
Sometimes I click around and check out other branches and do pull requests and then it works again.
Mostly I have to restart VS to get it working again.
Has anyone else had this issue? How did you resolve?
I am also using two factor auth. if that is the issue. (Doesn't appear to be the issue)
I also receive this error when starting up VS sometimes:
We were unable to automatically populate your Visual Studio Team Services accounts.
The following error was encountered: TF400813:
Resource not available for anonymous access. Client authentication required.
So perhaps it is that the github.com authentication is being lost at some point during interactions and restarting VS fixes it.
Another clue is that when github.com can't be reached, it can't be browsed to in the browser in Visual Studio. It can be browsed to fine in Chrome (or FireFox or IE). Visual Studio also seems to lose connection to nuget.org occasionally as well, the effect appears to be the same.
Possible related issue:
Visual Studio/C#: Nuget Unable to connect to remote server
UPDATE: This happens on two different ISPs and one of them was not on the corporate firewall (this rules out network issues). When the issue happens it actually shuts down ALL network communication from within Visual Studio, so this isn't just a github.com issue. I have a ticket open with Microsoft, hopefully we will get it resolved and I can post the answer for everyone.
After back and forth with Microsoft support and the release of VS 2017.
The answer is to upgrade!
How can I fix this error so that the migration completes please?
OH-SCM-009: Error occurred while sync. GetAndDownloadFile :The server returned content type text/html; charset=UTF-8, which is not supported.
Retrys all seem to fail at same changeset ID 371
Thank you
depending on your on-premises TFS version, the issue could be in your TFS Data Cache (on the machine where TFS is deployed) or configuration of Visual Studio or even corruption of data.
This (https://social.msdn.microsoft.com/Forums/vstudio/en-US/b3c9ab89-17b0-45b1-bf70-4c338ae6b523/the-server-returned-content-type-texthtml-charsetutf8-which-is-not-supported?forum=tfsgeneral) thread might be referred to, for a possible solution. Which suggests the user to clear his cache.
In any case, it might be a good idea to contact Microsoft Support or try posting on Social MSDN.
I habe a web role in azure. It is running fine locally in development app fabric, but fails silently when deployed to Azure (simply no response at all for any request).
I assume it's some problem with the web.config, but that is happening so early that it occurs already before I can set up the diagnostic stuff in global asax. As said, it's working fine locally, but there is simply no response at all from the azure system.
How can I find out what specifically is wrong to be able to solve it like get the exception text, stack trace, IIS application system error log or anything that could hint me to the real problem?
The absolute first thing that is run in a Web role is not your application but the OnStart() method in WebRole.cs in your Azure project. This is the place to add code to monitor your Web site.
The standard technique is to copy your application trace logs and the Windows event logs to Azure table storage, together (if appropriate) with instrumentation for CPU usage, IIS statistics and what-have-you.
A good introduction to this is here: http://blog.bareweb.eu/2011/01/beginning-azure-diagnostics/
and a good followup with details on the specifics you'll need in your application is here: http://blog.bareweb.eu/2011/03/implementing-azure-diagnostics-with-sdk-v1-4/
which remains applicable for the Azure SDK 1.5.
Once you are capturing diagnostics, you can either use Visual Studio to view them directly, or you can use a tool like the Cerebrata Azure Diagnostics Manager to graph and filter them automatically. This tool is a little rough around the edges (especially for larger systems with multiple instances: the graphs aren't really useful) but is as good as it gets at the moment.
An alternative approach is to use Remote Desktop to connect to the remote instance and do some spelunking in the Windows event logs and suchlike. You can also use the Internet Explorer browser that's on the remote instance to directly connect locally to the application and see any errors etc. that may otherwise be hidden.
Personally I'd only do this if the diagnostic storage mechanism isn't working: production servers really should have remote desktop access turned off altogether to reduce the possible surface area for external attack.
Setting up diagnostics is the best long term solution to dealing with tracking errors in your application. If you want something a little more ad-hoc you can either catch the errors and write them to blob storage or use your own light weight trace listener.