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)
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.
I am trying to update a cloud service to use .NET 4.6. I changing the osFamily="4" to osFamily="5" in the .cscfg file as specified here: https://learn.microsoft.com/en-us/azure/cloud-services/cloud-services-guestos-update-matrix
Looking at my file system I have this SDK version installed:
C:\Program Files\Microsoft SDKs\Azure.NET SDK\v2.9
Looking at Web PI, I have these installed:
VS Community 2105 with Azure SDK - 2.9.6
VS Community 2105 with Azure SDK - 3.0
Microsoft Azure SDK for .NET (VS 2015) - 2.9.6
Microsoft Azure SDK for .NET (VS 2015) - 3.0
I normally use Powershell cmdlets to deploy using New-AzureDeployment/Set-AzureDeployment from a build & deployment server. I will occasionally deploy from my desktop using powershell for testing.
If I leave the osFamily="4" unchanged and deploy with Powershell everything works as expected.
If I use VS2015 and the Publish Azure Application tool to do the deployment it succeeds as expected if I choose either osFamily="4" or osFamily="5".
Checking which module is used:
C:\> (Get-Command Set-AzureDeployment).Module.Path
C:\Program Files\WindowsPowerShell\Modules\Azure\3.8.0\Azure.psm1
Running the deployment Set-AzureDeployment (given an existing package has been deployed) gives me the following error -
Set-AzureDeployment : BadRequest : The OS family 5 you are trying to deploy is not supported by the SDK package. The SDK package supported OS families:3,4,1,2,98. Please try to deploy to a different operating system. To do this specify a different osFamily and/or osVersion in your .cscfg file.
I don't see which SDK "package" the commandlet is complaining about...any ideas?
Try using a newer version of the 2.9 Azure Authoring Tools.
I reproduced this problem with Azure Authoring Tools 2.9.1, but remedied it by upgrading to version 2.9.5.3. Actually it's mentioned as fixed in the release notes for Azure '3.0' SDK (download link):
Visual Studio now supports deploying Cloud Services to OS Family 5
(Windows Server 2016) virtual machines. For existing cloud services,
you can change your settings to target the new OS Family. When
creating new cloud services, if you choose to create the service using
.net 4.6 or higher, it will default the service to use OS Family 5.
For more information, you can review the Guest OS Family support
table.
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.
Im new to Azure and wanted to create a Continuous Integration build using TFS. I created a build definition but building my Cloud App with simple website using a hosted buildserver in the build definition fails with error:
C:\a\src\myAzure\myAzure\myAzure.ccproj (70): The imported project "C:\Program Files (x86)\MSBuild\Microsoft\VisualStudio\v11.0\Windows Azure Tools\2.0\Microsoft.WindowsAzure.targets" was not found. Confirm that the path in the declaration is correct, and that the file exists on disk.
I can however build locally, and manually Publish to Azure and it will deploy fine.
Im suspecting that the hosted buildserver of TFS does not support Azure 2.0?
Is there a way around this problem or will I have to forget the idea of using CI?
Seems to be so since the Build is a preview feature of the Team Foundation Service. There was the same thing with Azure SDK 1.8, but they updated the Build Servers in a couple of days. Hope that it will not take long this time.
UPDATE:
"No, TF Service hosted build machines do not have the new SDK 2.0 at this time. We expect all users to have Azure SDK 2.0 support post June 1st. In the meantime you will need to use an on-prem build controller with the bits you need and deploy to Azure from there."
(C) Trevor Hancock from Microsoft
http://social.msdn.microsoft.com/Forums/en-US/azuretfs/thread/2df796d5-1abb-4b89-a571-0b7a62b80d55
UPDATE 2:
I've managed to complete a successful build using TFS build servers with SDK 2.0 So I think this problem is resolved for now. In future I recommend not to do updates to new versions of Azure SDK until the TFS build servers are ready.
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.