Can't start Query Analyzer on SQL Cluster

Have you experienced such problem in a Windows Cluster environment :
Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise Edition
Error : The Query Analyzer could not be started on the first node :
ISQLW.EXE - Entry Point Not Found
The procedure entry point ''? could not be located in the dynamic
link library SQLGUI.dll.>
> Have you experienced such problem in a Windows Cluster environment :
> Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise
Edition
> Error : The Query Analyzer could not be started on the first node :
> ISQLW.EXE - Entry Point Not Found
> The procedure entry point ''? could not be located in the dynamic
> link library SQLGUI.dll.
--
It's possible the SQLGUI.DLL is corrupt. Rename the file in the cluster and
copy from a machine which works.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.|||> Have you experienced such problem in a Windows Cluster environment :
> Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise Edition
> Error : The Query Analyzer could not be started on the first node :
> ISQLW.EXE - Entry Point Not Found
> The procedure entry point ''? could not be located in the dynamic
> link library SQLGUI.dll.
>
>
How did you solve this problem?
User submitted from AEWNET (http://www.aewnet.com/)|||> Have you experienced such problem in a Windows Cluster environment :
> Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise Edition
> Error : The Query Analyzer could not be started on the first node :
> ISQLW.EXE - Entry Point Not Found
> The procedure entry point ''? could not be located in the dynamic
> link library SQLGUI.dll.
>
>
How did you solve this problem?
User submitted from AEWNET (http://www.aewnet.com/)

Can't start Query Analyzer on SQL Cluster

Have you experienced such problem in a Windows Cluster environment :
Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise Edition
Error : The Query Analyzer could not be started on the first node :
ISQLW.EXE - Entry Point Not Found
The procedure entry point ??? could not be located in the dynamic
link library SQLGUI.dll.
>
> Have you experienced such problem in a Windows Cluster environment :
> Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise
Edition
> Error : The Query Analyzer could not be started on the first node :
> ISQLW.EXE - Entry Point Not Found
> The procedure entry point ??? could not be located in the dynamic
> link library SQLGUI.dll.
It's possible the SQLGUI.DLL is corrupt. Rename the file in the cluster and
copy from a machine which works.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.
|||
> Have you experienced such problem in a Windows Cluster environment :
> Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise Edition
> Error : The Query Analyzer could not be started on the first node :
> ISQLW.EXE - Entry Point Not Found
> The procedure entry point ??? could not be located in the dynamic
> link library SQLGUI.dll.
>
>
How did you solve this problem?
User submitted from AEWNET (http://www.aewnet.com/)
|||
> Have you experienced such problem in a Windows Cluster environment :
> Windows 2000 Advanced Server, SQL Cluster with MS SQL 7.0 Enterprise Edition
> Error : The Query Analyzer could not be started on the first node :
> ISQLW.EXE - Entry Point Not Found
> The procedure entry point ??? could not be located in the dynamic
> link library SQLGUI.dll.
>
>
How did you solve this problem?
User submitted from AEWNET (http://www.aewnet.com/)

can't see print messages during the running a of stored procedure

I have a stored procedure running from Query Analyzer that runs for a long
time and would like to have status messages print out during the procedure.
They all seem to come when the procedure is complete - is there any way to
have them print while it is running. I 've actually tried having the main
SP call a smaller SP with prints, but they don't come out till the end as
well.
Help to a new Transact SQL writer,
Thanks
TW
TW,
I don't know how to do just what you want, but you could try pumping your
messages into a trace table. Then you could query that table while the
long-running stored procedure continues. Transaction isolation levels would
affect how this works for you.
Russell Fields
"Weave" <tweaver60@.suscom.net> wrote in message
news:10apu6dm256v76@.corp.supernews.com...
> I have a stored procedure running from Query Analyzer that runs for a long
> time and would like to have status messages print out during the
procedure.
> They all seem to come when the procedure is complete - is there any way to
> have them print while it is running. I 've actually tried having the main
> SP call a smaller SP with prints, but they don't come out till the end as
> well.
> Help to a new Transact SQL writer,
> Thanks
> TW
>
|||You could use RAISERROR and the NOWAIT option instead of PRINT.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Weave" <tweaver60@.suscom.net> wrote in message news:10apu6dm256v76@.corp.supernews.com...
> I have a stored procedure running from Query Analyzer that runs for a long
> time and would like to have status messages print out during the procedure.
> They all seem to come when the procedure is complete - is there any way to
> have them print while it is running. I 've actually tried having the main
> SP call a smaller SP with prints, but they don't come out till the end as
> well.
> Help to a new Transact SQL writer,
> Thanks
> TW
>

Can't Run Query Analyzer

When trying to access Query Analyzer from Enterprise Manager, I receive the
error, "The specified file was not found". I don't know what happened, as it
was working fine yesterday, and I've made no changes to the system in the
interim. SQL Server 2000 Standard Edition running under Win 2003 Server, sp1.
Any immediate thoughts would be welcome.Hi
You may want to check out http://tinyurl.com/85xwc, you could re-add it as
an external tool or re-install the client tools should fix it.
John
"Mike Kelly" <Mike Kelly@.discussions.microsoft.com> wrote in message
news:D0FE4485-A324-44C3-B4EC-59E996B84987@.microsoft.com...
> When trying to access Query Analyzer from Enterprise Manager, I receive
> the
> error, "The specified file was not found". I don't know what happened, as
> it
> was working fine yesterday, and I've made no changes to the system in the
> interim. SQL Server 2000 Standard Edition running under Win 2003 Server,
> sp1.
> Any immediate thoughts would be welcome.

Can't Run Query Analyzer

When trying to access Query Analyzer from Enterprise Manager, I receive the
error, "The specified file was not found". I don't know what happened, as it
was working fine yesterday, and I've made no changes to the system in the
interim. SQL Server 2000 Standard Edition running under Win 2003 Server, sp1
.
Any immediate thoughts would be welcome.Hi
You may want to check out http://tinyurl.com/85xwc, you could re-add it as
an external tool or re-install the client tools should fix it.
John
"Mike Kelly" <Mike Kelly@.discussions.microsoft.com> wrote in message
news:D0FE4485-A324-44C3-B4EC-59E996B84987@.microsoft.com...
> When trying to access Query Analyzer from Enterprise Manager, I receive
> the
> error, "The specified file was not found". I don't know what happened, as
> it
> was working fine yesterday, and I've made no changes to the system in the
> interim. SQL Server 2000 Standard Edition running under Win 2003 Server,
> sp1.
> Any immediate thoughts would be welcome.

Can't Run Query Analyzer

When trying to access Query Analyzer from Enterprise Manager, I receive the
error, "The specified file was not found". I don't know what happened, as it
was working fine yesterday, and I've made no changes to the system in the
interim. SQL Server 2000 Standard Edition running under Win 2003 Server, sp1.
Any immediate thoughts would be welcome.
Hi
You may want to check out http://tinyurl.com/85xwc, you could re-add it as
an external tool or re-install the client tools should fix it.
John
"Mike Kelly" <Mike Kelly@.discussions.microsoft.com> wrote in message
news:D0FE4485-A324-44C3-B4EC-59E996B84987@.microsoft.com...
> When trying to access Query Analyzer from Enterprise Manager, I receive
> the
> error, "The specified file was not found". I don't know what happened, as
> it
> was working fine yesterday, and I've made no changes to the system in the
> interim. SQL Server 2000 Standard Edition running under Win 2003 Server,
> sp1.
> Any immediate thoughts would be welcome.

Can't run OpenQuery against OLAP Database

I'm trying to execute a query against an AS 2000 database from query analyzer. I've created the linked server using the "Microsoft OLE DB Provider for OLAP Services" ("Allow InProcess" checked) but I'm getting an error message: "Could not get the data of the row from the OLE DB provider 'MSOLAP'.
[OLE/DB provider returned message: An unexpected internal error has occurred.]
OLE DB error trace [OLE/DB Provider 'MSOLAP' IRowset::GetData returned 0x80040e21: Data status returned from the provider: [COLUMN_NAME=[Measures].[Act] STATUS=DBSTATUS_E_UNAVAILABLE]]."

Has anyone seen this problem before? Do you know what is needed to fix it? I had been able to execute an OpenQuery against another AS2000 database but that was with another machine and I can't pin point what I did to get it to work (the machine had a lot installed on it and I'm not sure what did the trick).

Any help is greatly appreciated.

Carmen.

Please make sure that AS2000 SP4 client components are installed on that machine. I recall similar bug that was fixed in one of the SPs.|||

Thanks, Irina. All machines involved have SP4 installed on them. I think there is something missing on the client as well as on the server. Here is why:

Old laptop connecting to Server A: OK

Old laptop connecting to Server B: Error

New laptop connecting to Server A: Error

New laptop connecting to Server B: Error

If the problem was only on the new laptop, the old one should be able to connect to Server B. And if the problem was only on Server B, the new laptop should connect to Server A.

Thanks,

Carmen.

|||

Actually, I found that what is different on my old laptop is that it has SP3 instead of SP4.... And I think I read it somewhere about SP4 causing this problem. Does anyone knows of a fix for this?

Thanks,

Carmen

Can't login to Enterprise Manager or Query Analyzer

Hello,
We are running SQL Server 7.0 databases on 3 separate
systems. We have found that recently we are unable to log
into these databases via Enterprise Manager (Enterprise
Manager will run by when you attempt to connect to the
database it will lock up). We were able to work around
that by just using Query Analyzer, but now that has
stopped working. The same problem: after being prompted
for user name/password (we are using SQL Server Security)
it hangs while displaying the "Connecting to..." message.
Has anyone encountered this before? We initially copied
the Query Analyzer executable (isqlw.exe) from the CD to
the server and that fixed it for a short time. Any ideas
on how to fix this permenantly and what is causing the
problem?
Thanks.Did you remove the default database for the logins? If so, you can change
it using sp_defaultdb via QA.
"Todd Biggar" <tbiggar@.nelcomail.com> wrote in message
news:03cb01c38dd0$3f9e7890$a301280a@.phx.gbl...
> Hello,
> We are running SQL Server 7.0 databases on 3 separate
> systems. We have found that recently we are unable to log
> into these databases via Enterprise Manager (Enterprise
> Manager will run by when you attempt to connect to the
> database it will lock up). We were able to work around
> that by just using Query Analyzer, but now that has
> stopped working. The same problem: after being prompted
> for user name/password (we are using SQL Server Security)
> it hangs while displaying the "Connecting to..." message.
> Has anyone encountered this before? We initially copied
> the Query Analyzer executable (isqlw.exe) from the CD to
> the server and that fixed it for a short time. Any ideas
> on how to fix this permenantly and what is causing the
> problem?
> Thanks.
>|||Unfortunately we can't log in with QA either; it hangs on
us too. The actual applications we wrote to hit the
database seem to be connecting without any problems, but
neither Enterprise Manager nor Query Analyzer will respond
when we try to connect.
>--Original Message--
>Did you remove the default database for the logins? If
so, you can change
>it using sp_defaultdb via QA.
>"Todd Biggar" <tbiggar@.nelcomail.com> wrote in message
>news:03cb01c38dd0$3f9e7890$a301280a@.phx.gbl...
>> Hello,
>> We are running SQL Server 7.0 databases on 3 separate
>> systems. We have found that recently we are unable to
log
>> into these databases via Enterprise Manager (Enterprise
>> Manager will run by when you attempt to connect to the
>> database it will lock up). We were able to work around
>> that by just using Query Analyzer, but now that has
>> stopped working. The same problem: after being prompted
>> for user name/password (we are using SQL Server
Security)
>> it hangs while displaying the "Connecting to..."
message.
>> Has anyone encountered this before? We initially copied
>> the Query Analyzer executable (isqlw.exe) from the CD to
>> the server and that fixed it for a short time. Any
ideas
>> on how to fix this permenantly and what is causing the
>> problem?
>> Thanks.
>
>.
>|||I think what Scott was getting at was to try to log on using
osql from the command line and change the default database
if that's what the issue is. You can at least try to log in
using osql from the command line. If you need to change the
default database, you can use something along the lines of:
OSQL -S YourServer -E -Q "EXEC sp_defaultdb 'YourLogin',
'master'"
-Sue
On Wed, 8 Oct 2003 13:30:30 -0700, "Todd Biggar"
<tbiggar@.nelcomail.com> wrote:
>Unfortunately we can't log in with QA either; it hangs on
>us too. The actual applications we wrote to hit the
>database seem to be connecting without any problems, but
>neither Enterprise Manager nor Query Analyzer will respond
>when we try to connect.
>>--Original Message--
>>Did you remove the default database for the logins? If
>so, you can change
>>it using sp_defaultdb via QA.
>>"Todd Biggar" <tbiggar@.nelcomail.com> wrote in message
>>news:03cb01c38dd0$3f9e7890$a301280a@.phx.gbl...
>> Hello,
>> We are running SQL Server 7.0 databases on 3 separate
>> systems. We have found that recently we are unable to
>log
>> into these databases via Enterprise Manager (Enterprise
>> Manager will run by when you attempt to connect to the
>> database it will lock up). We were able to work around
>> that by just using Query Analyzer, but now that has
>> stopped working. The same problem: after being prompted
>> for user name/password (we are using SQL Server
>Security)
>> it hangs while displaying the "Connecting to..."
>message.
>> Has anyone encountered this before? We initially copied
>> the Query Analyzer executable (isqlw.exe) from the CD to
>> the server and that fixed it for a short time. Any
>ideas
>> on how to fix this permenantly and what is causing the
>> problem?
>> Thanks.
>>
>>.|||Unfortunately this doesn't work either; I've tried various combinations of
usernames, database names and login names but even running osql is
non-responsive. It will just sit there at the prompt until I break out.
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8r09ovouoej90ecvvgtn3taunct8t8rohi@.4ax.com...
> I think what Scott was getting at was to try to log on using
> osql from the command line and change the default database
> if that's what the issue is. You can at least try to log in
> using osql from the command line. If you need to change the
> default database, you can use something along the lines of:
> OSQL -S YourServer -E -Q "EXEC sp_defaultdb 'YourLogin',
> 'master'"
> -Sue
> On Wed, 8 Oct 2003 13:30:30 -0700, "Todd Biggar"
> <tbiggar@.nelcomail.com> wrote:
> >Unfortunately we can't log in with QA either; it hangs on
> >us too. The actual applications we wrote to hit the
> >database seem to be connecting without any problems, but
> >neither Enterprise Manager nor Query Analyzer will respond
> >when we try to connect.
> >
> >>--Original Message--
> >>Did you remove the default database for the logins? If
> >so, you can change
> >>it using sp_defaultdb via QA.
> >>
> >>"Todd Biggar" <tbiggar@.nelcomail.com> wrote in message
> >>news:03cb01c38dd0$3f9e7890$a301280a@.phx.gbl...
> >> Hello,
> >>
> >> We are running SQL Server 7.0 databases on 3 separate
> >> systems. We have found that recently we are unable to
> >log
> >> into these databases via Enterprise Manager (Enterprise
> >> Manager will run by when you attempt to connect to the
> >> database it will lock up). We were able to work around
> >> that by just using Query Analyzer, but now that has
> >> stopped working. The same problem: after being prompted
> >> for user name/password (we are using SQL Server
> >Security)
> >> it hangs while displaying the "Connecting to..."
> >message.
> >>
> >> Has anyone encountered this before? We initially copied
> >> the Query Analyzer executable (isqlw.exe) from the CD to
> >> the server and that fixed it for a short time. Any
> >ideas
> >> on how to fix this permenantly and what is causing the
> >> problem?
> >>
> >> Thanks.
> >>
> >>
> >>
> >>.
> >>
>|||You'll probably want to go through your SQL Server error
logs and try to find out what the problem is. Also, check
the status of the service in the services applet - I've seen
something similar when the service was hung up in a
"Starting" status (it should say "Started" not starting).
-Sue
On Thu, 9 Oct 2003 10:44:21 -0500, "Todd Biggar"
<tbiggar@.new.rr.com> wrote:
>Unfortunately this doesn't work either; I've tried various combinations of
>usernames, database names and login names but even running osql is
>non-responsive. It will just sit there at the prompt until I break out.
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:8r09ovouoej90ecvvgtn3taunct8t8rohi@.4ax.com...
>> I think what Scott was getting at was to try to log on using
>> osql from the command line and change the default database
>> if that's what the issue is. You can at least try to log in
>> using osql from the command line. If you need to change the
>> default database, you can use something along the lines of:
>> OSQL -S YourServer -E -Q "EXEC sp_defaultdb 'YourLogin',
>> 'master'"
>> -Sue
>> On Wed, 8 Oct 2003 13:30:30 -0700, "Todd Biggar"
>> <tbiggar@.nelcomail.com> wrote:
>> >Unfortunately we can't log in with QA either; it hangs on
>> >us too. The actual applications we wrote to hit the
>> >database seem to be connecting without any problems, but
>> >neither Enterprise Manager nor Query Analyzer will respond
>> >when we try to connect.
>> >
>> >>--Original Message--
>> >>Did you remove the default database for the logins? If
>> >so, you can change
>> >>it using sp_defaultdb via QA.
>> >>
>> >>"Todd Biggar" <tbiggar@.nelcomail.com> wrote in message
>> >>news:03cb01c38dd0$3f9e7890$a301280a@.phx.gbl...
>> >> Hello,
>> >>
>> >> We are running SQL Server 7.0 databases on 3 separate
>> >> systems. We have found that recently we are unable to
>> >log
>> >> into these databases via Enterprise Manager (Enterprise
>> >> Manager will run by when you attempt to connect to the
>> >> database it will lock up). We were able to work around
>> >> that by just using Query Analyzer, but now that has
>> >> stopped working. The same problem: after being prompted
>> >> for user name/password (we are using SQL Server
>> >Security)
>> >> it hangs while displaying the "Connecting to..."
>> >message.
>> >>
>> >> Has anyone encountered this before? We initially copied
>> >> the Query Analyzer executable (isqlw.exe) from the CD to
>> >> the server and that fixed it for a short time. Any
>> >ideas
>> >> on how to fix this permenantly and what is causing the
>> >> problem?
>> >>
>> >> Thanks.
>> >>
>> >>
>> >>
>> >>.
>> >>
>|||Turns out the default network libary got changed to Named Pipes somehow. I
removed all the entries in the Client Utility and readded them and now it
works.
Thanks for all the help!
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:8r09ovouoej90ecvvgtn3taunct8t8rohi@.4ax.com...
> I think what Scott was getting at was to try to log on using
> osql from the command line and change the default database
> if that's what the issue is. You can at least try to log in
> using osql from the command line. If you need to change the
> default database, you can use something along the lines of:
> OSQL -S YourServer -E -Q "EXEC sp_defaultdb 'YourLogin',
> 'master'"
> -Sue
> On Wed, 8 Oct 2003 13:30:30 -0700, "Todd Biggar"
> <tbiggar@.nelcomail.com> wrote:
> >Unfortunately we can't log in with QA either; it hangs on
> >us too. The actual applications we wrote to hit the
> >database seem to be connecting without any problems, but
> >neither Enterprise Manager nor Query Analyzer will respond
> >when we try to connect.
> >
> >>--Original Message--
> >>Did you remove the default database for the logins? If
> >so, you can change
> >>it using sp_defaultdb via QA.
> >>
> >>"Todd Biggar" <tbiggar@.nelcomail.com> wrote in message
> >>news:03cb01c38dd0$3f9e7890$a301280a@.phx.gbl...
> >> Hello,
> >>
> >> We are running SQL Server 7.0 databases on 3 separate
> >> systems. We have found that recently we are unable to
> >log
> >> into these databases via Enterprise Manager (Enterprise
> >> Manager will run by when you attempt to connect to the
> >> database it will lock up). We were able to work around
> >> that by just using Query Analyzer, but now that has
> >> stopped working. The same problem: after being prompted
> >> for user name/password (we are using SQL Server
> >Security)
> >> it hangs while displaying the "Connecting to..."
> >message.
> >>
> >> Has anyone encountered this before? We initially copied
> >> the Query Analyzer executable (isqlw.exe) from the CD to
> >> the server and that fixed it for a short time. Any
> >ideas
> >> on how to fix this permenantly and what is causing the
> >> problem?
> >>
> >> Thanks.
> >>
> >>
> >>
> >>.
> >>
>