After 2 days of investigation, it appears that our totally unexplained 'object reference not set to an instance of an object' error was caused by Verbose diagnostic logging being enabled and not being returned back to normal immediately after our feature upgrade.
There appears to be a bug with Verbose logging that causes unexpected errors like the above.
Note to self: If you're turning on Verbose logging, before testing the site ALWAYS return it back to its usual setting.
Source
Sharing revelations on C# and SharePoint
No comments:
Post a Comment