As you both have suggested it turned out to be a wrong version of the Oracle Data Provider on the production server. It was one version older than on the development machine, and did not properly support Entity Framework.

Thanks for all help; I would have used some time to figure out the connection between the "general purpose" exception thrown by DevForce and the ODP version.

Case closed,

Mikael

2. Debug mode ran differently than Release mode - even locally but it appeared the problem was only on the server (built in release mode).

 

What version of IIS is prod? Is your windows 64bit? Is the server? Same version of odp.net?

 

I wish you a quick resolution!

 

Is there any possibility that you can trap the exception and inspect the inner exception(s)? DevForce is throwing that exception when an ArgumentException is raised when opening the EF ObjectContext, and it appears that an ArgumentException can be thrown for any number of reasons. Since the problem occurs only when deployed, I'd guess a configuration-related problem, either with the Oracle provider or IIS. Here's a promising link to someone reporting a problem with their data provider - http://forums.asp.net/t/1692257.aspx/1.

I've put in som logging to the GetKey method. The complete log file is attached for completness.

 

 

 

The error message you're getting is somewhat general purpose, and would most commonly indicate that your IDataSourceKeyResolver hasn't been found.  Since your implementation has been found, then the next question is what is its GetKey method returning, and why does DevForce (or EF) think it's invalid?  If you can add TraceFns diagnostic messages to your code that will help isolate the problem.  The TraceFns messages will be written to the debug log, along with DevForce log messages, and are a handy tool for diagnosing problems outside of Visual Studio.  If it's not possible to modify the code ... then we'll have to think of Plan B.

My guess is it doesn't since it's throwing the exception above. Verify that the assembly containing PilenKlage.DevForceDataSource is also deployed, probed and discovered.

I have also verified that the GetKey method runs to completion and does what it should. As mentioned above, it all works when run from within Visual Studio 2010.

 

Any other ideas?

 

Thanks

You might want to ensure that the assembly containing your custom IDataSourceKeyResolver is being probed and discovered. The debug log will contain more detailed information regarding this.

See http://drc.ideablade.com/xwiki/bin/view/Documentation/logged-info for more info.

 

 

 

What am I missing in the deployment or server configuration? (The most frustrating is that I experienced this same exception early in the development process, but I'm completely unable to remember how I fixed it.)

 

Thanks