upgrade from 2.70 to 3.50.13

upgrade from 2.70 to 3.50.13

Postby trevor » Wed 29 Nov 2006 17:51

Howdy,

We recently upgraded from 2.70 to 3.50.13. Now one of my applications gives me the following errors;

[IndexOutOfRangeException: Index was outside the bounds of the array.]
CoreLab.MySql.a6.e() +794
CoreLab.MySql.a6.a(Byte[]& A_0) +138
CoreLab.MySql.b.a(a6 A_0, Int32 A_1) +150
CoreLab.MySql.b.a(e[]& A_0, Int32& A_1) +310
CoreLab.MySql.b.a(Byte[] A_0, Int32 A_1, Boolean A_2) +84
CoreLab.MySql.v.d() +858
CoreLab.MySql.MySqlCommand.a(CommandBehavior A_0, IDisposable A_1, Int32 A_2, Int32 A_3) +1902
CoreLab.Common.DbCommandBase.b(CommandBehavior A_0) +113
CoreLab.Common.DbCommand.ExecuteReader(CommandBehavior behavior) +4
CoreLab.MySql.MySqlCommand.ExecuteReader(CommandBehavior behavior) +5
DA.CorelabDA.ExecRead(String sql, CommandBehavior commandBehaviour) +92
Project1.Tools.Search(String term) +258
Project1.results.Page_Load(Object sender, EventArgs e) +2295
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +750


and;


[MySqlException: Net packets out of order: received[4], expected[1]]
CoreLab.MySql.az.a() +202
CoreLab.MySql.az.c() +27
CoreLab.MySql.b.a(e[]& A_0, Int32& A_1) +65
CoreLab.MySql.b.a(Byte[] A_0, Int32 A_1, Boolean A_2) +84
CoreLab.MySql.v.d() +858
CoreLab.MySql.MySqlCommand.a(CommandBehavior A_0, IDisposable A_1, Int32 A_2, Int32 A_3) +1908
CoreLab.Common.DbCommandBase.b(CommandBehavior A_0) +113
CoreLab.Common.DbCommand.ExecuteReader() +6
CoreLab.Common.DbCommandBase.ExecuteScalar() +29
DA.CorelabDA.ExecScalar(String sql) +109

[DatabaseException: Error Executing Database Query]
DA.CorelabDA.ExecScalar(String sql) +242
Project1.results.Page_Load(Object sender, EventArgs e) +1891
System.Web.UI.Control.OnLoad(EventArgs e) +67
System.Web.UI.Control.LoadRecursive() +35
System.Web.UI.Page.ProcessRequestMain() +772


They're completely random in appearance; I receive one or the other and it seems like I get the out of range error more. I've compiled in the licenses.licx file, and installed both 1.1 and 2.0 executables on the server, and the new dll is going up live. We're happening to query a 4.1.9 mysql server.

Would you (or anyone else) have any ideas as to why this might be happening? Is there a changelog available from 2.70 to 3.50.13, or anything major that would have changed that would impact/relate to this?

Thanks in advance!
trevor
 
Posts: 3
Joined: Mon 30 Jan 2006 21:49

Postby trevor » Wed 29 Nov 2006 20:40

for s & giggles i decided to move my data to a 5.x mysql database. things work fine now.

so for anyone else having the same problem, upgrade your old database :wink:
trevor
 
Posts: 3
Joined: Mon 30 Jan 2006 21:49

Postby Alexey » Thu 30 Nov 2006 07:17

Just for your information, the latest version is 3.50.14.
Alexey
 
Posts: 2756
Joined: Mon 13 Mar 2006 07:43


Return to dotConnect for MySQL