Can't set the owner to the current login

I'm using express edition, compatibility set to 2005.

I'm logged in as DOMAIN\user, using windows authentication.

When I try to set the owner to this login, I get a "login does not exist on the server" error. Setting the owner to sa works fine.

Any fix to this problem ? Also - can I just work with the owner set to sa or can this cause problems in the future ?

Thanks.

If you could supply a little code that reproduces the error we could probably get an answer for you. What objects are you trying to own?

Yes, you can set the owner to sa, but then you have to work with the object as that login. It would be better to have that object owned by someone with only the rights that they absolutely need.

|||

The property that I'm trying to set is the database owner - in the database properties' files page. I need to do this in order to use diagrams, which are not available without a valid owner.

|||I see. Express doesn't allow diagrams.|||

Buck,

Thank you for trying to help.

The diagrams work fine - but the thing is that I have to set the owner to sa in order to work with them. The problem is that although I am logged in as DOMAIN\user, the server claims there is no such login when I try to set the database owner to that login.

|||

u may be login as Domain/User but in the database the user mapped to this login may be different .. check that...

SP_helpLogins 'Domian/Username' -- to get all the users mapped to this login

Madhu

|||

You know what - you're right! I was working on the older Express versions.

http://blogs.msdn.com/vsdata/archive/2004/09/30/236215.aspx

They have indeed put the diagrams back into Express.

Anyway, you seem to have a different issue, then. Have you tried putting the domain\user in the sysadmins group in SQL Server? I don't suggest leaving them there, but that might help you narrow the problem down. You only need to be in the db_owner role, but you can go high and bring the user account to that role later.

What message are you getting in the logs about this?

|||

I'm sorry, but I'm a newbie to sqlserver.

I guess I need to do some more reading before I can try to do these things (like putting the domain\user in the sysadmins group or using SP_helpLogins). I'm using Mannagement Studio Express and I can't find the correct way to do it.

sql

can't register server in enterprise manager

I have a SQL 2000 Server that I just recently moved into an AD domain from
an NT domain. We created new windows authentication accounts for all users
and things have worked fine except for a couple of people. Three people
can't access any databases.
On my PC, if I login as myself and go to EM I can register this server with
no problems. If I login as one of these users, I get the following when
trying to register the server:
A connection could not be established to <servername>
Reason: Login failed for user <domain>\<user>
Please verify SQL Server is running and check your SQL Server registration
properties and try again.
SQL is definitely running and it is not a password problem since I logged in
just fine to the PC. Also, the user has local Administrator access to the
PC. I don't understand why 3 out of 30 login accounts are doing this. Can
anyone help?
Thanks.Hello,
You may want to first create a new domain user and then add it as a SQL
login to test the sitaution. If the issue does not occur, it seems to be
some issue with the specific user accounts. You may want to try following
steps for a problemtic domain login.
1. Remove all SQL logins with similar name from SQL logins
2. Remove the domain user from the AD
3. Try to create a new domain user with the same name, and add it again as
a SQL login.
4. Test if the issue still occurs at this time.
If the issue perists, you may try the following steps to isolate the issue:
1. Add the following registry keys:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
DisableStrictNameChecking DWORD Value=1
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
DisableLoopbackCheck DWORD
Value=1
2. Edit the Local Security policy and set ?Network Security: LAN Manager
authentication level? to ?Send LM and NTLM responses?
3. Test if the issue occurs at this time.
926642 Error message when you try to access a server locally by using its
FQDN or its CNAME alias after you install Windows Server 2003 Service Pack
1: "Access denied" or "No network provider accepted the given network path"
http://support.microsoft.com/default.aspx?scid=kb;EN-US;926642
If you have any update on the issue, please feel free to let's know. Thank
you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||r
Take a look into ERROR.LOG , what is says?
When you create a login for one of those people what default database you
granted for them? Does it exist? Perhaps it is in suspect mode?
"r" <none@.none.com> wrote in message
news:uqolHls%23HHA.3900@.TK2MSFTNGP02.phx.gbl...
>I have a SQL 2000 Server that I just recently moved into an AD domain from
>an NT domain. We created new windows authentication accounts for all users
>and things have worked fine except for a couple of people. Three people
>can't access any databases.
> On my PC, if I login as myself and go to EM I can register this server
> with no problems. If I login as one of these users, I get the following
> when trying to register the server:
> A connection could not be established to <servername>
> Reason: Login failed for user <domain>\<user>
> Please verify SQL Server is running and check your SQL Server
> registration properties and try again.
> SQL is definitely running and it is not a password problem since I logged
> in just fine to the PC. Also, the user has local Administrator access to
> the PC. I don't understand why 3 out of 30 login accounts are doing this.
> Can anyone help?
> Thanks.
>

