I have an Azure Worker Role (WR) which is supposed to pick up it's config from the .cscfg files using:
var setting = CloudConfigurationManager.GetSetting("My.Setting.Name");
Running in the emulator this is fine, I get the:
Getting "My.Setting.Name" from ServiceRuntime: PASS.
message. However, when I publish to my remote environment, I get:
Getting "My.Setting.Name" from ServiceRuntime: FAIL.
Getting "My.Setting.Name" from ConfigurationManager: FAIL.
messages. In the 'CloudServices/Configure' section of the Azure Management Portal I can see the setting listed in the configuration, and it's set correctly.
I'm using Azure SDK 2.0
Are you deploying correct Azure SDK .DLL's with your project? Did you by chance upgrade recently to a newer Azure SDK? I would check your .DLL references to make sure that they all match across the solution
Related
I don't know why this issue is happening, but I am confident that the configuration was done properly.
I created an Azure VM, installed Jenkins in that, and created a freestyle project. And Then I added the git and Azure Service Principle credentials to the global unrestricted access to Jenkins credentials (system). When I try to add a post-build setup of publishing to an azure web app, I get the following errors.
I have added images, please open the links and look into them, and help me out.
As you can see, the service principle has been successfully verified.
But in the second picture, when I try to access the resource group, it says none, even though I have created a resource group, app service plan, app services etc.
I tested in my enviroment and facing the same Issue,Even after Succefully verified the service principle.
Did few reaseach and found that Azure App Service Plugin is up for adoption and under maintaiance and few of them as been deprecated and also they are looking for new maintainer. The Same issue is happing with other Azure plugin as well like Azure Storage,Azure Cosmos and many more...
Even though in the document its stated you can install the Azure App Service plugin manually before officially release but when i tried to install the maven repro its prompting for enter the credential to download the repro. Seems its private repro we can't access.
For Workaround for this issue or for more information you can reach out to Jenkins Community Team or Support.
I have created an azure web service app used for testing purposes and run into a .Net / http issue (500.30). Ive looked into a lot of troubleshooting but nothing has worked or pointed me in the right direction.
It seems to get more info on the issue, I can use the stdout logs in the Azure app service through Kudu. This has been configured this and the files it creates are blank? Has anyone encountered this before?
What have I did, I set it up in the web.config file setting the stdlog to true but this creates the files with no info. I then removed the inprocess=hosting section as I read this fixed it for others but no joy.
Any pointers in the right direction would be appreciated
HTTP Error 500.30, The log file is created but empty - This kind of scenario is trapped by the SDK when publishing a self-contained app.
There is a term called RID (Runtime Identifier) used to identify target platforms where a .NET Core application runs.
If the RID doesn't match the platform target then the SDK produces the above kind of errors.
For example, win10-x64 RID with <PlatformTarget>x86</PlatformTarget> in the project file.
Troubleshooting steps:
<PlatformTarget>x86</PlatformTarget> enables the IIS app pool for 32-bit apps in an x86 framework-dependent deployment and set Enable 32-bit Apps to True from the app pool's Advanced Settings of IIS Manager.
500.30 is In-Process Startup Failure as it's cause can be usually determined from entries in the Application Event Log and the ASP .NET Core Module stdout log.
The app is misconfigured due to targeting a version of the ASP .NET Core shared framework that isn't present. Check which versions of the ASP .NET Core Shared framework are installed on the target machine.
If you're using Azure Key Vault, check the policies in the targeted Key Vault to ensure that the correct permissions are granted.
Also, please visit this Thread related to logging not working fix.
And Application Insights should be enabled to get the log files in the Storage account.
You can stream the logs from the portal or using CLI:
az webapp log tail --name appname --resource-group myResourceGroup
Use this reference to get the logs using the simple queries.
You need to enable application logging first.
Click on the App Service logs menu
In Application logging, select File System
In Quota (MB), specify the disk quota for the application logs. In Retention Period (Days), set the number of days the logs should be retained.
Save
You can stream the logs from the portal or by using the CLI
az webapp log tail --name appname --resource-group myResourceGroup
I want to download ADLGen2 file to my local server using ADF.
I tried to set up self hosted integration run-time, but I am getting below error
the integration runtime (self-hosted) node has encountered an error during registration
The account through which I have logged into my azure portal and the account which has access on my local machine are completely different.
Azure Portal login : xyz_abc#gmail.com
Local machine login: officiallogin#companyname
Is the issue because of 2 completely different logins
Can you please let me know how to resolve this issue.
Thanks,
Raksha
When you say "The account through which I have logged into my azure portal and the account which has access on my local machine are completely different", make sure to uninstall and re-install the self-hosted integration runtime manually choosing the option2.
OR
You may try to uninstall the current self-hosted integration runtime. Maybe you can try the Option1. It will install and register the integration runtime automatically.
Reference: Create and configure a self-hosted integration runtime.
I have an Azure App deployed. This app is tested locally (in VS Code) & deployed via Azure Devops (using Azure Pipeline). It successfully runs in local environment while testing. It also has deployment slots enabled.
Bindings used in this Azure Functions are ServiceBus (trigger) and Storage (output). Also the Function App has a package.json in the root of the project for installing the dependencies (as per this article).
When accessing the app in Azure portal I get this error:
When I access the staging slot, I get this error(Error about bindings):
Errors on staging are related to binding errors, but looking at this Integrate page for staging slot it seems they are recognized correctly.
How can I get rid of these errors? What am I missing? Am I missing some extensions of these bindings. And why the error on production slot has the message An error has occurred. with no more detail.
For V2 function you need to register service bus extension using CLI:
https://learn.microsoft.com/en-us/azure/azure-functions/functions-bindings-register#local-development-azure-functions-core-tools
Team,
I am a beginner in Azure stuff and need your advice. I have recently updated my Azure cloud service application from SDK 2.1 to SDK 2.9. But now the Azure cloud service role errors saying that "Invalid service definition or service configuration".
The XML specification is not valid: The 'schemaVersion' attribute is invalid - The value '2013-03.2.0' is invalid according to its datatype 'http://schemas.microsoft.com/ServiceHosting/2008/10/ServiceDefinition:SchemaVersion' - The Enumeration constraint failed.
and many such errors like
Error Role: 'ABCApplication', setting 'Microsoft.WindowsAzure.Plugins.Caching.NamedCaches' in all service configurations could not be found in the service definition.
How should I fix the above?
My question is Do i have to publish to the azure portal to get a new service definition or service config. Did the azure SDK update affect anything here?
Or do i have to make changes in the service definition or config according to the new SDK?
Please help.
In consideration of your used SDK has changed, per my experience, the first one you need to do is to update the schemaVersion in your XML file for the verification.
The schemaVersion for the Azure SDK 2.9 is schemaVersion="2015-04.2.6" that can be got and verified by creating a new Azure Cloud project targeting Azure SDK 2.9 and looking at the ServiceConfiguration.cscfg file. Then you can re-compile and re-publish it to upgrade your service to check whether it works.
Best would be to create a new cloud project with the existing web application a web role to it. Ofcourse there would be a pain to recreate the device definition and service config from scratch.