Devart Forums

We have recently upgraded our LinqConnect Professional to 4.2 version and since then we have issues with data mapping quite often.

The typical issue is...

1. An exception is thrown when data mapping fails. And then when I reset IIS, it goes away

Any idea how to fix this issue ?

Please give us the following information:
1) the current build number (x.xx.xxx) of your LinqConnect
2) which build (x.xx.xxx) were you using previously?
3) if possible, localize the issue and send us a small test project with the corresponding DDL/DML script for reproducing
4) the full stack trace of the error