@stevedennis said in Proget Service/Site Crashes with 500 Error: shared memory provider error 40 Thank you for the insights, I was also thinking the sql server was the most significant thing. It is on the same server but it's also a virtual server, I don't think it's a hardware failure there. There is another sql server running on the server for chocolatey central management, there may have been a conflict with a mismatched version dependency on that app for the dotnet-aspnetmodule-v2 where I need the 16.x version for CCM but I accidentally upgraded to the 17.x version. At the moment the issues hasn't recurred since the day I reported it and I'm hoping having fixed that dependency has fixed the issue. I found some other things that mention local sql aliases needing to exist, I do use many dns aliases in the server's config so I might try making those as sql named pipe aliases to see if that makes any difference, though it seems a long shot.