Support Q & A Home

Ask A Question

Anyone can ask or answer a question here, but our support engineers actively monitor your questions; we typically answer within a day or two.

Filter
Viewing Page 5 of 128 (20 questions out of 2560)
2
replies

Hi since the 2018-08-04 the UpdateChecker fails with this error in the Executions logs :

INFO: Checking for updates from inedo.com...
ERROR: Error checking for updates: System.Net.WebException: The remote server returned an error: (411) Length Required.
at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at System.Threading.Tasks.TaskFactory1.FromAsyncCoreLogic(IAsyncResult iar, Func2 endFunction, Action1 endAction, Task1 promise, Boolean requiresSynchronization)
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.ScheduledTasks.General.UpdateCheckerScheduledTask.<GetUpdatesXmlAsync>d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.ScheduledTasks.General.UpdateCheckerScheduledTask.<ExecuteAsync>d__1.MoveNext()

Product: ProGet
Version: 5.1.5

4
replies

Hello,

I am using a PSensure to collect the information. I have a map expression configured on the server variable as to to check for disk labels:
%DiskLabel %(C: OSDisk, D: DataDisk1)

And this runs in a role to collect for each server it is assigned to:
##AH:UseTextMode

## Ensure Disk Label configuration
PSEnsure
(
    Key: Disk Label Check,
    Value: True,
    Collect: >>
        $ServerVariable = $DiskLabel
        $Disks = Get-WmiObject -Class Win32_LogicalDisk -Filter "DriveType=3"
        $ServerVariable.GetEnumerator() |ForEach-Object {  if ( ($Disks.DeviceID).Replace(':','') -contains ("$($_.Key)")) { $y = $disks | Where-Object -Property DeviceID -match $_.Key; $y.VolumeName -eq $($_.Value) }}
    >>,
    Configure: >>
        write-output "The fix is in"
    >>
);

But when it collects, even though the values are both true, it reports as drift. Ideas?

Product: Otter
Version: 2.0.10

2
replies

The following error occurrs when I try to run the Software Update Check on a fresh install of ProGet (Server 2016, IIS, SQL Express):

Checking for updates from inedo.com...
Error checking for updates: System.Net.WebException: Der Remoteserver hat einen Fehler zurückgegeben: (411) Länge erforderlich.
 bei System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
 bei System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise, Boolean requiresSynchronization)
— Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde —
 bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
 bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
 bei Inedo.ProGet.ScheduledTasks.General.UpdateCheckerScheduledTask.<GetUpdatesXmlAsync>d__3.MoveNext()
— Ende der Stapelüberwachung vom vorhergehenden Ort, an dem die Ausnahme ausgelöst wurde —
 bei System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
 bei System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
 bei Inedo.ProGet.ScheduledTasks.General.UpdateCheckerScheduledTask.<ExecuteAsync>d__1.MoveNext()

Product: ProGet
Version: 5.1.9

1
replies

I set up a new npm feed in a fresh ProGet installation. When I set the npm registry to that feed and try to install any package, npm is stuck on the "readLocalPackageData" step and doesn't progress any further.

When I use the official registry, everything works fine. What is the cause of this?

Product: ProGet
Version: 5.1.9

3
replies

We tried to update ProGet from 5.1.8 to 5.1.9 and the Updater (Offline Installer) ran into the following exception:

Debug: Executing OBJECTS\4.PROCEDURES\1.NuGetPackagesV2_SetListed.sql...
Error: Unhandled Exception: System.Data.SqlClient.SqlException: Incorrect syntax near '('.
Error: Must declare the scalar variable "@NuGetPackageV2_Id".

I we try to start the updater again it doesn't offer to update ProGet any more but wants to install a new version instead.

I attached the complete logfile to Ticket [EDO-5296]

Product: ProGet
Version: 5.1.9

1
replies

Hi,

Is it possible (or could this be considered as a change request if not) to include Metadata alongside Asset blobs? For example, as simple description stored alongside a file. It would be great if this could be done as users definable fields.

This potentially could be extended to allow the API to then retrieve asset metadata.

Thanks,

Simon

Product: ProGet
Version: 5.1.9

1
replies

Hi, I want to delete (not unlist) a number of older packages in our nuget feed under proget. I saw in a number of questions posted here hat i think the only way to do that is to make a DELETE http call to the url of the package you want to delete. This call would include a nuget apikey in the headers.

