Vault 4.1.1 Error

AOverton · Post by **AOverton** » Wed May 14, 2008 4:57 pm

I recently installed 4.1.1 Client, and in trying to connect to my server I get an error message saying "Input string was not in a correct format". I get this even trying to login as the admin user. Can anyone give me a clue as to what this means?

Many thanks!

Beth · Post by **Beth** » Thu May 15, 2008 12:27 pm

Can you check your Vault Server Log to see if anything was logged there?

Also, did anything show up in either the client or server Event Viewer logs?

AOverton · Post by **AOverton** » Thu May 15, 2008 12:36 pm

Nothing shows up on the client, but there are entries on the server of successful logins and logouts. Nothing about the error I'm receiving on one of the clients though.

Thanks for your response.

Beth · Post by **Beth** » Thu May 15, 2008 1:20 pm

Could you open a client, client cancel to not connect to a server, then press Ctrl-Alt-Shift-F12 to start client-side logging? At the bottom of the window, it will give you the path to the log. Then try the action again and check the log for errors.

AOverton · Post by **AOverton** » Thu May 15, 2008 1:39 pm

Ok, that created a log of the error. Here's what it says for my latest login attempt:

5/15/2008 12:33:52 PM <generic>: [GUIClientWorkerThread:4920] [System.FormatException: Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at VaultClientOperationsLib.LocalSettings.GetInt(String key)
at VaultClientPresentationLib.GUIClientInstance.ConnectToServer(String& outserverPath, Boolean forceDialogShow, String& outprofileName, String& outusername, Boolean& outbUseSSL, Boolean& outbAutoLogin)
at VaultClientPresentationLib.GUIClientThread.ProcessCommand(GUIClientThreadCommand command, GUIClientThreadCommandResult& outputResult)]Input string was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo info)
at VaultClientOperationsLib.LocalSettings.GetInt(String key)
at VaultClientPresentationLib.GUIClientInstance.ConnectToServer(String& outserverPath, Boolean forceDialogShow, String& outprofileName, String& outusername, Boolean& outbUseSSL, Boolean& outbAutoLogin)
at VaultClientPresentationLib.GUIClientThread.ProcessCommand(GUIClientThreadCommand command, GUIClientThreadCommandResult& outputResult)

Stack Trace:
at VaultClientPresentationLib.GUIClientInstance.ShowCommandException(Exception e, IWin32Window dialogOwner)
at VaultClientPresentationLib.GUIClientThread.ProcessCommand(GUIClientThreadCommand command, GUIClientThreadCommandResult& outputResult)
at VaultClientPresentationLib.GUIClientThread.Start()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

Beth · Post by **Beth** » Thu May 15, 2008 4:15 pm

Does it make a difference whether you are using the machine name or an IP address?

AOverton · Post by **AOverton** » Thu May 15, 2008 4:21 pm

No, I tried both and get the same error. I've even re-installed Vault 4.1.1 to no avail. It worked with earlier trial version (4.0.6 I believe) I was using, but not since I've upgraded to new version.

Beth · Post by **Beth** » Mon May 19, 2008 12:39 pm

Was everyone else able to upgrade ok?

Let's try the following:

First, close Vault and Visual Studio.

Run regedit. Then go to this area: HKEY_CURRENT_USER\Software\SourceGear\Fortress\Client\Settings. You are going to delete everything in the settings folder there. Close regedit.

Run Vault and let me know the results.

AOverton · Post by **AOverton** » Tue May 20, 2008 11:24 am

Yes, other team members have been able to upgrade and connect successfully.

I removed the registry entries, and still get the same error message. I even uninstalled and removed all registry entries, and was still unable to connect.

Beth · Post by **Beth** » Tue May 20, 2008 1:45 pm

What is the OS of the machine you have the client installed on?

Can you look in your cache area, %username%/local settings/application data/SourceGear/Vault_1/Client and see if you have a settings.xml file?

AOverton · Post by **AOverton** » Tue May 20, 2008 4:53 pm

Windows XP Profession Version 5.1(Build 2600.xpsp_sp2_gdr.070227-2254 : Service Pack 2)

There is only a file named Profiles in the cache area. settings.xml file doesn't exist.

Beth · Post by **Beth** » Wed May 21, 2008 10:41 am

Can you send an email to support at sourcegear.com (attn: Beth) with a link to this thread? I think I need to take a closer look to see what's going on.