Hello!
We have some very nasty issues:
For some reason (probably our problem) some statements doesnt work, select does, but functions like insert doesnt work anymore (maybe the application doesnt get so far). We log although the select statements and they are made correctly. We installed then dbmonitor (yes 2 times this happened till now, which we debug. They claim it happens very frequently, that our application doesnt work well, but a new start fix it). The problem is dbmonitor doesnt show nothing. restarting the application doesnt work. deleting the user and re-adding the user on windows xp fixes the problem. We dont have a clue what could it possibly be, but the 2 times we installed dbmonitor while the application was running(we didnt want to restart since when we restart the problem is fixed) harmed our apllication so bad, we could even show the 1. form.
Any ideas what it could be or how to avoid it?
Thx in advance.
(our application was made with mydac 5.00.1.7 with delphi 7 dbmonitor was 2.10)
Application doesnt work, installing dbmonitor causes permanent crash
-
iskywalker
- Posts: 16
- Joined: Mon 25 Jun 2007 15:00
Your application and DBMonitor must be started under the same user's account. If you run them under different accounts, monitoring will not work.
If you cannot ensure running DBMonitor and your application under the same account, you can use another two ways to log SQL queries:
1) add a handler to the OnSQL event of the TMyMonitor component in your application;
2) enable logs of MySQL, for more information see the log option description in the MySQL Reference Manual.
If you cannot ensure running DBMonitor and your application under the same account, you can use another two ways to log SQL queries:
1) add a handler to the OnSQL event of the TMyMonitor component in your application;
2) enable logs of MySQL, for more information see the log option description in the MySQL Reference Manual.
-
iskywalker
- Posts: 16
- Joined: Mon 25 Jun 2007 15:00
Hello Thank you for your answer!
DBmonitor was started under the same account! Although the account is very limited, but this was in the 2nd case, in the first case it was with normal privileges. in the second case we tryied to run it as administrator:
runas /user:Administrator dbmonitor
Logging the application is a nice idea (which i already thought to use), but it does explain why the application does crash on the start, and why dbmonitor doesnt show nothing (after and before closing the broken apllication). Logging the mysql directy on the server isnt also an option for us, since the error of our application is hard the reproduce and the enterprise in which our apllication is running have lots of access, so it would be like to look for a needle in a haystack.
Is there a way in which dbmonitor can compromise the running application so severily that it crashes?
DBmonitor was started under the same account! Although the account is very limited, but this was in the 2nd case, in the first case it was with normal privileges. in the second case we tryied to run it as administrator:
runas /user:Administrator dbmonitor
Logging the application is a nice idea (which i already thought to use), but it does explain why the application does crash on the start, and why dbmonitor doesnt show nothing (after and before closing the broken apllication). Logging the mysql directy on the server isnt also an option for us, since the error of our application is hard the reproduce and the enterprise in which our apllication is running have lots of access, so it would be like to look for a needle in a haystack.
Is there a way in which dbmonitor can compromise the running application so severily that it crashes?