Bug #17508 | Update query causes Access Violation during parameter binding | ||
---|---|---|---|
Submitted: | 17 Feb 2006 8:20 | Modified: | 30 Jun 2007 14:51 |
Reporter: | David Stevenson | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / ODBC | Severity: | S2 (Serious) |
Version: | 3.51.12 | OS: | Windows (Windows XP w/SP2) |
Assigned to: | CPU Architecture: | Any |
[17 Feb 2006 8:20]
David Stevenson
[27 Feb 2006 17:23]
Jorge del Conde
Hi! I was unable to reproduce this bug. Can you please send me your queries and create table statements (and possibly even a project file) so that we can track this bug down ? Thanks!
[3 Mar 2006 2:15]
David Stevenson
Alright! I have found a dataset that will crash the ODBC connector. Attached is a database schema: schema_msproject. Run this schema using 'source' in MYSQL command client. It will create a database: 'proj1'. Open Microsoft Project 2003 (with most recent service pack), and open the file Shelby...75.mpp. Click save as... and select ODBC. Save it using the MYSQL ODBC Driver to the database proj1. IT WILL CRASH. Then... reimport the schema. Open "Shelby ...60.mpp" and save it to the same database. IT WILL NOT CRASH. the only difference between the two is that the last 15 tasks have been deleted. Does it have to be the last 15 tasks? NO! We've tried lots of combinations of deleting tasks, and they all seem fail with between 60 and 75 tasks.
[3 Mar 2006 2:16]
David Stevenson
The MYSQL schema that sets up an MSProject database with the right tables.
Attachment: schema_msproject (text/plain), 34.23 KiB.
[3 Mar 2006 2:19]
David Stevenson
A sample MSProject 2003 file with 60 tasks
Attachment: Shelby Development-60.zip (application/x-zip-compressed, text), 100.99 KiB.
[3 Mar 2006 2:19]
David Stevenson
A sample MSProject 2003 file with 75 tasks.
Attachment: Shelby Development-75.zip (application/x-zip-compressed, text), 167.39 KiB.
[5 Jun 2006 8:40]
Tonci Grgin
Hi David. Thanks for your problem report and sorry for the delay. I don't have MS Projects so I have to ask you to provide small standalone test case in VS2003 showing this problem.
[5 Jul 2006 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[12 Mar 2007 14:04]
vivid me
I have the problem and I want to use MySQL ODBC to save/load data to/from MS-Project. I use Connector 3.51 and MySQL 4.1.10a-nt. I tried a big MPP file containing above 1000 activities and after saving around 500 rows of tasks error entitled: "[MySQL][ODBC 3.51 Driver][mysqld-4.1.10a-nt] mysql server has gone away" happen and remaining data left away!!!! what is the solution!!! New connector or New MySQL or NONE!
[12 Mar 2007 15:11]
vivid me
By the way!!! I checked back the data inserted in MySQL and I found that all tasks have been inserted into table! but during saving to ODBC the error which I said still occurred! I don't know whether this error makes further ploblem in data or not! I check a 2140 task project in MSP and all tasks got in the table. I have made some changes to the "schema_msproject.txt" file: here is the change (is it OK or not): find: "ENGINE=InnoDB DEFAULT CHARSET=latin1;" replace with: "TYPE=MyISAM;" Help me if "[MySQL][ODBC 3.51 Driver][mysqld-4.1.10a-nt] mysql server has gone away" error does something to my data or not. Thanks Further
[12 Mar 2007 15:50]
Tonci Grgin
Hi, AFAIS > find: "ENGINE=InnoDB DEFAULT CHARSET=latin1;" > replace with: "TYPE=MyISAM;" MS Project is trying to save data to InnoDB table while, possibly, you have InnoDB dissabled in your my.ini file. You should search for and modify respective settings to make your *environment* work. > Help me if "[MySQL][ODBC 3.51 Driver][mysqld-4.1.10a-nt] mysql server has gone away" error does something to my data or not. Check general query log from server to see what was sent to MySQL server.
[13 Mar 2007 13:59]
vivid me
MSP fills the tables in MyISAM type, but two table left empty after the error which I explain above occures, these two are: msp_conversions msp_string_types does anybody knows the problem? how can I be sure that all data are saved by MySQL ODBC from MSproject?
[28 Jun 2007 9:23]
Vishnu Naicker
Running MS Projects 2002 Professional via ODBC 3.51.12. Tried latest version 3.51.16 (loads properly). Open MS Project crashes. Database version: 5.0.16nt. Client application: Microsoft AccessXP with latest service pack. Access connection is fine. Can load/update fine. The problem is trying to load larger MS project files via odbc. The problem is similar to the previous posts. Tables were InnoDB. Converted them to MyISAM. Problem still persists. Tried loading larger proect files into MS AccessXP via ODBC. Works fine. Please help. The problem seems to be with the ODBC connection as the MSAccess update is very quick with MS Projects. Hardware: HP Compaq NC8000 Operating System: Windows 2000 Professional Tried this on: Hardware: Intel 945GP Operating System: Windows XP Professional Problem persists.
[28 Jun 2007 12:10]
Tonci Grgin
Hi all. As I said I don't have MS projects nor do I know much about it so we'll have to take a longer way around... Please attach: - General query log from MySQL server from the moment you start import till the moment error occurs (and more if insert / load continues) - my_sql_sqrevr.err file from MySQL servers data directory - ODBC trace from driver manager - SHOW CREATE TABLE for table that fails - my.ini / cnf file from MySQL server I am willing to give this one more try.
[29 Jun 2007 6:59]
Vishnu Naicker
Resolved error loading file. Switched on the error log and founf the (Got a packet bigger than 'max_allowed_packet' bytes) SET GLOBAL max_allowed_packet=10000000; This resovled the error. Thanks for the pointers. Will try larger project files. Is there a setting that must be made on the client side? thank you for the prompt feedback.
[29 Jun 2007 7:24]
Vishnu Naicker
I loaded an MS Project file containing 10,000 activities and it went fine. I had to increase the max_packet_allowed to 32,000,000. Although a 10,0000 activity schedule is unrealistic. Its a good test of the MySQL server. Thanks again for the good work.
[30 Jun 2007 14:51]
Tonci Grgin
Vishnu, it is hard to tell what happens in all of the clients accessing MySQL server, as you can tell first-hand, so we need to get as much info as possible. In any case, I am glad the problem is solved.