I have inherited an non working AzureDev Ops 2019 server.
I have been tasked to fix it.
The only thing I seem to be able to access is the Administration console.
The site collections (which I am guessing the should look like websites) just show a web structure.
It is like it is missing the default page.
When I try to modify the "group membership" or "administer security" I get "Http 500 internal server error. Please contact your administrator. There was an error contacting the server".
I have tried repairing Azure DepOps but to no wail.
Can anyone please point to information on how to fix or trouble shoot issues on a DevOps 2019?
I have looked at application logs and IIS logs but there is nothing useful there.
thank you for your help in advance
Related
I am in need of assistance with my Meta's Conversion API and Google Tag Manager setup. I have successfully set up a web and server container, with the server container being manually configured and running on AWS.
I am currently working on the "Publish resources" section, but am encountering an error that says "Publishing failed. We were unable to publish the resources to your Google Tag Manager account. Please try again." I would greatly appreciate it if someone could provide some guidance in resolving this issue.
For reference, my web container is running on web.example.com, the tagging server is running on tagging.example.com, and the preview server is running on debug.tagging.example.com. I have followed this guide to set up my server-side tag manager on AWS: deploy-server-side-google-tag-manager-aws/.
Here are some screenshots:
The error
Console error
Console error link
I google-searched for this error and all I can find is other people with the same error but no solution was provided. I have also emailed Google and Meta support but I haven't gotten a response yet.
I'm working on a UWP project and wanted to check back in my code into Visual Studio Team Services. However, I can't. Visual Studio gave me an error saying that I was off line. I tried to go to manage my connections and connect to VSTS, but that failed, giving me this:
In the past there was always a link to reenter my credentials, but as you can see from the above error, there is no way of reentered my credentials. Going to Home doesn't work. Where do I reenter my credentials to my VSTS account?
With the help of Greg Duncan, I've got a way of fixing this. Thought I'd post it in case others experience the same problem.
In Visual Studio, go to Help, Register Product and then Sign Out (https://support.microsoft.com/en-us/help/2892152/-client-authentication-required-error-message-after-you-upgrade-from-p which is for VS 2013, but I’ve confirmed it looks the same in VS 2015 and VS 2017)
check with the permission of team services that you are in the readers or stakeholder access level.
We've previously been able to deploy our Java web application through Eclipse to Azure with no issues, but recently today we kept receiving an error message that says
FTP client can't store the artifact, reply code: 550
Anybody know what Azure is trying to say here ? Why would it suddenly start giving a 550 error? Deploying to a different Azure web application works fine, just can't seem to deploy to the same one as before.
The 550 error code of FTP on IIS normally means deny access or no permission to do some operation. Please try these ways as below.
Restart your Azure WebApp on Azure portal.
Reconfigure the deployment credentials with new username and password on Azure portal.
Remote Administration of Windows Azure Websites using IIS Manager to check the configuration for FTP. For example, there is a similar thread from SuperUser https://superuser.com/questions/845357/iis-ftp-folder-access-issues-550 which you can refer to.
Hope it helps.
The issue can also be caused if there is no webapps folder. Assure that path exists:
/site/wwwroot/webapps/
How can I add an external TFS Connection to TFS 2017 to allow it to connect to TFS 2013?
I navigated to http://tfsserver:8080/tfs/collection/team_project_name/_admin/_services?_a=resources and clicked New Service Endpoint. I selected External TFS
When I go to verify the connection after entering all the relevant information, I get the below error.
Failed to query service endpoint api: http://tfsserver:8080/tfs/collection/_apis/projects. Error Message: The remote server returned an error: (401) Unauthorized..
Here is a screenshot of the error.
The odd thing is that if I make a GET request to http://tfsserver:8080/tfs/collection/_apis/projects without any authentication I get a 200 OK response back with project information.
I have configured basic authentication per the tfs cli guide. How can I verify that basic authentication is configured correctly? When I try to login with tfx, I get the following screen.
I have the following extensions installed on the TFS 2017 instance.
Package Management
Release Management Utility tasks
TFS artifacts for Release Management
I am using Microsoft Visual Studio Team Foundation Server Version 15.105.25910.0
According to the screenshot, you are using TFS artifacts for Release Management extension to connect to another TFS instance.
Make sure the things below:
Make sure the collection URL you enter is correct. In your screenshot, the URL you enter is ended with "_home".
Make sure Basic Auth is enabled on TFS server.
Seems you are using the extension TFS artifacts for Release Management which provides a service endpoint to connect to an external TFS or VS Team Services Collection.
After test with TFS2013, I could reproduce your issue and got the same error information. The solution please see below:
Since you are connecting to TFS2013, it works with basic
authentication only. You’ll need to enable basic authentication
support for the TFS Server which handling TFS2013.
Also please make sure the username to connect to the external TFS
collection are with Domain in front of. Then will get a green
verfifed status.
The presence insight server on bluemix has been quite unstable now. Cannot get access to the server.
Is there any way to deploy the instance on softlayer server for production?
There were definitely some problems with PI last evening, but the team worked until early this morning to get them resolved. It looks like the system is back up and functioning. Are you still seeing the issue?
Also, as a general reference, this page has service status details on it that may be of help if you notice a problem.