SQL Complete - SQL 2005 - Frequently crashes.

[kamiller42]

I was using the free version of SQL Complete with SQL Server Management Studio for SQL 2005 with no problems. Well, certainly nothing major I remember.

I upgraded to the full version, and I find it extremely unstable. The Studio crashes about every 2 hours. The crash always occurs when Complete is trying to display some insight. The tool goes into some infinite lookup and screen redraws fail. After a few moments, the tool dies and the Microsoft report a problem windows pops up.

This isn't how Complete always dies. Sometimes it saves itself from a complete crash. When this happens, the Studio's screen redraw is all messed up. Things fail to draw. Some draw, but in odd places, like the status bar at the top of the screen.

This is really slowing me down. Any suggestions?

[alexa]

Could you please provide us the following information:

1. Full version dbForge SQL Complete.
2. Full version of Management Studio.
3. Full version of SQL server.
4. List of the other Management Studio addins you may have installed in the system.
5. Name and bitness of your operating system.
6. Versions of Service Packs for your operating system and Management Studio.
7. Was the green progress bar displayed inside the status bar at the very bottom of the screen before it happened?
8. How many connections are there in Object Explorer?
9. How do you manage all the connections? Do they all exist in Object Explorer or you create a few of them and then disconnect as needed?
10. What is the size of the database you are working with?
11. Is there any antivirus or firewall installed in the system?

Please also send us the full text of any possible error message or error report and the screenshot reflecting the issue to supportATdevartDOTcom for further investigation.

[kamiller42]

Sorry. I guess I could have given more details. I spend at least 8 hours a day writing SQL code. Decided to post when editor when down for the hundredth time. Anyone reading this and considering the product, yes, it can a real time saver. I type a lot less.

Here is the info:
I am using Windows XP 32-bit with the latest service packs and hots fixes in a 2GB RAM VM. I use no anti-virus or firewall.
SQL Complete 3.5.83
SQL Server is 2005 Enterprise. I usually have at least 2 connections active object explorer and on average 6 SQL windows open.
I primarily work in 2 databases. Here are the stats:
Database1 -- 135 tables, 1,426 fields
Database2 -- 411 tables, 5,415 fields

Microsoft SQL Server Management Studio 9.00.4035.00
Microsoft Analysis Services Client Tools 2005.090.4035.00
Microsoft Data Access Components (MDAC) 2000.085.1132.00 (xpsp.080413-0852)
Microsoft MSXML 2.6 3.0 4.0 6.0
Microsoft Internet Explorer 8.0.6001.18702
Microsoft .NET Framework 2.0.50727.3634
Operating System 5.1.2600

Not sure if related, but I can tell what conditions will make SQL Complete unstable. Whenever I am done for the day, I close my notebook lid and it goes to sleep. When I wake it up, the SQL tool has lost its connections as expected, but MS does a good job of re-establishing connections. In editors, just execute "use database1" twice. First time produces error, but second does the trick. When I do this, I can work for a little while before SQL Complete crashes.

Another situation, related to the above, makes for an unstable environment. That is when a network connection is lost. For instance, I connect sometimes via VPN and the connection drops because internet lost or wireless drop. I can get reconnected and back up and running in the SQL tool, but it will just as unstable as when I wake notebook up.

While the symptoms are the same, I don't think it's the same issue. I can be wired into a network, have a solid connection, work for 2 hours and still experience a crash.

[alexa]

Could you please also answer the following questions:

1. Were you previously using the free edition (that you had no issues with) of the same version 3.5.83 or earlier?
2. Did you upgrade it to the licensed version of dbForge SQL Complete or the Trial one?
3. Are there other Management Studio addins installed in the system? Which ones?
4. Does MSSMS take much operating memory with dbForge SQL Complete being installed?

