Re: SQL 2005 Express-Database does not have a valid owner?

Error 0x54b is: (Win32) 0x54b (1355) - The specified domain either does not
exist or could not be contacted.

This means that the account running your SQL service cannot contact the
domain controller for the domain 'MYDOMAIN' to get the account information
for 'MYDOMAIN\MyUserAccount'. Usually, NETWORK SERVICE should be able to do
this, so it should not be an error in the instalation. An often case when
this error happens is when working on a machine that is joined to the domain
but not currently connected to the domain (like when I take my work laptop
and work on it from home). In this case you can log into the SQL Server
using your cached Windows credentials, but SQL Server cannot use this cached
credentials to verify the account info when you try things like CREATE LOGIN
.... FROM WINDOWS or EXECUTE AS.

--
This posting is provided "AS IS" with no warranties, and confers no rights.

HTH,
~ Remus Rusanu

SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"news.sbcglobal.net" <groomeryNOSPAM@xxxxxxxxxxxxxxxxxxx> wrote in message
news:RK3fg.103240$dW3.36220@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
The account running my SQL Server Service is 'NETWORK SERVICE'

Here is the error message I received (note that I have changed the name of
the domain and the user account):

Msg 15404, Level 16, State 19, Line 2
Could not obtain information about Windows NT group/user
'MYDOMAIN\MyUserAccount', error code 0x54b.

I'm curious, was this an error in the way I installed SQL Server? Thanks
again for your help?



"Remus Rusanu [MSFT]" <remus.rusanu@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eKkffyChGHA.1520@xxxxxxxxxxxxxxxxxxxxxxx
What account is running your SQL Server service?

Logged in as 'MYDOMAIN\MyUserAccount', can you run this test script and
tell me if it works or if you get an error:

CREATE DATABASE [testdb];
GO

USE [testdb];
GO

EXECUTE AS USER = 'dbo';
GO

REVERT;
GO

--
This posting is provided "AS IS" with no warranties, and confers no
rights.

HTH,
~ Remus Rusanu

SQL Service Broker
http://msdn2.microsoft.com/en-us/library/ms166043(en-US,SQL.90).aspx
"news.sbcglobal.net" <groomeryNOSPAM@xxxxxxxxxxxxxxxxxxx> wrote in
message news:7u0fg.43006$Lm5.1031@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Thanks for the reply. I didn't import the database. In fact I created
it on the same computer I'm using right now.

However, when I went to Security - Logins, I found that there was no
entry for MYDOMAIN\MyUserAccount, and when I tried to add it, there was
no option but to add local users. I double checked just now and found
that MYDOMAIN\MyUserAccount is an administrator on this machine.

Since I created this database on this machine and SQL Server recognized
me long enough to assign ownership of the database to me, I can't
understand why it isn't recognizing me now. Just so I can keep working,
I've changed ownership to 'SA' as someone recommended earlier, but I
really want to be able to use Windows Authentication in this database
and I still don't think I'm any closer to being able to do that.

I've read everything I can get my hands on about SQL Server security and
I can't find where (or if) I'm going wrong. I'm still in the market for
a solution to this problem if anyone has any other ideas.

Thanks!

"PSPDBA" <DissendiumDBA@xxxxxxxxx> wrote in message
news:1148990978.353719.231850@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
If this database was imported from somewhere else, the
MYDOMAIN\MyUserAccount may own the database, but may not be a valid
logon to the SQL Server. Check the Security - Logins to see whats in
there. My guess is that you'll find something is strange in that
configuration.









.

Relevant Pages

  • Re: SQL account rights
    ... Please advice what is the best, suitable rights rather than domain admin ... Warren Brunk - MCITP - SQL 2005, ... Add it as a login to the SQL Server ... files, or backups, make sure that the service account has Full ...
    (microsoft.public.sqlserver.security)
  • Re: User authentication
    ... There are 2 SQL Server 2005 ... 1 SQL Server 2000 installed on another server ... Windows account instead to run backup jobs. ...
    (microsoft.public.sqlserver.clients)
  • Re: SQL 2000 Server gets hacked
    ... Thank you Beth. ... > placed a strong password on the 'sa' account?) ... Your SQl Service itself shouldn't be running as a ... (SQL Agent requires more, but not SQL Server). ...
    (microsoft.public.sqlserver.security)
  • Re: SQL 2000 Server gets hacked
    ... Thank you Beth. ... > placed a strong password on the 'sa' account?) ... Your SQl Service itself shouldn't be running as a ... (SQL Agent requires more, but not SQL Server). ...
    (microsoft.public.sqlserver.security)
  • Re: Microsoft Search service cannot be administered under the present user error SP3
    ... - Have not modified Administrator account, but i ran the SQL script anyway. ... SQL account is not a local administrator. ... > has this server ever been upgrade from SQL Server 7.0 or is this SQL ...
    (microsoft.public.sqlserver.fulltext)