Hi @lucas-almeida_8120, This a known issue that we are currently working through. It seems to be an issue with some bad/duplicate data in your database. The current workaround is to downgrade to ProGet 2023. We are hoping to have a fix ready soon. Thanks, Dan

A possible solution to this is to use Extended Properties in SQL. That way you can check the version of the files in the upgrade and not re-create them when they have already been updated?

Hi @lucas-almeida_8120 , This error implies that there's some kind of database corruption or other error that happened while updating the database a while ago. But it's hard to say; this is the first time I've seen this error. Unfortunately, unless I were to analyze a backup of your database and try to reproduce the installation/upgrade, I won't be able to offer any guidance or scripts that could repair the state of things. From here, I would recommend rolling back to whatever version was working, then starting a new ProGet server and importing your packages. Best, Alana

@lucas-almeida_8120 it's hard to say; it's likely due to some kind of operating system configuration or issue that's preventing the service from restarting. We haven't seen this happen very often, and restarting the web is not a common activity. It's probably not worth spending time investigating or trying to resolve, especially given the age of the server. You'd probably have to look at the Windows service logs to find what the issue might be.