After installing VaultClient_3_5_1 I found that whenever I open a folder in Windows Explorer, it would always open in a new window. It has proven to be impossible to correct windows to open a folder in the same window (yes, have toggles obvious setting in tools->option and tried all sorts of things). Please see this forum:
http://social.technet.microsoft.com/For ... f=required
Any ideas on what I can do? Is there a compatible version of Vault Client I can download and use?

Windows 7 isn't supported yet, but you have a better chance of working with newer versions of Vault instead of older versions. At the very least you should consider upgrading your server and client to Vault 3.5.3.

The latest version, Vault 5.0, has had some testing on Windows 7, and so far, we've had some good results with that.

I went ahead and installed Vault 3.5.1 client on my Windows 7 machine, and didn't get the results you have. My folders all open in the same window. Can you show a screenshot of what options you have set so I can compare? Also, which Windows 7 version are you using? (Enterprise, pro, or some other) Do you have the whole version number for the version of Windows 7 (in case I need to try a different version)?

I installed version 3.5.3 and caused the same problem. I downloaded and installed the latest version (v5) and everything was fine after the install.

I'm using Windows 7 Ultimate (RTM) build 7600.

Ok, I'm a bit behind on my version. I'll get my Windows 7 updated.

Version 5 is the one that was tested with Windows 7, and that will ultimately be the best choice.

This happened on my Windows 7 PC and it was due to an install of Sourcegear Vault 3.0 that overwrites a registry entry used by many programs. The three it affected on my PC were Internet Explorer 8 (most links will not open), Windows Explorer (double click opens a new search window) and MS SQL Server Management Studio 2008 errors with COM error. This is all due to two registry entries containing {B8DA6310-E19B-11D0-933C-00A0C90DCAA9} overwriting the correct ones.

To fix this, save the info below into a reg file and run it to correct the registry entries on your PC. A reboot is required to get the double click working correctly in Explorer.

WARNING: Backup your registry or these registry entries below to be on the safe side.

[COPY FROM]
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}]
@="IServiceProvider"

[HKEY_CLASSES_ROOT\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}\NumMethods]
@="4"

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

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}]
@="IServiceProvider"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}\NumMethods]
@="4"

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

OK, solution was found, from this forum:
http://social.technet.microsoft.com/For ... f=required

Here's the post (from KevinInNZ):
This happened on my Windows 7 PC and it was due to an install of Sourcegear Vault 3.0 that overwrites a registry entry used by many programs. The three it affected on my PC were Internet Explorer 8 (most links will not open), Windows Explorer (double click opens a new search window) and MS SQL Server Management Studio 2008 errors with COM error. This is all due to two registry entries containing {B8DA6310-E19B-11D0-933C-00A0C90DCAA9} overwriting the correct ones.

To fix this, save the info below into a reg file and run it to correct the registry entries on your PC. A reboot is required to get the double click working correctly in Explorer.

WARNING: Backup your registry or these registry entries below to be on the safe side.

[COPY FROM]
Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}]
@="IServiceProvider"

[HKEY_CLASSES_ROOT\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}\NumMethods]
@="4"

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

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}]
@="IServiceProvider"

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Interface\{6D5140C1-7436-11CE-8034-00AA006009FA}\NumMethods]
@="4"

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

Just a reminder for others coming across this thread, older versions of Vault are not supported on Windows 7. I'd recommend upgrading to Vault 5.0, because your best chance of success will be that version.

That being said, I think we found an easier way of dealing with this. We reproduced the issue and were able to fix it by running the following:

Code: Select all

regsvr32 "%programfiles%\Internet Explorer\ieproxy.dll"

This MUST be run as administrator. One way of doing that is to create a shortcut that runs that command and then running the shortcut as administrator.

Beth,

Thanks for the command. I had to alter it slightly for it to work for us as we are running Windows 7 64 bit and our issue was with IE 8 32 bit. I simply changed the “Program Files” directory as the example provided registered the file in “Program Files” 64 Bit by default (at least for me).

Code: Select all

regsvr32 "C:\Program Files (x86)\Internet Explorer\ieproxy.dll"

This worked for us. Hope it makes sense.

Thanks again.

Thanks for the update. The additional information is appreciated.