I'm afraid you can't use Integrated Authentication with Docker.

The client simply doesn't support it, which means IIS will always challenge with 401 prompts. A work-around to this is to set up a separate IIS Site (pointing to same directory) that doesn't have integrated auth configured.

Batch files need to be executed by "cmd.exe". Instead, you can directly execute a ".cmd" file.

There's really no difference between the versions as far as performance is concerned.

At first, try to determine why it's slow; a very common cause is connectors are broken or slow. Disable those, and see if it helps.

Try to see what queries are slow. API vs WebPages, search, etc. That will start clueing into the next area to look.

If you can share more data as what you find, we can provide more specific advice on where to look

Sorry, I misunderstood it myself and responded too quickly.

You're right, the OtterConfiguration_Key points to a DSC Property. It's not an alias, like I had assumed. But looking closer, I see that it is.

It seems this would require a feature/change request to fix; might not be so bad, but I'm not familiar enough w/ it to be certain.

If you're finding that you're having trouble with specific versions, please provide a detailed reproduction case with a specific package, and the specific steps you took; this way we can investigate it.

We do not provide a migration utility or tool, but if you create one we would be happy to share it with the community.

This is not a known issue, and is unrelated to the upgrade, the v3 url, etc. So, it must be some problem on your server with being able to connect to nuget.org

See: https://inedo.com/support/tutorials/proget/getting-started-with-nuget-feeds-in-proget-and-visual-studio

You should really be using the Ensure-RegistryValue operations for this, because it will do the exact same thing while being easier to maintain and visualize.

The Otter_ConfigurationKey must be unique per configurable item on the server. So, in this case, you should make a string based on the registry key+value. You can use the full key+value, or perhaps something like this:

PSDsc Registry
(
  Otter_ConfigurationKey: SecurityZones3_2100,
  Key : "HKLM:\SOFTWARE\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\Zones\3",

  ValueName : "2100",
  ValueType : 'Dword',
  ValueData : "3"
);

I totally agree! Thanks for pointing this out.

I've filed this is a bug report (OT-254), so it will get fixed in a future maintenance release

You can use $PSEval for this pretty easily:

set $a = 2;
set $b = 3;
set $c = $PSEval($a + $b);

You can do this with default values.

template Check_Version<$App, $Role=default>
{

}

And then test if it's the default value to see if it wasn't passed in

Soon --- this is a known issue, but we are in the process of resolving it; please see InedoCore#96

This is a known issue, but we are in the process of resolving it; please see InedoCore#96

At this time, the only thing we're aware of that can cause "Could not resolve function" is that the function has not been loaded by the service. Functions are stored in extensions, and Split is stored in Inedo Core extension, so this would actually cause all sorts of errors.

I created an issue (BM-3255) to give a warning if this extension is not loaded. But please restart the service, check for extension load errors in the message center, and try again.

Restarting the service would be the only way to resolve this, since extensions are loaded at service start.

The error message is coming from within the network stack inside of ASP.NET's hosting components, and errors like this tend to indicate problematic underlying infrastructure, such as drivers, hardware/memory. They are often quite rare and not reproducible, and thus can be difficult to diagnose or debug.

The Integrated Web Server was not designed to handle problematic infrastructure, and as such will simply crash when receiving certain "impossible" scenarios from the network stack. Certain errors are not safe to try/catch (because they imply a corrupt process memory state), which is why they are done.

If you are finding "service autorecovery" not enough, then you should switch to IIS hosting. IIS is very robust, and uses a worker process model and can handle a lot of these underlying problems. When a worker process crashes (which it will do in the same scenario -- unsafe exceptions), IIS will spin up a new one almost instantly.

This was a result of a imcompatable script with 2005, but it has been fixed as of 5.1.11. We are also displaying warning if you're using unsupported version of SQL

We are only aware of that message occurring in the two cases I mentioned, and haven't had reports of the contrary. From here, please use a tool like Fiddler or Wireshark to identify the exact request/response patterns that are happening. You can see the authentication headers sent, and it's possible there's a typo or something in a name or password.

We take problems very seriously, but we need to prioritize where to spend engineering resources tracking down problems. This was a edge case that we could not reproduce, and had a very minor impact, and only affected a very small number of free users with a very specific configuration; a free user was able to track down the underlying cause and we fixed it.

Hi,

the script who is stored in a global module

##AH:UseTextMode
module ParseURL<out $JsonFile>

{

set $URL = $DEPLOYABLE_URL;

set $PATH = $DEPLOYABLE_PATH;

set @MYLIST = @();

Log-Debug Split URL /;

foreach $DATA in @Split($URL,"/")
{
    # Log-Debug $Data;
    set $DATA = $Trim($DATA);

    if $DATA != ""
    {
        set @MYLIST = @ListInsert(@MYLIST, $DATA);
    }
}

......

Sometimes, it works, but the major part of the time I have the error resumed above.
I found nothing in the diagnostic center et nothing in the event viewer of the widows server.

Does exist other logs somewhere ?

Kind Regards

You can reset the Admin user account password by stopping the ProGet Windows service, then running ProGet.Service.exe and selecting the "ResetAdminPassword" option. Make sure to restart the Windows service when finished.