Vault gives "Input string not in correct format" o

[djkunkel]

Hello,

We are evaluating your fine product, but we are having an issue with two of our developer machines (out of 5). The other machines work perfectly and we have successfully used the repositories we've created.

There is nothing in the server log (even with debug logging on) except for a login and logout message (so I know it is connecting in some respect) for the same second. No error message is recorded in ...\Localsettings\Temp\VaultGUIClient.txt for the current user either.

All client machines are XP Pro SP2. We are running client 4.0.4 (15848) and server 4.0.4.15848 running on IIS 5.0 W2K with SQL Server 2005.

When logging in using the GUI tool we get the error message right after clicking OK on the "Connect to server" dialog:

Input string was not in a correct format.

Using the command line tool we got a slightly more informative error message:
vault GET -host XXXXXXXXXX -user kunkedj -password simple -repository "Main" "$\command\cal.txt"

System.Exception: The connection to the server failed: server can
not be contacted or uses a protocol that is not supported by this client. Input
string was not in a correct format. ---> System.FormatException: Input string
was not in a correct format.
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffe
r& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseInt32(String s, NumberStyles style, NumberFormatInfo in
fo)
at VaultClientOperationsLib.UserOptionsCollection.GetOptionAsInt(String optio
nName)
at VaultClientOperationsLib.ClientInstance.UpdateWorkingFolderOptionsFromUser
Options()
at VaultClientOperationsLib.ClientInstance.Login(String urlbase, String usern
ame, String password)
at VaultClientIntegrationLib.ServerOperations.Login(AccessLevelType altComman
d, Boolean bAllowAuto, Boolean bSaveSession)
--- End of inner exception stack trace ---
at VaultClientIntegrationLib.ServerOperations.Login(AccessLevelType altComman
d, Boolean bAllowAuto, Boolean bSaveSession)
at VaultClientIntegrationLib.ServerOperations.Login()
at VaultCmdLineClient.VaultCmdLineClient.ProcessCommand(Args curArg)
at VaultCmdLineClient.VaultCmdLineClient.Main(String[] args)

Note: This command line works fine for the 3 machines that aren't experiencing this issue.

Do you have any suggestions? I've tried everything I can think of.

Thanks for your time.

[Beth]

uses a protocol that is not supported by this client

That would tell me that the client is a different version. Check to see if the clients and the server are the same version.

Also, debug logging doesn't start until an iisreset is performed.

[djkunkel]

That sounds reasonable, except I downloaded the client once and installed the same msi file on each machine. They are certainly the same release.

I noticed that the inner exception is from a string to int conversion function of the UpdateWorkingFolderOptionsFromUser
Options() method of ClientInstance from one of you libraries.

I did performed an iisreset. Things certainly got more verbose in the error log, but no detail between the login - logout for the non-working machines.

I've also tried reinstalling vault on both machines.

I replaced the host name and ip in the log excerpt below.

----8/31/2007 11:14:34 AM beccin--(host name removed)--SSL Disabled Beginning SQL transaction 54881489
----8/31/2007 11:14:34 AM beccin--(host name removed)--SSL Disabled SQL transaction 54881489 successfully committed.
----8/31/2007 11:14:34 AM beccin--(host name removed)--SSL Disabled Login
----8/31/2007 11:14:34 AM beccin--(host name removed)--SSL Disabled GetUserOptions returned: Success
----8/31/2007 11:14:34 AM beccin--(host name removed)--SSL Disabled Logout
----8/31/2007 11:14:34 AM --()-- Beginning SQL transaction 39086322
----8/31/2007 11:14:34 AM --()-- SQL transaction 39086322 successfully committed.
----8/31/2007 11:14:34 AM --()-- Beginning SQL transaction 45653674
----8/31/2007 11:14:34 AM --()-- SQL transaction 45653674 successfully committed.

[Beth]

You are still getting the same error message?

"The input string is not in the correct format" tells me the server can't understand what the client is sending it.

What is the OS the client is on? Do you know which .NET frameworks you have installed?

Are you able to open the Vault GUI without logging in (just hit cancel) and then go to Help - Technical Support and copy the information from there to me?

What might also help is if you can go to a client that is working, open the Vault GUI, connect and select a repository, and select Help - Technical Support and provide that information too. That will provide me with the information on a working client plus the server environment information.

[djkunkel]

From a machine that works:

Client Information
Vault Client Version: 4.0.4.15848
.Net Framework Version: 2.0.50727.832
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 2 GB
Time Zone: (GMT-06:00) Central Time (US & Canada)

