# Has this been tested against a perforce repository
**URL:** https://www.finalbuilder.com/forums/t/has-this-been-tested-against-a-perforce-repository/4823
**Category:** Discussion
**Created:** [April 25, 2012, 12:47pm UTC](https://www.finalbuilder.com/forums/t/has-this-been-tested-against-a-perforce-repository/4823 "2012-04-25T12:47:58Z")
**Posts on this page:** 9
**Page:** 1
### Author:  [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [April 25, 2012, 12:47pm UTC](https://www.finalbuilder.com/forums/t/has-this-been-tested-against-a-perforce-repository/4823/1 "2012-04-25T12:47:58Z")
I already have p4v installed on the system and I am able to populate my work directory. However when I try to set up the New Respository. I get _Validation Error: The property Perforce.Default does not have a value. p4.exe might not be installed. _
A second thought is that I am misunderstanding the Repositories page. Is it only for creating repositories and not for plugging into preexisting ones?
---
### Author:  [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [April 25, 2012, 2:38am UTC](https://www.finalbuilder.com/forums/t/has-this-been-tested-against-a-perforce-repository/4823/2 "2012-04-25T02:38:17Z")
It has been tested, but the validation stuff is new and possibly not quite 100%. We’re doing another review of all the repository types at the moment to make sure everything works as it should. Repositories in continua are for hooking up to existing Version Control repositories.
The error that “Perforce.Default” does not exist suggests the Server Property Collector (property collectors are how we detect the location of tools) did not find the Perforce client on the server. A quick look at the code suggests it’s looking for p4.exe in this order : “%PATH%”, “%PROGRAMFILES%\Perforce\bin”, “%PROGRAMFILES(x86)%\Perforce\bin”
Which version of perforce are you using? I’ll talk to the dev who wrote the perforce code tomorrow (it’s a holiday here today) and see which versions of perforce it was tested with.
---
### Author:  [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [April 25, 2012, 10:53am UTC](https://www.finalbuilder.com/forums/t/has-this-been-tested-against-a-perforce-repository/4823/3 "2012-04-25T10:53:49Z")
The perforce Visual Client version is _Rev.Perforce Visual Client/NTX64/2012.1/442152_ . p4.exe can be found under %PROGRAMFILES%\Perforce. But that location was added to the %PATH%.
---
### Author:  [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [April 26, 2012, 12:00pm UTC](https://www.finalbuilder.com/forums/t/has-this-been-tested-against-a-perforce-repository/4823/4 "2012-04-26T12:00:52Z")
Hmmm… I’m getting the same error message for “Subversion.Default” Which suggests that the problem is something else besides the %PATH%
---
### Author:  [@paulsamways](https://www.finalbuilder.com/forums/u/paulsamways)
#### Post date: [April 26, 2012, 9:01am UTC](https://www.finalbuilder.com/forums/t/has-this-been-tested-against-a-perforce-repository/4823/5 "2012-04-26T09:01:11Z")
Hi,
The path which is used by the Repository plugins is determined by the server side property collectors (Administration -\> Builds -\> Property Collectors). The default property collector for the Perforce had the incorrect path of %PROGRAMFILES%\Perforce, where it should of included the bin directory. We’ve fixed this for the next build, you’ll just need to go update the collector on your server to reference the correct path for Perforce. Same would go for Subversion.
Paul.
---
### Author:  [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [April 30, 2012, 10:24am UTC](https://www.finalbuilder.com/forums/t/has-this-been-tested-against-a-perforce-repository/4823/6 "2012-04-30T10:24:37Z")
Ok. I’ll wait for the next build to continue investigating. Your response is a little confusing. %PROGRAMFILES%\Perforce is the correct location for p4. %PROGRAMFILES%\Perforce\bin is the wrong location.
---
### Author:  [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [May 1, 2012, 12:06pm UTC](https://www.finalbuilder.com/forums/t/has-this-been-tested-against-a-perforce-repository/4823/7 "2012-05-01T12:06:05Z")
The most recent build was last night (234), you can always find the most recent build information pinned at the top of this forum. I think Paul got it backwards in his post, it is checking %PROGRAMFILES%\Perforce in the last few builds we uploaded.
---
### Author:  [@Vincent](https://www.finalbuilder.com/forums/u/Vincent)
#### Post date: [May 1, 2012, 12:10pm UTC](https://www.finalbuilder.com/forums/t/has-this-been-tested-against-a-perforce-repository/4823/8 "2012-05-01T12:10:29Z")
I forgot to mention, before you update, go to the Admin menu (top right of page, then Builds) and in the property collector section, delete the Perforce property collectors, and then install the update. That will ensure you pick up the changed property collectors (otherwise you will need to edit them).
---
### Author:  [@deleted\_user](https://www.finalbuilder.com/forums/u/deleted_user)
#### Post date: [May 1, 2012, 10:51am UTC](https://www.finalbuilder.com/forums/t/has-this-been-tested-against-a-perforce-repository/4823/9 "2012-05-01T10:51:20Z")
Not sure if this has changed in the next build. But looking at the property collector section. I noticed why subversion isn’t working. You are looking under Program files(x86) yet I’m using the 64-bit version of TortoiseSVN. Note: TortoiseSVN now comes with the svn command line tools.