forums › forums › SQLyog › SQLyog: Bugs / Feature Requests › Migration Tool – "could Not Create Ssh Tunnel" Error
- This topic is empty.
-
AuthorPosts
-
-
May 2, 2006 at 6:02 am #9662scottahMember
I have a saved job that I have been doing almost every week for the last few months, no problems until the upgrade.
I get this terminal error
“Could not create SSH tunnel for source server.”
My connection has nothing to do with SSH…
Thanks,
Scott
-
May 2, 2006 at 6:14 am #21504peterlaursenParticipant
I think you must explain a little more in detail.
1) The category chosen is 'Migration Tool'. Is it a Migration(ODBC-import) job we are talking about?
2) What does the… tag look like in that job file?
3) “I get this terminal error” I understand that you are running SJA from command-line?
You are PERFECTLY sure that you DID specify a job-file for MIGRATION/ODBC-import?
-
May 5, 2006 at 5:34 am #21505scottahMemberpeterlaursen wrote on May 2 2006, 06:14 AM:I think you must explain a little more in detail.
1) The category chosen is 'Migration Tool'. Is it a Migration(ODBC-import) job we are talking about?
2) What does the… tag look like in that job file?
3) “I get this terminal error” I understand that you are running SJA from command-line?
You are PERFECTLY sure that you DID specify a job-file for MIGRATION/ODBC-import?
1.
Yes ODBC import.
2. I just took a look. It had SSH tunnel info in there, no idea why. Removed it and it starts off OK.
3. Nope running from the GUI
I love the tool, but things like being unable to tick mappings in the map popup that it automatches. Eg. It sees columns in the source and the destination tables named the same, so it matches them, they show up as a new row in the mappings table, but it wont let me TICK it. Why???
scottah wrote on May 5 2006, 05:25 AM:1.Yes ODBC import.
2. I just took a look. It had SSH tunnel info in there, no idea why. Removed it and it starts off OK.
3. Nope running from the GUI
I love the tool, but things like being unable to tick mappings in the map popup that it automatches. Eg. It sees columns in the source and the destination tables named the same, so it matches them, they show up as a new row in the mappings table, but it wont let me TICK it. Why???
Hmm actually in the mapping table, where it says a fieldname underneath the destination table name, doesn't mean it actually exists…. perhaps this is my problem. Although this happens to me often.. I will post more once I find a solid example.
-
May 5, 2006 at 6:09 am #21506peterlaursenParticipant
OK ..
1) The XML-did not have in it what you expected. So that is solved
2) The mapping issue. I don't understand quite if there is an issue or not?
-
May 5, 2006 at 6:04 pm #21507diroddiMember
I am having the same problem. I updated to 5.11 and cannot run a job that I have run weekly for about a year.
My connection works fine(with ssh tunnel), so it must have something to do with the Migration Toolkit.
-
May 6, 2006 at 12:56 am #21508peterlaursenParticipant
If you want us to help you with that you will have to give more information.
If I tell you 'my car won't start – if did before changing the tyres' then what can you do about it?
Could you explain what that job is doing and what the error is?
-
May 7, 2006 at 11:45 pm #21509scottahMemberpeterlaursen wrote on May 5 2006, 06:09 AM:OK ..
1) The XML-did not have in it what you expected. So that is solved
2) The mapping issue. I don't understand quite if there is an issue or not?
1. Yep, solved
2. Its not an issue that I have a solid example for, More somethign that I have noticed once or twice. Will re-post once I get a solid example. Don't want to waste anyone's time.
-
May 8, 2006 at 4:04 pm #21510diroddiMemberpeterlaursen wrote on May 6 2006, 12:56 AM:@diroddi
If you want us to help you with that you will have to give more information.
If I tell you 'my car won't start – if did before changing the tyres' then what can you do about it?
Could you explain what that job is doing and what the error is?
Sorry for the confusion Peter.
After upgrading to version 5.11, I get the error “Could not create SSH tunnel for source server” when trying to 'Run immediately' a saved session in the Migration Toolkit.
This saved session works fine under version 5.02, as I just ran it without any troubles.
-
May 8, 2006 at 6:43 pm #21511peterlaursenParticipant
hmmm….
I think we have a similar report in our ticket system. So looks like there is 'something to it'.
I see two possibilities
1) it is a problem wuth sja.exe itself.
2) porblem occurs when sqkyog.exe 'gives control' to sja.exe
Can you run the saved job from command-line?
-
May 8, 2006 at 7:05 pm #21512diroddiMemberpeterlaursen wrote on May 8 2006, 06:43 PM:hmmm….
Can you run the saved job from command-line?
Can't run at the command-line either. It spits out the same error.
-
May 8, 2006 at 7:11 pm #21513peterlaursenParticipant
thanks … it is then not related to the sqlyog.exe file at all.
I'll wait for Ritesh to read tomorrow.
-
May 9, 2006 at 1:30 am #21514RiteshMember
Is it possible to mail me the schema file and if possible grant temporary access to your MySQL server?
-
May 12, 2006 at 7:10 am #21515
-
May 15, 2006 at 11:10 pm #21516diroddiMemberRitesh wrote on May 12 2006, 07:10 AM:
That fixed it.
Thank you
-
-
AuthorPosts
- You must be logged in to reply to this topic.