Cannot Open Query analyser from SQL Enterprise Manager

I intalled SQL200SP4 on my Windows 2003 server and now, I cannot open Query
analyser from SQL Enterprise Manager.
I get the following message: "The specified file was not found"
I can go to Query Analyser directly from the Start Menu and it works fine.
Can you please suggest, what I should do to fix this?
Thanks
Hello!
I thought this was a managed Newsgroup.
Anyone from Microsoft with a clue, why this is happening and how can I fix
this?
Thanks
"gurusinghj" wrote:

> I intalled SQL200SP4 on my Windows 2003 server and now, I cannot open Query
> analyser from SQL Enterprise Manager.
> I get the following message: "The specified file was not found"
> I can go to Query Analyser directly from the Start Menu and it works fine.
> Can you please suggest, what I should do to fix this?
> Thanks
|||gurusinghj wrote:
> I intalled SQL200SP4 on my Windows 2003 server and now, I cannot open
> Query analyser from SQL Enterprise Manager.
> I get the following message: "The specified file was not found"
> I can go to Query Analyser directly from the Start Menu and it works
> fine.
> Can you please suggest, what I should do to fix this?
> Thanks
Make sure the SQL tools are in your path. The default might look
something like the following in the path environment variable:
"C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;"
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||Thanks David,
But i do have this in path, but I still get this issue.
Thinking back, I did once install SQL Server 2000 Desktop Engine (MSDE)
after SQl server was already installed. (Another application that I
installed, did the insalltion, without me knowing.)
I did subsequently uninstall it. Do you think, that might have messed up
some registry settings.
Any help on how to restore these back, will be really appreciated.
Thanks
"David Gugick" wrote:

> gurusinghj wrote:
> Make sure the SQL tools are in your path. The default might look
> something like the following in the path environment variable:
> "C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;"
>
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
|||gurusinghj wrote:
> Thanks David,
> But i do have this in path, but I still get this issue.
> Thinking back, I did once install SQL Server 2000 Desktop Engine
> (MSDE) after SQl server was already installed. (Another application
> that I installed, did the insalltion, without me knowing.)
> I did subsequently uninstall it. Do you think, that might have messed
> up some registry settings.
> Any help on how to restore these back, will be really appreciated.
I doubt it. MSDE does not have any client tools and I doubt it would
add/change the PATH variable. If you open a command window and type
ISQL.EXE from the C:\ root folder, does QA come up? Also make sure the
"Start In" folder is the same as the "Target" folder in the shortcut for
SQL EM. The Target should look something like:
C:\WINDOWS\system32\mmc.exe /s "C:\Program Files\Microsoft SQL
Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC"
David Gugick
Quest Software
www.imceda.com
www.quest.com
|||I get the same problem right after installing MSDE also
"David Gugick" wrote:

> gurusinghj wrote:
> I doubt it. MSDE does not have any client tools and I doubt it would
> add/change the PATH variable. If you open a command window and type
> ISQL.EXE from the C:\ root folder, does QA come up? Also make sure the
> "Start In" folder is the same as the "Target" folder in the shortcut for
> SQL EM. The Target should look something like:
> C:\WINDOWS\system32\mmc.exe /s "C:\Program Files\Microsoft SQL
> Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC"
>
> --
> David Gugick
> Quest Software
> www.imceda.com
> www.quest.com
>
|||In SQL Enterprise Manager (SEM), go to Tools->External Tools; add the path
to isqlw with the parameters
-S[SRV] -d[DBN]
A new menu item should be created under Tools that will launch QA with the
right database and server context based on SEM.
If the "file not found" messge box appears, you might need the full path for
isqlw.exe OR ensure the "isqlw.exe" string appears in the "command field".
If the path contains spaces, you need to wrap the path with double quotes.
The -S and -d parameters are optional but allow you to bypass the connection
dialog each and every launch.
Regards,
Keith
This posting is provided "as is" without inferring rights or warranties.
"jdehne" <jdehne@.discussions.microsoft.com> wrote in message
news:66BE5CD0-0CE9-46E3-A258-A033FD06E75A@.microsoft.com...[vbcol=seagreen]
>I get the same problem right after installing MSDE also
> "David Gugick" wrote: