> Same thing happened to us. We reinstalled .NET frameworks and Visual Studio(s) and then
> ran
aspnet_regiis -i. That fixed the problem
...Which is all very well, except that Symantec admit that, with this patch in place, when you run
aspnet_regiis, it throws an exception (which is exactly what I'm seeing when I try to run it)
http://service1.symantec.com/SUPPORT/ent-security.nsf/docid/2010012709305848
It's shocking that they let this bug through, and even worse that they are demanding that users
request
a patch to fix the issue, rather than making it widely available. After all, this is a problem which they
admit has the following hilarious side-effect:
Symptoms:
-.NET Applications do not function.
-Commands such as aspnet_regiis.exe throw an exception.
Sounds a bit critical to me...
(And it wasted hours of my time yesterday, as I believed the
Event Viewer error, saying that it was a
user-rights issue.)
Shocking.