Forum / Devolutions Password Server - Bug Report

Webinterface searchfunction not working

  • Create an Issue
  • Cancel


I have encountered an issue when trying to search for existing entries. After entering the search phrase multiple error mails were generated and no entries were found.

The following are some of the error messages, that were produced. All three were from one search action:


Error:
InvalidOperationException - Die Deserialisierung der Verbindung ist fehlgeschlagen. Die Daten sind leer oder die Verschlüsselung ist beschädigt. Details: ConnectionName: , ConnectionID: e2f320e4-1c84-4b3d-a20f-4b72f82f97a0, SecurityProvider: Default at Devolutions.Server.ConnectionManager.DeserializeConnection(ConnectionInfoEntity connectionInfo) --- Die Deserialisierung der Verbindung ist fehlgeschlagen. Die Daten sind leer oder die Verschlüsselung ist beschädigt. Details: ConnectionName: , ConnectionID: e2f320e4-1c84-4b3d-a20f-4b72f82f97a0, SecurityProvider: Default Source:
Devolutions.Server.Common

-----------------------------------------------------------------------------------------------------------------------------------
Error:
InvalidOperationException - Die Deserialisierung der Verbindung ist fehlgeschlagen. Die Daten sind leer oder die Verschlüsselung ist beschädigt. Details: ConnectionName: , ConnectionID: c2950473-4f35-450d-b534-ce47a47ffbcb, SecurityProvider: Default at Devolutions.Server.ConnectionManager.DeserializeConnection(ConnectionInfoEntity connectionInfo) --- Die Deserialisierung der Verbindung ist fehlgeschlagen. Die Daten sind leer oder die Verschlüsselung ist beschädigt. Details: ConnectionName: , ConnectionID: c2950473-4f35-450d-b534-ce47a47ffbcb, SecurityProvider: Default
Source:
Devolutions.Server.Common
-----------------------------------------------------------------------------------------------------------------------------------

Error:
NullReferenceException - Object reference not set to an instance of an object. at Devolutions.Server.ServerCacheManager.<>c__DisplayClass43_3.b__9(Connection c) at System.Linq.Enumerable.<>c__DisplayClass6_0`1.b__0(TSource x) at System.Linq.Enumerable.WhereListIterator`1.MoveNext() at System.Linq.Buffer`1..ctor(IEnumerable`1 source) at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source) at Devolutions.Server.Controllers.APIControllers.V2.BackendApiController.GetPartialMultiVaultSearch(SearchMultiVaultInfo multivaultInfo) at lambda_method(Closure , Object , Object[] ) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.b__9(Object instance, Object[] methodParameters) at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken) --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ApiControllerActionInvoker.d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Filters.ActionFilterAttribute.d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Web.Http.Filters.ActionFilterAttribute.d__5.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Filters.ActionFilterAttribute.d__0.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ActionFilterResult.d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Filters.AuthorizationFilterAttribute.d__2.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Web.Http.Controllers.ExceptionFilterResult.d__0.MoveNext() --- Default
Source:
Devolutions.Server.Common

Clock3 mths

Hello,

What Password Server version are you using?

Could you please try to reset the server cache in Administration - Reset Server Cache (Entries, Vaults) to see if this will help?

Best regards,



Érica Poirier

signaturesignature

Clock3 mths


Hello,

Resetting the server cache fixed the problem. Is this behaviour so common, that the reset needs to be made regularly?

best wishes,

Niklas Heine

Clock3 mths

Hello,

Thank you for your feedback and glad that resetting the server cache has resolved the issue.

It should not be common to reset the cache. We will investigate this a bit further. A ticket has been sent to our engineering department. For future references, the internal ticket number is DPS-3594. Once an update will be available, we will post it in this thread.

As a workaround, you could configure IIS to recycle nightly so the server cache will then be reset on a regular basis. Please see the following knowledge base article to set the automatic recycling in IIS.
https://devolutions.atlassian.net/servicedesk/customer/portal/1/article/602767371

Best regards,



Érica Poirier

signaturesignature

Clock3 mths

Hello,

I want to inform you that this issue has been resolved internally and the fix will be available in DPS version 2019.2.x that should be released in the upcoming weeks.

Best regards,



Érica Poirier

signaturesignature

Clock24 days