Home/ Questions/Q 385681
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-12T15:30:13+00:00

Background I have a BLL DLL that uses NHibernate. I share the same BLL

  • 0

Background

I have a BLL DLL that uses NHibernate. I share the same BLL between a client application and the WCF service (even though the client runs on another machine).

I can successfully use either SqlServerCe or SqlServer driver with the BLL with the client application but can only use the SqlServer driver for the WCF.

If I change the hibernate.cfg.xml to use SQL Server I am able to use the service as required with no exceptions being thrown.

The Error

The exact error from the log4net output is:

2421, 5, DEBUG, NHibernate.Connection.DriverConnectionProvider, (null),Obtaining IDbConnection from Driver 
2483, 5, DEBUG, NHibernate.Connection.DriverConnectionProvider, (null),Exception thrown obtaining connection: Exception has been thrown by the target of an invocation.

I also have the following code in my WCF code behind file:

AppDomain.CurrentDomain.SetData("SQLServerCompactEditionUnderWebHosting", true);

NOTES

  • WCF bin directory contains all required DLL’s for NHibernate and SqlServerCe
  • Does not matter if System.Data.SqlServerCe.dll is in the GAC
  • Does not matter if System.Data.SqlServerCe.dll is added to the web.config file under assemblies
  • Operating Systems is Windows Server 2003 R2 SP2
  • .NET Framework 3.5SP1 installed
  • Visual Studio 2008 installed
  • Just incase, I uninstalled anything to do with compact edition but this still did not resolve the issue

The Question

How would you try and determine why NHibernate cannot load the SqlServerCe framework?

What forensic analysis would you perform to try and accurately determine the problem so that you can then find ways of resolving it?

Update 1

Incase it was my code I just created a simple website and am able to successfully use the ORM to insert and retrieve records using a hard-coded path to the SDF database. If I use the same hibernate configuration file for the webservice then exception is generated. This does narrow down the problem to the WCF implementation.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Well, clearing the ASP.NET temp cache did not do anything and deleting and republishing my site did nothing, but reverting to an VM Snapshot on the Windows 2003 R2 SP2 O/S did!

    An update or myself must have done something to the OS that caused the problems.

    I have a different problem now as the SQL is not successfully running under the environment but at least the NHibernate driver is loading and running to which this question was asking.

    Update: Yes, I can only get NHibernate talking to SQL Server still and this is fine for the webservice endpoint. We will investigate the issues at a later stage. Marking this answer as the correct one as no other comments have been added.

    • 0