Hello Martin, I've filed PG-1422 to stop ProGet from checking whether anonymous users have any feeds they can access. You may also want to check in SSMS whether any of the indexes need to be rebuilt or reorganized.

We recommend usign the drop folder (step #3) instead, but this could work when the "package clean-up" task runs, because it will reconcile database and disk package data.

Just discovered Kevin's answer here which should work: http://inedo.com/support/questions/4058#inline-post-5062

This was indeed removed from v5 for a variety of reasons, but we do plan to bring it back. It was very problematic to display this information on the web after connecting to it from an agent, etc.

Please refer to the High-level Architecture Diagram to see the components of a ProGet installation. The Database is a SQL Server database. The Web and Indexing Nodes are both .NET application that interact with the database using the standard SqlClient API. The connection string you specify in the configuration file is assigned to the ConnectionString property of that API. All of this is very standard, but it's very likely that your DBA/Network Admins configured the SQL Server you wanted to use in such a way that a simple/intuitive connection string was not sufficient. Maybe they used a special port, security, etc.; they would be much better suited to answer your question about why it's so complicated :) Also, please note that the ProGet Installer will create/update the tables and object in the database. ProGet itself does not modify (nor have the privileges to modify by default) the database structure. If you wish to install the database component outside of the installer, then you will need to follow the Manual Installation Instructions.

That error message is coming directly from your remote SQL Server, and it can mean several different things: wrong password is specified for sql_tg_proget on that server the tg_proget database does not exist on that server the sql_tg_proget user does not have access to tg_proget on that server SQL Authentication is disabled on that server, or another setting is preventing the application from logging in to the database using that name/password; for security purposes, SQL Server does not log these reasons to the client In this situation, your connection string needs to be modified to either point to the correct server, and/or use the correct username, password, and database, or the sql server needs to be configured to permit that connection string. There is no other configuration required (or even possible) on the application side to connect to the database. Only the connection string.

Thanks for the quick response. Yes, sooner would be great. I will start using the new feature as soon as you can release it, with or without documentation.

If you're able to get it up and running, then we'll definitely support as per usual. Basically we just don't have the knowledge/expertise to help install / set-it up on Azure (we haven't even tried it ourselves). But it should work... they seem to support a lot more parity with regular SQL Server, and a lot of installs are on SQL Azure.

You can move BuildMaster from one server to another using the backup and restore instructions. However, I would suggest using the built-in retention policies to purge old items instead of that script.

Hi Simon, If those buttons aren't lighting up, then the machine doesn't have internet access and can't request a key. Just go to my.inedo.com and request one instead, then enter it in. You don't need to manually install, but FYI that zip file would be in the manual installation package.

Glad to hear it! Thanks for letting us know.

Yes, SQL Server 2014 is supported - I will update that article.

Yes, just edit the connection string in both the web and services directory.

Wanted to follow up on this issue and thank you for the response. We upgraded from 4.1.5 to 4.1.6 and I reran a script that should have failed and it did indeed throw an error. SQL Server Extension was upgraded to 4.1.3.0 and the expected error is thrown. Thanks again. Source and Target directory same; splitting. AgentBasedAction Initialization Complete: Temp Directory: C:\Program Files\BuildMasterAgent_AGTTMP_A4_S0\TMP Source Directory: C:\Program Files\BuildMasterAgent_AGTTMP_A4_S0\SRC Target Directory: C:\Program Files\BuildMasterAgent_AGTTMP_A4_S0\WRK Server: XXXXXXXXXXXXX (Id: 2) Initializing action... Initialization complete. Executing... DB Version: 1 Current Version: 1 Total Scripts in BuildMaster: 8 Scripts Reported Run by Target DB: 10 Determining scripts that need to be run... Scripts to run: 1 Executing FailFailFail The script "FailFailFail" execution failed. SQL Error: Cannot find the object "dbo.KSJHFKSHFKJSSKFLSJKDF" because it does not exist or you do not have permissions. Execution Complete. Execution complete. Finalizing... Target directory unused; joining with source. Finalization complete.