Azure Webjobs with some known Facts.

Recently we successfully migrated worker role Queue jobs to Web jobs and below are the set of issues we encountered.

Special thanks to Kanivalan Raju who got this compiled.


When you deploy web jobs in azure cloud, you may come across the following errors.

Error 1
Error :Command cmd was aborted due to no output nor CPU activity for 121 seconds.

Resolution-

add key = "SCM_COMMAND_IDLE_TIMEOUT" value = "100000"

add key = "WEBJOBS_IDLE_TIMEOUT" value = "100000"

http://stackoverflow.com/questions/26596968/azure-webjob-timeout-configuration-settings


Error 2 : Certificate with website_load
Its important to load your certificates with this key appsetting.

WEBSITE_LOAD_CERTIFICATES

Resolution –

Add key ‘Add WEBSITE_LOAD_CERTIFICATES’ with thumbprint values as below
X509Certificate2 certificate=null;
X509Store certificateStore =new X509Store(StoreName.My, Storelocation.CurrentUser);


Error 3: Long file name
While publishing the webjob from VS, below error occurred and publish failed

The specified path, file name, or both are too long. The fully qualified file name must be less than 260 characters, and the directory name must be less than 248 characters.

Resolution :

As mentioned in error, make sure the path and file name of the web job not exceeds 250



Hope these resolution comes handy for folks working on similar problem statement.

Azure Data Centre Migration and Publish profile online download

While we are about to do lift and shift we realize this going to be very tedious task of migration. Still we are half way and looking for more productive and effective solution to migration azure cloud service from US data centre to Australia data centre.

When we look at this option given in this article, we felt this is what we want to go for however this got lot of caveat and problems based on infrastructure and the way it is done for public azure cloud.

https://azure.microsoft.com/en-us/blog/azure-data-center-migration-just-got-easier/

Few things to consider while you try to hook into this solution.

Problem with Download Publish Profile .

Publish profile download link is old and its refer to old reference
Try this https://manage.windowsazure.com/PublishSettings/index?Client=&SchemaVersion=&DisplayTenantSelector=true

Instead of this
https://windows.azure.com/download/publishprofile.aspx


This will act as wiki for me as I progress I will keep adding the problem statement and solution around so that it help others in similar issue.

1. Login to https://manage.windowsazure.com. So that session will ensure you got publish profile established properly.
2.Download Publish profile as per above link. Ensure right subscription and environment is selected.https://windows.azure.com/download/publishprofile.aspx
3. Download code from GitHub https://github.com/persistentsystems/adcms
4. *** Enable Nuget package- Tools- Extensions and Updates
5. *** Ensure all unwanted service is deleted where there is no deployment package .

Findings:-
We struggle to migrate database instance and databases from US to AUS. The only reason we looking at more automated approach which was not covered in the above migration checklist.

http://stackoverflow.com/questions/29837141/azure-online-sql-database-management-is-unavailable

V12 Azure SQL database is not supporting manage db online . We can connect using sql server management studio for the same. The only important thing is your client system should have port and firewall enabled for the access to cloud database. Else you may have tough time connecting to outside network to enable the same.

 

Redis Cache Architecture point of view

Thinking Redis cache stores key value pair just like any native .net code would do, is not just that. What we don't realize is that the cache can be distributed and centrally stored for multi server or webfarms. Not only cache management even session state management can be easily achieve using azure redis cache.

In theory we able to distribute load on server to certain extent to make it available to end users with better throughout ,low latency and easy data management.

1. Distributed caching
2. Centrally stored
3. Easy session management
4. Easy to clear and revisit cache expiry policy.


https://azure.microsoft.com/en-us/documentation/articles/cache-dotnet-how-to-use-azure-redis-cache/

Modern Web ApI and Cache repository Simpify.

https://code.msdn.microsoft.com/windowsdesktop/ASPNET-WebApi-Use-Redis-as-a0d942a3

Redis Manager

https://github.com/rgl/redis/downloads

Windows Azure Storage Issue with Micirosoft.DataServices.Client loading assembly

Summary-
This problem is most common with windows Azure SDK version where it get conflicts with versions of dll related to Micirosoft.DataServices.Client . As a temporary get away to this problem is to just exclude it from runtime tags in your app.config or web.config. Beware you need again need to fix if you have to deploy this to production environment.

Sometime update to Nuget package doesn't work the way we want.

http://www.dinohy.com/post/2014/04/02/Windows-Azure-Could-not-load-file-or-assembly-MicrosoftDataServicesClient-Version=5600.aspx