I'm completely new to Azure and I've read much of the online help already. I am trying to deploy a .Net website but it won't finish the initialization and I think it may relate to the SDK version. The instance won't start so I can't connect to debug the
issue.
The website works fine on my local machine. I've even gone so far as to run the website locally but point to Azure's storage and SQL instances and that works without error. I confirmed that I'm not using local storage anywhere in my settings.
When I upload the site to Azure, it will build the VM, initialize and then go into a busy state where it finally fails. I suspect that the issue is the SDK but I would like some feedback. I'm using 1.7 but in the Azure management console, it says 1.6.21103.1459.
In my web.config file, these are the settings:
I've also confirmed that the references in the project all point to the 1.7 version. One final point is that the only warning I receive is regarding log4net:
Warning 61 The project 'Time Entry System' is dependent on the following assembly: C:\windows\assembly\GAC_64\log4net\1.2.10.0__692fbea5521e1304\log4net.dll. This assembly is not in the package. To make sure that the role starts, add this assembly as a reference
to the project and set the Copy Local property to true. Time Entry System 1 1 Timeclox
I believe that the above is coming from a 3rd party nuget package. I've added the 1.2.11.0 version to the deployment (I can't locate 1.2.10.0) but don't think that this is relevant to the problem.
So my first question is, how can I get the SDK versions straightened out? I can not figure out why Azure is picking up a different version. Additionally, is there some way for me to debug on the server when it goes into a busy state and doesn't allow a
remote connect?
JonnyBravoII
Member
43 Points
74 Posts
SDK Version and hung initialization
Aug 10, 2012 01:11 PM|LINK
I'm completely new to Azure and I've read much of the online help already. I am trying to deploy a .Net website but it won't finish the initialization and I think it may relate to the SDK version. The instance won't start so I can't connect to debug the issue.
The website works fine on my local machine. I've even gone so far as to run the website locally but point to Azure's storage and SQL instances and that works without error. I confirmed that I'm not using local storage anywhere in my settings.
When I upload the site to Azure, it will build the VM, initialize and then go into a busy state where it finally fails. I suspect that the issue is the SDK but I would like some feedback. I'm using 1.7 but in the Azure management console, it says 1.6.21103.1459. In my web.config file, these are the settings:
<dependentAssembly>
<assemblyIdentity name="Microsoft.WindowsAzure.StorageClient" publicKeyToken="31bf3856ad364e35" culture="neutral" />
<bindingRedirect oldVersion="0.0.0.0-1.7.0.0" newVersion="1.7.0.0" />
</dependentAssembly>
I've also confirmed that the references in the project all point to the 1.7 version. One final point is that the only warning I receive is regarding log4net:
Warning 61 The project 'Time Entry System' is dependent on the following assembly: C:\windows\assembly\GAC_64\log4net\1.2.10.0__692fbea5521e1304\log4net.dll. This assembly is not in the package. To make sure that the role starts, add this assembly as a reference to the project and set the Copy Local property to true. Time Entry System 1 1 Timeclox
I believe that the above is coming from a 3rd party nuget package. I've added the 1.2.11.0 version to the deployment (I can't locate 1.2.10.0) but don't think that this is relevant to the problem.
So my first question is, how can I get the SDK versions straightened out? I can not figure out why Azure is picking up a different version. Additionally, is there some way for me to debug on the server when it goes into a busy state and doesn't allow a remote connect?