Server Information
Server version information unavailable

License Information
License information unavailable

Another machine that works:

Client Information
Vault Client Version: 4.0.4.15848
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 1021.54 MB
Time Zone: (GMT-06:00) Central Time (US & Canada)

Server Information
Vault Server Version: 4.0.4.15848
.Net Framework Version: 2.0.50727.42
Operating System: Microsoft Windows 2000 Server
Service Pack: 4.0
OS Version: 5.0.2195
Timezone: (GMT-06:00) Central Time (US & Canada)
SQL Version: Microsoft SQL Server 2005 - 9.00.3042.00 (Intel X86)
Feb 9 2007 22:47:07
Copyright (c) 1988-2005 Microsoft Corporation
Standard Edition on Windows NT 5.0 (Build 2195: Service Pack 4)

License Information
1 serial number(s):
1 of 1: 10 full users, expiring 9/28/2007

From one of the non-working machines:

Client Information
Vault Client Version: 4.0.4.15848
.Net Framework Version: 2.0.50727.832
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 2 GB
Time Zone: (GMT-06:00) Central Time (US & Canada)

Server Information
Server version information unavailable

License Information
License information unavailable

All the working machines have .NET 1.1 and 2.0 installed. My machine (that works) has .NET 3.0 as well. The non-working machines have 1.1, 2.0 and 3.0.

I've tried restarting one of the non-working machines in safe-mode with networking support and got the same message.

[djkunkel]

I've used Charles (www.xk72.com/charles) the web debugging proxy on one of the non working machines. I've attached the requests and responses that occur on that machine. I noticed on one request (labeled 4 in the attachment), the server returns a FailInvalidSessionToken message.

[Beth]

I know that error you received means something if it's received by the Vault server log and it would point to IIS.

I'm going to have you try one more time reinstalling the .NET framework on your client, but do it the way I do to see if that helps.

Open a command prompt and change directories to C:\WINDOWS\Microsoft.NET\Framework\v2.0......(whatever those numbers may be). Then run the command:

Code: Select all

aspnet_regiis.exe -u

When that completes run:

Code: Select all

aspnet_regiis.exe -i

[djkunkel]

I'll assume you want me to reinstall ASP.NET on the server machine, since the clients don't have IIS installed.

I'll have to wait until there is a good time to bring all of our ASP.NET 2.0 applications down.

In the meantime, I'm going to try to run a vault server on my development machine and connect to it from these failing clients and see if something different happens.

[Beth]

Well, I meant on a client. I just checked with one of my clients that I don't think has IIS and it still has that command for uninstalling and reinstalling the .NET framework. Just try it on the client, not on the server.

If that doesn't work then I'm going to have you try adding a line to your VaultGUIClient.exe.config. Between the following tags:

<system.net>
<defaultProxy>

Add the following:

<settings>
<httpWebRequest useUnsafeHeaderParsing="true" />
</settings>

More information about what that does can be found here: http://www.west-wind.com/WebLog/posts/39679.aspx

[djkunkel]

I've narrowed down the problem further. I get the same message even with my development server as a Vault server.

I also get the message when connecting to:
vaultdemo.sourcegear.com

Only the computer's primary user get this issue. When I log into the machine, the error doesn't happen. We are both members of the local Administrator group on the machine and there are no processes that load differently as far as I can tell (startup group, user's Run key in the registry).

What I really would like to know is what could cause the server to send back that FailInvalidSessionToken message (from the log I attached) so that I can fix whatever discrepancy exists for these users.

[djkunkel]

In response to your message Beth about aspnet_regiis:

I did run it on the client machine. The -u command throws an error that IIS is not installed.

-i works, but no change in the error message.

I believe that the aspnet_regiis only installs the ASP.NET components into IIS.

[Beth]

Did you get a chance to check the second suggestion?

[djkunkel]

Yes, the useUnsafeHeaderParsing had no effect on the error message.

[Beth]

Can I get a full Vault Server Log? You can either post that here or email it to support at sourcegear.com (attn: Beth).

Also, can you place the server in Debug mode? That is done in the Admin web page. You will need to perform an iisreset after that change.

Can you turn on client side logging on the problem clients? Information on how to do that can be found here: http://support.sourcegear.com/viewtopic.php?p=5375. Just start the Windows Forms Client logging.

[djkunkel]

I have done as you asked and posted the files as attachments.

By the way, thank you so much for being patient and responsive.