We are having problems with the shelve, if a user attempts to shelve a file or files it appears to work, but the shelve set is not in the list when the user looks to unshelve the files.
Looking in the log we see entries like this:
Code: Select all
----04/12/2017 08:49:19 i.gray--desktop39.paragon.pgn(192.168.97.18)--SSL Disabled Login
----04/12/2017 08:49:33 i.gray--desktop39.paragon.pgn(192.168.97.18)--SSL Disabled Login
----04/12/2017 08:49:39 i.gray--desktop39.paragon.pgn(192.168.97.18)--SSL Disabled Login
----04/12/2017 08:50:03 i.gray--desktop39.paragon.pgn(192.168.97.18)--SSL Disabled Rolling Back a transaction at VaultServiceSQL.VaultSqlConn.RollbackTransaction(Boolean bShowStacktrace)
at VaultServiceAPILib.VaultServiceAPI.EndSaveShelveSet(VaultIntShelve vis, Int32 nUserID, Int64& ssid)
at VaultService.VaultService.EndSaveShelveSet(String strShelveID, Int64& ssid)
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeMethodInfo.UnsafeInvokeInternal(Object obj, Object[] parameters, Object[] arguments)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Web.Services.Protocols.LogicalMethodInfo.Invoke(Object target, Object[] values)
at System.Web.Services.Protocols.WebServiceHandler.Invoke()
at System.Web.Services.Protocols.WebServiceHandler.CoreProcessRequest()
at System.Web.Services.Protocols.SyncSessionlessHandler.ProcessRequest(HttpContext context)
at System.Web.Script.Services.ScriptHandlerFactory.HandlerWrapper.ProcessRequest(HttpContext context)
at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
at System.Web.HttpApplication.PipelineStepManager.ResumeSteps(Exception error)
at System.Web.HttpApplication.BeginProcessRequestNotification(HttpContext context, AsyncCallback cb)
at System.Web.HttpRuntime.ProcessRequestNotificationPrivate(IIS7WorkerRequest wr, HttpContext context)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
at System.Web.Hosting.UnsafeIISMethods.MgdIndicateCompletion(IntPtr pHandler, RequestNotificationStatus& notificationStatus)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotificationHelper(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
at System.Web.Hosting.PipelineRuntime.ProcessRequestNotification(IntPtr rootedObjectsPointer, IntPtr nativeRequestContext, IntPtr moduleData, Int32 flags)
----04/12/2017 08:50:03 i.gray--desktop39.paragon.pgn(192.168.97.18)--SSL Disabled EndSaveShelveSet returned: FailShelvedFileNameIsNull
----04/12/2017 08:50:03 i.gray--desktop39.paragon.pgn(192.168.97.18)--SSL Disabled EndSaveShelveSet returned: FailShelvedFileNameIsNull
----04/12/2017 08:50:10 i.gray--desktop39.paragon.pgn(192.168.97.18)--SSL Disabled Logout
----04/12/2017 08:50:11 i.gray--desktop39.paragon.pgn(192.168.97.18)--SSL Disabled Login
----04/12/2017 08:50:38 i.gray--desktop39.paragon.pgn(192.168.97.18)--SSL Disabled Logout
----04/12/2017 08:50:39 i.gray--desktop39.paragon.pgn(192.168.97.18)--SSL Disabled Login
----04/12/2017 08:50:58 i.gray--desktop39.paragon.pgn(192.168.97.18)--SSL Disabled Logout
----04/12/2017 08:50:59 i.gray--desktop39.paragon.pgn(192.168.97.18)--SSL Disabled Login
Any suggestions?