Operations | Monitoring | ITSM | DevOps | Cloud

Today’s IT teams are facing a greater demand for services than ever before, and often doing so with increasingly limited resources. This inevitably leads to one of the most common yet challenging decisions corporate IT leaders must face throughout their career: should we keep this in-house, or should we outsource it? Understanding the nuances of the MSP vs internal IT debate is the first step to making an informed choice for your business.

One service can’t connect to another (or can’t establish a database connection) – underneath this simple definition, there can be two very different conditions. First – we may have a service process down. In this case, the Kernel stack is operational, so we are getting the packet back, indicating the connection was refused. Second – when network flow is completely disrupted due to connectivity issues, firewall, or a node being completely down.

In the ever-evolving world of network operations, staying ahead of the curve is crucial. With the exponential growth of data, increasing complexity of networks, and rising demand for seamless connectivity, traditional network management methods are becoming insufficient. Artificial Intelligence (AI) is the transformative technology poised to radically transform network operations. By integrating AI into network management, organizations can achieve unprecedented efficiency, reliability, and performance.

I was just asked how to troubleshoot an HTTP Error 500.19 - Internal Server Error when trying to launch an ASP.NET Core website on IIS. I have seen this error too many times for both ASP.NET and ASP.NET Core so decided to write a blog post about at least one, obvious, fix. The problem happens when deploying the ASP.NET or ASP.NET Core website to IIS and getting the following error message in the browser.