@atripp We had the same error when upgrading each node on a high availability install. Does the upgrade routine delete and recreate the stored procedures for each node upgrade? It felt like there was no check of a version for each node upgrade.
scott.wright_8356
@scott.wright_8356
Best posts made by scott.wright_8356
-
RE: SQL Error after upgrade version
-
RE: Maven Andriod Endpoint URL
@atripp said in Maven Andriod Endpoint URL:
We have a problem with this on our old server. We have the packages on the feed. We have imported them to the new ProGet Server. The connector is setup correctly.
It is healthy
It is connected to the feed.
When we request the package, we are after we get the following.
We have attempted to import the old servers' packages directory as a temporary fix, but we get the following error for all the imports from the other package directory.
Added Maven Package com.android.tools.build/gradle 1.5.0.
Could not add file "\proget-smb.wtg.zone\Proget\F12\android.arch.core\common\1.1.0\common-1.1.0-sources.jar". There was not matching pom file.
Could not add file "\proget-smb.wtg.zone\Proget\F12\android.arch.core\common\1.1.0\common-1.1.0.jar". There was not matching pom file.When we look at packages that were successfully imported, we get the following error:
With a corresponding record in the diagnostic log.
Level:Error Category:Web Message:An error occurred in the web application: Object reference not set to an instance of an object. Details:URL: http://proget.wtg.zone/feeds/Maven-Android/com.android.tools.build/com.android.tools.build.gradle/1.5.0 Referrer: https://proget.wtg.zone/packages User: SW User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 Edg/122.0.0.0 Stack trace: at Inedo.ProGet.Feeds.Maven.MavenFeed.Inedo.ProGet.Feeds.IBrowsablePackageFeed.ListPackageVersionsAsync(BrowsablePackageId id) at Inedo.ProGet.WebApplication.Pages.Packages.PackagePageBase.CreateChildControlsAsync() at Inedo.ProGet.WebApplication.Pages.ProGetSimplePage.InitializeAsync() at Inedo.Web.PageFree.SimplePageBase.ExecutePageLifeCycleAsync() at Inedo.Web.PageFree.SimplePageBase.ProcessRequestAsync(AhHttpContext context) at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
Latest posts made by scott.wright_8356
-
RE: Conda Feed to SMB Share
@rhessinger Wonderful, thank you very much and credit to Pawel Ostrowski who also did a lot of investigation on this
-
RE: Conda Feed to SMB Share
Hi Alana,
What we did find to get our small applications working was the following post. This mentioned that when opening the file the path should start with four backslashes. "\\"
This worked for our small applications and allowed the SQL lite package to work over the SMB share.
Regards Scott
-
RE: Conda Feed to SMB Share
Hi Alana,
We have written many simple programs using the same SQL Lite package as above. We cannot find a scenario where SQL Lite works over an SMB share, and we have been able to find content that says not to use it over the network. We were able to confirm that the create database option works fine. It is the opening that fails every time. What happens with the OpenOrCreateDatabase is it rolls back the file created when the open fails, so you end up with nothing.
https://www.sqlite.org/useovernet.html
https://stackoverflow.com/questions/788517/sqlite-over-a-network-share
We are using the IIS setup. Has this been tested with IIS and SMB share for Conda? I assume the index information for the package repository is what is going into the SQL Lite DB? Would it not be faster to store this information locally on each node? Does the SQL Lite DB need to be shared?
Is there an option to set the Conda/Debian package storage on the network share and the SQL Lite DB locally for each node?
Regards Scott
-
RE: Conda Feed to SMB Share
Hi Alana,
We wrote a program to use the SQL Lite library and ran it from the ProGet Node.
This is from the ProGet node server to our ProGet SMB share, and there are no issues. It is just the ProGet application that is having a problem.
-
Conda Feed to SMB Share
Hi Support,
We have an issue creating a Conda feed to an SMB share. The SQL Lite file cannot be created there; we are running a High Availability structure with no issues with NuGet, Npm, Python, and Maven feeds. With the Conda feed, we get
Is there a particular port that ProGet requires when communicating with SMB share for SQL Lite? We can get the feed working with local storage on one of the nodes but not with the shared storage. When we put the SQL lite file there manually and refresh the feed, it is deleted. It is like clearing the file and then attempting to write it there using a different process than the other feeds.
Regards Scott
-
RE: ProGet New Vulnerability scanning removes ability to block a package
Thank you very much for this, Alana. Very much appreciated.
-
RE: ProGet New Vulnerability scanning removes ability to block a package
Hi Alana,
How do we set the package status to blocked? I cannot find this option against these packages, which is what I have been looking for. I remember it being there, but it appears to be gone in version 23.0.31. Also, regarding the above response, do you intend to allow users to modify the vulnerability database or not? The style of the answer indicates no.
Regards Scott
-
ProGet New Vulnerability scanning removes ability to block a package
Hi Support,
We have an issue with the Moq library in NuGet. The Vulnerability assessment is wrong and has a limited list of versions to block.
PGV-2358804: Moq v4.20.0-rc to 4.20.1 share hashed user data
We have confirmed that 40.20.2 and 4.20.69 still have the vulnerability, but we cannot clock these in the new versions of ProGet now. How do we extend the vulnerabilities to block packages that are a problem? I can understand why these versions were missed, as you need to go through the commits that make up the versions and check them for yourself. This is why the ability to block manually on the existing version was so important.
Regards Scott
-
Package Latest Version not showing in All Versions
Hi Support,
We often have an issue showing up for a npm feed. The feed is a public cache feed of https://registry.npmjs.org with metadata caching enabled. What is happening is that on the feed when searching the package, it is showing the latest version.
When selecting that version, we get the following error.
Also, we cannot see the latest package when looking at All Versions.
This issue fixes itself over time. However, for example, this package is updated hourly, consumed as a dependency, and causes intermittent build issues in our CD/CI.
Regards Scott
-
ProGet Enteprise License Update
Hi Support,
We just updated our High Availably structure with a new ProGet Enterprise license key and received the following error message.
Logged:2/04/2024 9:32:36 AM Level:Error Category:Web Message:An error occurred in the web application: No primary service node has been registered. Details:URL: http://proget.wtg.zone/administration/licensing/change-license-key Referrer: https://proget.wtg.zone/administration/licensing/change-license-key User: SW User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36 Edg/122.0.0.0 Stack trace: at Inedo.ProGet.WebApplication.AggregateServiceMessengerClient.GetPrimaryNodeId() at Inedo.ProGet.WebApplication.AggregateServiceMessengerClient.SendMessage(ServiceMessage message) at Inedo.ProGet.WebApplication.Pages.Administration.Licensing.ChangeLicenseKeyPage.<>c__DisplayClass1_0.<<CreateChildControls>b__0>d.MoveNext() --- End of stack trace from previous location --- at Inedo.Web.PageFree.SimplePageBase.ExecutePageLifeCycleAsync() at Inedo.Web.PageFree.SimplePageBase.ProcessRequestAsync(AhHttpContext context) at Inedo.Web.AhWebMiddleware.InvokeAsync(HttpContext context)
I went back to the page and found the key had successfully updated. I manually ran the activation process. It appears to be working, as the expiry date has updated on the license.
Regards Scott