Issue after upgrading to AppFabric 1.1: Client Version Error

Answered Issue after upgrading to AppFabric 1.1: Client Version Error

  • Wednesday, April 25, 2012 8:52 AM
     
     

    I had been running AppFabric 1.0 on Windows 7 without any problems.  I upgraded to 1.1.  I removed my old references to Microsoft.ApplicationServer.Caching.Client.dll and Microsoft.ApplicationServer.Caching.Core.dll and added new references from the 1.1 folder (C:\Program Files\AppFabric 1.1 for Windows Server).

    I've configured my web.config exactly as described here:

    http://msdn.microsoft.com/en-us/library/hh361702.aspx

    I've also added a reference to Microsoft.Web.DistributedCache.dll.

    Now when I attempt to run my project I get the following error:

    ErrorCode<ERRCA0019>:SubStatus<ES0001>:Check the client version. It should be within the allowed version range on the server. If necessary, upgrade the client to the allowed version.

    Both the client and server are my Win 7 local machine.

    Any ideas?

All Replies

  • Wednesday, April 25, 2012 1:18 PM
     
     

    Are the 1.0 binaries GAC'ed by any chance on any of the boxes ?

    Also, can you share the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppFabric\V1.0\Version key's contents ?

  • Wednesday, April 25, 2012 1:41 PM
     
     

    There was definitely nothing in the GAC, I'm only using a standalone developer machine as both client and server.

    I've uninstalled AppFabric completely, I am currently installing Win 7 SP1 and will then attempt a clean install of AppFabric 1.1 and will report back with those registry values if I still have a problem. Thanks.

  • Wednesday, April 25, 2012 1:47 PM
     
     

    There was definitely nothing in the GAC, I'm only using a standalone developer machine as both client and server.

    I've uninstalled AppFabric completely, I am currently installing Win 7 SP1 and will then attempt a clean install of AppFabric 1.1 and will report back with those registry values if I still have a problem. Thanks.

    Cool, let us know if you keep hitting issues. By default 1.0 binaries are GAC'ed but upgrade should take care of it in most cases.
  • Thursday, April 26, 2012 7:47 AM
     
     

    Installing from scratch has now got me to a point where the cache is usable.

    I'm having issues in powershell. When I first launch it I get an error 

    "Use-CacheCluster : ErrorCode<ERRCAdmin040>:SubStatus<ES0001>:Failed to connect to hosts in the cluster".

    I'm then trying to change the TimeToLive on my cache like "Set-CacheConfig default -TimeToLive 1200"

    which is giving me the following error:

    PS C:\Windows\system32> Set-CacheConfig default -TimeToLive 1200
    Set-CacheConfig : Object reference not set to an instance of an object.
    At line:1 char:16
    + Set-CacheConfig <<<<  default -TimeToLive 1200
        + CategoryInfo          : NotSpecified: (:) [Set-CacheConfig], NullReferen
       ceException
        + FullyQualifiedErrorId : System.NullReferenceException,Microsoft.Applicat
       ionServer.Caching.Commands.SetCacheConfigCommand

    Interestingly I tried "Restart-CacheCluster" which worked and showed my Service as being up however the version Info was 0 [0,0][0,0], is this correct?

    Also, while running in Visual Studio in my application and I can read and write to the cache. However once I publish my website to my local machine and run under IIS I get the following error:

    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 the firewall on all cache hosts. Also the MaxBufferSize on the server must be greater than or equal to the serialized object size sent from the client.)

    The inner Exception is:

    {"The socket connection was aborted. This could be caused by an error processing your message or a receive timeout being exceeded by the remote host, or an underlying network resource issue. Local socket timeout was '10675199.02:48:05.4775807'."}

    This is all running on a standalone machine so there are no network variables in play.

    I'm really at a loss to understand how so many things could be different between 1.0 and 1.1 to cause so many issues.

    It still appears though that something is not right with my installation.

    I would appreciate any assistance.




    • Edited by keithnolan Thursday, April 26, 2012 7:50 AM
    • Edited by keithnolan Thursday, April 26, 2012 8:15 AM
    • Edited by keithnolan Thursday, April 26, 2012 8:24 AM
    •  
  • Thursday, April 26, 2012 1:53 PM
     
     

    As previously asked the contents of HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\AppFabric\V1.0\Version key

    BeginAllowedClientCodeVersionRange - 1

    BeginAllowedCodeVersionRange - 3

    CodeVersion - 3

    EndAllowedClientCodeVersionRange - 3

    EndAllowedCodeVersionRange - 3

    This confuses me even more as these values look correct yet my host displays all zeros in the version info field.

  • Thursday, April 26, 2012 2:29 PM
     
     Answered
    It actually turns out that the root cause of all the issues was that the "Remote registry service" was not started before the AppFabric service. I had started it but after the AppFabric service when I then stopped the AppFabric service and restarted things started working.
    • Marked As Answer by keithnolan Thursday, April 26, 2012 2:29 PM
    •