Password Manager 5.8, Password Manager Service stops Running

I recently upgraded Password Manager from version 5.7 to 5.8.  I have been having issues attempting to log into the PMUser and PM Help desk sites.  I get an error saying to check the event log right after I enter in my domain username.  After about 10-15 minutes the Password Manager Service will stop running.  No helpful event logs say why the service stopped running.  I already have a case opened with support but so far there has not been a resolution.  I've enabled verbose logging and attached the logs to the case.  From what I can see those logs also don't provide any info as to why the service stops running and why I get the errors.  Anyone else experience this before?  If I don't attempt to log into the PM User site than the Password Manager Service will continue to run.

The Password Manager Event log shows this.

Result: CriticalError

Info:

System.TimeoutException: This request operation sent to net.pipe://127.0.0.1/QPM.Service.Services.UserService did not receive a reply within the configured timeout (00:01:00).  The time allotted to this operation may have been a portion of a longer timeout.  This may be because the service is still processing the operation or because the service was unable to send a reply message.  Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.

Server stack trace:

   at System.ServiceModel.Dispatcher.DuplexChannelBinder.Request(Message message, TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   at QPM.Service.Interfaces.Services.IWorkflowService.SetRuntimeAndExecute(WorkflowRequest request, CommandName command, RuntimeBase runtime)

   at QPM.UI.Common.MVC.Controllers.HomeController.GetViewModel(Nullable`1 commandName, RuntimeBase runtime)

   at QPM.UI.Common.MVC.Controllers.HomeController.Index(CommonViewModel commonViewModel)

   at lambda_method(Closure , ControllerBase , Object[] )

   at System.Web.Mvc.ReflectedActionDescriptor.Execute(ControllerContext controllerContext, IDictionary`2 parameters)

   at System.Web.Mvc.ControllerActionInvoker.InvokeActionMethod(ControllerContext controllerContext, ActionDescriptor actionDescriptor, IDictionary`2 parameters)

   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass42.<BeginInvokeSynchronousActionMethod>b__41()

   at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethod(IAsyncResult asyncResult)

   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass37.<>c__DisplayClass39.<BeginInvokeActionMethodWithFilters>b__33()

   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49()

   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass4f.<InvokeActionMethodFilterAsynchronously>b__49()

   at System.Web.Mvc.Async.AsyncControllerActionInvoker.EndInvokeActionMethodWithFilters(IAsyncResult asyncResult)

   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<>c__DisplayClass2a.<BeginInvokeAction>b__20()

   at System.Web.Mvc.Async.AsyncControllerActionInvoker.<>c__DisplayClass25.<BeginInvokeAction>b__22(IAsyncResult asyncResult)

  • We have seen this same issue on a few sites where the Password Manager service is stopping.  Unfortunately at this point in time there is no resolution.  The best resource would be Technical Support who can engage engineering to assist in finding resolution to this issue.  If this is production you may need to role back to 5.7.1 where this issue is not occurring.

    Thanks

    Stephen