my example and the error i am receiving:
DELETE
https://packages.zywave.com/nuget/Integration/Zywave.Shared.MailQueue.Contracts/2.0.780495.190245
"You are not authorized to delete a package in this feed."

what would cause this error to occur? if there is a permission somewhere that we should look at? if so, specifically where in proget?

Product: ProGet
Version: 5.0.13

3
replies

After our upgrade to 5.1.7 (free) from a 4.1.3 version, we lost most, if not all of our custom internal packages that we had uploaded. We noticed this only after having run in production for a while. It got worse when we converted the feeds to the v2 version when we were prompted to do so in the UI. In looking at backups of the DB, after the upgrade, it seems the packages are there in the NuGetPackages table, but they are not visible in the UI.

Is there anything we can do to add these packages back in besides finding the version of them in NuGet package cache somewhere and re-uploading them? Any recommendations you may have, including going back to the old version we were running, would be great.

Product: ProGet
Version: 5.1.7

1
replies

Previous versions load the InedoCore extension successfully from https://inedo.com/den/feed/download/inedox/InedoCore/1.0.6, but version 5.1.x does not load it. I failed to find any relevant logs as to why, and the extension list simply does not show it.

I have verified the extension location to be /var/proget/extensions, and if I download the extension from the Web UI, this is also where it ends up.

If I place a corrupt zip file in its location (i.e. /var/proget/extensions/InedoCore.upack), there is an error shown on the extensions page that it cannot unzip the .upack, so it seems the files are in the right place.

The same problem occurs with e.g. the Azure plugin.

Is there any change in 5.1 that could affect how extensions are loaded?

Product: ProGet
Version: 5.1.8

2
replies

Hi, we are using Proget in High Avability mode with Active Directory(new) and the InedoCore 1.06 extensions installed.

It seems like that nested AD groups are not working.
In the Security task page I added an AD group that contains multiple other AD groups the View & Download Packages task to the Scope of one of our feed.

When I test priviliges with multiple users that are members of the group wich is a member of the group with the task View & Download Packages they can't view the feed and I have the message that they can't view the feed.

Product: ProGet
Version: 5.1.5

3
replies

Hi we are getting a lot of this error in the diagnostic center searched here but I've found nothing of the sort. Do any of you have any idea has to what could be the cause of those errors ? We are using Proget in High Avability mode with Active Directory(new)

Category : FailoverDetectionRunner

