Sunday, November 29, 2015

iis - Anticipating/preventing patch or upgrade problems on database/web servers

I maintain 2 environments in my current project, 2 servers (1 Web Server & 1 SQL Server) for both production and Test. Last month we installed/upgraded to the lated Microsoft patches/securities and the Report Manager from Reporting Services stopped working in the Test database server. After days of troubleshooting I found that the ASP.NET 2.0 Web Service Extension in ISIS was completely removed and everything was set to prohibited.



I can't say for sure but I think this was caused by the patch/updated that I'd done on that server a few day prior. What can one do to anticipate or prevent these types of impacts on SQL Server, Reporting Services, IIS, ASP.NET when a patch is installed?

No comments:

Post a Comment

linux - How to SSH to ec2 instance in VPC private subnet via NAT server

I have created a VPC in aws with a public subnet and a private subnet. The private subnet does not have direct access to external network. S...