AppFabric Azure Caching : The remote name could not be resolved *.windows.net

A lot of internal customers seem to face this issue since *.windows.net is not directly resolvable within corpnet. In this case you need to install Forefront TMG Client . Another interesting case is when you deploy your web application which uses caching under an app-pool whose identity is a system account (like NetworkService, I think…

1

AppFabric Azure Caching : Quota throttling errors

(This article is focused and valid only for Azure AppFabric Caches and not for Windows Server AppFabric Caches.) Azure AppFabric Caches come with quota limits. Quota limits are mentioned here. Here are some of the reasons why you might be throttling on: 1. Bandwidth or Transactions: This means that you are actually in need of…

0

Azure AppFabric Caching – ErrorCode<ERRCA0017>:SubStatus<ES0006> : What to do?

ErrorCode<ERRCA0017>:SubStatus<ES0006>:There is a temporary failure. Please retry later. (One or more specified cache servers are unavailable, which could be caused by busy network or servers. For on-premises cache clusters, also verify the following conditions. Ensure that security permission has been granted for this client account, and check that the AppFabric Caching Service is allowed through…

3

Changing the Windows Azure Web Host application pool identity

Sometimes, need may arise to change the app pool identity of the azure web host you are working with locally on Development Fabric/Compute Emulator.  By default, the web host runs under a temporary application pool with NTAUTHORITY\NETWORK SERVICE account. This account may not have access to some key local/remote resources.(e.g. using the proxy server to…

0