Message : Unhandled exception: 12051356IndexingServers_SetUpdated60`Transaction (Process ID 91) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

Details : System.Data.SqlClient.SqlException (0x80131904): 12051356IndexingServers_SetUpdated60Transaction (Process ID 91) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction. at System.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__174_0(Task1 result)
at System.Threading.Tasks.ContinuationResultTaskFromResultTask2.InnerInvoke() at System.Threading.Tasks.Task.Execute() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Inedo.Data.DatabaseContext.DbResult.<CreateAsync>d__10.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Inedo.Data.DatabaseContext.<ExecuteInternalAsync>d__33.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Inedo.Data.DatabaseContext.<ExecuteNonQueryAsync>d__31.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at Inedo.Data.DatabaseContext.<ExecuteScalarAsync>d__301.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.ProGet.Service.FailoverDetectionRunner.<RunAsync>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Inedo.TaskRunner.<RunInternalAsync>d__43.MoveNext()
ClientConnectionId:71ce329c-75d7-4073-acfc-1f28a203de39
Error Number:50000,State:42,Class:13

Product: ProGet
Version: 5.1.5

1
replies

Has anyone tried to install project using AWS RDS to host SQL? The installer is saying I don't have the permissions even though we have full rights to SQL

Product: ProGet
Version: 5.1.8

1
replies

I just wanted to make a post to express my interest in BM-3239, that would allow users to dynamically specify a plan or module to invoke, and see if there is any additional interest from the community. I think with this operation we could get some really powerful flexibility in our workflows. This operation would let us create "wrappers" for our call statements that could do some pretty cool stuff. For example we could more easily aggregate the runtime of specific steps.

module InvokePlanTimerWrapper<$PlanName, %PlanArguments>
{
    set $StartTime = $PSEval(Get-Date);

    Invoke-Plan $PlanName
    (
        Name: $PlanName,
        Arguments: %PlanArguments
    );

    set $EndTime = $PSEval(Get-Date);

    set $script = >>
        `$start = [datetime]"$StartTime"
        `$end = [datetime]"$EndTime"
        (New-TimeSpan -Start `$start -End `$end).seconds
    >>;
   
    set $Diff = $PSEval($script);

    Log-Information Plan $PlanName took $Diff seconds to complete.;
}

We could also create a form of retry logic that doesn't rerun steps that already succeeded.

module InvokePlanReexecuteWrapper<$PlanName, %PlanArguments>
{

    set %ExecutedSteps = %PackageVariable(ExecutedSteps);
    set @ExecutedStepsForEnvironment = @MapItem(%ExecutedSteps, $EnvironmentName);

    if $IsReexecution && $ListIndexOf(@ExecutedStepsForEnvironment, $PlanName) == -1
    {
        Invoke-Plan $PlanName
        (
            Name: $PlanName,
            Arguments: %PlanArguments
        );
    
        set @ExecutedStepsForEnvironment = @ListInsert(@ExecutedStepsForEnvironment, $PlanName);
        set %ExecutedSteps = %MapRemove(%ExecutedSteps, $EnvironmentName);
        set %ExecutedSteps = %MapAdd(%ExecutedSteps, $EnvironmentName, @ExecutedStepsForEnvironment);
    
        Set-ReleaseVariable(
            Variable: ExecutedSteps,
            Value: %ExecutedSteps,
            Release: $ReleaseNumber,
            Package: $PackageNumber
        );
    }
}

Product: BuildMaster
Version: 6.0.10

6
replies

I've been working to clean up legacy items and I am confused by one aspect.
In the report it is saying i have legacy template variables but when I view the Variables page in the admin it is not indicating any legacy variables.

So just wanting to clarify what is it this is complaining about?

The main variables I have are release templates and pipeline and while the variable names listed are some I have the log listing the legacy variables is not clear where they are.

Product: BuildMaster
Version: 6.0.10

1
replies

Can we upgrade from Proget Free version to enterprise version ? And what does this upgrade process include?

Product: ProGet
Version: 5.1.8

7
replies

Hi,

We're occasionally seeing timeouts when pushing Nuget packages to Proget, and they often occur at the same time as the following message in the logs:

Logged: 8/20/2018 7:57:33 AM
Level: Error
Category: ExtensionsManager
Message: Error initializing extensions manager.
Details: System.ArgumentNullException: Value cannot be null.
Parameter name: key
at System.ThrowHelper.ThrowArgumentNullException(ExceptionArgument argument)
at System.Collections.Generic.Dictionary2.FindEntry(TKey key) at System.Collections.Generic.Dictionary2.TryGetValue(TKey key, TValue& value)
at Inedo.Extensibility.ExtensionsVerifier.GetAssemblyLoadResults(InedoExtensionsManager extensionsManager)
at Inedo.Extensibility.InedoExtensionsManager.InitializeAssemblies()
at Inedo.Extensibility.InedoExtensionsManager.Initialize(String[] builtIn)

Any idea what might cause this?

We're using Proget 5.1.7, running in IIS on Server 2012 R2. The package source and Proget are on the same network.

Product: ProGet
Version: 5.1.7

2
replies

Hi,
After being sure that I found a bug with the new dotnet tool install -g flow, with the help of Microsoft employees, I ended up realizing that ProGet was being overzelous with respect to the case sensitivity when searching / serving packages.

According to the official nuget implementation, package Ids are case INsensitive:
https://github.com/NuGet/NuGet.Client/blob/1a1c474aab5c1e851b416c583ca4c6d727bd94e3/src/NuGet.Core/NuGet.Packaging.Core/comparers/PackageIdentityComparer.cs#L70

When I push into proget a package with mixed casing, and later run a "dotnet tool install -g" command, the dotnet tool client searches for lower case package-id, and proget fails to find such a package since it is doing a case sensitive search.

After renaming my package to all lower case, everything seems to work again.

I hope I've managed to explain myself properly.

It seems like proget SHOULD switch to case insensitive search in order to be compatible with the nuget protocol "spec" and dotnet tool install -g, more specifically.

Hope you will consider changing the default behavior for ProGet!

Product: ProGet
Version: 5.1.8

4
replies

Hello

Is there support for Azure AD authentication on the roadmap? If so are you able to give any visibility to when we might see this feature become available?

We would like to move our proget setup from on-prem to in azure using your docker image. But for that to work and be secure we would require authentication against azure AD.

I look forward to your reply.

Mark

Product: ProGet
Version: 5.1.7

12
replies

As I found a workaround I thought I just pust this has a question.

After upgrading from 4.7.14 to 5.1.7 build 2 the ProGet Windows service did not start.

The event log reviels the following errors:

Application: ProGet.Service.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Net.HttpListenerException

Server stack trace:
at System.Net.HttpListener.AddAllPrefixes()
at System.Net.HttpListener.Start()
at Inedo.Web.Server.HttpListenerHost.Start(WebServerConfiguration settings)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(System.Runtime.Remoting.Messaging.IMessage, System.Runtime.Remoting.Messaging.IMessage)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(System.Runtime.Remoting.Proxies.MessageData ByRef, Int32)
at Inedo.Web.Server.HttpListenerHost.Start(Inedo.Web.Server.WebServerConfiguration)
at Inedo.Web.Server.IntegratedServer.ProcessRequests()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()


An unhandled exception occurred and the process was terminated.

Application ID: ProGet.Service.exe

Process ID: 1240

Exception: System.Net.HttpListenerException

Message: Access is denied

StackTrace:
Server stack trace:
at System.Net.HttpListener.AddAllPrefixes()
at System.Net.HttpListener.Start()
at Inedo.Web.Server.HttpListenerHost.Start(WebServerConfiguration settings)
at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)

Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Inedo.Web.Server.HttpListenerHost.Start(WebServerConfiguration settings)
at Inedo.Web.Server.IntegratedServer.ProcessRequests()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()


This smells like the URL has not been properly pre-registeret by the installer during the upgrade (URLACL).
I was able to workaround this by changing the ProGet service account from NetworkService to LocalSystem.

Have you heard of this issue before?
Does the installer normally register the URL for the service account?

Product: ProGet
Version: 5.1.7

10
replies

Suddenly our ProGet installation is getting SQL timeouts. I've seen that the configuration has been moved to a central configuration file: https://inedo.com/support/documentation/proget/reference/config-files

The SQL connectionstring is still valid, but it seems the application is not reading the connectionstring from the shared config file?
I tried putting ConnectionString and EncryptionKey inside Web_appSettings.config and App_appSettings.config but still get the same error.

Don't I need a customconfiguration section declaration for "InedoAppConfig" inside Web.config and Proget.Service.exe.config ?

Is anyone else experiencing this issue?

Server Error in '/' Application.
The wait operation timed out
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.ComponentModel.Win32Exception: The wait operation timed out
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[Win32Exception (0x80004005): The wait operation timed out]
[SqlException (0x80131904): Execution Timeout Expired. The timeout period elapsed prior to completion of the operation or the server is not responding.]
System.Data.SqlClient.<>c.<ExecuteDbDataReaderAsync>b__174_0(Task1 result) +1161090 System.Threading.Tasks.ContinuationResultTaskFromResultTask2.InnerInvoke() +108
System.Threading.Tasks.Task.Execute() +71
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
Inedo.Data.<CreateAsync>d__10.MoveNext() +341
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
Inedo.Data.<ExecuteInternalAsync>d__33.MoveNext() +1239
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
Inedo.ProGet.Data.<Dashboards_GetDashboardInfoAsync>d__91.MoveNext() +731
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) +14139265
Inedo.ProGet.WebApplication.Pages.<CreateChildControlsAsync>d__2.MoveNext() +411
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
Inedo.ProGet.WebApplication.Pages.<InitializeAsync>d__1.MoveNext() +348
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
Inedo.Web.PageFree.<ProcessRequestAsync>d__46.MoveNext() +283
System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) +14139120
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) +62
System.Web.TaskAsyncHelper.EndTask(IAsyncResult ar) +69
Inedo.Web.Handlers.AsyncHandlerWrapper.EndProcessRequest(IAsyncResult result) +34
System.Web.CallHandlerExecutionStep.OnAsyncHandlerCompletion(IAsyncResult ar) +178
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.6.1590.0

Product: ProGet
Version: 5.1.7

Ask A Question
Page: 1 2 3 5 7 8 9 10 128