I've seen several threads on this same problem. When I try to go to any module settings as superuser I get a NullReferenceException at DotNetNuke.Security.PermissionsGrid.<>c__DisplayClass1<EnsureRole>b__0(RoleInfo r).

Yes, I have a Portal 0. Yes, I have modify permissions on the web.config.

 This became a problem after upgrading from 5.6.3.

Sebastian, your suggestion just sent me down the wrong path. TurboDNN is not the answer to every problem. I figured it out though. The nullreferenceexception was being thrown in some module settings classes, but the stack trace was extremely misleading. Someone who doesn't understand for loops copypasted the same method into these classes which led me to believe it was something that was being inherited. This is related to a platform bug in that if one settings class is broken, it breaks all the other module settings. Recycling the application pool in IIS will fix this. According to a closed bug report I found, this has been fixed in an unstable 8.(something) release. I think it may have to do with returning a new ModuleInstanceContext() if something is null, but I haven't tested it. Please share this information with the many others who are having the same issue.

 Best Regards,

 Derek