Error ... "Input string was not in a correct format."

[franksmall]

After changing user profiles in windows XP we are now getting the error "Input string was not in a correct format." when connecting to Vault using Vault Client. Vault version 4.1.4 build 18402

[Beth]

What exactly was changed when you say you changed user profiles?

A user's client-side cache is stored in their local profile.

How far do you get on the login? By that, I mean does the failure occur as soon as the user tried opening the client, or after they click login, or after they select the repository to connect to?

Also, are you using Active Directory authentication with Vault?

[franksmall]

A new account was setup in Active Directory for each of our users that had a generic named account. (We went from generic logins to named account logins ...). This was the only change in AD. Each new account was added to the local administrors group so that the new user would have admin rights on his/her box. Nothing else was changed locally.

We are NOT using AD authentication in Vault.

When opening up Vault Client the login box appears ... after entering information ... immediately after clicking Ok a error dialog opens up with one sentence ... "Input string was not in a correct format.". No repository information is displayed ... it does not get that far.

I verified that the users could get to the vault service ... http://ncit/vaultservice/vaultservice.asmx. They could get to the web service in Internet Explorer.

If the users log in with their old profile they can connect normally to vault. Everything works as expected.

[Beth]

Would it be possible for you to post the entire error?

Also, can you look inside your Vault Server Log to see if an error is posted there at the same time?

[franksmall]

The error is ... "Input string was not in a correct format." ... I'll look for the server error log now ..

[Beth]

I tried to reproduce the issue, but it wouldn't do the same thing for me. I suspect that it might be trying to access the old cache location.

What I think might help here is to uninstall the client, backup the registry, search through the registry for SourceGear and remove any remaining entries, and remove any cache remnants under %USERPROFILE%\Local Settings\Application Data\SourceGear\ (if on XP) or %USERPROFILE%\\AppData\Local\Sourcegear (if on Vista). Make sure to clear out the cache for the OLD user profile. Once the machine is clear, install the Vault client while logged in as the new user profile.

[franksmall]

Thanks Beth ... we will give it a try.

[Beth]

Let me know your results. I'm working on putting together a virtual AD domain so I can try this again, but it will take me a little time.

[franksmall]

Beth ... I finally got the bottom of the issue. It turns out that our Network Administrator took it on himself to use "Altiris PC Transplant" to migrate the profiles. It turns out that by re-creating the profile manually we have no issues connecting to Vault. Only AFTER running Altiris did the issue show up. I am afraid to recommend to my team to start deleting things out the registry or profile as that has a very bad down side should the wrong thing be deleted!

[Beth]

I'm happy you found the issue. I wouldn't have guessed a profile migration product. Also, I understand being hesitant about the registry, which is why I suggested a backup, but I'm happier that route wasn't needed.