By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
438,856 Members | 2,179 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 438,856 IT Pros & Developers. It's quick & easy.

Query Analyzer locks up!

P: n/a
Hey all,

I'm having this weird problem on my Windows 2003 Server machine..

Whenever I open two connection pages in Query Analyzer, then close one
of them, it locks up and I have to kill the task.

I read a posting somewhere that said this could be due to an MDAC
installation problem, but I've run MDAC Component Checker and all files
are ok, version 2.8. Also, since I'm running Windows 2003 and MDAC 2.8
is the latest, I can't reinstall it.

There has to be some other cause for this. Why would QA lock up every
time I close a page?

-John

Jul 23 '05 #1
Share this Question
Share on Google+
11 Replies


P: n/a
Just noticed it also happened with only one page/connection open.
Seems to happen mostly when I've opened a .SQL file then try to close
it.

Forgot to mention I am on SP3a so that shouldn't be the issue either.
Very strange behavior though..

Jul 23 '05 #2

P: n/a
So no one knows why this happens? Am I the only one??

Jul 23 '05 #3

P: n/a
So no one knows why this happens? Am I the only one??

Jul 23 '05 #4

P: n/a
Hi

It seems like it!!

Is the database you are connecting to on the same server?
Have your tried different protocols?
What version of the client tools are you running?
Have you tried running profiler?

John

<jo*******@hotmail.com> wrote in message
news:11**********************@z14g2000cwz.googlegr oups.com...
So no one knows why this happens? Am I the only one??

Jul 23 '05 #5

P: n/a
It happens against my local server and remote ones.

Ya, I've tried different protocols, same thing. Local connections use
LPC, remote use TCP.

My version of client tools is 8.00.760 (SP3) which is the latest.

Profiler shows an AUDIT LOGOUT when I close a pane / connection in QA,
as expected. QA locks up after this.

In fact, I don't have to do *anything* for it to happen. If I open two
..SQL files and close one of them, QA will lock up and I have to kill
the process.

It gets really anoying because I spend a lot of time in Query Analyzer.
If no ones had this problem before I guess I'll have to wait till I
reimage my machine, not that that will likely do anything...

Jul 23 '05 #6

P: n/a
By the way, on an unrelated topic I can't stand the new format for
Google Groups. It really sucks and I hope the change it back.

Jul 23 '05 #7

P: n/a
It happens against my local server and remote ones.

Ya, I've tried different protocols, same thing. Local connections use
LPC, remote use TCP.

My version of client tools is 8.00.760 (SP3) which is the latest.

Profiler shows an AUDIT LOGOUT when I close a pane / connection in QA,
as expected. QA locks up after this.

In fact, I don't have to do *anything* for it to happen. If I open two
..SQL files and close one of them, QA will lock up and I have to kill
the process.

It gets really anoying because I spend a lot of time in Query Analyzer.
If no ones had this problem before I guess I'll have to wait till I
reimage my machine, not that that will likely do anything...

Jul 23 '05 #8

P: n/a
Hi

Have you checked the event log?
If your log outs are audited then it seems to be a client error.
If this is only QA then it is not likely to be an MDAC issue.
You may want to remove the client tools and re-install them.
You don't state the OS, but you may want to check it for patches. You may
also want to check the disc for errors and making sure that no other
application such as privacy control or virus checker is causing a problem.

John

<jo*******@hotmail.com> wrote in message
news:11**********************@c13g2000cwb.googlegr oups.com...
It happens against my local server and remote ones.

Ya, I've tried different protocols, same thing. Local connections use
LPC, remote use TCP.

My version of client tools is 8.00.760 (SP3) which is the latest.

Profiler shows an AUDIT LOGOUT when I close a pane / connection in QA,
as expected. QA locks up after this.

In fact, I don't have to do *anything* for it to happen. If I open two
.SQL files and close one of them, QA will lock up and I have to kill
the process.

It gets really anoying because I spend a lot of time in Query Analyzer.
If no ones had this problem before I guess I'll have to wait till I
reimage my machine, not that that will likely do anything...

Jul 23 '05 #9

P: n/a
Try setting it to show the title only if you haven't already done this.
It's still not brilliant, but better than the one I got when they first
changed it.

Jul 23 '05 #10

P: n/a
(jo*******@hotmail.com) writes:
It happens against my local server and remote ones.

Ya, I've tried different protocols, same thing. Local connections use
LPC, remote use TCP.

My version of client tools is 8.00.760 (SP3) which is the latest.

Profiler shows an AUDIT LOGOUT when I close a pane / connection in QA,
as expected. QA locks up after this.

In fact, I don't have to do *anything* for it to happen. If I open two
.SQL files and close one of them, QA will lock up and I have to kill
the process.

It gets really anoying because I spend a lot of time in Query Analyzer.
If no ones had this problem before I guess I'll have to wait till I
reimage my machine, not that that will likely do anything...


I'm afraid to diagnose this without access to your machine, as it seems
that it is corrupt in one way or another. It could be that you have
installed some program which somehow interfers with QA, but what it could
be is anybody's guess.

You could try reinstalling the SQL Server tools and reapplying the service
pack. If that doesn't help, I would consider sratching the Windows
installation, and be considerate with what you reinstall.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinf...2000/books.asp
Jul 23 '05 #11

P: n/a
AJ
I have the same issue on my machine (running Windows XP SP2). It seems
to be an issue with QA on some machines with particular video cards
(mine is an NVIDIA GeForce4 420). I researched this issue some time back
and found an article on MSDN (I did not remember the link). There is a
fix for this issue but to get the fix you need to call Microsoft *and*
if they find out that the issue is caused due to a problem with the
graphics card - they will issue the fix and not charge you for the
support incident. Apparently this is the case as the fix is still
undergoing testing and has not yet been released as a hot fix.

I did not bother calling MS as I did not want to go through the trouble
of calling support, etc., etc. and I am just going to wait for the fix
to be available. I just go to Task Manager after closing QA to make sure
that the isqlw.exe is not still running.

Note: This is an issue only if you have Windows XP with SP2 (I am not
sure about Windows 2003). I did not have this issue before installing
SP2 for Windows XP. QA worked fine then.

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!
Jul 23 '05 #12

This discussion thread is closed

Replies have been disabled for this discussion.