Page 1 of 1

Tmysqlmonitor gives error 10061

Posted: Wed 23 May 2012 13:36
by john_kuiper
Today I upgraded MyDac 5.8 to MyDac 7.1.6.
The database connection works fine sofar, but everytime I do a query to the database, I get a socketout error:
Project Bolwin.exe raised exception class SocketException with message 'Socket error 10061'.
This is only when TMySQLMonitor is set on a datamodule.

Must I set an extra option in TMysqlmonitor to get it work? DBMonitor 3.x als installed.
With version 5.8 there were no problemns at all

Re: Tmysqlmonitor gives error 10061

Posted: Wed 23 May 2012 14:20
by AndreyZ
Hello,

Such behaviour is correct. If TMySQLMonitor.Active is True and there is no DBMonitor running or TMySQLMonitor.DBMonitorOptions.Port is incorrect, the 'Socket error 10061' error is generated. You will see this error only if you run your application from IDE. You will not see this error when you run the executable file of your application.

Re: Tmysqlmonitor gives error 10061

Posted: Thu 24 May 2012 07:10
by john_kuiper
Okay.
It's still a strange behavour. Just like Indy FTP compoments in IDE.
Could this 'warning' solved in the near future. It's very annoying when debugging an application.

Re: Tmysqlmonitor gives error 10061

Posted: Thu 24 May 2012 08:44
by AndreyZ
You can avoid this problem by setting the TMySQLMonitor.Active property to False, or by removing the moDBMonitor option from the TMySQLMonitor.Options property. Using any of these ways, you will not see the 'Socket error 10061' error.