Can't expand localhost icon...

Hi all,
Something that should have been straightforward turned out to be rather
problematic. Thankfully this is only a test machine. SQL Server 2000 Dev
Edition on XP Pro.
I detached a [BLAH] database file with Enterprise Manager, deleted the
corresponding BLAH.MDF/.LDF files, copied newer versions of those files from
another machine where the old files used to be, then was going to reattach
as usual with the following sequence:
Reload SQL Server Enterprise Manager
Expand Microsoft SQL Servers
Expand SQL Server Group
Try to expand (local)
At this point I got the following:
"Unable to connect to server localhost: Server: Msg 4064, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open user
default
database. Login failed."
WTF? I didn't delete any other file, or detach any other database...I'm
ruling out any problem with the newer .MDF/.LDF files, because I'm not even
getting to the point where I can even try to reattach.
Ideas?Argh...never mind...I just found Q307864. No clue why Google failed to
return it the first time around (*before* I posted my original question)...
I still have no idea though why the problem started...|||Homer,
That error message is normal.Iam assuming that the login uses the same
database that you detached, as the default one.While you were connecting to
the server through EM, the login failed since the default database was not
online.
Use master as default database to avoid situations like this.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"Homer J. Simpson" <root@.127.0.0.1> wrote in message
news:uRT3WfsLEHA.644@.tk2msftngp13.phx.gbl...
> Hi all,
> Something that should have been straightforward turned out to be rather
> problematic. Thankfully this is only a test machine. SQL Server 2000 Dev
> Edition on XP Pro.
> I detached a [BLAH] database file with Enterprise Manager, deleted the
> corresponding BLAH.MDF/.LDF files, copied newer versions of those files
from
> another machine where the old files used to be, then was going to reattach
> as usual with the following sequence:
> Reload SQL Server Enterprise Manager
> Expand Microsoft SQL Servers
> Expand SQL Server Group
> Try to expand (local)
> At this point I got the following:
> "Unable to connect to server localhost: Server: Msg 4064, Level 16, State
1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open use
r default
> database. Login failed."
> WTF? I didn't delete any other file, or detach any other database...I'm
> ruling out any problem with the newer .MDF/.LDF files, because I'm not
even
> getting to the point where I can even try to reattach.
> Ideas?
>|||"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:%23tKHyvtLEHA.892@.TK2MSFTNGP09.phx.gbl...
> Homer,
> That error message is normal.Iam assuming that the login uses the same
> database that you detached, as the default one.While you were connecting
to
> the server through EM, the login failed since the default database was not
> online.
> Use master as default database to avoid situations like this.
It's very possible this is the case--I can't remember...however I use this
particular database almost exclusively on this test machine, so I can see
how I might have changed the default at some point...|||Hi Homer,
I am reviewing your post now. I want to know that after you change the
default database of all users to MASTER, is the problem resolved? Please
feel free to let us know that if you still have any problem. We are glad to
help.
Thanks.
Best regards
Baisong Wei
Microsoft Online Support
----
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.sql

Can't expand localhost icon...

