After installing SourceGear Vault client v3.1.9 on a Microsoft Windows 7 RTM 64bit machine, opening a new tab in Microsoft Internet Explorer 8 (32 bit), by pressing ctrl + click on a link, the new tab will hang, showing a white screen. This is caused by the installation of the SourceGear Vault client v3.1.9. (The Microsoft Internet Explorer 8 (64 bit) does not have this problem).
An error will also occur when you open the Microsoft SQL Server Management Studio and connect to a SQL Server instance:
Unable to cast COM object of type ‘System.__ComObject’ to interface type ‘Microsoft.VisualStudio.OLE.Interop.IServiceProvider’. This operation failed because the QueryInterface call on the COM component for the interface with IID ‘{6D5140C1-7436-11CE-8034-00AA006009FA}’ failed due to the following error: No such interface supported (Exception from HRESULT: 0x80004002 (E_NOINTERFACE)). (Microsoft.VisualStudio.OLE.Interop)
Solution
> Install the SourceGear Vault client v3.1.9 in "C:\Program Files (x86)\SourceGear\Vault Client"
> Backup all files and folders from the folder "C:\Program Files (x86)\SourceGear\Vault Client" to a backup folder "C:\Program Files (x86)\SourceGear\Vault Client Backup"
> Uninstall the SourceGear Vault client v3.1.9
> Restore all files and folders from the "C:\Program Files (x86)\SourceGear\Vault Client Backup" to the "C:\Program Files (x86)\SourceGear\Vault Client"
> Create a FixSourceControlProviderOnWin7x64.reg file and paste the following values:
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceCodeControlProvider]
"ProviderRegKey"="Software\\SourceGear\\Vault Client"
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceCodeControlProvider\InstalledSCCProviders]
"SourceGear Vault Client"="Software\\SourceGear\\Vault Client"
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceGear]
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\SourceGear\Vault Client]
"SCCServerName"="SourceGear Vault Client"
"SCCServerPath"="C:\\Program Files (x86)\\SourceGear\\Vault Client\\VaultIDE.dll"
> Run the FixSourceControlProviderOnWin7x64.reg file.
8 Replies to “Microsoft Windows 7 RTM 64bit and Internet Explorer 8 new tab hang after Vault Client v3.1.9 installation”
Leave a Reply
This site uses Akismet to reduce spam. Learn how your comment data is processed.
Hi Roel, thanks for the post. I had (have) this same exact problem and its a huge pain. I did exactly as instructed above but am still experiencing the same tab issue with ie and SQL Server Management Studio.
I verified that the registry settings are there but do you have any other suggestions? I am using the vault client 3.1.9 as well.
-Paul
Sorry for the double post but if I right click on ie or sql and “Run as Administrator” all works fine. I only have 1 user setup on my machine, and thats me and my account type is Administrator.
Do you know how to make these applications “Run as Administrator” by default? Do you know why, even though I am setup as an administrator, it still takes me having to click on “Run as Administrator” and is not acting appropriately by default?
Thanks,
Paul
Internet Explorer 8 seems to be the best browser for me. I can open more than 20 windows simultaneously without crashing. IE7 and IE6 is unstable that if you open more than windows at a time it just freezes or causes the blue screen.
@Paul – Try this:
1. Run an elevated Command Prompt as Administrator
2. Run regsvr32 “%SystemRoot%\System32\actxprxy.dll”
3. Run regsvr32 “%ProgramFiles%\Internet Explorer\ieproxy.dll”
4. Maybe restart (but I don’t think required)
I also had the symptom whereby clicking on a folder in Explorer would open a new window despite the configuration settings saying to use the *same* window.
Dean
This solution also fixed in issue with Building and debugging a Windows Azure in Visual Studio 2010.
http://social.msdn.microsoft.com/Forums/en-US/windowsazuredevelopment/thread/76329951-cf2a-4bb0-bca6-9e52fd963987
http://stackoverflow.com/questions/4809804/windows-azure-training-kit-guestbook-demo-get-error-when-building
Hi Roel, while searching for this solution for ages.. I finally came across your blog (again). This solved my issues with SSMS.
Thanks 🙂