Here are the full details of the issue we are having with the Maven connector. Is this a FIPS issue? Servers are probably hardened more than most where I work, but this was not a problem until we upgraded to 5.1.7.

Message

The type initializer for 'Lucene.Net.Store.FSDirectory' threw an exception.

Details

System.TypeInitializationException: The type initializer for 'Lucene.Net.Store.FSDirectory' threw an exception. ---> System.SystemException: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)
at System.Security.Cryptography.MD5.Create()
at Lucene.Net.Store.FSDirectory..cctor() ---> System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.InvalidOperationException: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
at System.Security.Cryptography.MD5CryptoServiceProvider..ctor()
--- End of inner exception stack trace ---
at System.RuntimeMethodHandle.InvokeMethod(Object target, Object[] arguments, Signature sig, Boolean constructor)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at System.Security.Cryptography.CryptoConfig.CreateFromName(String name, Object[] args)
at System.Security.Cryptography.MD5.Create()
at Lucene.Net.Store.FSDirectory..cctor()
--- End of inner exception stack trace ---
at Lucene.Net.Store.FSDirectory..cctor()
--- End of inner exception stack trace ---
at Inedo.ProGet.Feeds.Maven.MavenConnector.Search(String searchTerm)
at Inedo.ProGet.Feeds.Maven.MavenFeed.Search(String searchTerm)
at Inedo.ProGet.WebApplication.UnifiedFeedBrowsing.Feeds.MavenFeedDataFactory.GetPackagesAsync(Feed feed, String searchTerm, Int32 count)
at Inedo.ProGet.WebApplication.Pages.Feeds.BrowseFeedPage.<GetPackagesAsync>d__10.MoveNext()

Product: ProGet
Version: 5.1.7

Our database backups were explicitly taken the exact moment before the upgrade as is our practice. We do not allow ProGet to perform the backups. We did not make configuration changes on retention or package store either. Current and prior settings were to keep the latest 30 versions, and according to the docs, retention policies are ignored in the free version (meaning it "runs" them but nothing gets deleted). We switched from a paid version to the free version during this upgrade.

We do have backups of the packages and were able to re-import them through the drop folders. I was simply looking to see if there were experiences with this and whether or not it could have been a bug in the upgrade.

In reviewing the event log, I see the exact packages that are missing being deleted the next day at 1:52 PM by the user UNKNOWN. Is there anything internally that would use that user? From what I understand, the only users would be Admin and Anonymous if it was someone doing it via the web portal. It happened once at this time and no PKGDEL was ever logged again except for a real one by the Admin.

We're probably going to stop looking as we've restored all of the packages, but if it helps anyone else, great! :)

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