Page 2 of 2
Posted: Tue 15 May 2007 09:57
by Alexey
Does the problem persists?
Posted: Tue 15 May 2007 13:58
by Zoran
Yes. After I switch to version 2.* and restart IIS, everything works fine again. I can try using another development environment if You think it may help.
Posted: Wed 16 May 2007 12:44
by Alexey
I don't get you. If you are using PostgreSQLDirect for .NET1.1, why do you switch to .NET2.0 in IIS?
Could you please clarify?
Posted: Wed 16 May 2007 13:59
by Zoran
Sorry. After I switch back to Corelab driver version 2.55 (not .Net 2.0) everything works fine. .Net 1.1 + Corelab 2.55 => OK. .Net 1.1 + Corelab 3.0 => error.
Posted: Thu 17 May 2007 06:31
by Alexey
Which error? "Could not load type CoreLab.Common.DbConnection"? If yes, you should make sure that all 2.55 assemblies are removed during uninstall.
Bug fixed
Posted: Thu 24 May 2007 20:44
by Zoran
Now Corelab 3.0 works. I suppose I managed to reference a wrong Corelab DLL.
It seems that the problem with aborted transaction doesn't exist anymore. After almost 2 days I haven't received any error. Before the fix, there used to be dozens of them.
Posted: Fri 25 May 2007 07:04
by Alexey
Terrific!