That should be the latest version. The error is some sort of internal error in memcached, and unfortunately I have no idea what causes it, maybe the memcached developers can help? I know I encountered it before when I accidentally caused some sort of resource starvation, but for single gets across machines you should never, ever see it. We've been running memcached on Windows Server 2003 and 2008, XP, Vista and Windows 7 without ever getting that problem.
/Henrik On Thu, Sep 17, 2009 at 07:30, Adi <[email protected]> wrote: > > Which version of BeIT memcached client should be used to resolve that > problem please give me its link, i have tried this: > http://code.google.com/p/beitmemcached/downloads/list > > But had the same error. > > Please let me know how to avoid CAS functionality? Does it mean Code > Access Security? that can be disable by using a command line "caspol - > s -off", tried this too and had the same behavior. > > > On Sep 16, 6:12 pm, Henrik Schröder <[email protected]> wrote: > > http://markmail.org/message/u3fzaqohrx4dtdxz#query:+page:1+mid:6llcxe... > > > > Does the above thread describe what you're trying to do? Are you using > the > > latest version of my client? Can you avoid using the CAS functionality? > > > > /Henrik > > > > > > > > On Wed, Sep 16, 2009 at 11:49, Adi <[email protected]> wrote: > > > > > Hi, > > > I have created a sample application by using BeIT.MemCached client to > > > test memcached ver 1.2.5, it is working fine on my PC (Vista > > > Professional) but when i access or want to store data from another PC > > > (that is also on the same network) i faced this error: > > > > > "Failed to write, and not due to blocking" > > > > > Than i run the client application / server 1.2.5 on Windows Server > > > 2003 and tried to Get the value from local memcached server but still > > > the same problem persist. > > > > > I have alsr tried MemCached ver 1.2.1 and 1.2.6, but the problem > > > persist. Please let me know is this problem specific to client (BeIT) > > > or Memcached Server. I have also red other post but didn't find the > > > solution of this problem. > > > > > Waiting for your reply. > > > Adeel >
