You're the 3rd customer who has experienced this specific random errors. Unfortunately, we're still unable to repro even after using clues from the previous 2 reported issues. Fortunately, there was a workaround (or two).

The first issue can be read here.  http://www.ideablade.com/forum/forum_posts.asp?TID=1885 - http://www.ideablade.com/forum/forum_posts.asp?TID=1885 . In this particular case, the workaround was to refactor out the IPrincipal, IIdentity interface to using DevForce UserBase class. For example,

public partial class User : IbEm.Entity, IPrincipal, IIdentity to public partial class User : IbEm.Entity, IdeaBlade.EntityModel.UserBase

The second issue was sent through the support web form so it's not available to be shared. But in that particular case, the customer's workaround was to remove his custom LoginManager entirely.

So with that said, I'm hoping your case can provide more clues so we can repro and pin this down. The previous 2 cases (and your case?), seem to point that the problem is somewhere within the security model. Would you be able to provide the implementation of your SecAppUser class and the class this property is defined on? And so far, are you seeing the exception on this property only?

 

I will follow up shortly.

 

I have a temp principal object I am working with and for testing I had added an IEnumerable of SecUserPrivilege. When a user (SecAppUser) in the LoginManager and then I was setting GcsPrincipal.Privileges = user.SecUserPrivileges. If I build this collection (using say a privilege class) rather then using the navigation I do not get the null reference. Does that make sense?

 

I have attached (or am going to try to) a zip with the loginmanager and the model. There are no partials on the model. The loginmanager as included does not erro, but I commented the line that would make it throw the randomness.

 

http://www.ideablade.com/forum/uploads/531/nullreference.zip - uploads/531/nullreference.zip

Would you be able to upload your debug log during a failed run? I have created test cases with a similar LoginManager and a Principal object structure but I still would like to know what kind of operation that we're doing on the client that will trigger the exception. Thanks.

Just want to follow up on this to see if you'll be able to provide the information above. It will greatly help me track down this curious bug. Thanks!

 

My computer failed since then and since I had fixed our app when I was done rebuilding my computer I forgot all about this problem. That sample was on the old PC and I can't remember the specifics. I am going over my source control history to see if I can find the source that had the problem and maybe it will refresh my memory.

 

I do remember that if I returned a collection of entities that had a navigation property in an IPrincipal (in this case from my login manager) it would lead to the error. I believe if I removed the navigation property I did not have the problem or if I created a custom object (my final soluction) to fill the collection there was no problem. There was no specific item that triggered the exception that I could track down. It could have been related to checking IsInRole (which did not linq on that collection) but I had nothing that directly accessed the navigation property that was throwing the null exception. Also at the time of error if you inspect the value that just threw the exception...it was NOT null. To get the error I would just refresh the page over and over until it eventually threw the error. On each row it would check IsInRole which is in that code I included above. I was calling the

 

public bool IsInRole(string componentCode) { //TODO: revisit return (from item in Components where string.Concat(item.SecAppCatCd + item.SecAppComp).ToUpper() == componentCode.ToUpper() select item).FirstOrDefault().IsNotNull(); }

 

Sorry I dropped this...

Hi midnit;