Cannot open user default database. Login failed?

Hi All,
I have not been using my SQL server 2000 for a while on this particular
machine. I had my account disabled and just got it re-enabled at work.
Login name is the same and password has changed as it does every 30 days. I
am trying to get into my server but keep getting the following error
message:
"SQL Server registration Failed because of the connection failure displayed
below. Do you wish to Register anyway?"
"Cannot open user default database. Login Failed"
I am at a loss and if anyone could suggest something to me other than
un-installing the instance and re-installing it, I would be appreciative.
Thanks,
JohnSeems like your account doesnt´have access to the default database, just try
to EXEC sp_grantdbaccess
with an administrative account for this user.
HTH, Jens Süßmeyer.
"John Rugo" <jwrugo@.patmedia.net> schrieb im Newsbeitrag
news:ObRFOWIfDHA.2320@.TK2MSFTNGP12.phx.gbl...
> Hi All,
> I have not been using my SQL server 2000 for a while on this particular
> machine. I had my account disabled and just got it re-enabled at work.
> Login name is the same and password has changed as it does every 30 days.
I
> am trying to get into my server but keep getting the following error
> message:
> "SQL Server registration Failed because of the connection failure
displayed
> below. Do you wish to Register anyway?"
> "Cannot open user default database. Login Failed"
> I am at a loss and if anyone could suggest something to me other than
> un-installing the instance and re-installing it, I would be appreciative.
> Thanks,
> John
>|||John,
See if this helps...
'Locked Out of SQL Server - Q. I locked myself out of SQL Server without
being able to log on with a sysadmin login. Can I fix this, or do I need to
reinstall SQL Server'
http://www.microsoft.com/sql/techinfo/tips/administration/May3.asp
--
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"John Rugo" <jwrugo@.patmedia.net> wrote in message
news:ehaGFkIfDHA.1764@.TK2MSFTNGP09.phx.gbl...
> Unfortunately I can't get in as sa or any other login account using osql
or
> enterpise mgr or sql analyzer. I think I will have to uninstall the
> instance and re-install it. the odd thing is that SA doesn't even work.
> Thanks for you help.
> "Jens Süßmeyer" <jsuessmeyer@.[REJECT_SPAM]web.de> wrote in message
> news:OfsbMfIfDHA.1872@.TK2MSFTNGP09.phx.gbl...
> > Seems like your account doesnt´have access to the default database, just
> try
> > to EXEC sp_grantdbaccess
> > with an administrative account for this user.
> >
> > HTH, Jens Süßmeyer.
> >
> > "John Rugo" <jwrugo@.patmedia.net> schrieb im Newsbeitrag
> > news:ObRFOWIfDHA.2320@.TK2MSFTNGP12.phx.gbl...
> > > Hi All,
> > >
> > > I have not been using my SQL server 2000 for a while on this
particular
> > > machine. I had my account disabled and just got it re-enabled at
work.
> > > Login name is the same and password has changed as it does every 30
> days.
> > I
> > > am trying to get into my server but keep getting the following error
> > > message:
> > >
> > > "SQL Server registration Failed because of the connection failure
> > displayed
> > > below. Do you wish to Register anyway?"
> > >
> > > "Cannot open user default database. Login Failed"
> > >
> > > I am at a loss and if anyone could suggest something to me other than
> > > un-installing the instance and re-installing it, I would be
> appreciative.
> > >
> > > Thanks,
> > > John
> > >
> > >
> >
> >
>

cannot generate SSPI context

Hi,
This only happens on a particular user's machine so far. the user is using
ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k server.
With the MS Access running , suddenly the error happend when i ping the sql
server i can get its ip addr
i have checked the ms article on the SSPI but it does not seem to apply for
me in my case
appreciate any advise
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forum...tivity/200512/1One thing to check is the SQL Client Network stack. This is configured in th
e
(SQL Server) Client Network Utility. What you will probably find is that the
working clients either have Named Pipes before TCP/IP, or left out TCP/IP.
While the problem client will have TCP/IP first, or left out Named Pipes.
At a guess, you are running the SQL Server with a Domain Account, but it
does not have the permission to register the SQL Server's SPN (Service
Principal Name). This means that it cannot use delegation, which probably
isn't a problem for you guys. But when someone tries to attach using TCP/IP,
it can't use Kerberos and throws the error.
Clients that connect Named Pipes just by-pass Kerberos and security account
delegation.
I may have gotten a couple of the details mixed up, I'm not 100% on this.
There is a good Trouble Shooting page in the SQL Support and in BOL, under
Administering SQL Server is a page called "Security Account Delegation" that
is worth a read.
Good luck
"maxzsim via droptable.com" wrote:

> Hi,
>
> This only happens on a particular user's machine so far. the user is usin
g
> ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k serve
r.
> With the MS Access running , suddenly the error happend when i ping the s
ql
> server i can get its ip addr
> i have checked the ms article on the SSPI but it does not seem to apply fo
r
> me in my case
> appreciate any advise
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forum...tivity/200512/1
>

cannot generate SSPI context

Hi,
This only happens on a particular user's machine so far. the user is using
ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k server.
With the MS Access running , suddenly the error happend when i ping the sql
server i can get its ip addr
i have checked the ms article on the SSPI but it does not seem to apply for
me in my case
appreciate any advise
tks & rdgs
Message posted via droptable.com
http://www.droptable.com/Uwe/Forums...ivity/200512/1
One thing to check is the SQL Client Network stack. This is configured in the
(SQL Server) Client Network Utility. What you will probably find is that the
working clients either have Named Pipes before TCP/IP, or left out TCP/IP.
While the problem client will have TCP/IP first, or left out Named Pipes.
At a guess, you are running the SQL Server with a Domain Account, but it
does not have the permission to register the SQL Server's SPN (Service
Principal Name). This means that it cannot use delegation, which probably
isn't a problem for you guys. But when someone tries to attach using TCP/IP,
it can't use Kerberos and throws the error.
Clients that connect Named Pipes just by-pass Kerberos and security account
delegation.
I may have gotten a couple of the details mixed up, I'm not 100% on this.
There is a good Trouble Shooting page in the SQL Support and in BOL, under
Administering SQL Server is a page called "Security Account Delegation" that
is worth a read.
Good luck
"maxzsim via droptable.com" wrote:

> Hi,
>
> This only happens on a particular user's machine so far. the user is using
> ms access, using odbc link to connect to SQL Server 2000 SP3a on W2k server.
> With the MS Access running , suddenly the error happend when i ping the sql
> server i can get its ip addr
> i have checked the ms article on the SSPI but it does not seem to apply for
> me in my case
> appreciate any advise
> tks & rdgs
> --
> Message posted via droptable.com
> http://www.droptable.com/Uwe/Forums...ivity/200512/1
>