It can have several causes: - Invalid SQL used to load the collection; - Invalid/wrong foreign keys specified in the mapping; - The session that the entity was loaded from has been disposed while some of its lazy properties haven't been loaded; - ...
Have a look at the InnerException, it may give more clues. RP On Monday, January 5, 2015 9:11:37 PM UTC, Anthony Nadar wrote: > > Is the bug "NHibernate.Exceptions.GenericADOException: could not > initialize a collection" resolved? > > We are not sure why this occurs, as per different forum comments, this > seems to be related to session issues, while a entity is being used by one > session, other session tries to access the same entity. > > Is this how NHibernate is designed to work, or a fix is needed for this > (if not fixed in earlier releases)? > > Regards, > Anthony > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers. For more options, visit https://groups.google.com/d/optout.
