"socket error 10061" with IBDac v4.0.2

Discussion of open issues, suggestions and bugs regarding IBDAC (InterBase Data Access Components) for Delphi, C++Builder, Lazarus (and FPC)
Post Reply
birmain
Posts: 1
Joined: Wed 27 Oct 2010 10:27

"socket error 10061" with IBDac v4.0.2

Post by birmain » Thu 20 Oct 2011 18:47

Hello
I'm using Delphi 7 and use InterBase Data Access Components v4.0.2. When I run the application from the Delphi environment, every time you open or close a transaction skips the exception "socket error 10061."

When the application is executed outside the environment does not miss any exception.

This happens with both 1.5.6 and 2.5.1 Firebird, but everything works fine when I use the components v3.10.0.16

This exception is serious?, Is a bug?, How could solve?

I hope your news

AndreyZ

Post by AndreyZ » Mon 24 Oct 2011 10:43

I cannot reproduce the problem. Please try creating a small sample to demonstrate this problem and send it to andreyz*devart*com.

mariusz
Posts: 62
Joined: Wed 16 Jul 2008 21:04
Location: Poland / Poznan
Contact:

Post by mariusz » Mon 05 Dec 2011 21:28

Hi!

I use D7 + IBDAC 4.1.3 + FB (32) 2.5.0.26074. I found same error today, after update IBDAC from 3.60.0.24 version.
My project is quite big, so I have problem making "small sample" especially, that I have other projects that doesn't make any problem.

AndreyZ

Post by AndreyZ » Tue 06 Dec 2011 11:25

This error can be caused by the TIBCSQLMonitor component. If there is no dbMonitor running or the port is incorrect, the "Socket Error 10061" error is raised. To solve the problem in this case, you should set the TIBCSQLMonitor.Active property to False, or set the TIBCSQLMonitor.Option.moDBMonitor property to False. Please note that in this case you will see the 'Socket error 10061' error only if you run your application from IDE. You will not see this error when you run the executable file of your application.

mariusz
Posts: 62
Joined: Wed 16 Jul 2008 21:04
Location: Poland / Poznan
Contact:

Post by mariusz » Wed 07 Dec 2011 08:51

You are right!
Settings TIBCSQLMonitor.Option.moDBMonitor = False solves the problem.

Thank you :)

AndreyZ

Post by AndreyZ » Wed 07 Dec 2011 11:39

It's good to see that this problem was solved. If any other questions come up, please contact us.

Post Reply