I'm deploying a few Azure services to the Cloud and they fail with the following error, "Unable to reach watchdog.servicebus.appfabriclabs.com" when tryng to connect to the ServiceBus.
When I ping this host the address cannot be resolved. However, when I ping watchdog.servicebus.windows.net this is resolved.
Is there an explicit way to make my services use watchdog.servicebus.windows.net instead? Something wrong with my subscription maybe?
This is likely due to using the CTP/Labs version of the Microsoft.ServiceBus.dll. For Azure production environment you should be using version 1.0, 1.5 or 1.6 corresponding to Azure SDK versions. It appears that you have a version that is targets the LABS environment and may be versioned 2.0/99 etc.
You can obtain the latest ServiceBus client dll from NuGet or downloading the Azure SDK. Another thing to check for is if you have any servicebus.config file in .NET config directories that may be pointing to the LABS environment, more details on that are here.
Related
I am using Azure DevOps to deploy a .Net Web Application. I wanted to update to the new Os Family which is based on Windows 2019 so i can Update my projects to .net framework version 4.7.2 as seen here. I have updated my cloud service configuration '.cscfg' file to osFamily="6" but when i try to deploy the app even though the Build succeeds i get this error when i reach the Release step in Azure pipeline:
The OS family 6 you are trying to deploy is not supported by the SDK package. The SDK package supported OS families:3,4,5,1,2,98,97. Please try to deploy to a different operating system. To do this specify a different osFamily and/or osVersion in your .cscfg file.
I am using the Hosted VS2017 agent.
According to the error information it indicates that the OS family 6 are not supported by Hosted VS2017 agent.
Based on the link you mentioned that Compatible SDK versions should be Version 2.9.6+.
So my workaround is that you could use the Self-host agent with latest Azure SDK installed. We could download the latest Azure SDK from this link.
or you could have a try to install the Azure SDK on the Host 2017 agent (without test)
You also could give your feedback to Azure Devops team.
Is there a way to keep Diagnostics 1.0 but upgrade to Azure SDK 2.5?
We use very simple diagnostics that just writes into Trace (and as a result into storage table). We also deploy our service as a package via Azure portal. Introducing of Diagnostics 1.3 is a quite a breaking change for our process, since it requires PowerShell to deploy Diagnostics extension.
I tried to revert back Cloud configuration files (import Diagnostics module) but it is not working. It seems that I have to stay on SDK 2.4 for now.
Is there a way to keep Diagnostics 1.0 but upgrade to Azure SDK 2.5?
Unfortunately No. If you upgrade your Cloud Services to SDK 2.5, you can't use diagnostics 1.0. You have to use 1.3 version of the diagnostics.
We did the same with our projects and faced more or less the same issues as you faced and had to revert back. What we did was kept SDK 2.5 installed on the machines however our projects still use SDK 2.4 i.e. all referenced libraries in our project are from SDK 2.4.
Hi I'm really new on Azure.
I've VS 2012 and Azure SDK 2.1, when I run my web application with the emulator all work fine.
But when I deploy on azure I have the error message :
Could not load file or assembly
'Microsoft.WindowsAzure.ServiceRuntime, Version=2.1.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its
dependencies. The system cannot find the file specified.
Is the Windows Azure platform using an older version? how can I solve this problem, please.
I would venture to say that there are two possibilities (in order of likely-hood):
1) CopyLocal=True for the ServiceRuntime and it should be false. ServiceRuntime is already deployed on the Azure machines. You don't want to deploy your own.
2) Somehow your Cloud service config is configured to use an older version of Azure which is forcing the deployed VM to use SDK 2.0 or lower while your code is expecting v2.1. Make sure that osFamily, osVersion, and schemaVersion all are up to sniff with respect to being on 2.1 (I believe schemaVersion is what defines the proper Azure SDK version)
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
We just upgraded from the Windows Azure 1.7 SDK to 2.0.
This created a lot of problems in the codebase, but we got them ironed out and running locally.
Now when we try to publish to our cloud service machine in Azure, the worker role keeps trying to run but can't start.
My guess is that the cloud service machine is missing the 2.0 SDK.
Is there some way to install this manually on the remote machine? I can RDP and I've been looking around, but I can't seem to a) Verify which version it's trying to use and b) How to install a newer SDK.
I've found some errors about the worker role not running, but they're pretty uninformative.
The solution ended up being pretty simply, but I imagine other people will run into this problem.
We had 5-7 projects all referencing Azure SDK 1.8. Specifically these libraries:
Microsoft.ServiceBus
Microsoft.WindowsAzure.Configuration
Microsoft.WindowsAzure.Diagnostics
Microsoft.WindowsAzure.ServiceRunTime
Microsoft.WindowsAzure.StorageClient
If the project is a cloud service project, you need to right click on the project, go to properties, and upgrade the project. This changes the deployment when publishing. It will create the Azure VM based on the cloud service Azure SDK version. I missed that at first.
All the libraries above need to be upgraded to SDK 2.0 in all projects. Initially I missed some projects that were dependencies - and missing the Microsoft.ServiceBus library.
The last part was moving from Microsoft.WindowsAzure.StorageClient to Microsoft.WindowsAzure.Storage. I guess for SDK 2.0 they changed the library name, which has also introduced some breaking code changes.
After all that the cloud service now publishes correctly. Whew.