Azure的缓存 - 在升级失败后的SDK 2.1和2.1缓存 [英] Azure Caching - Failure after upgrading to SDK 2.1 and caching 2.1

问题描述

它看起来像有一些问题在这个话题已经打开，但我相信我的可能会有所不同。我的设置：

It looks like there are a number of questions already open on this topic, but I believe mine might be different. My setup:

• 1的Azure缓存工作者角色


• 1 Web角色

直到大约一个星期前，他们在和谐的存在，直到我试图升级到Azure的缓存2.1。一旦我这样做，我是用没有这样的主机已知的问题，似乎那里已经影响了很多开发商的折磨。我发现很多的问题和指示我我的Azure SDK安装升级到新的2.1版网站。我已经做了所有这些事情：

Up until about a week ago, they existed in harmony, until I tried to upgrade to Azure caching 2.1. Once I did that, I was afflicted with the "No such host is known" problem that seems to have affected many developers out there. I found many questions and sites that directed me to upgrade my Azure SDK installation to the new 2.1 version. I have done all of these things:

• 安装最新的Azure SDK 2.1


• 卸载的Azure SDK 2.0


• 卸载并重新安装Azure的缓存2.1


• 我所有的缓存设置三重检查配置


• 三重检查所有的引用都指向了最新的版本，而不是旧的


• 升级我的Azure项目以2.1单击鼠标右键，去属性，点击升级

和我仍然得到以下（我的错误）

Exception type: SocketException 
Exception message: No such host is known
at System.Net.Dns.HostResolutionEndHelper(IAsyncResult asyncResult)

这是比大多数其他问题和网站都出现了较为典型的错误，这是不同的（更多常见的错误，而不是我）

This is different than the more typical error that most other questions and sites are showing, which is (More commonly reported error, not mine):

No such host is known 
Exception message: No such host is known
at Microsoft.ApplicationServer.Caching.AsyncResultNoResult.EndInvoke()

我大约30小时后故障排除这一点，真的可以使用一些帮助。也许我只是缺少关于SDK的升级某一步骤？不知怎的，也许偷偷它依然使用旧版本的DLL的？有没有检查这除了查看项目中的每个参考的路径一定万无一失的方法（我已经做了，他们都匹配）？

I am about 30 hours into troubleshooting this, and could really use some help. Maybe I am just missing some step about the upgrade of the SDK? Somehow maybe sneakily it is still using an old version of a DLL? Is there some foolproof way to check this besides looking at the path of every reference in the project (which I have already done, and they all match up)?

推荐答案

不是一个真正的答案，但一些意见可能帮助你诊断问题：

Not really an answer but some comments which might help you diagnose the problem:

• 的Visual Studio 2012 /更新3 - 请确保您有适用于VS.最新更新我们已通过类似的问题了，这是来帮助我们的事情之一。



• 收集大量的缓存诊断的数据 - 在你的缓存配置部分，更改 Microsoft.WindowsAzure.Plugins.Caching.DiagnosticLevel 值 4 在缓存工人角色的配置部分。你这样做之后，添加code以下行缓存工人角色的的OnStart（）方法：

• Visual Studio 2012/Update 3 - Please ensure that you have latest updates applied to VS. We had gone through similar problems and this was one of the things that helped us.

• Collect lots of cache diagnostics data - In your cache configuration section, change the Microsoft.WindowsAzure.Plugins.Caching.DiagnosticLevel value to 4 in your cache worker role's configuration section. After you do that, add the following lines of code in your cache worker role's OnStart() method:

DiagnosticMonitorConfiguration dmConfig = DiagnosticMonitor.GetDefaultInitialConfiguration();

// Configure the collection of cache diagnostic data.
CacheDiagnostics.ConfigureDiagnostics(dmConfig);

DiagnosticMonitor.Start("Microsoft.WindowsAzure.Plugins.Diagnostics.ConnectionString",
    dmConfig);

return base.OnStart();

这应该可以给你究竟是怎么回事的想法。

Hopefully this should give you an idea about what exactly is going on.

这篇关于Azure的缓存 - 在升级失败后的SDK 2.1和2.1缓存的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！