Error using SDK 2.0

Question

Hi Everyone, 

 

I am getting same error as described here - http://social.msdn.microsoft.com/Forums/en/appfabricctp/thread/9bfcdfe0-c29f-4f09-b342-b566adf7dea1

 

The line 

DataCache dataCache = dataCacheFactory.GetDefaultCache();

Fails with

[DataCacheException: ErrorCode<ERRCA0030>:SubStatus<ES0001>:Acs Request for Token failed. One of the reasons could be an invalid authorization token.Error:Code:400:SubCode:T1006:Detail:The required field 'wrap_password' is missing.]

I tried to create new namespace with no luck, so putting the question up again. My config is as follows:

<dataCacheClient deployment="Simple">
    <hosts>
      <host name="ticketsagewebsales-2.cache.appfabriclabs.com" cachePort="22233" />
    </hosts>
    <securityProperties mode="Message">
      <messageSecurity
          authorizationInfo="YWNzOmh0dHBzOi8vdGlja2V0c2FnZXdlYnNhbGVzLTItY2FjaGUuYWNjZXNzY29udHJvbC5hcHBmYWJyaWNsYWJzLmNvbS9XUkFQdjAuOS8mb3duZXImJmh0dHA6Ly90aWNrZXRzYWdld2Vic2FsZXMtMi5jYWNoZS5hcHBmYWJyaWNsYWJzLmNvbQ==">
      </messageSecurity>
    </securityProperties>
  </dataCacheClient>

 

Thank you in advance for your help.

Answer 1

Hi I am getting the exact same error message as well, but I get it when trying to run the  TrySessionCloud sample project.

 

[WebException: The remote server returned an error: (400) Bad Request.]
   System.Net.WebClient.UploadValues(Uri address, String method, NameValueCollection data) +487
   System.Net.WebClient.UploadValues(String address, String method, NameValueCollection data) +35
   Microsoft.ApplicationServer.Caching.AcsHelpers.GetToken(String serviceNamespace, String acsHostName, String issuerName, String issuerKey, String appliesTo) +357

[DataCacheException: ErrorCode<ERRCA0030>:SubStatus<ES0001>:Acs Request for Token failed. One of the reasons could be an invalid authorization token.Error:Code:400:SubCode:T1006:Detail:The required field 'wrap_password' is missing.]
   Microsoft.ApplicationServer.Caching.AcsHelpers.GetToken(String serviceNamespace, String acsHostName, String issuerName, String issuerKey, String appliesTo) +981
   Microsoft.ApplicationServer.Caching.ClientAcsSecurity.get_Token() +200
   Microsoft.ApplicationServer.Caching.TransportUtility.AddAuthenticationHeader(Message message, DataCacheSecurity dataCacheSecurity) +103
   Microsoft.ApplicationServer.Caching.WcfClientChannel.SendMessage(EndpointID endpoint, Message message, TimeSpan timeout, WaitCallback callback, Object state, Boolean async) +347
   Microsoft.ApplicationServer.Caching.WcfClientChannel.Send(EndpointID endpoint, Message message, TimeSpan timeout) +61
   Microsoft.ApplicationServer.Caching.WcfClientChannel.Send(EndpointID endpoint, Message message) +58
   Microsoft.ApplicationServer.Caching.SimpleClient.Send(EndpointID endpoint, RequestBody request) +100
   Microsoft.ApplicationServer.Caching.SimpleClient.SendMsgAndWait(RequestBody reqMsg, IRequestTracker& tracker) +673
   Microsoft.ApplicationServer.Caching.DataCache.SendReceive(RequestBody reqMsg, IMonitoringListener listener) +184
   Microsoft.ApplicationServer.Caching.DataCache.ExecuteAPI(RequestBody reqMsg, IMonitoringListener listener) +45
   Microsoft.ApplicationServer.Caching.SimpleClient.GetCacheProperties() +385
   Microsoft.ApplicationServer.Caching.DataCacheFactory.GetCache(String cacheName) +1301
   Microsoft.Web.DistributedCache.DataCacheFactoryWrapper.CreateDataCacheFromFactory(DataCacheFactory factory, String cacheName) +39
   Microsoft.Web.DistributedCache.CacheHelpers.RunCacheCreationHooks(CacheConnectingEventArgs fetchingEventArgs, IDataCacheFactory dataCacheFactory, Object sender, EventHandler`1 fetchingHandler, EventHandler`1 fetchedHandler) +166
   Microsoft.Web.DistributedCache.DistributedCacheSessionStateStoreProvider.CreateInternalProvider(IHttpRuntime httpRuntime, SessionInitializationData initData, IDataCacheFactory dataCacheFactory, EventHandler`1 cacheFetching, EventHandler`1 cacheFetched) +193
   Microsoft.Web.DistributedCache.DistributedCacheSessionStateStoreProvider.GetInternalProvider() +202
   Microsoft.Web.DistributedCache.DistributedCacheSessionStateStoreProvider.CreateNewStoreData(HttpContext context, Int32 timeout) +39
   System.Web.SessionState.SessionStateModule.InitStateStoreItem(Boolean addToContext) +87
   System.Web.SessionState.SessionStateModule.CompleteAcquireState() +119
   System.Web.SessionState.SessionStateModule.BeginAcquireState(Object source, EventArgs e, AsyncCallback cb, Object extraData) +561
   System.Web.AsyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +96
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +184

 

