Just installed Vault Client and Vault Admin 2.0.4 (upgraded from 2.0.2) and I am getting the following exception in Vault Admin during loading:
____________________________________________________________
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.ArgumentException: '0' is not a valid value for 'Value'. 'Value' should be between 'Minimum' and 'Maximum'.
at System.Windows.Forms.NumericUpDown.set_Value(Decimal value)
at VaultAdmin.FormMain.CommandDisplayServerOptions()
at VaultAdmin.FormMain.FormMain_Load(Object sender, EventArgs e)
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///c:/windows/microsoft.net/framework/v1.1.4322/mscorlib.dll
----------------------------------------
VaultAdmin
Assembly Version: 2.0.4.2190
Win32 Version: 2.0.4.2190
CodeBase: file:///C:/Program%20Files/SourceGear/Admin%20Tool/VaultAdmin.exe
----------------------------------------
____________________________________________________________
After clicking the "Continue" Button it will continue, but I don't have a good feeling about it.
Regards Ken
Vault Admin 2.0.4 throughs an exception
Moderator: SourceGear
-
Guest
Thanks for the report.
I believe what you are seeing happens if the DelayThreshold or DelayDurationSeconds values are not greater than zero.
If you look in your vault.config file (which is in your VaultService folder)
are the <DelayThreshold> and <DelayDurationSeconds> elements listed? If so, make sure the values for both are greater than zero.
If those elements do not exist for some reason (the server *should* put them there if they are not there) add the following elements to the vault.config file (these are default values).
<DelayThreshold>10</DelayThreshold>
<DelayDurationSeconds>30</DelayDurationSeconds>
The DelayThreshold is the number of login attempts a user gets before the user gets "cut off". The DelayDurationSeconds is the number of seconds after the failed attempts before the user can log in again.
I have logged this as a bug.
Mary Jo Skrobul
SourceGear LLC
I believe what you are seeing happens if the DelayThreshold or DelayDurationSeconds values are not greater than zero.
If you look in your vault.config file (which is in your VaultService folder)
are the <DelayThreshold> and <DelayDurationSeconds> elements listed? If so, make sure the values for both are greater than zero.
If those elements do not exist for some reason (the server *should* put them there if they are not there) add the following elements to the vault.config file (these are default values).
<DelayThreshold>10</DelayThreshold>
<DelayDurationSeconds>30</DelayDurationSeconds>
The DelayThreshold is the number of login attempts a user gets before the user gets "cut off". The DelayDurationSeconds is the number of seconds after the failed attempts before the user can log in again.
I have logged this as a bug.
Mary Jo Skrobul
SourceGear LLC
-
Ken Schreck
Vault Admin 2.0.4 throughs an exception
Hi Mary,
I guess you refer to the file called: VaultAdmin.exe.Config. Here is my original file:
____________________________________________________________
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.net>
<defaultProxy>
<!--
The following entry enables reading of the per user (LAN) Internet settings.
Adding additional proxy settings, without first setting to "false",
will individually override. Note that "Automatic configuration" and
"automatic configuration scripts" cannot be read.
<proxy> settings:
usesystemdefault="[true|false]" - Read settings from Internet Options (see above)
proxyaddress="[string]" - A Uri string of the proxy server to use.
bypassonlocal="[true|false]" - Enables bypassing of the proxy for local resources.
-->
<proxy usesystemdefault="true"/>
<!--<proxy usesystemdefault="false" proxyaddress="http://proxyhost:proxyport"
bypassonlocal="false"/> -->
<!-- use this section to disable proxy use for matching servers
example:
<bypasslist>
<add address="bypassRegexString" />
</bypasslist>
-->
</defaultProxy>
</system.net>
</configuration>
___________________________________________________________
Adding the two elements made things only worse. Do you have an example of a default "clean" VaultAdmin.exe.Config ?
Regards Ken
I guess you refer to the file called: VaultAdmin.exe.Config. Here is my original file:
____________________________________________________________
<?xml version="1.0" encoding="utf-8" ?>
<configuration>
<system.net>
<defaultProxy>
<!--
The following entry enables reading of the per user (LAN) Internet settings.
Adding additional proxy settings, without first setting to "false",
will individually override. Note that "Automatic configuration" and
"automatic configuration scripts" cannot be read.
<proxy> settings:
usesystemdefault="[true|false]" - Read settings from Internet Options (see above)
proxyaddress="[string]" - A Uri string of the proxy server to use.
bypassonlocal="[true|false]" - Enables bypassing of the proxy for local resources.
-->
<proxy usesystemdefault="true"/>
<!--<proxy usesystemdefault="false" proxyaddress="http://proxyhost:proxyport"
bypassonlocal="false"/> -->
<!-- use this section to disable proxy use for matching servers
example:
<bypasslist>
<add address="bypassRegexString" />
</bypasslist>
-->
</defaultProxy>
</system.net>
</configuration>
___________________________________________________________
Adding the two elements made things only worse. Do you have an example of a default "clean" VaultAdmin.exe.Config ?
Regards Ken
Sorry if I was unclear in the previous message.
Its not the vaultadminexe.config file that should be changed.
The file that should be changed is a vault.config file in the VaultService directory (the default location is c:\\inetpub\wwwroot\vaultservice\vault.config) on the Vault Server machine.
Its not the vaultadminexe.config file that should be changed.
The file that should be changed is a vault.config file in the VaultService directory (the default location is c:\\inetpub\wwwroot\vaultservice\vault.config) on the Vault Server machine.
Mary Jo Skrobul
SourceGear
SourceGear
-
Ken Schreck