My IT department recently posted a mass of updates to our servers. I have a Server 2003 R2 (x86) that is a 1 tier TFS 2008 host using SDQL Server 2005 std edition. After this set of updates the maintenance plans are failing with "Bad IL Range". They don't even log that they have started in the SQL logs. After researching it appears to be related to a .Net corruption.
I have tried backing out the updates to no effect. A SQL Repair did not change anything. I have tried repairing .Net 2.0 - the screen never come up after the "gathering information" message. A .Net re-install just says that it is already installed.
Anybody have any ideas? I'm tired of backing up databases by turning off SQL server and manually copying files (not to mention the problem with growing log files).
Thanks in advance.