Login Failure with Fortress 1.1.2 and CruiseControl.NET 1.4

[obrion]

I have just converted from using SourceSafe to using Fortress as our source control repository (what a blessing!). Now I am trying to update our automated builds to use Fortress, but I have run into a difficulty. I downloaded the current CruiseControl.NET plugins and followed the directions in the supplied readme, which basically means I copied the DLLs into the CruiseControl.NET server directory and updated the ccnet.config file to try to use vaultplugin instead of the previous vss provider. When I try to force the build, I end up with the following failures in the ccnet log:

2008-07-30 12:30:06,519 [Netclient-Fortress-CI:DEBUG] In FortressVaultSourceControl.GetModifications()
2008-07-30 12:30:15,536 [Netclient-Fortress-CI:ERROR] Vault Login Failed: The server uses a protocol that is not supported by this client.
2008-07-30 12:30:15,536 [Netclient-Fortress-CI:INFO] No modifications detected.
2008-07-30 12:30:15,536 [Netclient-Fortress-CI:INFO] Building: Dashboard triggered a build (ForceBuild)
2008-07-30 12:30:15,536 [Netclient-Fortress-CI:DEBUG] In FortressVaultSourceControl.GetSource()
2008-07-30 12:30:24,553 [Netclient-Fortress-CI:ERROR] Vault Login Failed: The server uses a protocol that is not supported by this client.

Any suggestions for how I resolve the login errors? I have looked around and cannot find anywhere to configure what protocols are enabled. I must be missing something pretty basic.

Robert O'Brion
AT&T

[shannon]

Did you specify vaultplugin or fortressplugin in your config file?

[obrion]

I specified vaultplugin. I just switched it to "fortressplugin" (would seem to make sense). It looks like the login was now successful:

2008-07-30 12:49:02,140 [Netclient-Fortress-CI:INFO] Project: 'Netclient-Fortress-CI' is first in queue: 'Netclient-CI' and shall start integration.
2008-07-30 12:49:02,140 [Netclient-Fortress-CI:DEBUG] In FortressVaultSourceControl.GetModifications()
2008-07-30 12:49:02,200 [Netclient-Fortress-CI:DEBUG] Refresh() successful.
2008-07-30 12:49:02,200 [Netclient-Fortress-CI:DEBUG] Current folder version is 98. Last integrated folder version was 98.
2008-07-30 12:49:02,200 [Netclient-Fortress-CI:INFO] [$/v7/current] has not changed.
2008-07-30 12:49:02,200 [Netclient-Fortress-CI:INFO] No modifications detected.
2008-07-30 12:49:02,200 [Netclient-Fortress-CI:INFO] Building: Dashboard triggered a build (ForceBuild)
2008-07-30 12:49:02,200 [Netclient-Fortress-CI:DEBUG] In FortressVaultSourceControl.GetSource()
2008-07-30 12:49:02,206 [Netclient-Fortress-CI:INFO] Getting source from Fortress

But I got the following exception when it was trying to get the source, and no source was retrieved from the repository:

VaultClientOperationsLib.GetLatestVersionFailedException: Exception of type 'VaultClientOperationsLib.GetLatestVersionFailedException' was thrown.
at VaultClientOperationsLib.ClientInstance.ProcessGetFileRequests(GetFileInfo[] infos, MakeWritableType makeWritable, SetFileTimeType setFileTime, MergeType merge, Boolean updateHiddenFilesOnly, String ancestorFullPath, Boolean flat, String ancestorDiskPath, OverwritePrompt PromptData, Boolean isLabelGet, String currentPathToLabelItem, Int64 labelID, Boolean isRetry, Boolean isGetByDisplayVersion)
at VaultClientOperationsLib.ClientInstance.Get(VaultClientFolder[] folders, Boolean forceLatest, MakeWritableType makeWritable, SetFileTimeType setFileTime, MergeType merge, OverwritePrompt PromptData)
at VaultClientOperationsLib.ClientInstance.Get(VaultClientFolder folder, Boolean recursive, Boolean forceLatest, MakeWritableType makeWritable, SetFileTimeType setFileTime, MergeType merge, OverwritePrompt PromptData)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.FortressClient.GetVersion(String repositoryFolderPath, String workingDir, Int64 folderVersion)
at ThoughtWorks.CruiseControl.Core.Sourcecontrol.FortressVaultSourceControl.GetSource(IIntegrationResult result)
at ThoughtWorks.CruiseControl.Core.IntegrationRunner.Build(IIntegrationResult result)

Any further suggestions? I looked at the fortress log since I had set it to debug and it looks like the requests were being processed, but no files on the build server. Maybe a permissions issue on the file system somehwere?

Robert

[shannon]

I think you've hit a bug that's been fixed for the 1.1.3 release. If you'd like a pre-release build with the fixes send me an email at shannon at sourcegear dot com and I can give you a link to download that.