Welcome to the Inedo Forums! Check out the Forums Guide for help getting started.
If you are experiencing any issues with the forum software, please visit the Contact Form on our website and let us know!
Error initializing extensions manager
-
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.Dictionary
2.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
-
Yes, it just involves changing the license key.
Please refer to License Key Management
-
Hi Alana,
Thanks for your reply. Can you clarify what you mean? We're using ProGet Free and the license key shows as valid/activated.
Do we need to generate a new one?
-
I'm sorry, I accidently replied to here instead of this post. Please disregard it; the issue has nothign to do with your license.
I don't have an answer to your question, but another engineer will help soon. Note that if you have a paid license you can use a support ticket.
But someone will respond to this soon!
-
Make sure the following configuration values in
Admin
>Advanced Settings
are set to an accessible directory (note that the defaults from the installer are shown here, double-check that they are valid in your installation):Extensions.ExtensionsPath
-C:\Program Files\ProGet\Extensions
Extensions.ServiceTempPath
-C:\ProgramData\ProGet\ExtensionsTemp\Service
Extensions.WebTempPath
-C:\ProgramData\ProGet\ExtensionsTemp\Web
-
Hi Tod,
Those paths are still set to the defaults and they're present and accessible on the server.
Is there anything else it could be referring to?
-
This took a while to track down, but that error message is ultimate caused by having an extension that fails to load along with a value set for
Extensions.BuiltInExtensionsPath
, and the error message will be fixed as part of issue: ILIB-52However, this error is only generated when the extensions manager is initialized, which occurs when the integrated web server (or IIS application pool) is restarted. This means that either the timeout you're experiencing causes the website to restart, or the timeout is caused by the web server restarting.
You could try setting
Diagnostics.MinimumLogLevel
to0
temporarily to get debug logging, or examine the Windows Event Log to see if there are any .NET errors that cause the web application to restart.
-
Hi Tod,
Thanks for looking into this. I just checked and can confirm that the last time we received this error it matched up with an app pool recycle.
I'm not sure yet whether this is the source of all our timeouts, but that's certainly given us something to work with.
I'll post again if we suspect any other Proget related issues.
Thanks again.