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.
> >>
> >>
> >>
> >>.
> >>
>