This forum has been disabled. Please visit our new Help Desk at help.jitterbit.com

Access to MySQL

Questions and answers for configuring and deploying your integrations.

Access to MySQL

Postby jlandry on Mon Jun 26, 2006 12:21 pm

I'm currently trying to bring a couple fields from Access to MySQL as a test before I try with the whole database.

After successfully importing 5,900 or so of the 10,000 entries, the operation fails and this shows up in the logs:

Fatal Error:
Transformation failed

Error:
Failed to perform transformation.
Transformation failed.
Last Error - Insert SQL statement is empty (Insert mode). [CODE:10094]

Insert SQL statement is empty (Insert mode). [CODE:10094]

Unable to insert data into database. [CODE:10209]


For detailed information please check the file 'C:\Program Files\Jitterbit Integration Server\DataInterchange/Temp/LOG/13_37cefd30-9921-4661-bc36-871449ebb121.txt'.


I've looked in the db to see what might have caused the failure and I can't seem to see what could be the problem. All entries around the final imported entry look to be fine.

I also looked for the temporary log file "13_37cefd30-9921-4661-bc36-871449ebb121.txt" but had no luck finding it.

I've verified that the following is specified in jitterbit.conf:
Code: Select all
[TransformationEngine]
WriteLog=1


Currently running Jitterbit Server 1.1.0 PREVIEW 4 on Windows XP Pro SP2 with Jitterbit Client 1.1.0 (Preview 2) on Windows 2000 SP4.
jlandry Bookmark and Share
Community Member
Community Member
 
Posts: 11
Joined: Mon Feb 13, 2006 11:36 am
Location: Connecticut, USA

Postby Frank on Mon Jun 26, 2006 3:10 pm

Hi jLandry,

If I have the debug log, I might be able to tell what's the problem. Since you have turned on the WriteLog, the debug log was already generated. The file name is MXForm_trans*.txt and can be found under the directory
C:\Program Files\Jitterbit Integration Server\DataInterchange\Temp\Debug

If you can't tell which file to send, you can clear the directory and run the transformation to generate the file again.

If it is possible, please also send us the jitterpak for the project and input access database. We might have to duplicate the run here to find the problem.

My email is
frank.chu@jitterbit.com

Frank
Frank Bookmark and Share
Jitterbit Hero
Jitterbit Hero
 
Posts: 136
Joined: Mon Feb 13, 2006 12:40 pm

Postby jlandry on Tue Jun 27, 2006 2:00 pm

I was able to fix the problem. Turns out there were some blank entries in Access making SQL upset. I was able to make it ignore them. Thanks for pointing me in the right direction!
jlandry Bookmark and Share
Community Member
Community Member
 
Posts: 11
Joined: Mon Feb 13, 2006 11:36 am
Location: Connecticut, USA


Return to Using Jitterbit


SourceForge.net Logo  open source integration