Thanks you Rich it is working !.

Hi @cronventis, Thanks for confirming thsi for me. I already have the fix in for ProGet 6.0.5 which is expected to release on Friday. Thanks, Rich

@rhessinger Thank you, Much appreciated. :)

@hwittenborn thanks for letting me know -- that was going to be my next suggestion. It's very possible the key had an unexpected combination of properties/permissions and that didn't translate to the v6 internal model But easy enough to recreate in a case like that :)

Hi Alana, Thanks for the reply. We've got a ticket on our backlog to upgrade, but we're blocked for ... reasons ... and we might not be able to do that for a while. We managed to kludge a workaround - there's only one dev team using Maven feeds so we suggested they give the Maven Central a feed higher priority in their build config so it scans that first - it seems to have at least hidden the issue for the time being :-). I'll follow up if we've still got the issue after upgrading, whenever that might be... Thanks again, Mike

Hi @scusson_9923, Glad to hear it! Thanks for following up as well! Thanks, Rich

@sbindra_9387 you can enter the activation code in ProGet, when you click the activate button Here is the instruction for manual activation: https://docs.inedo.com/docs/myinedo-activating-a-license-key

Hi @patrick-groess_2616 , The /symbols/<feed-name> URL is only for Visual Studio's Symbol Location setting, and is used to download symbols. Do not try to use it with nuget.exe, it will give that error. You need to use /nuget/<feed-name> to push symbol or nuget.exe packages. Thanks, Alana

Hi @Dan_Woolf, Thanks for your Information, we have a paid version of ProGet. I think your pgscan tool is exactly what I'm looking for, I'll looking into it. Regards, Kurt

hi, I had in the proxy configuration both allowed, ssl and non ssl. The Web.BaseUrl must be make empty. All self connector using http://localhost as base url.

If you want to delete long directory paths you should use Long Path Tool. It is great tool.

Hi @gdivis, I've just installed v7.0.14 and the behaviour seems improved. On the original thread track; Using hub v1.3.7 the upgrade from v7.0.13 to v7.0.14 went through without getting stuck. After upgrade, both Test and Production web pages were able to load in less than 2 minutes. There is CPU spiking; but seems more spread out and the max memory is now two thirds of what it was; however within 6 minutes of startup its back around the 160MB - 350MB (it was idling at 160MB before upgrade) which is a definite improvement. Thanks, Paul

Hi @rhessinger, Thanks for the fix in 7.0.14 Loving your work once again !! [image: 1637601792944-a5e9bb54-bdf1-41ac-b4a9-c4e29e00c4b3-image.png] Regards, Paul

Hi Rich, Just installed 7.0.14; thanks for the fix Regards, Paul

Hi @jev_1362, The file should be saved on the server in the storage path. Can you check and see if that file exists locally on the server? You can find the storage path for your asset directory by navigateing to Assets and then clicking the pencil to the right of the asset directory. Then click the Storage & Retention tab and you will see your storage path there. Also, do you see any errors int eh diagnostics center when you try to download that file? Thanks, Dan

Hi @lukel_3991, I think we have two different issues that are happening here. The first one it seems to not be synchronizing over the extensions. What version of PowerShell do you have installed on your remote server and the otter server? The PowerShell based agent-less servers connect using PSRemoting over WSMAN. Could you please try to connect to your remote server using Enter-PSSession in PowerShell on your Otter server and try to run some commands to make a temp folder and write a file to it using the same credentials Otter users to connect to that server? It almost feels like there may be a permissions issue. The other issue seems like their could an issue with your OtterScript itself. Would you be able to share the OtterScript you are trying to run? Thanks, Dan

Hi @tcddpmonqxvfmiuyla_2318, No problem, thanks for updating with what you found the problem to be. Thanks, Dan

Hi @forcenet_4316, Thanks for bringing this to our attention. I'm not sure how this slipped through, but I made sure it is fixed in the next release, ProGet 6.0.3. The final fix is tracked via PG-2043. Thanks, Rich

Hi @r-riedinger_1931 , That error indicates that the database code (Stored Proc) didn't get updated, or is somehow out of sync with the installed version. Is it possible that you're pointing to an older database? You may want to run the installer again, just to make sure. Dean