Vault on Windows 2003 Server 64bit - when?

[Martin.Vobr]

Hello,
I'm evaluating the Vault and run into problems after installing the Vault server on 64bit Windows 2003 server. When trying to login to webservice the "is not a valid Win32 application. (Exception from HRESULT: 0x800700C1) " error appears.

After searching the support forum I've found, that Vault is not officially supported on 64bit Windows yet. It look like the 64bit support is in the todo list.

Could you please tell me when do you plan to release 64bit enabled version?

[lbauer]

We don't have a definite timeframe just yet -- hopefully some time this summer. We had hoped to include this in Vault 3.5, but found there are a number of configurations we have to account for in the installation. We want to make sure we have tested all scenarios.

[Martin.Vobr]

Thanks for your reply.

[Perry]

What about the Vault GUI client -- is it supported on Windows Server 2003 x64 ?

[lbauer]

No.

Vault is not yet supported on 64-bit Windows operating systems.

However, Vault Server and Client are supported on 64-bit hardware if you are running 32-bit Windows operating systems on the 64-bit machines.

[Tonyb]

I run the valut client in windows XP x64 and don't have any problems at all.

[lbauer]

In some cases a Vault client on a 64-bit OS can work if it's connecting to Vault server on a 32-bit OS. But in our testing, we've run into too many cases where Vault doesn't install properly or the client crashes, etc., so we're not able to support Vault on 64-bit OS's just yet.

[Perry]

Vault IDE client seems to routinely freeze on Windows 2003 x64.

It happens when I alt-tab to it.

Of course, because of the alt-tab bug in Vault IDE client (which I reported elsewhere, and I don't remember if I got any response or timeline on when that might get fixed), it isn't immediately obvious. You alt-tab to the Vault IDE client, and it hangs as usual, but on Windows 2003 x64, sometimes it hangs not just for a while like on other OS, but instead hangs apparently forever.

So it's off to task manager to kill Vault IDE client and restart it.

(I understand that Vault isn't supported on Windows 2003 x64, but I prefer to wait and hope for a port by SourceGear, and struggle by in the meantime with killing & restarting the IDE, than to try to migrate to another product.)

(edited)

[Perry]

Do you have any supported or recommended solutions for customers who have 64-bit operating systems, and have some code in Vault?

(I'm just now busy killing the Vault IDE again, because it hung again.)

[Perry]

The smarter question that I should be asking, probably, is:

Is it safe for me to run the Vault GUI on Windows 2003 x64, and just kill it and restart it when it crashes, as a workaround until Vault supports 64-bit operating systems?

[lbauer]

We wish we had answers for you but until we've thoroughly tested Vault with 64-bit Windows, we just don't have an educated response.

We need to test all the variables, like Vault Clients on 64-bit Windows or 32-bit Windows connecting to Vault Servers on 32-bit Windows or 64-bit Windows, Visual Studio integration with Vault on 64-bit Windows connecting to a Vault Server on 64-bit Windows, etc., etc.

For the present, Vault is not supported on 64-bit Windows or with other 64-bit apps like 64-bit SQL Server 2005. We are testing Vault in all these scenarios, but this is still work in progress.

[Perry]

My small datapoint is unchanged: I've done some simple checkouts, modifications, and checkins, using Vault IDE client on 2003 x64, and the only bug I've seen is that sometimes the Vault IDE hangs (or at least, it gets much slower than it usually is, so slow that I cannot distinguish it from a hang). I kill it with task manager, and restart it. I've not seen any negative effects of this.