Application Crash

[garyt]

I am using a full/registered version of SQLyog Enterprise, latest version.

As mentioned above, my operating system is Vista64.

The following problem is reproducible every time.

1. I have set up Query which works fine (access to a remote database).

2. I am selecting the Export As and choose CVS file.

3. Then I click on the button “…” next to – Save to file –

– Window Save As opens to select a file name –

4. Following I am entering a file name and click on selection option “Previous Location” to choose a location.

5. At that point the application crashes every time with the message:

Runtime Error!

Microsoft Visual C++ Runtime Library

Program:C:Program Files (x86)SQLyog EnterpriseSQLyogEnt.exe

This application has requested the Runtime to terminate in an

unusual way.

Please contact the application's support team for more information.

[peterlaursen]

1) what is 'latest version'? 8.05 or 8.1 beta? Please always refer to the exact version number (believe it or not – but sometimes users refer to a 2-3 years old version as the 'latest version'! 🙂 )

2) Have you tried to reboot? It looks to me like an issue with Windows DEP (Data Execution Prevention) feature. A reboot will normally solve this! You should notice that this crash (as I understand) happens in a Windows Explorer dialogue and not in the SQLyog Window. Vista has lots of such issues (I did not experience a single in Windows 7 RC and also not in XP before SP3).

[garyt]

My version is 8.05.

Yes, I have tried reboot and even reinstall, always the same.

Also, I want to mention that I can manually click to a new save location and it works.

Only when I click on the downward pointing triangle “previous location” the application crashes.

[peterlaursen]

OK .. thanks for the feedback! We will try to reproduce and debug this of course.

[nithin]

Hello,

This issue is not reproducible at our end, still we are trying.

In between we also like to know some more information that help us to analyze the issue and solve it quickly.

1. For you this issue only happens when 'Export As' as CSV? Or Also Is it happens you like when save the main editor content?

2. Does this issue happen with a particular table or all tables?

3. How many rows you have for that table to export?

4. Can you please try this case with a small table?

5. Also please confirm you have enough memory where you save(please try once with other than 'C' drive)?

Please let us know the details.

Thanks

Nithin

[garyt]

nithin wrote on May 25 2009, 02:39 AM:

Hello,

This issue is not reproducible at our end, still we are trying.

In between we also like to know some more information that help us to analyze the issue and solve it quickly.

1. For you this issue only happens when 'Export As' as CSV? Or Also Is it happens you like when save the main editor content?

2. Does this issue happen with a particular table or all tables?

3. How many rows you have for that table to export?

4. Can you please try this case with a small table?

5. Also please confirm you have enough memory where you save(please try once with other than 'C' drive)?

Please let us know the details.

Thanks

Nithin

1. It does not matter which format, it always happens. Don't understand what you mean by “save the main editor content?”

2. Happens with all tables.

3. The main table has 3302 rows, but I also tried with about 100 and same problem.

4. See my answer in 3.

5. No space issue, I have 750Gb available. Also tried a different loaction, all the same.

Also, I think there might be still a miss understanding. I can export my query results as long as I select the location manually. It only happens when I click on Previous Location and it happens every time.

Here is an image to make sure:

http://s240.photobucket.com/albums/ff108/B…use_error-1.png

The moment I click as shown in the picture above, I get the following error:

http://s240.photobucket.com/albums/ff108/B…rrent=error.png

[navyashree.r]

We found similar issues reported with other programs too…

We cannot reproduce and believe it is problem with Windows Explorer. We would like to code some workaround – but as long as it is not reproducible for us this is almost impossible… So, could you please try to reproduce this crash on another system? And also can you please confirm whether have you faced same issue with other applications too?

FYI go through the links below,

http://forums.adobe.com/thread/309405

http://www.vistax64.com/vista-mail/80850-m…time-error.html

Quote:

It does not matter which format, it always happens. Don't understand what you mean by “save the main editor content?”

“Save the main editor content” means Type a query in an Query Editor and Save the contents (Ctrl +S). So, can you confirm here too same issue while saving?

Regards,

Navya

[peterlaursen]

A few more comments;

1) You should also notice that this save diaologue (where the error occurs) is not (much) our code. It is a Windows standard (probably shipped with Windows in some system .dll) that is invoked by a Windows API call. Basically just a function call with parameters. You will find other programs use same dialogue. It is not reproducable with other applications?

2) (maybe a silly idea) but I would consider to

— run CHCKDSK on all drives (with -f or -r parameter)

— use some utility to remove orphaned MRU (most recently used) entries from the registry (I use this http://www.macecraft.com). In particular if you have changed drive letters or a 'previous' is on a removable drive that is not attached

[Author]

Posts