ADSubtract strikes again after upgrade

[ray023]

Hi Guys,

We purchased Source Vault today and upgraded to 2.0.1.

Everything works well except for my client box.
Remeber the article here**:
http://support.sourcegear.com/viewtopic.php?t=135

I haven't changed my machine.config since the upgrade.
It still says <proxy usesystemdefault="true"/>

However, I get the same "unable to connect error" with 2.0.1.

If I unload the adsubtract app, it works.

Is there something similar I can do for 2.0.1?


**

Since AdSubtract is probably not mandated by your network, you could try telling the .Net framework to not go through the system default proxy. Look in you machine.config under the <defaultProxy> section and change

<proxy usesystemdefault="true"/>

to

<proxy usesystemdefault="false"/>

Restart your vault client, and you should be good.

[jeremy_sg]

If you want to tell Vault to not go through adsubtract, then you'll need that setting to be false. Also, you should look in your VaultGuiClient.exe.config for the same setting. It could be that the config file there is overriding the machine.config.

[ray023]

If you want to tell Vault to not go through adsubtract, then you'll need that setting to be false

LOL. I can just see your eyes rolling up as you read that message. It had a minor typo.
The setting actually is <proxy usesystemdefault="false"/>
in both machine.config AND--since your last message--VaultGUIClient.exe.config

However, I still get the attached error when trying to load the Vault Client.

[jeremy_sg]

Try setting the proxy to:

<usesystemdefault="false" proxyaddress="http://bogus:bogus" bypassonlocal="false">

Setting proxyaddress to something bogus should force .Net to try and fail to connect to a proxy, then skip the proxy entirely. You'll need to restart the Vault client after changing this setting.

[ray023]

Hi Jeremy,
I assume you mean:
<proxy usesystemdefault="false" proxyaddress="http://bogus:bogus" bypassonlocal="false"/>

b/c I get a "file not well formed" error if I try to save the other way.

First made the change in Vault Client config file and tested: didn't work.
Made the change in both configuration files mentioned above: didn't work.

I tried to attach a copy of the program but it said it was too big (2.77MB).

Is there a way I can get you a copy of this program to test? it's the same one I have except it's unregistered.

[jeremy_sg]

You're right. The XML portion of my brain hasn't booted up this morning. Try setting the hostname of your vault server in IE's bypass list as a workaround. You can get to that list through the advanced button by where you set the proxy address and port. I don't think that it's the proxy's fault that the proxy setting in Vault isn't working, and I don't think that we will be able to fix Vault to work with AdSubtract, since I bet it's the SOAP content of the Vault messages that's confusing AdSubtract.

[ray023]

Got it!!!

Although I didn't see the exact setting you referred too, I did find a checkbox called Bypass proxy server for local addresses
here:
Tools/Internet Options/Connections/Lan Settings/
Proxy Server Portion

Once checked, I was able use to Vault flawlessly.

I even restored the usesystemdefault="true" in both config files and it still worked.

Thanks for all your help!

P.S. Unless your app starts popping up webpages like "spyware is on your machine" or "guaranteed <ADVERTISEMENT SPAM>", I won't insist that Adsubtract work with Vault

[dan]

P.S. Unless your app starts popping up webpages like "spyware is on your machine" or "guaranteed <ADVERTISEMENT SPAM>", I won't insist that Adsubtract work with Vault

Actually, we were just thinking that the "<ADVERTISEMENT SPAM> market" would have good synergy with source control tools. I guess we'll put that on the back burner for now

[ray023]

One final note:
After a reboot, adsubtract would deselect the Bypass Proxy option.

So, I did what Jeremy had mentioned earlier:
added the IP address and machinename to the "bypass list" that's located here:
Tools/Internet Options/Connections/Lan Settings/Advanced

There's a textbox at the bottom where you can put "Exceptions".

I had to do this while adsubtract in memory, add the exceptions, then unload adsubtract and reboot. Very strange, but it's working.

Besides the trouble it's caused here, believe it or not, it's a decent app.