Hi all,
Something that should have been straightforward turned out to be rather
problematic. Thankfully this is only a test machine. SQL Server 2000 Dev
Edition on XP Pro.
I detached a [BLAH] database file with Enterprise Manager, deleted the
corresponding BLAH.MDF/.LDF files, copied newer versions of those files from
another machine where the old files used to be, then was going to reattach
as usual with the following sequence:
Reload SQL Server Enterprise Manager
Expand Microsoft SQL Servers
Expand SQL Server Group
Try to expand (local)
At this point I got the following:
"Unable to connect to server localhost: Server: Msg 4064, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open user default
database. Login failed."
WTF? I didn't delete any other file, or detach any other database...I'm
ruling out any problem with the newer .MDF/.LDF files, because I'm not even
getting to the point where I can even try to reattach.
Ideas?
Argh...never mind...I just found Q307864. No clue why Google failed to
return it the first time around (*before* I posted my original question)...
I still have no idea though why the problem started...
|||Homer,
That error message is normal.Iam assuming that the login uses the same
database that you detached, as the default one.While you were connecting to
the server through EM, the login failed since the default database was not
online.
Use master as default database to avoid situations like this.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"Homer J. Simpson" <root@.127.0.0.1> wrote in message
news:uRT3WfsLEHA.644@.tk2msftngp13.phx.gbl...
> Hi all,
> Something that should have been straightforward turned out to be rather
> problematic. Thankfully this is only a test machine. SQL Server 2000 Dev
> Edition on XP Pro.
> I detached a [BLAH] database file with Enterprise Manager, deleted the
> corresponding BLAH.MDF/.LDF files, copied newer versions of those files
from
> another machine where the old files used to be, then was going to reattach
> as usual with the following sequence:
> Reload SQL Server Enterprise Manager
> Expand Microsoft SQL Servers
> Expand SQL Server Group
> Try to expand (local)
> At this point I got the following:
> "Unable to connect to server localhost: Server: Msg 4064, Level 16, State
1
> [Microsoft][ODBC SQL Server Driver][SQL Server]Cannot open user default
> database. Login failed."
> WTF? I didn't delete any other file, or detach any other database...I'm
> ruling out any problem with the newer .MDF/.LDF files, because I'm not
even
> getting to the point where I can even try to reattach.
> Ideas?
>
|||"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:%23tKHyvtLEHA.892@.TK2MSFTNGP09.phx.gbl...
> Homer,
> That error message is normal.Iam assuming that the login uses the same
> database that you detached, as the default one.While you were connecting
to
> the server through EM, the login failed since the default database was not
> online.
> Use master as default database to avoid situations like this.
It's very possible this is the case--I can't remember...however I use this
particular database almost exclusively on this test machine, so I can see
how I might have changed the default at some point...
|||Hi Homer,
I am reviewing your post now. I want to know that after you change the
default database of all users to MASTER, is the problem resolved? Please
feel free to let us know that if you still have any problem. We are glad to
help.
Thanks.
Best regards
Baisong Wei
Microsoft Online Support
Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
Please reply to newsgroups only. Thanks.

Cant connect to SQL Server 2005 Express from VStudio 2005 pro.?

Hello
I can't do subject. It says the SQL Server does not allow remote connections, but in SQL Server surface area conf. it is turned on.
What to do?
CheersGot it to work now. I wrote localhost as with SQL Server 2000, and changed it to .\SQLExpress
Cheers

Can't connect to server - real newbie here

SLQ 2000, Win XP Pro network
I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall turned
off)
The SQL server seems to be running fine in that I can access the default
tables from the local computer. The problem is, I can't connect to the SLQ
Server from another XP Pro client computer using Enterprise Manager. That
is, I can't register it. I get a "server does not exist" error.
I've tried both Windows authentication and SQL Server authentication. To
use SQL auth. I'm assuming that all I have to do is create a new login on
the server, which I have done. I've made sure this login is an administrator
with ownership and public rights to each database.
What else should I check or setup?
All help greatly appreciated!!Karl wrote:
> SLQ 2000, Win XP Pro network
> I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> turned off)
> The SQL server seems to be running fine in that I can access the
> default tables from the local computer. The problem is, I can't
> connect to the SLQ Server from another XP Pro client computer using
> Enterprise Manager. That is, I can't register it. I get a "server
> does not exist" error.
> I've tried both Windows authentication and SQL Server authentication.
> To use SQL auth. I'm assuming that all I have to do is create a new
> login on the server, which I have done. I've made sure this login is
> an administrator with ownership and public rights to each database.
> What else should I check or setup?
> All help greatly appreciated!!
What name are you using for the SQL Server? Can you see the other PC on
the network. Try using the IP address in case the name is not resolving
properly.
--
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply.
As it turns out, I was trying this on a new installation of XP Pro running
SP 2 as I mentioned. As soon as I updated SQL 2000 with its service pack 3,
I was able to connect to the server from the client computers. Leave it to
my 14 year old son to suggest this solution. :-)
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:eR5zVb84EHA.3596@.TK2MSFTNGP12.phx.gbl...
> Karl wrote:
> > SLQ 2000, Win XP Pro network
> >
> > I installed SQL (developer) 2000 on an XP Pro running SP2 (firewall
> > turned off)
> >
> > The SQL server seems to be running fine in that I can access the
> > default tables from the local computer. The problem is, I can't
> > connect to the SLQ Server from another XP Pro client computer using
> > Enterprise Manager. That is, I can't register it. I get a "server
> > does not exist" error.
> >
> > I've tried both Windows authentication and SQL Server authentication.
> > To use SQL auth. I'm assuming that all I have to do is create a new
> > login on the server, which I have done. I've made sure this login is
> > an administrator with ownership and public rights to each database.
> >
> > What else should I check or setup?
> >
> > All help greatly appreciated!!
> What name are you using for the SQL Server? Can you see the other PC on
> the network. Try using the IP address in case the name is not resolving
> properly.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>