In case you were facing the "Error creating window handle" message, please be aware that, initially, such issue is not connected with dbForge SQL Complete. There appears to be insufficiency of the handles that the operating system allocates to applications. It means that one of the processes in the operating memory took a large amount of handles and the 'ssms.exe' process just didn't have enough ones for successful functioning.

You can find out how many handles are taken by applications as follows:

1. Invoke Windows Task Manager.
2. Switch to the 'Processes' tab.
3. Select 'View -> Select Columns' from the main menu.
4. Select the 'Handles' option.
5. Find the value in the 'Handles' column against the image name.

We would also recommend you to restart the PC more often instead of using the sleep or hibernation mode in order to avoid such problem.

[kamiller42]

1. I was using the free edition with no problems.
2. I upgraded to the licensed version SQL Complete. I downloaded the latest full version and installed. Don't remember if installer removes previously installed Trial version.
3. No other add-ins.
4. The app has been running for a little over 4 hours. (That's a long time without a crash, but it's over several short sessions.) Working set is only 18MB. Private bytes is 151MB.

I have never seen "Error creating window handle" error. The crash is always the tool trying to display a window when entering a context. The IDE goes locked and some seconds later, the MS crash report window pops up. I submitted some. Not sure how you can get them. If some of the reports are stored in a local cache, I can get them to you.

That's what happens during a fatal crash. Sometimes it recovers but the screen redraw is crazy. For instance, the results grid won't draw when running a select statement. Tab borders stop drawing. Stuff like that.

[kamiller42]

There is one thing I haven't tried and maybe I should. Uninstall SQL Complete, perform a cleaning of anything left behind and reinstall SQL Complete.

[alexa]

Could you please also try to perform the procedure below and let us know the result:

1. Uninstall dbForge SQL Complete with all the options being selected on the 'Uninstall options' page of the Uninstall wizard.

2. Open Windows Explorer and paste:

%programfiles%\Devart\

3. Find and delete the 'dbForge SQL Complete' folder.

4. Reinstall dbForge SQL Complete.

[kamiller42]

I will try your instructions. Thanks for them. Makes it easier to clean out and trya gain.

I wanted to share some screenshots of what the SQL Management tool looks like when it begins to crash. This is not a fatal crash, but continued use will lead to a fatal crash.

Resources at the beginning of its demise.


Screen redraws begin to fail quickly. Tabs and results grid fail to draw.


This popped up. Never seen before.

[alexa]

Could you please update us on whether this issue was resolved after following the provided instructions?

[kamiller42]

I performed the steps: uninstalled and deleted SQL Complete directory. The situation is not better. In fact, it might be worse. It seems to crash more frequently. I keep PS Pad open on the side to save my work as I go because I don't know when things will go bad.

Here is another occassion where the tool crashed...
Crashed when insight window popped up.


Things not sure but might be contributing factor:
1) I have not restarted Windows since re-installing.
2) Doing cross database work, like writing queries which join tables between databases.

[alexa]

From the screenshot you provided it follows that the error report was raised by SSMS, but not by dbForge SQL Complete. Anyway, is there any possibility to provide us the full text of the error report for further investigation?

Also, please try to remove the checkmark from the 'Close when done' option in the 'Error Reporting' dialog box and try to continue working in SSMS.

Please also let us know whether you have installed other Devart products in the system.

[kamiller42]

Here's the error event signature:


It builds an error report. I can view it in a scrolling window, but can't copy/paste it. Doesn't allow. Also, report is huge. If you know where the report submit file is, I could get it.

[alexa]

Thank you for the reply.

We are currently investigating this issue and will get back to you with the result as soon as possible.

[kamiller42]

I have switched back to the SQL Complete free edition to see if things improve.

Forgot to mention the other Devart products I have installed: SQL Decrypter and DB Monitor. I also have Unidac, but that has more than likely nothing to do with this issue.

[kamiller42]

An update on this. I installed the free edition. While it on rare occassions appears to lock the SMSS up, it does come back and SMSS never crashed.

I noticed a new version of the full version came out. I will give it a test drive.