current transaction is aborted, commands ignored...

Discussion of open issues, suggestions and bugs regarding ADO.NET provider for PostgreSQL
Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Tue 15 May 2007 09:57

Does the problem persists?

Zoran
Posts: 44
Joined: Thu 28 Apr 2005 21:55
Location: Zagreb, Croatia

Post by Zoran » Tue 15 May 2007 13:58

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.

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Wed 16 May 2007 12:44

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?

Zoran
Posts: 44
Joined: Thu 28 Apr 2005 21:55
Location: Zagreb, Croatia

Post by Zoran » Wed 16 May 2007 13:59

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.

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Thu 17 May 2007 06:31

Which error? "Could not load type CoreLab.Common.DbConnection"? If yes, you should make sure that all 2.55 assemblies are removed during uninstall.

Zoran
Posts: 44
Joined: Thu 28 Apr 2005 21:55
Location: Zagreb, Croatia

Bug fixed

Post by Zoran » Thu 24 May 2007 20:44

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.

Alexey
Posts: 2756
Joined: Mon 13 Mar 2006 07:43

Post by Alexey » Fri 25 May 2007 07:04

Terrific!

Post Reply