Not Enough Timers available when instantiating a TMyQuer
Not Enough Timers available when instantiating a TMyQuer
When the following steps are executed, (in the current server environment), instantiating the main form produces a 'Not enough Timers available' exception after about 10 seconds of doing something. Note this is without even assigning a connection to the query or even assigning a MySQL server to the connection. It is purely an object instantiation issue, not a connection issue. This occurs every time without fail.
Using MyDAC 5.50.0.36 compiled with Borland Delphi 2005 Professional and AtoZed Intraweb v7.2.36...
1) Create a new ISAPI extension application and elect not to Pool Data Connections.
2) Drop a TMyCOnnection and a TMyQuery on the main form, both with all parameters left as default.
3) Compile as an ISAPI DLL and deploy
A production application with the same components (and now with the same repeatable error) was working fine for 6 months until today and no changes had been made to the application at that time.
Another ISAPI application in the same environment compiled with an earlier version of MyDAC is still working.
The above 2 points would indicate that a server O.S / IIS configuration change or upgrade is now incompatible with this version of MyDAC. I am awaiting confirmation of configuration and O.S changes that may have taken place on the server but wanted to post asap to see if there was a known issue/fix. I have checked the release notes http://www.devart.com/mydac/History.html for later versions but this issue is not discussed.
Using MyDAC 5.50.0.36 compiled with Borland Delphi 2005 Professional and AtoZed Intraweb v7.2.36...
1) Create a new ISAPI extension application and elect not to Pool Data Connections.
2) Drop a TMyCOnnection and a TMyQuery on the main form, both with all parameters left as default.
3) Compile as an ISAPI DLL and deploy
A production application with the same components (and now with the same repeatable error) was working fine for 6 months until today and no changes had been made to the application at that time.
Another ISAPI application in the same environment compiled with an earlier version of MyDAC is still working.
The above 2 points would indicate that a server O.S / IIS configuration change or upgrade is now incompatible with this version of MyDAC. I am awaiting confirmation of configuration and O.S changes that may have taken place on the server but wanted to post asap to see if there was a known issue/fix. I have checked the release notes http://www.devart.com/mydac/History.html for later versions but this issue is not discussed.
-
Challenger
- Devart Team
- Posts: 925
- Joined: Thu 17 Nov 2005 10:53
-
Challenger
- Devart Team
- Posts: 925
- Joined: Thu 17 Nov 2005 10:53
In the mean time, can you expand on what event may have triggered the bug on the server as it only started to fail recently without changes to the application.?
Also, is there any options I can set/unset on the Query object that will avoid the error for now?
Finally, how can I find out when the patch has been released. Will I be contacted?
Many thanks.
Also, is there any options I can set/unset on the Query object that will avoid the error for now?
Finally, how can I find out when the patch has been released. Will I be contacted?
Many thanks.
Any comment?
Could someone from the Devart team comment re my last post?
Many Thanks.
Many Thanks.
-
Challenger
- Devart Team
- Posts: 925
- Joined: Thu 17 Nov 2005 10:53