Been facing this for a few days already. I wonder if there's anyone else having this kind of issue.
I go to My Apps in JIRA and select "Azure Pipelines for JIRA" then click on "Get Started" (I had already configured this once so it worked before) and get the following error:
Error and console from JIRA
It mentions deprecated JS, cookies, and a server 500 error. Not sure what needs to be done here.
I can reproduce this issue and try to install the plugin via a new account again, I will get the 500 issue.
I have report this issue in the GitHub and Azure DevOps Developer Community, you could follow these links to get the latest news.
Thank you for helping us build a better Azure DevOps.
Update1
Produce team response:
We have run into additional issues, and would need a couple more weeks. I am working on it to get the fix in place as soon as possible.
Related
I have multiple agents created with Dialogflow and many of them are live in Production. However, suddenly the Dialogflow projects disappeared and now I see only the option to create a new agent.
However, I see that Production Agents are working fine. I verified it through the app that I created which is connected to Dialogflow API.
The google cloud status dashboard is reporting that the problem has been solved. I checked my agents and they came back.
Same happened to me today, then I accessed after some time and they were back, but when I tried to work on an agent after a bit it gave error and all the agents disappeared again. I think they may be having server issues?
I just created a new Agent and the agent that disappeared came back.
please follow GCP status page for more info status.cloud.google.com
I'm trying to setup an instance of Azure time series insight with a PAYG(preview) tier. But this is the result I get:
It seems that the deployment wasn't successful after all. Even though it worked while following the tutorial from here. When I try "Go to environment", I get notified that I'm "Unable to open the uri. Please try again later.".
Other colleagues tried and got the same result. Is this a bug? Or did we miss something?
Any help or news would be welcome.
Thank you
Quentin
I am trying to deploy an application to the Azure Service Fabric using the release definition task. When it gets to the task to deploy the server is returning the following error:
The type initializer for 'Microsoft.ServiceFabric.Powershell.Constants' threw an exception
I checked the Endpoint configuration and it appears to be set up as it is supposed to be:
No Authentication (this is an internal text box)
Cluster endpoint: tcp://[service fabric server]:19000
It downloads the artifacts without a problem, but in deploy it searches for the paths for publish profile and application package and finds them. After it finds them it throws the error. I have tried replacing TCP in the endpoint with http, added and removed the :19000 as well and all I get is this error. I have been searching online with little success. Any help to this end is much appreciated.
John
After lots of researching trying every suggestion I could find, we decided try and connect to the machine via Powershell on the box and it too was returning this error. So we uninstalled the SDK and re-installed it and the connection could be made and the builds started to work. I don't know exactly why it failed, but apparently a re-install did the trick. It may have been a bad install, or it could have been a versioning problem. Either way, try a re-install first.
I have API Connect installed with mongodb connector over a remote server.
When I access the IBM API Connect through browser, all is fine, but when I go to DataSources where my DB is, and try to hit Update Schema button as shown in the image, an error occurs showing this:
Cannot GET /apim/dataSources/partials/dataSourceMigrate.html
P.S. I gave full permission for my project directory (/var/www/) with full ownership for www-data group and still the same.
Anyhelp would be appreciated.
FINALLY AND AFTER 2 MONTHS OF WAITING, I've got an answer from IBM Bluemix Support and sorry to bring the bad news, which is the following:
Hi Ghassan,
Thanks for sending the additional files. I checked with our development team and they found a bug in the code.
The fix will be available in a future release of the apic command line, but I don't have a date for it yet.
I will further discuss the plans to release this fix and will update you as soon as possible.
IBM Bluemix Developer Support and Enablement Team
A fix has been provided for this issue in iFix versions of 5.0.3.0, 5.0.4.0 as well as newer versions of API Connect. If you are still experiencing this issue, please update to a later version that includes the fix.
I am trying to install Umbraco by using the Azure Marketplace. There they offer a template for it. I am always receiving the error below. I tried to install it a couple of times now but I always get the same error.
Does anybody know what this error message means? Is anybody able to install Umbraco by using the template in the Azure Marketplace?
]
You're asking 2 questions above.
Please see my answers and proposed troubleshooting guide/workaround below:
The error message means that the MSDeploy process failed due to some error which renders it unable to deploy the web deploy package for your Umbraco web app.
Yes I am able to provision a Umbraco web app from the Azure Market successfully (Location: Central US) and couldn't reproduce your issue
Troubleshooting Guide:
Append .scm in front of the azurewebsites.net of your Umbraco Web App as shown below and go to the Url.
Click on the Diagnostic Dump. You will be prompted to download a .zip file
Extract the zip file. You should see 2 folders at root level
Go into
LogFiles\SiteExtensions\MSDeploy
You should see the detail log files for MSDeploy
Detailed MSDeploy log messages are in the appManagerLog.xml file.
If it is related to client side issue which can be resolved by yourself, you can try to resolve it and try again.
If it is related to server side issue, you should create a support ticket for Microsoft to look into with the detailed MSDeploy log which pinpoints the root cause which will help them a lot.
Hope this is useful.
A Microsoft employee confirmed this is a bug in the application currently. I have to wait for a fix.
I have encountered numerous problems with the Azure installer of Umbraco, try setting it up in VS2015 then publishing it to Azure. I have found that this works well.