If the package does exist, and you can download the package from the ProGet UI, then it indicates that there is no problem with ProGet. The UI uses the same download URL, and whatever is shown in the UI will be shown in the API. To further troubleshoot, I recommend you to use Fiddler and trace the HTTP requests. You can also inspect the ProGet message center to see what error requests are being made tot the ProGet server.

Your server is configured to disable the use of .NET's MD5 processing libraries, which means ProGet cannot read or write Maven index files. You can disable this at the server level: https://www.schneider-electric.com/en/faqs/FA282064/ You can also edit the configuration file; https://docs.microsoft.com/en-us/dotnet/framework/configure-apps/file-schema/runtime/enforcefipspolicy-element

Please refer to KB#1090 for how to grant service control permissions and avoid this service control error. If you're getting a 404, then you're not using the proper API Endpoint URL. I'm guessing, you're using whatever URL in your browser? Please refer to this tutorial for how to configure this in Visual Studio.

You need to create an API in the ProGet UI; API Access and API keys

This is a property of the service. Just go to "Services" on your computer, edit the service, and change the Auto-recorvery options.

Dean, thanks for the reply. I am hoping it makes it into this release, as each server I import I have to go into the properties of each one manually and change the raft from not configured to default. While I am trying to build traction for this product, this process of touching each machine does not give a good impression. Thanks for the update!

Dean, that's great news! Thanks!

Hello, after trying for a half hour, I was not able to get the $PSEval to successfully do any math operations for me, but something I hadn't tried in my hours of troubleshooting this is try putting the variable last and the number first, and the PSEnsure worked great at that point.

Hi, I got the InedoCore extension from an other installation on an other machine. And I copied it into the extension folder, restart the service and it works now. Thanks for the answers. KR.

After some digging I determined that Mpa (%) types are not currently supported. I was able to get past this by embedding JSON in a scalar string, and then use %FromJson() to convert to a Map type in OtterScript.

Hello Jeremy, It seems that the Maven feed code in ProGet is incorrectly identifying all prerelease Maven package versions as snapshot versions. I've filed this as PG-1380.

Thanks Alana, we will update our the inedo Core when the new version will be available.

You can do this with default values. template Check_Version<$App, $Role=default> { } And then test if it's the default value to see if it wasn't passed in

Soon --- this is a known issue, but we are in the process of resolving it; please see InedoCore#96

This was a result of a imcompatable script with 2005, but it has been fixed as of 5.1.11. We are also displaying warning if you're using unsupported version of SQL

We are only aware of that message occurring in the two cases I mentioned, and haven't had reports of the contrary. From here, please use a tool like Fiddler or Wireshark to identify the exact request/response patterns that are happening. You can see the authentication headers sent, and it's possible there's a typo or something in a name or password.

We take problems very seriously, but we need to prioritize where to spend engineering resources tracking down problems. This was a edge case that we could not reproduce, and had a very minor impact, and only affected a very small number of free users with a very specific configuration; a free user was able to track down the underlying cause and we fixed it.

Hi, thanks for your reply. Fortunately, this particular feed contained low amount of packages, so i've just backuped them for ProGet ProgramData folder, deleted this feed via Proget UI, recreated feed and uploaded packages back, and now it works. I agree with you and suppose that there were some MSSQL issue, but decided to solve this issue using easiest and fast way for me.

We believe we have fixed this as PG-1377, which will be included in ProGet 5.1.11. Thank you!