I believe TeamCity requires that the APIkey is passed in, regardless of if the feed requires it or not. You can just use name:pass as the api key in this case.

Can you be more specific? What do you mean by, "entire database"? The built-in Change Scripts feature will allow you to script an entire database if needed, and ensure change scripts get run once and only once.

Oddly, running the service in interactive mode seems to have solved the problem: the deployment is now complete. I didn't do anything but stop the service and start it interactively, and I didn't notice anything unusual in the output. It did look like it found the action and ran it, as far as I can tell, but didn't say what had been in the way.

Issue #21 opened in Github. Thanks for the comments!

In this case, it sounds like the service account has some sort of enumeration problem with groups. This is not uncommon. As a test, i would suggestto run the ProGet webapp (either in IIS or the hosted web service) with your domain account. And of course, if you do find out specifically what caused this from the groups/permissions side of things, an update would most certainly be appreciated :)

Hi Tod Sorry for that, these are the correct images: ProGet browser https://www.dropbox.com/s/lp00uc995s3h5rl/2014-07-10 15_28_09-GamePlay 2.0.23.png Nuget Package Explorer https://www.dropbox.com/s/ev7bteduhh7hkb3/2014-07-10 17_44_31-NuGet Package Explorer_GamePlay.2.0.23.png The request from Nuget Explorer fails and I assume the same thing happens with the Nuget Package Manager in Visual Studio: Request: GET http://srvsedevtfs01:81/nuget/default/FindPackagesById()?$orderby=Published%20desc&$select=Id,Version,Authors,DownloadCount,VersionDownloadCount,PackageHash,PackageSize,Published&id='XXXXXX.XXXXXX.XXXXXX.GamePlay' HTTP/1.1 DataServiceVersion: 2.0;NetFx MaxDataServiceVersion: 2.0;NetFx User-Agent: NuGet Package Explorer/3.8.0.0 (Microsoft Windows NT 6.1.7601 Service Pack 1) Accept: application/atom+xml,application/xml Accept-Charset: UTF-8 Host: srvsedevtfs01:81 Accept-Encoding: gzip, deflate Response: HTTP/1.1 404 Not Found Cache-Control: private Content-Length: 6505 Content-Type: text/html; charset=utf-8 Server: Microsoft-HTTPAPI/2.0 X-AspNet-Version: 4.0.30319 X-UA-Compatible: IE=edge Date: Fri, 11 Jul 2014 14:30:39 GMT <h1> Request handler not found (404) </h1> <div class="subH1"> An unexpected error has occured while processing your request. </div> <h2>Error Details:</h2> <div style="overflow: auto; height: 100px; border: 1px dotted #A00; padding: 10px; color: #A00;"> /nuget/default/FindPackagesById()?$orderby=Published%20desc&amp;$select=Id,Version,Authors,DownloadCount,VersionDownloadCount,PackageHash,PackageSize,Published&amp;id=&#39;XXXXXX.XXXXXX.XXXXXX.GamePlay&#39; does not map to any handlers. The URL may have been entered incorrectly or linked to from an old reference. </div> <h2>Why am I seeing this page?</h2> <p> You were taken to this page because ProGet encountered an error without a specific or known resolution. </p> <h2>What else can I do about this?</h2> <p> Hopefully the error message above is helpful in determining what went wrong. </p>

Not possible currently, but something we could definitely add - I'll put an issue in for this.

Only the single agent port is required to be open. As a workaround, if you have BuildMaster database access, you can just set the status of the particular server to FORCE. If you have a custom extension, you could write a quick custom recipe that can do it as well - just implement the IServerRecipe interface for a RecipeBase object. You can find out how this works in the Creating an Auto-Deploying Custom Extension Application tutorial which contains a downloadable example project containing example recipe code.

You could try calling the stored procedure directly via the SQL API: DECLARE @B VARBINARY(MAX) SET @B = CAST('yourname' AS VARBINARY) SET CONTEXT_INFO @B EXEC Applications_PurgeApplicationData @Application_Id or view it in SSMS to see the actual SQL.

This is a known issue (BM-1546) for BuildMaster v4.3.8 and will be resolved in v4.3.9.

Thanks for this! We also use ProGet for internal assemblies and having symbols readily available through the NuGet package saved me from having to hack something together so we could have easy access to the PDBs.

You can also get this error if you do not supply a valid private key passphrase for the private key.

Were there any error messages before this happened? Either way, I would restart the BuildMaster service and web application. It also may be worth upgrading to the newest version to see if that helps.

Hi Tod, We upgraded from an older version, 3.6 to 4.3.8. The feature "Update Checklist" is a nice one and at the moment "all green". Execpt for one issue, the "Test your deployment plans". On our server we are running TFS 2010, version 10.0.30319.317. In Buildmaster we added the TFS2012 extension. Regarding your last remark "connections to TFS are now made by the BuildMaster service instead of the web application", do you mean by this that the "service-user"should have acces now to TFS ? Kind regards Martin

You'd have to disable the custom errors in all settings, but regardless, we believe the problem was that the clone procedure would fail if the database user did not have ALTER permissions on a certain table (don't worry, we weren't doing anything crazy -- just an identity insert). We've reworked them so that this is no longer a requirement. We'll have a maintenance release out today that should resolve it.

I can't seem to repro this - if I specify an API key for the feed that requires one, I get this error message: Failed to process request. 'There was an error processing the request: You are not authorized to add a package to this feed. By default, ProGet is not configured to allow unauthenticated users to publish packages to a feed. You will need to either authenticate (by using "name:pass" as your API Key) or give the Anonymous User the Feeds_AddPackage privilege.'. If I then use Admin:Admin or allow anonymous users to publish, then it works as expected. Did you change the Admin user's password by chance?

At the moment the MsTest extension requires a test file be specified. However, we do have the code public for this extension: https://github.com/inedo/bmx-mstest If you're interested modifying the extension quicker than we can, check out: http://inedo.com/support/tutorials/cloning-and-patching-an-inedo-extension As for email, that might require more customization. You can instead have users sign up for the "Execution Completed" notifier which will link them to the test results.

If you wrap the first package query in parentheses it should work: http://proget-server/nuget/{feedName}/Packages?$filter=(Id eq 'ProjectName.Deploy') and startswith(Version,'1.0')&$top=1&$orderby=Created desc

Unfortunately that is a limitation of the v3.X line of BuildMaster - releases were ordered and meant to be built on top of each other, e.g. once version 5 goes out, it is meant to encompass everything up through v5. If you were to upgrade to the 4.X line (make sure to read all the upgrade notes first), then you can actually re-order releases as necessary, and allow other advanced workflow options.

Fixed! The issue was that the subversion configuration was pointing to its local svn.exe instead of the one we had installed on the server. I had to change the 'Path to svn client' field to point to our copy of svn.exe. Thanks again.