@Dan_Woolf Sounds good, thanks for the response.

This has also been reported in our Jenkins extensions issues section, can you take a moment to respond to the questions I posed here? https://github.com/Inedo/inedox-jenkins/issues/26#issuecomment-454188149

The connection string used by ProGet is stored in its configuration file (see this documentation page for the format and location). The Windows user account used is whatever user the INEDOPROGETSVC service is running under - generally, ProGet configures this to be NetworkService, but could be configured to be any user account.

This seems to be related to a specific package that you have in your repository. Most likely it's bad/invalid metadata, and the specifics were not anticipated and thus it's crashing trying to read it. Unfortunately we would need to know a bit more about that package, and why it's causing this problem.

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

The error is generic and there are many reasons why the SSL/TLS negotiation may fail. ServicePointManager.SecurityProtocol property selects the version of the Secure Sockets Layer (SSL) or Transport Layer Security (TLS) protocol to use for new connections; existing c# connections aren't changed. Make sure the ServicePointManager settings are made before the HttpWebRequest is created, else it will not work. Also, you have to enable other security protocol versions to resolve this issue: ServicePointManager.Expect100Continue = true; ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 SecurityProtocolType.Tls SecurityProtocolType.Tls11 SecurityProtocolType.Ssl3; //createing HttpWebRequest after ServicePointManager settings HttpWebRequest request = (HttpWebRequest)WebRequest.Create("https://google.com/api/") If you create HttpWebRequest before the ServicePointManager settings it will fail and shows the error message.

Please review KB#1161 for instructions on how to update this.

Hi Ben. Thank you for the clarification of the problem scope. Look forward to the fix. Thank you for the quick response, much appreciated +1 Inedo has excellent support and reacts promptly.

The Integrated Web Server doesn't have many features, including request logging and tracking. So in this case, you'll want to upgrade to IIS: Please refer to KB#1013: Hosting Through IIS Instead of the Integrated Web Server

I'm not sure I totally understand what you mean by "had the path of where I stored the PoSh script"? Basically, when you create an asset in Otter, it is stored in a Raft, which is a sort of abstract file system. So, it's basically just a file (script-name.ps1) stored in this raft. We are working on building out our training videos (sadly, they take quite a while), but we'd love to learn what your overall goals are, and how we can build good content to help you reach those goals. In a lot of organizations, one of the most important things is "showing the value/success" of automation, infrastructure as code, etc. So we want to help with that too. Anyways, it's obvious quite a "big topic", so your best would be to get in touch with us, so we can work together directly.

Hmm , it's hard to say. It's just a random crash with no indiciation of a specific error... You should switch to IIS, perhaps then you can get better insight into what might be causing it... or the error might go away altogether.

The issue is related to packages missing SHA1 hashes in the ProGet databases; at some point packages were able to be added without them. We have updated the migration process internally to perform them if they are missing, and this fix will be included in the next maintenance release. Here is the tracking issue: https://inedo.myjetbrains.com/youtrack/issue/PG-1203

Hi Ben Lubar, The error messages are listed as follows: Add new ADUserDirectory.sql failed: 42601: syntax error at or near "IF" Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object at System.Web.Caching.Cache.ExpireItems (System.Object data) [0x00008] in <d777bf5120224d38839a5bae355ed440>:0 at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00008] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <77c9551943624fd18301ba6f78a841e5>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object at System.Web.Caching.Cache.ExpireItems (System.Object data) [0x00008] in <d777bf5120224d38839a5bae355ed440>:0 at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00008] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <77c9551943624fd18301ba6f78a841e5>:0 Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object at System.Web.Caching.Cache.ExpireItems (System.Object data) [0x00008] in <d777bf5120224d38839a5bae355ed440>:0 at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00008] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <77c9551943624fd18301ba6f78a841e5>:0 [ERROR] FATAL UNHANDLED EXCEPTION: System.NullReferenceException: Object reference not set to an instance of an object at System.Web.Caching.Cache.ExpireItems (System.Object data) [0x00008] in <d777bf5120224d38839a5bae355ed440>:0 at System.Threading.Timer+Scheduler.TimerCB (System.Object o) [0x00007] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem () [0x00008] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading.ThreadPoolWorkQueue.Dispatch () [0x00074] in <77c9551943624fd18301ba6f78a841e5>:0 at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback () [0x00000] in <77c9551943624fd18301ba6f78a841e5>:0 I hope this help.

Hello Ben, thanks for help. I can confirm that node.js v 6.11.4 with slash at the end of URL works ;)

In this case, it sounds like the permissions for AWS must not be correct...the user must have full control/read/write access to bucket you specify.

Solved by using link by Martin Helgseen http://inedo.com/support/questions/7217 Thanks

It's hard to say, but if you're not seeing anything come up when you visit the web interface.. it sounds like the web server or IIS isn't running or otherwise configured. The error you shared from the Windows Service would verify this (the service cannot talk to the web application either). Take a look at the Manual Installation Instructions to see if you can identify how things are mis-configured.

Hi Tod That is great news +1 Thanks for the very fast reply and hotfix release, which i look forward to. For now we have stabilised by loading a backup of our Proget server, rolling back to 4.6.7 so we are good for now :-D Regards Thomas

I have created an issue to add a feature to display a better error message when the base url property is invalid.  (PG-1107)