My config is as follows:

<

 

dataCacheClient deployment="Simple"

>

 

<

 

hosts

>

<

 

host name="testmoe1.cache.appfabriclabs.com" cachePort="22233"

/>

</

 

hosts

>

 

<

 

securityProperties mode="Message"

>

<

 

messageSecurity

 

 

authorizationInfo="YWNzOmh0dHBzOi8vdGVzdG1vZTEtY2FjaGUuYWNjZXNzY29udHJvbC5hcHBmYWJyaWNsYWJzLmNvbS9XUkFQdjAuOS8mb3duZXImJmh0dHA6Ly90ZXN0bW9lMS5jYWNoZS5hcHBmYWJyaWNsYWJzLmNvbQ=="

>

</

 

messageSecurity

>

 

</

 

securityProperties

>

 

</

 

dataCacheClient

>

 

 

 

Answer 2

Hi,

 

I'm looking into this issue. Will get back to you soon.

 

Thanks,

Akshat

Answer 3

Hi,

 

Can you let me know if the issue still persists i.e. if you go to the portal, do you see a different authorization info  than the one specified above? If so, can you try connecting using that auth info?

 

Thanks,

Akshat

Answer 4

Hi,

 

This is currently a known issue and we are working to get it resolved. We appreciate your patience. In the meanwhile, re-creating the cache should fix the problem. Could you try doing that?

 

Thanks,

Akshat

Answer 5

I have tried creating a new cache this morning.  I still get the same exact error in the TrySessionCloud sample page.  My new configuration values are as follows:

   <dataCacheClient deployment="Simple">    
    <hosts>
        <host name="moecachet1.cache.appfabriclabs.com" cachePort="22233" />
      </hosts>     
    <securityProperties mode="Message">
        <messageSecurity
        authorizationInfo="YWNzOmh0dHBzOi8vbW9lY2FjaGV0MS1jYWNoZS5hY2Nlc3Njb250cm9sLmFwcGZhYnJpY2xhYnMuY29tL1dSQVB2MC45LyZvd25lciYmaHR0cDovL21vZWNhY2hldDEuY2FjaGUuYXBwZmFicmljbGFicy5jb20=">
        </messageSecurity>
      </securityProperties>   
    </dataCacheClient>

Answer 6

Hi Erik,

 

Can you try deleting, re-creating this cache and then access the cache using the new token specifed in the portal? It might take a couple of times or more to get the things working. In the meanwhile, we will try to get the issue fixed.

 

Thanks,

Akshat

Answer 7

I am still facing this issue. Any idea about fix?
Just an observation, i think the Updated IP addresses for AppFabric Data Centers is causing this.

---

Cloud Management and Monitoring done right, http://www.cumulux.com/products/manageaxis/

Answer 8

I'm having the same issue here. It seems the Access Control Service is not configured for new Cache Namespaces.

Answer 9

Hi Akshat,

I've the same issue. Tried creating four different cache's, none works. Please let us know when this is resovled.

-sr

Answer 10

The AppFabric V2 Cache feature has gone live (i.e. it has moved from appfabriclabs to the Management Portal), and the issue seems to be resolved. At least I managed to configure a cache from the portal where the correct ACS settings was filled out automatically.

Apart from the feature being available in all datacentres it is also worth noticing that the max size of the cache has increased from 256 MB to 4GB.

 

Answer 11

I am on https://portal.appfabriclabs.com/ and added a new cache, I don't see any 4GB option, I am having exact same issue.

The AppFabric V2 Cache feature has gone live (i.e. it has moved from appfabriclabs to the Management Portal), and the issue seems to be resolved. At least I managed to configure a cache from the portal where the correct ACS settings was filled out automatically.

Apart from the feature being available in all datacentres it is also worth noticing that the max size of the cache has increased from 256 MB to 4GB.

 

Answer 12

I'm referring to the Windows Azure Management Portal (https://windows.azure.com) - not the AppFabric Labs. The Cache feature should be available under the menu item "Service Bus, Access Control & Caching".

Answer 13

This issue has been resolved now. Please re-try and let us know in case the problem still persists for you.

 

Thanks,

Akshat

Answer 14

We are still facing the issue.  I tried creating new caching still problem persists.  Plz help

Answer 15

I created cache in Asia region resolved the above issue, but started throwing this exception

ErrorCode<ERRCA0017>:SubStatus<ES0006>:There is a temporary failure. ... For on-premises cache clusters, also verify the following conditions. Ensure that security permission has been granted for this client account, and check that ... cache servers are unavailable, which could be caused by busy network or servers. ...

 

Your help will be appreciated