Comments
15 comments
-
Hi
What version of windows are you running on and do you get any error dialog. Also are you running on a slow machine or a machine with very little memory.
Lionel -
Another thing that I forgot to ask is what version of Query Analyzer do you have. You can find this out by the going to about dialog and it will be something like 8.00.760.
Lionel -
I'm running Windows Server 2003 with all the latest patches (but not IE7).
I've got 1GB RAM. My current commit charge is 718MB, currently with a limit of 1,734MB. It's got a 2.8GHz Pentium4 single-core CPU.
This happens even very soon after booting, before too much garbage is running.
I don't think that SQLPrompt is even getting as far as attempting to connect to a database. QA never gets far enough to show a UI, so I don't think it knows where to connect to yet.
This machine did have Beta 1 installed on it. I did uninstall it and there is no trace of the install directory. But maybe something's left in the registry...? -
Lionel wrote:Another thing that I forgot to ask is what version of Query Analyzer do you have.
-
Thanks a lot. We will try and reproduce the problem here.
Lionel -
I am having the same problem. I have uninstalled SQL Prompt 2. I am running this on Windows XP Pro.
-
Chris / sangha,
Can you try following the steps here please:
http://www.red-gate.com/messageboard/vi ... hp?p=14316
Thanks,
Neil -
Sorry, Neil, the proposed fix does not fix the problem. QA still exits immediately when started while SQLPrompt3's integration is enabled.
-
Chris,
If you log on to your desktop as a different user, does it work?
- Neil -
Yes, logging on as a different user does work just fine. Unfortunately, I need to be me.
-
Chris,
Can you try exiting QA and then deleting the following registry key (backing it up first):
HKEY_CURRENT_USER\Software\Microsoft\Microsoft SQL Server\80\Tools\SQL Query Analyzer\Toolbars
- Neil -
I'm back in business! 8)
Deleting that registry key did the trick. -
Deleting the registry key worked for me too. But now I am getting "Trial Expired". I cannot run SQL Prompt.
-
sangha,
I've pm'd you.
- Neil -
If anyone is still having issues with the QA support can you please send me a personal messge as I think I have fixed the problems.
Lionel
Add comment
Please sign in to leave a comment.
Note: I have SQL Prompt 2 installed, but I've disabled it.