I am attempting to use an Azure App Service Deploy task in Azure DevOps to deploy a file to an app service in Azure. I have been able to use this release pipeline to deploy to the same app service in the past. Two things have changed: I had to re-make the build machine (which exists in Azure), and the source code moved from Azure DevOps to GitLab.
The error I am running into is:
Error: (3/21/2019 4:34:45 PM) An error occurred when the request was processed on the remote computer.
Error: The server experienced an issue processing the request. Contact the server administrator for more information.
Well, I'm the server admin, and I don't have a clue.
Is there some log file I can look at for more information? Can someone please offer some suggestions?
I'm happy to provide additional information, I'm just not sure what would help at this point.
Thank you Tom Sun for directing me to the system.debug variable. That was very helpful. When I turned on the debugging the release worked, witch really doesn't make sense. I started the build machine after it had automatically shut down the day before, but then I had also rebooted the machine eight or nine times before that.
I removed the debug variable and the release still works.
I have no satisfying answer to how this issue was resolved and I don't know how to get the system in a state to reproduce the error.
An additional finding I have is that the artifact produced by the original build was a corrupt war file. Perhaps that had something to do with it?
Related
I am trying to publish blazor server web application to azure linux app service via visual studio community version 16.9.5
But it is failing with error information below:
Severity Code Description Project File Line Suppression State
Error Web deployment task failed. (Could not complete the request to
remote agent URL
'https://XXXXXXX.publish.azurewebsites.windows.net/msdeploy.axd?site=XXXXXXX-dev__staging'.)
Could not complete the request to remote agent URL
'https://XXXXXX.publish.azurewebsites.windows.net/msdeploy.axd?site=XXXXXX-dev__staging'.
The operation has timed out xxxxxx.web 0
I faced this issue earlier also but after one or two retry it was getting solved automatically. but this time I am unable to publish it after more than 20 tries. there is no exact information on exact problem anywhere.
Please suggest me if any exact cause of the error or solution.
Thanks,
Ashish
Troubleshooting:
Maybe you can try to set WEBSITE_WEBDEPLOY_USE_SCM=false on portal.
For more details, you can refer this post.
Why is application deployment failing on waws-prod-blu-167.publish.azurewebsites.windows.net?
In contrast, when using vs2019 was previously released, whether Service Dependencies were added.
Check whether the configuration of Service Dependencies is correct.
If all the above methods fail, please download publish profile and import to vs2019, then retry to publish your app.
I have Data Factory project in my solution. It compiled successfully on my machine. But when I triggered it from my tfs build server DataFactory throws an error at ParameterConfig.json
MsBuild\1.0\DataFactory.targets (35): Failed to download JSON schema
http://datafactories.schema.management.azure.com/internalschemas/2015-01-01-preview/Microsoft.DataFactory.Table.json
with exception message The remote name could not be resolved:
'datafactories.schema.management.azure.com'
I have added $schema in all the datasets, pipeline, and ParameterConfig files. This issue is intermittent. Someday it fails someday it works.
After lot more brainstorming I come to know that its totally intermittent issue.
I got related issues in Keyvault stuff also. Same error saying "Remote name could not be resolved".
What I observed is the URL mentioned above "http://datafactories.schema.management.azure.com" is not accessible from my build server account. So I used the trick and it works for me.
I have added "http://datafactories.schema.management.azure.com" site as a trusted site on my build server Internet settings.
It works! I didn't get any issues till now. My build is succeeded all the time.
I have deployed my web job on production environment and suddenly blob trigger stops working(Looking into App Insight I know that blob trigger is not called).
If I debug the same code from the local machine then it triggers blob trigger.But stopped working in the production environment.
Always On is enabled.
Also, I have these containers are present
azure-jobs-host-archive,
azure-jobs-host-output,
azure-webjobs-dashboard,
Microsoft.Azure.WebJobs.Host,
Installed packages:-
Microsoft.Azure.Webjobs installed version is 2.0.0,
Microsoft.Azure.WebJobs.Host installed version is 2.0.0
According to your description, we couldn't directly find out why the blob trigger doesn't work. I suggest you could follow below way to troubleshoot by yourself.
If I debug the same code from the local machine then it triggers blob trigger.But stopped working in the production environment.
Since you found your webjob could work well in local, I guess maybe there are something wrong with the connection string config in your web app.
I suggest you could try to follow below way to change the production environment appsetting to set the storage connection string in it.
1.Open the portal and edit the appsetting as below.
2.Create another web app and publish the web job to it and run.
If these two ways all doesn't help you solve the error, I suggest you could post the log/error message and the details codes about the web job.
More details about how to find the log/error message, you could follow below way.
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've been successfully using Azure for months. Today I'm getting the following error when I publish from via Web Deploy from Visual Studio 2013
Error 5 Web deployment task failed. (Could not connect to the remote computer ("waws-prod-hk1-001.publish.azurewebsites.windows.net"). On the remote computer, make sure that Web Deploy is installed and that the required process ("Web Management Service") is started. Learn more at: http://go.microsoft.com/fwlink/?LinkId=221672#ERROR_DESTINATION_NOT_REACHABLE.)
I tried downloaded a new Publishing Profile from the Azure Dashboard and turning off my firewall - no change.
I can't ping the listed server.
It seems to be the same issue as http://social.msdn.microsoft.com/Forums/windowsazure/en-US/83d4e635-2851-4526-b21b-31101d00aa86/web-deployment-task-failed-errorcouldnotconnecttoremotesvc?forum=windowsazurewebsitespreview
Any ideas? Thank you.
I had the exact same problem for a couple of days (sometimes I could published and sometimes not).
The problem was my internet configuration (not related to Microsoft or Azure in anyway).
To solve this issue I disconnected my modem (its actually modem+router) for 10 min and reconnect it and it was fixed!
Hope it will help someone someday...
Nevermind. It would appear that Azure was in a 'challenged' state.
It's working fine now..
What worked for me was disabling and re-enabling my network adapter.
The reasoning is, quite possibly naive, that having Fiddler running during a deployment will fail but it also changes the network state and that state continues
to exist even after exiting Fiddler (which disables the proxy).