It is a classic problem occurred when upgrade from Windows Server 2008 to Windows Server 2008R2. You can try to click the repair in program feature and restart the application pool would solve it.
If the answer is the right solution, please click "Accept Answer" and kindly upvote it. If you have extra questions about this answer, please click "Comment".
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.