Visual Studio 2005 Issue

dazfuller · Post by **dazfuller** » Fri Oct 19, 2007 9:17 am

We have just upgraded from Vault 3.5.2 to Fortress 1.0.4, I'm currently going through and removing studio bindings and re-adding them to get around the upgrade problem but every time I open a solution now the solution file is automatically being checked out? Is this something which can be stopped in the settings somewhere?

We're also getting the following error sometimes when we are adding solutions back into Fortress?

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)).

lbauer · Post by **lbauer** » Fri Oct 19, 2007 9:55 am

every time I open a solution now the solution file is automatically being checked out

Could you do a diff on the solution file (compare it to the latest version in the repository) to see if it has changed? It's possible that Fortress is checking out the file because it is changed and checking it back in will resolve the problem.

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)).

For this error try re-registering this dll:

Regsvr32 actxprxy.dll

Sometimes uninstalling Fortress or Vault clients unregisters this.

ian_sg · Post by **ian_sg** » Fri Oct 19, 2007 10:22 am

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)).

We haven't determined what causes this DLL to sometimes be left in an unregistered state, but it doesn't appear to be a SourceGear-specific problem. There's some more info here (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=120476&SiteID=1), where they reach the same conclusion: register actxprxy.dll.

dazfuller · Post by **dazfuller** » Mon Oct 22, 2007 2:44 am

Thanks for the DLL fix, that's worked a treat.

As for the solution file, I've checked and the solution file is not being changed, also it does not appear in the pending changes panel unless I check another file out?

ian_sg · Post by **ian_sg** » Tue Oct 23, 2007 8:21 am

After the solution file gets checked out, do a "Save All" to ensure any changes are written to disk. Is there still no change showing up for the solution file?

dazfuller · Post by **dazfuller** » Tue Oct 23, 2007 8:27 am

Just checked and the version in Fortress is identical to the local version even after a "Save All" so no changes have been made to it

stbpsegrera · Post by **stbpsegrera** » Wed May 07, 2008 1:54 pm

I am running Windows XP 64-bit with the latest client and I am receiving this error when I open SQL Server Management Studio. I am running the 64-bit Developer Edition of SQL 2005.

I am tried to register the DLL and even try to modification to the registry as suggested by Microsoft website, but nothing works.

Update: Seems to be an error with Object Explorer. I am able to access the databases using the view on the right side, but not on the left.

stbpsegrera · Post by **stbpsegrera** » Wed May 07, 2008 2:09 pm

Acutally if you are running any 64-bit OS, you will need to run register the dll, but under C:\Windows\SysWOW64 and that corrects my problem.

lbauer · Post by **lbauer** » Thu May 08, 2008 9:29 pm

Thanks for the information. I'm sure it will help other users.

mvdarend · Post by **mvdarend** » Fri May 09, 2008 4:23 am

stbpsegrera wrote:Acutally if you are running any 64-bit OS, you will need to run register the dll, but under C:\Windows\SysWOW64 and that corrects my problem.

Thank You! I registered especially to say that

This problem has been driving me crazy for the last two months.

lbauer · Post by **lbauer** » Wed May 14, 2008 8:48 am

We really appreciate the tips provided by our users on this forum.

Henrik · Post by **Henrik** » Sat Jun 13, 2009 9:28 am

Slightly off topic, but Vault 3.5 installs ok on Windows 7 64 bit (setup completes successfully), but it messes up SQL Server Management Console 2008 (the same error as others have described). Registering the DLL doesn't work.

I tried a couple of different ways but could only get back to a functioning system by using a restore point.

Henrik · Post by **Henrik** » Sat Jun 13, 2009 12:21 pm

I figured out how to make Vault 3.5 work on a Windows 7 64 bit system.

1) Install the Vault client using setup program.
2) Roll the install back out of your system using the last system restore point (it leaves the Vault program files, but clears out the damage to the registry made during the install).
3) Add the following registry settings to your system (change the D:\ drive reference below to the drive that you have Vault installed on). These settings will make Vault show as a provider in Visual Studio)

-- start of registry script --
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"="D:\\Program Files (x86)\\SourceGear\\Vault Client\\VaultIDE.dll"

-- end of registry script --

lbauer · Post by **lbauer** » Mon Jun 15, 2009 2:52 pm

Thanks for the info. Please note that Vault 3.5.x has not been tested on Windows 7 and is not officially supported, so if users run into other issues, SourceGear Tech Support may not be able to help.

MikeM · Post by **MikeM** » Sat Aug 15, 2009 4:44 pm

I am running Vault Client 4.0.4 with Windows 7 (64-bit) and had the same problems described here.

Not only does SQL Server Management Studio get screwed up, but so does Internet Explorer -- links would cease to open anywhere but in the same window and tab from where they were clicked. IE actually worked okay in 64-bit mode for me, and was broken in 32-bit.

Anyway, Henrik's solution above got me thinking about the registry and I took some time to compare an export of my registry before and after the Vault installation. I came up with a solution:

Copy the content between the lines into a .reg file, save it, then right-click it and choose "merge" and it should fix things.

--- Begin Registry Script ---
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}\ProxyStubClsid32]
@="{A4A1A128-768F-41E0-BF75-E4FDDD701CBA}"

--- End Registry Script ---

The way I figured this out, was that I noticed a registry key was added with a GUID of {B8DA6310-E19B-11D0-933C-00A0C90DCAA9} that referenced "actxprxy.dll", which is an important DLL for Internet Explorer and one that everyone says you have to re-register when you experience the problems we are having. Then, later in the registry, I found a changed key (the one above in my fix) that was referencing it. I simply changed the reference to point to the original GUID of {A4A1A128-768F-41E0-BF75-E4FDDD701CBA} and tried it. The original GUID referenced ieproxy.dll, which seemed to make sense. It worked, so I didn't do anything else with it. It'll at least get me by until my company decides to upgrade all of our source code to the latest version of Vault.

I hope this helps someone.

-Mike

SourceGear Support

Visual Studio 2005 Issue

Visual Studio 2005 Issue

Re: Visual Studio 2005 Issue

Re: Visual Studio 2005 Issue

Re: Visual Studio 2005 Issue

Re: Visual Studio 2005 Issue