Showing results for 
Search instead for 
Do you mean 
Community Home Request Access Read Blogs Share Your Ideas Search Community View My Settings
Reply
Copper Super Contributor
Posts: 172
Registered: ‎07-06-2010

Memcached Exception Issues

Recently my local build has been crashing unexpectedly with the following error logged:

 

ERROR Memcached.ClientLibrary.SockIOPool - Failed to get SockIO obj for: 127.0.0.1:11211 -- new socket is not connected

System.IO.IOException: Could not connect for 50 milliseconds

   at Memcached.ClientLibrary.SockIO.GetSocket(String host, Int32 port, Int32 timeout)

   at Memcached.ClientLibrary.SockIO..ctor(SockIOPool pool, String host, Int32 timeout, Int32 connectTimeout, Boolean noDelay)

   at Memcached.ClientLibrary.SockIOPool.CreateSocket(String host)

 

I cannot pinpoint what happened to cause this to occur, but it seems to be happening at random intervals. It always results in the session being killed and the user taken to the SLX login page.

 

What would cause this to occur?

Copper Super Contributor
Posts: 172
Registered: ‎07-06-2010

Re: Memcached Exception Issues (Windows 7 centric?)

[ Edited ]

I thought this was fixed by changing the framework target but I was wrong. This is still an issue. 

 

On two different Windows 7 machines I am seeing these exceptions. 

 

The VS debugger logs the following just before it dies - it causes the app to crash and the user is immediately logged out:

 

'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'd6iljsfc'
A first chance exception of type 'System.Threading.ThreadAbortException' occurred in mscorlib.dll
An exception of type 'System.Threading.ThreadAbortException' occurred in mscorlib.dll but was not handled in user code
'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\slxclient\36c72603\9978a500\App_Web_ly1knxqs.dll', Symbols loaded.
'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\slxclient\36c72603\9978a500\App_Web_zvllgdlx.dll', Symbols loaded.
The thread '<No Name>' (0x14c0) has exited with code 0 (0x0).
'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'C:\Windows\assembly\GAC_MSIL\System.Configuration.Install\2.0.0.0__b03f5f7f11d50a3a\System.Configuration.Install.dll', Skipped loading symbols. Module is optimized and the debugger option 'Just My Code' is enabled.
WebDev.WebServer20.exe Information: 0 : Loading none-isolated adapter, type=Sage.SalesLogix.Web.RootAdapter assembly=Sage.SalesLogix.Web, Version=7.5.4.7097, Culture=neutral, PublicKeyToken=null path=C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\slxclient\36c72603\9978a500\assembly\dl3\53d26441\ec2d0882_681ece01\Sage.SalesLogix.Web.DLL
WebDev.WebServer20.exe Information: 0 : Adapter loaded type=Sage.SalesLogix.Web.RootAdapter
'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'Assembly15046eadc776421297fabfa051843fc5'
'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'Module23d3c499f74b40a0a3a1c7d62f84d319'
'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'Assembly9406c93273194522b1fc21de75985d86'
'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'Moduleff138459e6dc4f06a78b84fa1c4a58cc'
The thread '<No Name>' (0x19e0) has exited with code 0 (0x0).
'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\slxclient\36c72603\9978a500\App_Web_it5hye-h.dll', Symbols loaded.
The thread '<No Name>' (0x1248) has exited with code 0 (0x0).
'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\slxclient\36c72603\9978a500\App_LocalResources.groupbuilder.baea0156.ry1j0my2.dll', Symbols loaded.
'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\slxclient\36c72603\9978a500\App_Web_asqxl-ga.dll', Symbols loaded.
'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\slxclient\36c72603\9978a500\App_Web_ge-vnar2.dll', Symbols loaded.
'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\slxclient\36c72603\9978a500\App_LocalResources.account.baea0156.l60l8rzi.dll', Symbols loaded.
'WebDev.WebServer20.EXE' (Managed (v2.0.50727)): Loaded 'C:\Windows\Microsoft.NET\Framework\v2.0.50727\Temporary ASP.NET Files\slxclient\36c72603\9978a500\App_Web_aefd3a8g.dll', Symbols loaded.
A first chance exception of type 'System.NullReferenceException' occurred in Sage.SalesLogix.Client.GroupBuilder.DLL
A first chance exception of type 'System.NullReferenceException' occurred in Sage.Platform.Application.UI.Web.DLL

 

I've deleted the cache several times. Still no dice. Any thoughts would be appreciated.

Copper Super Contributor
Posts: 172
Registered: ‎07-06-2010

Re: Memcached Exception Issues (Windows 7 centric?)

I would like to thank dva and mcessna for the following post:

http://community.sagesaleslogix.com/t5/Administration/Sage-Cache-Service-7-5-4/td-p/147965

 

On closer inspection it seems the Cache service was not installed on either machine. I grabbed the EXEs from the installation media and just ran them from my desktop... and the exceptions and odd behavior have finally disappeared. 

 

I can't remember whether the Cache service is a selectable option on installation, or if the installer itself just didn't complete a full installation. But it seems this approach is working.