Let me know if you can still log on with the SQL Server Management Studio.
Kev
I tried to log on as "sa" user and that is working OK.
I'll try to log on as "Web" user as soon as I come from work today and post results here.
Let me know if you can still log on with the SQL Server Management Studio.
Kev
I am only guessing here, but it could be a DLL problem.With the latest release, with the extended 500 error, I get the following message:
[AnyDAC][Phys][MySQL][LIBMYSQL] MySQL server has gone away
FYI I use a different server for the MySQL database and it's not gone for sure so it seems like it looses the connection with it.
I am only guessing here, but it could be a DLL problem.
Could you check that the version of libmysql.dll that is in the application directory is the same as the one in the MySQL install directory.
If not, then replace it with the MySQL one.
Regards
Kev.
The interface currently holds the same connection open all the time, and just checks for connectivity at the beginning of each request. This seems OK for MSSQL, as that is what I am using without getting these issues.I am only guessing here, but it could be a DLL problem.
Could you check that the version of libmysql.dll that is in the application directory is the same as the one in the MySQL install directory.
If not, then replace it with the MySQL one.
Regards
Kev.
The libmysql.dll in my MySQL directory did have a different size. Probably a different version so I replaced the one in the MP Web interface directory and restarted the interface. Lets see what it does after a few hours...
Edit: I tried it again and the same error appears. Seems it doesn't fix my problem.
The interface currently holds the same connection open all the time, and just checks for connectivity at the beginning of each request. This seems OK for MSSQL, as that is what I am using without getting these issues.I am only guessing here, but it could be a DLL problem.
Could you check that the version of libmysql.dll that is in the application directory is the same as the one in the MySQL install directory.
If not, then replace it with the MySQL one.
Regards
Kev.
The libmysql.dll in my MySQL directory did have a different size. Probably a different version so I replaced the one in the MP Web interface directory and restarted the interface. Lets see what it does after a few hours...
Edit: I tried it again and the same error appears. Seems it doesn't fix my problem.
I will implement a "timeout" on the connection - say 10 minutes of inactivity - and force a re-connect at the next request. It would appear that the MySQL server is "dropping" the open connection without disconnecting the socket (perhaps).
This may be a work-around for the problem.
I will post it as soon as I can, but I am a little busy for the next week...
Regards
Kev