VS2017 No Longer Working with SourceVault

[mdjtlj]

Greetings,

Hopefully we can take this off-line, but I've just started having a problem with all projects. The following is the typical scenario:

- Open up a project that was previously bound
- Do any action (check out a file, try to look at history, add a file, etc....), the VS freezes up.
- I've turned the debug logging on in the source control, but there doesn't seem to be any type of error in the log that I can see
- I literally have to CTRL-ALT-DELETE Visual Studio to get out of this. I'm unable to change windows.
- VS is perfectly fine until any activity that has to do with Source Vault is triggered
- There are no notifications displayed, nothing in the output, just totally unresponsive

I'm running 10.2.0, I've uninstalled/re-installed both the classic client and the VSIX plug-in, all to no avail.

The only way that I've been making any type of progress with my projects is to unbind them from source control. Then everything goes back to normal. There have not been any changes to the environment, outside of normal Windows updates. I will mention that the classic client (not integrated into VS) is working fine, it can see the repository, do all the things it needs, but the VSIX appears to be the problem. I even tried to uninstall the VSIX and rely on the classic integration in VS, same issue as above.

I'm pretty desperate at this point.

[mdjtlj]

As found in the log, the notifications are giving issues, which is what I'm also seeing in the VS if i open it and don't do anything related to SCC, it'll provide the same basic errors.

11/2/2024 9:04:35 AM <generic>: [<No Name>:785] Failed to retrieve items from the Notification Server - http://173.11.xxx.XXX/VaultNotifyServic ... rvice.asmx. [System.Net.WebException: The operation has timed out
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.VaultNotifyService.VaultNotifyService.RetrieveNotifications(String strNotifyAuthTicket, Int32 nDetailThreshold, Int32& nAppNotifyEnabled, NotificationItem[]& arNotifyItems)
at VaultClientPresentationLib.NotificationsView.RefreshNotificationItemsThreadProc(Object o)] The operation has timed out
at System.Net.HttpWebRequest.GetRequestStream(TransportContext& context)
at System.Net.HttpWebRequest.GetRequestStream()
at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
at VaultClientNetLib.VaultNotifyService.VaultNotifyService.RetrieveNotifications(String strNotifyAuthTicket, Int32 nDetailThreshold, Int32& nAppNotifyEnabled, NotificationItem[]& arNotifyItems)
at VaultClientPresentationLib.NotificationsView.RefreshNotificationItemsThreadProc(Object o)

11/2/2024 9:04:35 AM <generic>: [<No Name>:785] [Vault Message][Warning] Too many errors occurred retrieving application notification messagesfrom http://173.11.xxx.XXX/VaultNotifyServic ... rvice.asmx. Notifications retrieval has been disabled.
at SourceGearLLC.VaultVsipClient.VaultVsipClient.HandleEvent(MessageEvent e)
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.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
at VaultClientPresentationLib.GUIEventEngine.FireEventPrivate(Object o, BaseEvent e)
at VaultClientPresentationLib.GUIEventEngine.fireEvent(BaseEvent e)
at VaultClientPresentationLib.GUIClientInstance.EmitMessage(ProgressMessage message)
at VaultClientPresentationLib.NotificationsView.RefreshNotificationItemsThreadProc(Object o)
at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
at System.Threading.ThreadPoolWorkQueue.Dispatch()
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Not sure why this is going sideways at this point, there has been no network changes on the Vault server, nor the local laptop. I even went and disabled all firewalls, AV, etc.... on both sides, still no joy.

[Tonya]

Hello,

Perhaps a windows update possibly caused an issue if that's the only modification you can think of. Can you please send your Vault Server log to support@sourcegear.com? Also provide us with details in regards to your OS as well.

The errors you have followed up with are all in regards to email notifications. Are you using this feature? If not, you should disable it to prevent all the errors in your log. If you are using it, is it working accordingly?

Thanks,

Tonya