More problems with CruiseControl and Vault

[TimK]

Dhominator,

Do you mean removing the proxy settings from IE?

[Dhominator]

The vault client has proxy settings. Easy way to check is:

• login or runas cmd.exe as the OsUser that runs the build
  run the VaultClientGui
  login as the VaultUser that runs the build
  Tools->Options->Network Settings

In my case I found the proxy set and the build server name won't resolve from the outside world
Shocked

Vault dudes correct me here... To start from a clean slate on the build server I sometimes deleted the SourceGear directory under C:\Documents and Settings\OsUser\Local Settings\Application Data. This, of course, means you'll have to setup working directories, profiles, etc. again.

/jhd

[TimK]

Ok, tried everything you said and...still don't work.

[TimK]

Still cannot get this to work

[jclausius]

TimK:

From a GUI client (on the machine with the failure), connect to the Vault Server. Next run Help->Technical Support. What are the results?

Also, on the machine you successfully configured, was it a domain machine or stand-alone machine? What about your laptop?

[TimK]

My Laptop
Client Information
Vault Client Version: 3.1.7.3719
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft Windows XP Professional
Service Pack: 2.0
OS Version: 5.1.2600
Total Physical Memory: 1023.39 MB
Time Zone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London

Server Information
Vault Server Version: 3.1.7.3719
.Net Framework Version: 1.1.4322.2032
Operating System: Microsoft(R) Windows(R) Server 2003, Standard Edition
Service Pack: 0.0
OS Version: 5.2.3790
Timezone: (GMT) Greenwich Mean Time : Dublin, Edinburgh, Lisbon, London
SQL Version: Microsoft SQL Server 2000 - 8.00.818 (Intel X86)
May 31 2003 16:08:15
Copyright (c) 1988-2003 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: )

License Information
3 serial number(s):
1 of 3: 25 users, permanent
2 of 3: 1 users, permanent
3 of 3: 10 users, permanent
---------------------------------------------------------------------------------
The machine it worked from was a stand-alone W2K3 Server.
My laptop belongs to my company domain.

But - why does my laptop work perfectly when using ccnet.exe (cmd prompt version) but not with the service version running?

[jclausius]

When you configured the CC.Net service, what account did you use? A domain account or local machine account?

[TimK]

Tried both

[jclausius]

The user you used, was it in the Local Administrators or Domain Administrators group?

[TimK]

I used my domain username which is a local admin on the server hosting Vault

[ian_sg]

Tim,

The account running the service on your laptop needs to be an local administrator on your laptop, not on the server.

[TimK]

Hi Ian,

It is.

[TimK]

*** It's all started working ***

Well my laptop died to I needed to reinstall so I put Vault Client 3.5 on and still got the error messages saying "The vault server uses a protocol that is not supported by this client" (the Vault server version was 3.1.7).

I removed v3.5 and put on 3.1.7 and everything worked!

Why?
Are 3.17 and 3.5 client/server communication protocols incompatible?

[jclausius]

Are 3.17 and 3.5 client/server communication protocols incompatible?

Yes. A number of API calls changed so a mixture of Vault 3.5 / Vault 3.1.x is not possible.

[jslew]

Windows services do not have access to the HKCU registry hive, so if per-user settings are required, they need to be gotten from somewhere else when vault is being run from the CCSERVICE, regardless of who the service is set to run as.