The random, off-topic thread.
Originally Posted by daktruckie99,Jan 4 2008, 11:14 AM
3-day work weeks ROCK! I'm used to my 4 day week every other, but 3 is even better! 
I would almost rather a 5 day week, so I don't have to get it all done in 3... but who am I kidding, I still have time to post!
Can someone fix this for me? Thanks.
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
.NET Runtime Optimization Service (clr_optimization_v2.0.50727_32) - Failed to compile: Microsoft.ReportingServices.QueryDesigners, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 . Error code = 0x80070002
I can suggest a few fixes:
1) If you do not try to optimize the service, you will not get an optimization error.
2) If you do not try to compile, you will not get compilation errors.
What are you actually trying to do? .NET can be easy and it can also be a MF PITA
1) If you do not try to optimize the service, you will not get an optimization error.
2) If you do not try to compile, you will not get compilation errors.
What are you actually trying to do? .NET can be easy and it can also be a MF PITA
Originally Posted by daktruckie99,Jan 4 2008, 11:53 AM
I can suggest a few fixes:
1) If you do not try to optimize the service, you will not get an optimization error.
2) If you do not try to compile, you will not get compilation errors.
What are you actually trying to do? .NET can be easy and it can also be a MF PITA
1) If you do not try to optimize the service, you will not get an optimization error.
2) If you do not try to compile, you will not get compilation errors.
What are you actually trying to do? .NET can be easy and it can also be a MF PITA

Everything I've read said that most have gotten it after install SP1 for SQL 2005, but I didn't update SQL yet. I've also changed the service from manual to started most recently so I'm curious if it will come back now.
Other than the error I have no symptoms that any users have complained about.






