The Forum has been Updated
The code has been upgraded to the latest .NET core version. Please check instructions in the Community Announcements about migrating your account.
I'm in the process of moving my MySQL databases over to a new server and the Snitz database is proving problematic and I'm getting a HTTP:500 error after pointing the connection string to the new server's IP
The host has said..
Is there an easy fix for this editing the current connection string or is it a case of loading the ODBC 5.1 driver into the new server?
Here is my current connection string (important stuff edited out)
Thanks
The host has said..
it looks like because your previous MYSQL version was 5.1 and the new one is 5.5 that the connection information you are using is not supported
Is there an easy fix for this editing the current connection string or is it a case of loading the ODBC 5.1 driver into the new server?
Here is my current connection string (important stuff edited out)
Code:
strConnString = "driver={MySQL ODBC 5.1 Driver};option=16387;server=000.000.00.000;user=edit;password=edit;DATABASE=edit;" '##MySQL w/ MyODBC v5.1Thanks
Posted
Okay, donations in lieu of 'I'm a Genius' please forward to...
SOLVED IT
The issue was multiple,
Firstly the migration process from MySQL to MariaDB didn't work as expected so the resolve was to dump the database from the old server and import it into the new.
Then, for some reason Snitz software, MariaDB or the Linux OS did not like the fact that the table names were in lowercase so running multiple SQL commands to convert them from lowercase to upper case seemed to do the trick
The connection string I used is...
strConnString = "driver={MySQL ODBC 5.1 Driver};option=16387;server=IPAddress;user=odbd_user;
password=odbc_pwd;DATABASE=obdb_test;Port=3306;" '##MySQL w/ MyODBC v5.1
All other databases that were migrated with the exception of one and the Snitz db worked first time, so perhaps it is something to do with the code within both softwares making the db tables case sensitive, possibly
SOLVED IT
The issue was multiple,
Firstly the migration process from MySQL to MariaDB didn't work as expected so the resolve was to dump the database from the old server and import it into the new.
Then, for some reason Snitz software, MariaDB or the Linux OS did not like the fact that the table names were in lowercase so running multiple SQL commands to convert them from lowercase to upper case seemed to do the trick
The connection string I used is...
strConnString = "driver={MySQL ODBC 5.1 Driver};option=16387;server=IPAddress;user=odbd_user;
password=odbc_pwd;DATABASE=obdb_test;Port=3306;" '##MySQL w/ MyODBC v5.1
All other databases that were migrated with the exception of one and the Snitz db worked first time, so perhaps it is something to do with the code within both softwares making the db tables case sensitive, possibly
Posted
Well I spoke too soon, not so much with the above but regarding it all working ok, for some reason topic.asp post.asp post_info.asp threw up HTTP500 errors but these files are modified from the originals. Loading the originals fixed the error but then caused problems with various mods installed including our site supporters... not good 
Two ways around it I think, one is to go through a batch of fresh files, ie a new install, and add mods as required until I find out which one(s) don't work - very time consuming
OR, see if it's possible to get my hosts to modify the OS system files so that the Linux version accepts lower and upper case in MySQL. If that's possible then I can re-import a dump of the database and see if it works without further modification - the easiest route I think
Any thoughts?
Two ways around it I think, one is to go through a batch of fresh files, ie a new install, and add mods as required until I find out which one(s) don't work - very time consuming
OR, see if it's possible to get my hosts to modify the OS system files so that the Linux version accepts lower and upper case in MySQL. If that's possible then I can re-import a dump of the database and see if it works without further modification - the easiest route I think
Any thoughts?
Posted
by default the snitz code uses UPPERCASE table names when creating the database and in all it's queries, if yours were lower case then they were possibly created outside of the snitz setup code, plus your previous MySQL db must have been set to be case insensitive otherwise it would not have worked.
It my be laborious but you are probably best fixing whatever code/tables needs to be fixed to get the queries to work
It my be laborious but you are probably best fixing whatever code/tables needs to be fixed to get the queries to work
Posted
Our Snitz was first installed about 15/16 years ago Huw and over time it has been upgraded and modified.
The hosts are adamant they will not/can not make it case insensitive for what ever reasons and to be honest I don't have the time to go through the files to see what's what or not, I looked through topic.asp yesterday, all 1500+ lines within ours, and found a couple of bits but not sufficient to resolve the problem.
Likewise to start with a fresh copy of Snitz then add the mods and changes one at a time to find out which or what is causing the issue is again a big task and one I don't have time for at present.
Bearing in mind the future I'm looking at other hosting options as I think the present ones will not be the best option
The hosts are adamant they will not/can not make it case insensitive for what ever reasons and to be honest I don't have the time to go through the files to see what's what or not, I looked through topic.asp yesterday, all 1500+ lines within ours, and found a couple of bits but not sufficient to resolve the problem.
Likewise to start with a fresh copy of Snitz then add the mods and changes one at a time to find out which or what is causing the issue is again a big task and one I don't have time for at present.
Bearing in mind the future I'm looking at other hosting options as I think the present ones will not be the best option
Posted
Just an update - I'm in the process of moving hosts