Closed JacobIU closed 9 years ago
Hi @JacobIU, I have no idea what's going wrong (the primary reason, I don't work with .NET for last 3 years) - but I would suggest you clone that repo, build a debug version of assembly and rebuild your project against it. You will get valuable insights and maybe will upload PR with fix.
So, some poking around and I think I understand what is at play. If you don't have
<elmah>
<security allowRemoteAccess="true" />
</elmah>
defined, then elmah cannot be accessed remotely. Apparently, one of the side effects of this is the NullReferenceException
. So it's not the cause, it's a symptom. If you'd like, I'll make a pull request and update the readme.
False alarm. I don't think that's it. I need to do some more troubleshooting.
Okay, sorry, I think I can now confirm this was the problem. My theory is that the underlying error message from elmah caused ControllerContext
to be null, which caused the exception.
Pull Request #64 should fix this. Let me know if you have more issues after the next release.
Good afternoon,
I've recently added the elmah-mvc solution to a project and it works perfectly in iisexpress in local development. However, when deployed to the web server, it throws this NullReferenceException. I've browsed the code, but without a line number and no way to reproduce it locally, I don't have any idea about how to narrow it down any further. There are other applications on this IIS instance that use Elmah successfully, so I don't suspect a server problem.
I'm really at a loss. I'm happy to help troubleshoot, but I'm not even clear what else to try.