类型'Microsoft.WindowsAzure.StorageClient.StorageClientException“引发的异常 [英] Exception of type 'Microsoft.WindowsAzure.StorageClient.StorageClientException' was thrown

问题描述

类型'Microsoft.WindowsAzure.StorageClient.StorageClientException引发的异常。

有时候即使我们有织物运行和角色管理器就到了，我们得到这样的一个例外。

在该行emailAddressClient.CreateTableIfNotExist（EmailAddress的）在code减免;

 公共EmailAddressDataContext（CloudStorageAccount帐户）：
            基地（account.TableEndpoint.AbsoluteUri，account.Credentials）
{
   this.storageAccount =账户;   CloudTableClient emailAddressClient =
                新CloudTableClient（storageAccount.TableEndpoint.AbsoluteUri，
                                     storageAccount.Credentials）;
   emailAddressClient.CreateTableIfNotExist（EmailAddress的）;
}
 

解决方案

我给Windows Azure的表骆驼套管的名字所有的时间没有问题。

我不知道如果碰巧你已经用这个表名和最近删除呢？对于删除后一段时间（当表仍在异步删除），您将无法重新创建它。我相信409冲突是错误code在这种情况下，所期望的。

Exception of type 'Microsoft.WindowsAzure.StorageClient.StorageClientException' was thrown.

Sometimes even if we have the fabric running and the role manager is up, we get an exception of this sort.

The code breaks at the line emailAddressClient.CreateTableIfNotExist("EmailAddress");

public EmailAddressDataContext(CloudStorageAccount account) :
            base(account.TableEndpoint.AbsoluteUri, account.Credentials)
{
   this.storageAccount = account;

   CloudTableClient emailAddressClient =
                new CloudTableClient(storageAccount.TableEndpoint.AbsoluteUri, 
                                     storageAccount.Credentials);
   emailAddressClient.CreateTableIfNotExist("EmailAddress");
}

解决方案

I give Windows Azure tables camel-cased names all the time without issues.

I wonder if by chance you already used this table name and recently deleted it? For a time after deletion (when the table is still being deleted asynchronously), you won't be able to recreate it. I believe 409 Conflict is the error code to expect in that case.

这篇关于类型'Microsoft.WindowsAzure.StorageClient.StorageClientException“引发的异常的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！