can't register server

I have SQL Server 2k, sp3a, on a w2k, sp4 box. I'm at home, where I
have no domain. I have two clients, one w2k Pro, sp4, and the other
XP, sp1. I'm using Windows authentication. Neither can register my
server. The error msg is the same for both:
<mysvr> - SQL Server does not exist or access denied.
ConnectionOpen (Connect())
Mind you, the server did show up in the client window, so the client
does seem to know that the server does exist.
Might anyone have an iea as to what I've done wrong? Or haven't done?
Thanks in advance,
Tom
Do you have a firewall running on the box that is hosting SQL Server?
Perhaps it is blocking the connection attempts.
Keith
"Tcs" <tsmith@.eastpointcityNoSpam.org> wrote in message
news:s5ev619fasn9sskr0pdvevu9mfarrldo3l@.4ax.com...
>I have SQL Server 2k, sp3a, on a w2k, sp4 box. I'm at home, where I
> have no domain. I have two clients, one w2k Pro, sp4, and the other
> XP, sp1. I'm using Windows authentication. Neither can register my
> server. The error msg is the same for both:
> <mysvr> - SQL Server does not exist or access denied.
> ConnectionOpen (Connect())
> Mind you, the server did show up in the client window, so the client
> does seem to know that the server does exist.
> Might anyone have an iea as to what I've done wrong? Or haven't done?
> Thanks in advance,
> Tom
>
|||Tom hi,
Did you check your client network utility in your clients. Is any record in
there?
You use DHCP or static IP?
Is your name resolution correct?
Are your windows logins in the SQL Server logins?
Check these first
HTH
Andreas
"Tcs" wrote:

> I have SQL Server 2k, sp3a, on a w2k, sp4 box. I'm at home, where I
> have no domain. I have two clients, one w2k Pro, sp4, and the other
> XP, sp1. I'm using Windows authentication. Neither can register my
> server. The error msg is the same for both:
> <mysvr> - SQL Server does not exist or access denied.
> ConnectionOpen (Connect())
> Mind you, the server did show up in the client window, so the client
> does seem to know that the server does exist.
> Might anyone have an iea as to what I've done wrong? Or haven't done?
> Thanks in advance,
> Tom
>

Can't get SQL 2000 agent to run

