Ok, no doesn't seem like the exception details will help you.
What _will_ help you track it down, though is to enable logging.
Code:
<log4net>
<!-- Define some output appenders -->
<appender name="rollingFile" type="log4net.Appender.RollingFileAppender,log4net" >
<param name="File" value="log.txt" />
<param name="AppendToFile" value="true" />
<param name="RollingStyle" value="Date" />
<param name="DatePattern" value="yyyy.MM.dd" />
<param name="StaticLogFileName" value="true" />
<layout type="log4net.Layout.PatternLayout,log4net">
<param name="ConversionPattern" value="%d [%t] %-5p %c [%x] <%X{auth}> - %m%n" />
</layout>
</appender>
<appender name="NHibernateFileLog" type="log4net.Appender.RollingFileAppender">
<file value="logs/nhibernate.txt"/>
<appendToFile value="true"/>
<rollingStyle value="Size"/>
<maxSizeRollBackups value="10"/>
<maximumFileSize value="200KB"/>
<staticLogFileName value="true"/>
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%d{HH:mm:ss.fff} [%t] %-5p %c -> %m%n"/>
</layout>
</appender>
<!-- Setup the root category, add the appenders and set the default priority -->
<root>
<priority value="ALL" />
<appender-ref ref="rollingFile" />
</root>
<logger name="NHibernate" additivity="false">
<level value="DEBUG"/>
<appender-ref ref="NHibernateFileLog"/>
</logger>
</log4net>
as a child of configuration in app.config.
and
Code:
<section name="log4net" type="log4net.Config.Log4NetConfigurationSectionHandler,log4net" />
as a child of configurationSections, given that you have included the log4net assembly in the application.
If you then look up that file which is created when you run the program, NHibernate will have written debug information to that.
On the other hand, I agree, learning the basics should be easy enough. Try following the tutorial to the point instead, and have a look at codeproject and Billy McCafferty's articles there for a more thorough understanding of what you can do.
(and when you get to version 1.2 of his articles, consider my comment under the name [echo] instead of his own architecture in the enterprise app)