Server Error in '/' Application.

Timeout performing EXISTS FmkStr.urlrecord.active.id-name-language-39-Category-1, inst: 1, mgr: ProcessReadQueue, err: never, queue: 2, qu: 0, qs: 2, qc: 0, wr: 0, wq: 0, in: 7, ar: 1, clientName: WIN-SEO4MF37SU2, serverEndpoint: 127.0.0.1:6379, keyHashSlot: 6209, IOCP: (Busy=0,Free=1000,Min=48,Max=1000), WORKER: (Busy=12,Free=32755,Min=48,Max=32767), Local-CPU: unavailable (Please take a look at this article for some common client-side issues that can cause timeouts: https://github.com/StackExchange/StackExchange.Redis/tree/master/Docs/Timeouts.md)

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.TimeoutException: Timeout performing EXISTS FmkStr.urlrecord.active.id-name-language-39-Category-1, inst: 1, mgr: ProcessReadQueue, err: never, queue: 2, qu: 0, qs: 2, qc: 0, wr: 0, wq: 0, in: 7, ar: 1, clientName: WIN-SEO4MF37SU2, serverEndpoint: 127.0.0.1:6379, keyHashSlot: 6209, IOCP: (Busy=0,Free=1000,Min=48,Max=1000), WORKER: (Busy=12,Free=32755,Min=48,Max=32767), Local-CPU: unavailable (Please take a look at this article for some common client-side issues that can cause timeouts: https://github.com/StackExchange/StackExchange.Redis/tree/master/Docs/Timeouts.md)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:


[TimeoutException: Timeout performing EXISTS FmkStr.urlrecord.active.id-name-language-39-Category-1, inst: 1, mgr: ProcessReadQueue, err: never, queue: 2, qu: 0, qs: 2, qc: 0, wr: 0, wq: 0, in: 7, ar: 1, clientName: WIN-SEO4MF37SU2, serverEndpoint: 127.0.0.1:6379, keyHashSlot: 6209, IOCP: (Busy=0,Free=1000,Min=48,Max=1000), WORKER: (Busy=12,Free=32755,Min=48,Max=32767), Local-CPU: unavailable (Please take a look at this article for some common client-side issues that can cause timeouts: https://github.com/StackExchange/StackExchange.Redis/tree/master/Docs/Timeouts.md)]
   StackExchange.Redis.ConnectionMultiplexer.ExecuteSyncImpl(Message message, ResultProcessor`1 processor, ServerEndPoint server) +521
   StackExchange.Redis.RedisBase.ExecuteSync(Message message, ResultProcessor`1 processor, ServerEndPoint server) +70
   StackExchange.Redis.RedisDatabase.KeyExists(RedisKey key, CommandFlags flags) +180
   FmkStr.Core.Caching.RedisCacheManager.IsSet(String key) in D:\Project\FimkaStoreMobile\webapi\Libraries\FmkStr.Core\Caching\RedisCacheManager.cs:114
   FmkStr.Core.Caching.CacheExtensions.Get(ICacheManager cacheManager, String key, Int32 cacheTime, Func`1 acquire) in D:\Project\FimkaStoreMobile\webapi\Libraries\FmkStr.Core\Caching\Extensions.cs:37
   FmkStr.Services.Seo.UrlRecordService.GetActiveSlug(Int32 entityId, String entityName, Int32 languageId) in D:\Project\FimkaStoreMobile\webapi\Libraries\FmkStr.Services\Seo\UrlRecordService.cs:330
   FmkStr.Services.Seo.SeoExtensions.GetSeName(Int32 entityId, String entityName, Int32 languageId, Boolean returnDefaultValue, Boolean ensureTwoPublishedLanguages) in D:\Project\FimkaStoreMobile\webapi\Libraries\FmkStr.Services\Seo\SeoExtensions.cs:166
   FmkStr.Web.Framework.Seo.GenericPathRoute.GetRouteData(HttpContextBase httpContext) in D:\Project\FimkaStoreMobile\webapi\Presentation\FmkStr.Web.Framework\Seo\GenericPathRoute.cs:136
   System.Web.Routing.RouteCollection.GetRouteData(HttpContextBase httpContext) +239
   System.Web.Routing.UrlRoutingModule.PostResolveRequestCache(HttpContextBase context) +73
   System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +142
   System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step) +75
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +93


Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.4700.0