Need urgent help. The sql 2000 agent service never runs. Tried to run under a
domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
the sqlagent with -c -v switches from command line and got foll. 2 errors:
[298] sql server error 170, line 47: incorrect syntax near 'collate'.
[sqlstate 42000] (connisloginsysadmin)
[000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
but '(Unknown)' is not a member of the SysAdmin role
Tried the microsoft kb solns and still not running. Need this resolved
urgently. Pls help. Thks. We use sql 2000, sp4.Hi
How about using Service Control Manager.
EXEC master..xp_servicecontrol 'QUERYSTATE', 'SQLSERVERAGENT'
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:588DF7E4-D96A-4BAD-A1A5-44636138EE54@.microsoft.com...
> Need urgent help. The sql 2000 agent service never runs. Tried to run
> under a
> domain admin acct which belongs to SysAdmins role and still doesn't run.
> Ran
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.|||Hi
I don't see collate in any of the statements issued when SQL Agent is
stopped or started. You may want to profile the agent starting (including
errors and exception events) to see what is being processed.
Is there any other messages in the SQL Server logs?
Have you tried running this as the system account?
John
John
"duchov" wrote:
> Need urgent help. The sql 2000 agent service never runs. Tried to run under a
> domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
> the sqlagent with -c -v switches from command line and got foll. 2 errors:
> [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> [sqlstate 42000] (connisloginsysadmin)
> [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> but '(Unknown)' is not a member of the SysAdmin role
> Tried the microsoft kb solns and still not running. Need this resolved
> urgently. Pls help. Thks. We use sql 2000, sp4.|||"John Bell" wrote:
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
> > Need urgent help. The sql 2000 agent service never runs. Tried to run under a
> > domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
> > the sqlagent with -c -v switches from command line and got foll. 2 errors:
> >
> > [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> >
> > [sqlstate 42000] (connisloginsysadmin)
> >
> > [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> >
> > but '(Unknown)' is not a member of the SysAdmin role
> > Tried the microsoft kb solns and still not running. Need this resolved
> > urgently. Pls help. Thks. We use sql 2000, sp4.|||Hi John/Uri
setting the agent acct from either EM or service ctrl mngr has same result.
Only other errors in the sql logs are:
1) Operating system error = 31(A device attached to the system is not
functioning.).
This error is in multiple logs though not the current log. Any ideas on this?
2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
will see that 15457 error
popup if you pull up your SQL Server properties.)
3) Configuration option 'show advanced options' changed from 1 to 1. Run the
RECONFIGURE statement
to install..
Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
server properties
Initially agent was under local sys acct n it never ran which is y tried a
domain admin acct but still no success
How do I profile the agent startup/shutdown? I ran a trace via sql profiler
(included errors/exceptions) and manually tried to start agent. the trace
showed 2 records under an application name of sqlAgent - initial boot probe
with no info really. is this what u meant?
Reason this is important is b/c I scheduled some nightly sql backups to disk
n they never run b/c the agent service never starts. Hope u can help.
"John Bell" wrote:
> Hi
> I don't see collate in any of the statements issued when SQL Agent is
> stopped or started. You may want to profile the agent starting (including
> errors and exception events) to see what is being processed.
> Is there any other messages in the SQL Server logs?
> Have you tried running this as the system account?
> John
> John
> "duchov" wrote:
> > Need urgent help. The sql 2000 agent service never runs. Tried to run under a
> > domain admin acct which belongs to SysAdmins role and still doesn't run. Ran
> > the sqlagent with -c -v switches from command line and got foll. 2 errors:
> >
> > [298] sql server error 170, line 47: incorrect syntax near 'collate'.
> >
> > [sqlstate 42000] (connisloginsysadmin)
> >
> > [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
> >
> > but '(Unknown)' is not a member of the SysAdmin role
> > Tried the microsoft kb solns and still not running. Need this resolved
> > urgently. Pls help. Thks. We use sql 2000, sp4.|||Hi
An Operating System Errors seems like the problem is external to SQL server,
is there anything in the System Event logs?
John
"duchov" <duchov@.discussions.microsoft.com> wrote in message
news:885311AD-1FAC-4745-9430-D1F1A573796E@.microsoft.com...
> Hi John/Uri
> setting the agent acct from either EM or service ctrl mngr has same
> result.
> Only other errors in the sql logs are:
> 1) Operating system error = 31(A device attached to the system is not
> functioning.).
> This error is in multiple logs though not the current log. Any ideas on
> this?
> 2) spid52 Error: 15457, Severity: 0, State: 1 (a sql support site said You
> will see that 15457 error
> popup if you pull up your SQL Server properties.)
> 3) Configuration option 'show advanced options' changed from 1 to 1. Run
> the
> RECONFIGURE statement
> to install..
> Errors 2 & 3 are in today's log only and seems to be b/c checked the sql
> server properties
> Initially agent was under local sys acct n it never ran which is y tried a
> domain admin acct but still no success
> How do I profile the agent startup/shutdown? I ran a trace via sql
> profiler
> (included errors/exceptions) and manually tried to start agent. the trace
> showed 2 records under an application name of sqlAgent - initial boot
> probe
> with no info really. is this what u meant?
> Reason this is important is b/c I scheduled some nightly sql backups to
> disk
> n they never run b/c the agent service never starts. Hope u can help.
> "John Bell" wrote:
>> Hi
>> I don't see collate in any of the statements issued when SQL Agent is
>> stopped or started. You may want to profile the agent starting (including
>> errors and exception events) to see what is being processed.
>> Is there any other messages in the SQL Server logs?
>> Have you tried running this as the system account?
>> John
>> John
>> "duchov" wrote:
>> > Need urgent help. The sql 2000 agent service never runs. Tried to run
>> > under a
>> > domain admin acct which belongs to SysAdmins role and still doesn't
>> > run. Ran
>> > the sqlagent with -c -v switches from command line and got foll. 2
>> > errors:
>> >
>> > [298] sql server error 170, line 47: incorrect syntax near 'collate'.
>> >
>> > [sqlstate 42000] (connisloginsysadmin)
>> >
>> > [000] SQLServerAgent must be able to connect to SQLServer as SysAdmin,
>> >
>> > but '(Unknown)' is not a member of the SysAdmin role
>> > Tried the microsoft kb solns and still not running. Need this resolved
>> > urgently. Pls help. Thks. We use sql 2000, sp4.