Wednesday, March 2, 2016

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.




Post a Comment