I'm afraid there's not any further configuration. This will happen on any server, physical or virtual, when the SQL Server cannot be contacted. It's usually related to network connections, or the SQL Server is just totally bogged down from other things. See if rebooting fixed it, that will often help.

Hello Paul Here is the powershell script we are using. It is running from the server as a part of our init server script. We deploy the Otter/BuildMaster Agent and we run the script . Hope this help Regards Philippe Param( [Parameter(Mandatory=$false)] [string]$API = "https://#OTTERHOST#/api", [Parameter(Mandatory=$false)] [string]$SERVEUR = $env:computerName ) #end param # Extract AESKey [xml]$XmlDocument = Get-Content -Path "C:\Program Files\InedoAgent\InedoAgentService.exe.config" $AESKey=($XmlDocument.configuration.appsettings.add | where-object {$_.key -eq "EncryptionKey"}).value # # Grab list of registered server # $URI=$API+"/infrastructure/servers/list" $aListServer=Invoke-RestMethod -Method Post -Uri $URI -Headers @{'X-ApiKey' = '********************'} if ($aListServer.Name -contains $SERVEUR){ # # Mise à jour # $URI=$API+"/infrastructure/servers/update/"+$SERVEUR $body = @{ name="$SERVEUR"; hostname="$SERVEUR"; active=$true; serverType="windows"; port="46336"; encryptionType="AES"; encryptionKey=$AESKey } }else{ # # Creation # $URI=$API+"/infrastructure/servers/create/"+$SERVEUR $body = @{ name="$SERVEUR"; hostname="$SERVEUR"; serverType="windows"; active=$true; drift="automaticallyRemediate"; port="46336"; roles=@("Baseline"); environments=@("Integration"); encryptionType="AES"; encryptionKey=$AESKey } } # # Appel de l'API # Invoke-RestMethod -Method Post -ContentType 'application/json;' -Uri $URI -Body (ConvertTo-Json $body) -Headers @{'X-ApiKey' = '********************'} #

Understood, thanks for the explanation! So this is an issue on the Jetbrains end. We will definitely contact them and see the course of action that's available. Thanks again!

I'm not familiar with Zabbix, but there are two things you can do to check about the status of the components (Database, Web, Service): If the database (SQL Server) wasn't working, or there was a problem with the website configuration, then visiting / will yield a 500 or some other not available message. You can just query the ProGet service run state directly. You could parse the text on the /connectors page or use the native API to get a status of the connectors.

This is by design; it is the responsibility of a package author to license a package, and make sure that it's a standard license. This way, automated licensing monitoring can catch it. However, as you've noticed, this isn't the case for a lot of open source packages. So, in this case, you'll want to use a different workflow. Just create a "approved packages" feed, and promote approved packages into these feeds.

Hi, I have tested with npm and all is working now. Thanks very much. Regards Fabrice

This will be addressed in next maintenance release as PG-1294 . As a workaround, you can access the package directly by version number even without this fix.

Your best way to do this, would be to use the nuget client, and then pull the cached packages to your feed. "Pulling with dependencies" as a feature in ProGet would require implementing every dependency resolution algorithm of every version of every client, including the non-deterministic dependency resolution used by the npm client, and then somehow letting you select the algorithm version and the additional content required by the algorithm (such as .net framework target version).

Hi Paul, Your best bet would probably be to use Role Dependencies - the parent role would ensure that the module is installed: # Parent Role PSEnsure ( Key: InstallDSC, Value: 0, Collect: "if(Get-Module -Name cNtfsAccessControl -List -ErrorAction SilentlyContinue) { exit 0 } else { exit -1 }", Configure: install-module -Name cNtfsAccessControl -Force, UseExitCode: true ); Then, in the dependent role, you can safely use the module: # Dependent Role PSDsc cNtfsAccessControl::cNtfsPermissionsInheritance ( Otter_ConfigurationKey: ApplyPermissions_Key, Path: c:\temp, PreserveInherited: true, Enabled: true ); Note that this usage of Role Dependencies will require Otter 2.0.8 or later. In any case, if you don't want to or can't use Role Dependencies, you can simply put the PSEnsure operation inside an alwaysExecute block. Does this help?

Hello Pedro, Docker feeds appear to have been missed when the api user was added for feed authentication. I've filed PG-1295 to fix that. ProGet 5.1.0 is not released on Docker Hub, but you can build the image locally with this command: docker build -t inedo/proget:5.1.0 --build-arg PROGET_VERSION=5.1.0 github.com/Inedo/proget-docker

unfortunately this bug fix just missed the cut. But we will ship it in the next maintenance release, likely in a couple weeks. It's not scheduled yet.

Hello Great news Best Regards Philippe

Hello Tom and Brett, The endpoint being requested seems simple enough. For example, here's what it requests for -StartWith Inedo.. I've filed PG-1281 to add an implementation of this endpoint.

I can't seem to find any indication that endpoint is part of official NuGet API, but in ProGet if you want a specific file you can query as per this example: http://proget.company.com/package-files/download?packageId={packageId}&version={packageVersion}&feedName={feedName}&path={packageId}.nuspec A live example: https://proget.inedo.com/package-files/download?packageId=InedoLib&version=528.0.0&feedName=ExternalBuild&path=InedoLib.nuspec

I've come across this too... but I'm pretty certain it's not going to possible. In the visual editor, all properties all text boxes that are blank by default (which means, not specified), and any characters in those boxes are always escaped ("" would become "\"\""). I made a variable function called $Empty that just returns "". Maybe I'll submit as a pull request to InedoCore...

Hello Timofey, I've filed PG-1280 to hide the build metadata from NuGet version numbers when they are displayed in titles.

Hi Greg Due to my lack of time, I stop the migration and I am still working with 1.7. Therefore, I will make some test with the new release and let you know what is going on. We are intensively using Otter for deploying and configuring SQL, IIS, File Server, ... and the migration have to be handle carefully. Best regards Philippe

Hello Ludovic, This appears to happen when there is no version of your package tagged as latest. To fix it, click the Edit Details button on the latest version of your package and add a tag named latest (all lower-case). I've filed PG-1279 to fix this happening in the first place.

Hi Dean Thanks for the reply.

We will implement retention policy filtering by version. See the tracking issue here for updates: PG-1278 Hopefully it will be in the official v5.1 release (or soon-after maintenance release) but it may also be there earlier since we are also going to allow pre-release product versions to be downloaded from the Hub installer.