Azure AppFabric Cahing error: ErrorCode<ERRCA0030>:SubStatus<ES0001>:Acs Request for Token failed. One of the reasons could be an invalid authorization token.

Question

We have attempted to use Windows Azure AppFabric caching and intermittently received the following error.

ErrorCode:SubStatus:Acs Request for Token failed. One of the reasons could be an invalid authorization token.

The Azure release notes - http://msdn.microsoft.com/en-us/library/hh148155.aspx suggested this error could occur, but had been fixed in the latest release. However, for us, using the latest release did not fix the problem. We were attempting to use AppFabric for both Session State and Caching.

Is there still a known issue here?

Answer 1

Hi Bernard,

Thanks for your question.

I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.

Thanks.

---

Wenchao Zeng
Please mark the replies as answers if they help or unmark if not.
If you have any feedback about my replies, please contact [e-mail].
Microsoft One Code Framework

Answer 2

Is it possible that you post the complete call stack?

Answer 3

It was:

 

at Microsoft.ApplicationServer.Caching.AcsHelpers.GetToken(String serviceNamespace, String acsHostName, String issuerName, String issuerKey, String appliesTo)
at Microsoft.ApplicationServer.Caching.ClientAcsSecurity.get_Token()
at Microsoft.ApplicationServer.Caching.TransportUtility.AddAuthenticationHeader(Message message, DataCacheSecurity dataCacheSecurity)
at Microsoft.ApplicationServer.Caching.WcfClientChannel.SendMessage(EndpointID endpoint, Message message, TimeSpan timeout, WaitCallback callback, Object state, Boolean async)
at Microsoft.ApplicationServer.Caching.WcfClientChannel.Send(EndpointID endpoint, Message message, TimeSpan timeout)
at Microsoft.ApplicationServer.Caching.SimpleSendReceiveModule.Send(EndpointID endpoint, RequestBody request)
at Microsoft.ApplicationServer.Caching.SimpleSendReceiveModule.SendMsgAndWait(RequestBody reqMsg, TimeSpan requestTimeout, Boolean isCompressionEnabled, IRequestTracker& tracker)
at Microsoft.ApplicationServer.Caching.SimpleClient.SendMsgAndWait(RequestBody reqMsg, IRequestTracker& tracker)
at Microsoft.ApplicationServer.Caching.DataCache.SendReceive(RequestBody reqMsg, IMonitoringListener listener)
at Microsoft.ApplicationServer.Caching.DataCache.InternalGet(String key, DataCacheItemVersion& version, String region, IMonitoringListener listener)
at Microsoft.ApplicationServer.Caching.DataCache.<>c__DisplayClass49.b__48()
at Microsoft.Web.DistributedCache.DataCacheForwarderBase.<>c__DisplayClass2e`1.b__2d()
at Microsoft.Web.DistributedCache.DataCacheRetryWrapper.PerformCacheOperation(Action action)
at Microsoft.Web.DistributedCache.DataCacheForwarderBase.Get(String key)
at System.Web.Caching.OutputCache.Get(String key)
at System.Web.Caching.OutputCacheModule.OnEnter(Object source, EventArgs eventArgs)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

Answer 4

For most ErrorCode<ERRCA0030>:SubStatus<ES0001> I saw, the full message can be [DataCacheException: ErrorCode<ERRCA0030>:SubStatus<ES0001>:Acs Request for Token failed. One of the reasons could be an invalid authorization token.Error:Code:***:SubCode:***:Detail:***.]. Here the detail can give some hints of the possible cause.

If that does not help, you can consider change the code a little following http://blogs.msdn.com/b/akshar/archive/2011/05/01/azure-appfabric-caching-errorcode-lt-errca0017-gt-substatus-lt-es0006-gt-what-to-do.aspx so that you may get the inner exception which gives more details.

 

                ================

Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

 

Thanks & Regards,

Emma

Microsoft Online Community Support

 

 

 

Answer 5

It's possible there's a misunderstanding here. I'm using Windows Azure AppFabric caching - http://msdn.microsoft.com/en-us/library/gg278356.aspx

I set up a cache in the Azure Management portal, as far as I can see this doesn't offer any configuration options for the timeout, let me know if I'm missing something obvious.

 

Thanks.