Cannot create diagram and not run jobs with my domain account logi

Hi!
I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in with
my domain account (HIK\Tommy) wich is a member of the Administrators group on
my computer and there is a corresponding Windows login account with sysadmin
permissions in SQL Server.
I can do most things with that account, BUT when I try to create a diagram
to a database. SQL does not like the owner of the database (my domain
account)
This is the error message that show up:
"Database diagram support objects cannot be installed because this database
does not have a valid owner. To continue, first use the Files page of the
Database Properties dialog box or ALTER AUTHORIZATION statement to set the
database owner to a valid login, then add the database diagram support
objects."
Again when I try to run a job that is owned by my domain account (HIK\Tommy)
Following message arise:
"The job failed. Unable to determine if the owner (HIK\Tommy) of job
MaintenancePlan2 has server access (reason: Could not obtain information
about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE 42000]
(Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error
3621))."
I would be very grateful if you could come up with some suggestions.
Regards
TommyThis might be due to a mismatch between the 'dbo' user mapping and the
actual database owner. You can correct this with sp_changedbowner:
USE MyDatabase
EXEC sp_changedbowner 'HIK\Tommy'
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tommy" <Tommy@.discussions.microsoft.com> wrote in message
news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
> Hi!
> I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in with
> my domain account (HIK\Tommy) wich is a member of the Administrators group
> on
> my computer and there is a corresponding Windows login account with
> sysadmin
> permissions in SQL Server.
> I can do most things with that account, BUT when I try to create a diagram
> to a database. SQL does not like the owner of the database (my domain
> account)
> This is the error message that show up:
> "Database diagram support objects cannot be installed because this
> database
> does not have a valid owner. To continue, first use the Files page of the
> Database Properties dialog box or ALTER AUTHORIZATION statement to set the
> database owner to a valid login, then add the database diagram support
> objects."
> Again when I try to run a job that is owned by my domain account
> (HIK\Tommy)
> Following message arise:
> "The job failed. Unable to determine if the owner (HIK\Tommy) of job
> MaintenancePlan2 has server access (reason: Could not obtain information
> about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE 42000]
> (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error
> 3621))."
> I would be very grateful if you could come up with some suggestions.
> Regards
> Tommy|||Thanks for your suggestion but it does not work.
USE MyDatabase
EXEC sp_changedbowner 'HIK\Tommy'
doesn't change anything.
On the other hand it 's possible to change user to sa and everything works
OK, so it's my domain name that is the trouble. Have never had this problem i
SQL Server 2K.
/Tommy
"Dan Guzman" wrote:
> This might be due to a mismatch between the 'dbo' user mapping and the
> actual database owner. You can correct this with sp_changedbowner:
> USE MyDatabase
> EXEC sp_changedbowner 'HIK\Tommy'
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
> > Hi!
> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in with
> > my domain account (HIK\Tommy) wich is a member of the Administrators group
> > on
> > my computer and there is a corresponding Windows login account with
> > sysadmin
> > permissions in SQL Server.
> >
> > I can do most things with that account, BUT when I try to create a diagram
> > to a database. SQL does not like the owner of the database (my domain
> > account)
> >
> > This is the error message that show up:
> > "Database diagram support objects cannot be installed because this
> > database
> > does not have a valid owner. To continue, first use the Files page of the
> > Database Properties dialog box or ALTER AUTHORIZATION statement to set the
> > database owner to a valid login, then add the database diagram support
> > objects."
> >
> > Again when I try to run a job that is owned by my domain account
> > (HIK\Tommy)
> >
> > Following message arise:
> >
> > "The job failed. Unable to determine if the owner (HIK\Tommy) of job
> > MaintenancePlan2 has server access (reason: Could not obtain information
> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE 42000]
> > (Error 15404) The statement has been terminated. [SQLSTATE 01000] (Error
> > 3621))."
> >
> > I would be very grateful if you could come up with some suggestions.
> >
> > Regards
> > Tommy
>
>|||My apologies but I misread your post. I guess I should a finished my coffee
first :-)
For your first issue, the database needs to be in 90 compatibility mode in
order to create diagrams.
Regarding your second problem, run the SQL Server Configuration utility to
make sure the SQL Agent isn't running under the Network Service account.
Use a domain account.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tommy" <Tommy@.discussions.microsoft.com> wrote in message
news:753C2D7A-C719-4B67-8CCD-0E3A03A9B8D5@.microsoft.com...
> Thanks for your suggestion but it does not work.
> USE MyDatabase
> EXEC sp_changedbowner 'HIK\Tommy'
> doesn't change anything.
> On the other hand it 's possible to change user to sa and everything works
> OK, so it's my domain name that is the trouble. Have never had this
> problem i
> SQL Server 2K.
> /Tommy
> "Dan Guzman" wrote:
>> This might be due to a mismatch between the 'dbo' user mapping and the
>> actual database owner. You can correct this with sp_changedbowner:
>> USE MyDatabase
>> EXEC sp_changedbowner 'HIK\Tommy'
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
>> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
>> > Hi!
>> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in
>> > with
>> > my domain account (HIK\Tommy) wich is a member of the Administrators
>> > group
>> > on
>> > my computer and there is a corresponding Windows login account with
>> > sysadmin
>> > permissions in SQL Server.
>> >
>> > I can do most things with that account, BUT when I try to create a
>> > diagram
>> > to a database. SQL does not like the owner of the database (my domain
>> > account)
>> >
>> > This is the error message that show up:
>> > "Database diagram support objects cannot be installed because this
>> > database
>> > does not have a valid owner. To continue, first use the Files page of
>> > the
>> > Database Properties dialog box or ALTER AUTHORIZATION statement to set
>> > the
>> > database owner to a valid login, then add the database diagram support
>> > objects."
>> >
>> > Again when I try to run a job that is owned by my domain account
>> > (HIK\Tommy)
>> >
>> > Following message arise:
>> >
>> > "The job failed. Unable to determine if the owner (HIK\Tommy) of job
>> > MaintenancePlan2 has server access (reason: Could not obtain
>> > information
>> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE
>> > 42000]
>> > (Error 15404) The statement has been terminated. [SQLSTATE 01000]
>> > (Error
>> > 3621))."
>> >
>> > I would be very grateful if you could come up with some suggestions.
>> >
>> > Regards
>> > Tommy
>>|||Using a domain account for the Agent and SQL Server service solves the
problem with recognizeing job owner as my domain login (HIK\Tommy), but it
still don't like my domain login as database owner when trying to create a
diagram.
My administrator don't want me to use a domain account for services for
security reasons so, I'm going to use a workaround, e.g. use sa as owner
until this bug (?) is fixed.
Thank's anyway
Tommy
"Dan Guzman" wrote:
> My apologies but I misread your post. I guess I should a finished my coffee
> first :-)
> For your first issue, the database needs to be in 90 compatibility mode in
> order to create diagrams.
> Regarding your second problem, run the SQL Server Configuration utility to
> make sure the SQL Agent isn't running under the Network Service account.
> Use a domain account.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
> news:753C2D7A-C719-4B67-8CCD-0E3A03A9B8D5@.microsoft.com...
> > Thanks for your suggestion but it does not work.
> >
> > USE MyDatabase
> > EXEC sp_changedbowner 'HIK\Tommy'
> >
> > doesn't change anything.
> >
> > On the other hand it 's possible to change user to sa and everything works
> > OK, so it's my domain name that is the trouble. Have never had this
> > problem i
> > SQL Server 2K.
> >
> > /Tommy
> >
> > "Dan Guzman" wrote:
> >
> >> This might be due to a mismatch between the 'dbo' user mapping and the
> >> actual database owner. You can correct this with sp_changedbowner:
> >>
> >> USE MyDatabase
> >> EXEC sp_changedbowner 'HIK\Tommy'
> >>
> >> --
> >> Hope this helps.
> >>
> >> Dan Guzman
> >> SQL Server MVP
> >>
> >> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
> >> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
> >> > Hi!
> >> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging in
> >> > with
> >> > my domain account (HIK\Tommy) wich is a member of the Administrators
> >> > group
> >> > on
> >> > my computer and there is a corresponding Windows login account with
> >> > sysadmin
> >> > permissions in SQL Server.
> >> >
> >> > I can do most things with that account, BUT when I try to create a
> >> > diagram
> >> > to a database. SQL does not like the owner of the database (my domain
> >> > account)
> >> >
> >> > This is the error message that show up:
> >> > "Database diagram support objects cannot be installed because this
> >> > database
> >> > does not have a valid owner. To continue, first use the Files page of
> >> > the
> >> > Database Properties dialog box or ALTER AUTHORIZATION statement to set
> >> > the
> >> > database owner to a valid login, then add the database diagram support
> >> > objects."
> >> >
> >> > Again when I try to run a job that is owned by my domain account
> >> > (HIK\Tommy)
> >> >
> >> > Following message arise:
> >> >
> >> > "The job failed. Unable to determine if the owner (HIK\Tommy) of job
> >> > MaintenancePlan2 has server access (reason: Could not obtain
> >> > information
> >> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE
> >> > 42000]
> >> > (Error 15404) The statement has been terminated. [SQLSTATE 01000]
> >> > (Error
> >> > 3621))."
> >> >
> >> > I would be very grateful if you could come up with some suggestions.
> >> >
> >> > Regards
> >> > Tommy
> >>
> >>
> >>
>
>|||> My administrator don't want me to use a domain account for services for
> security reasons so, I'm going to use a workaround, e.g. use sa as owner
> until this bug (?) is fixed.
The Books Online (Setting up Windows Accounts) states that it is best is to
use minimally privileged accounts for services. If you don't want to use a
low privilege domain user, you can use a (minimally privileged) local
Windows user account. I don't think this a a bug, it's just that SQL 2005
is more secure out-of-the-box so additional configuration work is needed to
loosen up security according to your organization's security policies.
--
Hope this helps.
Dan Guzman
SQL Server MVP
"Tommy" <Tommy@.discussions.microsoft.com> wrote in message
news:ED165CD9-5A84-4D4F-AC22-BF57C87A1A16@.microsoft.com...
> Using a domain account for the Agent and SQL Server service solves the
> problem with recognizeing job owner as my domain login (HIK\Tommy), but it
> still don't like my domain login as database owner when trying to create a
> diagram.
> My administrator don't want me to use a domain account for services for
> security reasons so, I'm going to use a workaround, e.g. use sa as owner
> until this bug (?) is fixed.
> Thank's anyway
> Tommy
> "Dan Guzman" wrote:
>> My apologies but I misread your post. I guess I should a finished my
>> coffee
>> first :-)
>> For your first issue, the database needs to be in 90 compatibility mode
>> in
>> order to create diagrams.
>> Regarding your second problem, run the SQL Server Configuration utility
>> to
>> make sure the SQL Agent isn't running under the Network Service account.
>> Use a domain account.
>> --
>> Hope this helps.
>> Dan Guzman
>> SQL Server MVP
>> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
>> news:753C2D7A-C719-4B67-8CCD-0E3A03A9B8D5@.microsoft.com...
>> > Thanks for your suggestion but it does not work.
>> >
>> > USE MyDatabase
>> > EXEC sp_changedbowner 'HIK\Tommy'
>> >
>> > doesn't change anything.
>> >
>> > On the other hand it 's possible to change user to sa and everything
>> > works
>> > OK, so it's my domain name that is the trouble. Have never had this
>> > problem i
>> > SQL Server 2K.
>> >
>> > /Tommy
>> >
>> > "Dan Guzman" wrote:
>> >
>> >> This might be due to a mismatch between the 'dbo' user mapping and the
>> >> actual database owner. You can correct this with sp_changedbowner:
>> >>
>> >> USE MyDatabase
>> >> EXEC sp_changedbowner 'HIK\Tommy'
>> >>
>> >> --
>> >> Hope this helps.
>> >>
>> >> Dan Guzman
>> >> SQL Server MVP
>> >>
>> >> "Tommy" <Tommy@.discussions.microsoft.com> wrote in message
>> >> news:72BBE688-4C5D-4472-8404-513522E803A1@.microsoft.com...
>> >> > Hi!
>> >> > I'm using SQL Server 2005 Dev. Ed. on a local machine. I'm logging
>> >> > in
>> >> > with
>> >> > my domain account (HIK\Tommy) wich is a member of the Administrators
>> >> > group
>> >> > on
>> >> > my computer and there is a corresponding Windows login account with
>> >> > sysadmin
>> >> > permissions in SQL Server.
>> >> >
>> >> > I can do most things with that account, BUT when I try to create a
>> >> > diagram
>> >> > to a database. SQL does not like the owner of the database (my
>> >> > domain
>> >> > account)
>> >> >
>> >> > This is the error message that show up:
>> >> > "Database diagram support objects cannot be installed because this
>> >> > database
>> >> > does not have a valid owner. To continue, first use the Files page
>> >> > of
>> >> > the
>> >> > Database Properties dialog box or ALTER AUTHORIZATION statement to
>> >> > set
>> >> > the
>> >> > database owner to a valid login, then add the database diagram
>> >> > support
>> >> > objects."
>> >> >
>> >> > Again when I try to run a job that is owned by my domain account
>> >> > (HIK\Tommy)
>> >> >
>> >> > Following message arise:
>> >> >
>> >> > "The job failed. Unable to determine if the owner (HIK\Tommy) of
>> >> > job
>> >> > MaintenancePlan2 has server access (reason: Could not obtain
>> >> > information
>> >> > about Windows NT group/user 'HIK\Tommy', error code 0xea. [SQLSTATE
>> >> > 42000]
>> >> > (Error 15404) The statement has been terminated. [SQLSTATE 01000]
>> >> > (Error
>> >> > 3621))."
>> >> >
>> >> > I would be very grateful if you could come up with some suggestions.
>> >> >
>> >> > Regards
>> >> > Tommy
>> >>
>> >>
>> >>
>>

cannot create database error in sql express 2005

hi..

i have a pc that is on a domain with domain user rights and i installed a sql server express 2005..

when trying to create a new database am encountering an error:

create database permission denied in database 'master' (microsoft sql server error:262)

could anyone help how to go about this..am new to sql express.

thanks

So it seems that your are not logged in with a Windows account which has sufficient priviliedge "Create Database" to perform this action. If you have an account that is local administrator, try to login with this one and execute your DDL Actions.

HTH, Jens Suessmeyer.|||

what do you mean by an account that is local admin? an account outside the domain?

what if i still want to work within the domain? what probably the best sufficient priviledge that i could use? domain admin account?

pls. clarify

thanks

|||By default the local admin group is in in the group of the server administrators, so the domain admin are usally also members of the local admin group and therefore sa′s. YOu just have to login with a user with more permissions than the current one you are trying with.

HTH, Jens Suessmeyer.|||

btw, am using windows authentication mode and not sql authentication mode.. will that be ok...and also a check with my privileges the user am currently using is also a member of administrator built in group.. but not domain admin.

thanks

|||what am trying to achieve here is that.. clients pc can use sql server express without giving them full priveleges to access others pc's folders except for those folders that are shared..|||You could create a group on the local machine and add your user to that group. Then in SQL Server give that group the permissions you want.|||

am having this error when trying to create a diagram. (you are not logged on as database owner or system administrator. you might not be able to save changes to tables that you do not own in sql server express...certain edits require create table permission)

i would greatly appreaciate helping me how to give permissions.. if possible the most step by step guide pls.)

thanks

|||

Hi

THIS WORKED!!!!

Go to SQL Server manager >> Security >> Logins and find an account named "NT AUTHORITY\NETWORK SERVICE"

Open this and in the SERVER ROLE tab, give it DBCREATOR permissioin. Thats it. now you will be able to create the database.

Reason: When SharePoint administration website connects SQL database, it uses the account "NT AUTHORITY\NETWORK SERVICE". So this account must have DBCREATEOR permission

hope this helps

Regards,

Ash

|||

It took me a while to find the "SQL Server manager" mentioned in the post above this post.

Eventually I found out that Ash31 meant the "Microsoft SQL Server Management Studio". =)

Hopefully this will help people like me who can't find the SQL Server manager.

cannot create database error in sql express 2005

hi..

i have a pc that is on a domain with domain user rights and i installed a sql server express 2005..

when trying to create a new database am encountering an error:

create database permission denied in database 'master' (microsoft sql server error:262)

could anyone help how to go about this..am new to sql express.

thanks

So it seems that your are not logged in with a Windows account which has sufficient priviliedge "Create Database" to perform this action. If you have an account that is local administrator, try to login with this one and execute your DDL Actions.

HTH, Jens Suessmeyer.|||

what do you mean by an account that is local admin? an account outside the domain?

what if i still want to work within the domain? what probably the best sufficient priviledge that i could use? domain admin account?

pls. clarify

thanks

|||By default the local admin group is in in the group of the server administrators, so the domain admin are usally also members of the local admin group and therefore sa′s. YOu just have to login with a user with more permissions than the current one you are trying with.

HTH, Jens Suessmeyer.|||

btw, am using windows authentication mode and not sql authentication mode.. will that be ok...and also a check with my privileges the user am currently using is also a member of administrator built in group.. but not domain admin.

thanks

|||what am trying to achieve here is that.. clients pc can use sql server express without giving them full priveleges to access others pc's folders except for those folders that are shared..|||You could create a group on the local machine and add your user to that group. Then in SQL Server give that group the permissions you want.|||

am having this error when trying to create a diagram. (you are not logged on as database owner or system administrator. you might not be able to save changes to tables that you do not own in sql server express...certain edits require create table permission)

i would greatly appreaciate helping me how to give permissions.. if possible the most step by step guide pls.)

thanks

|||

Hi

THIS WORKED!!!!

Go to SQL Server manager >> Security >> Logins and find an account named "NT AUTHORITY\NETWORK SERVICE"

Open this and in the SERVER ROLE tab, give it DBCREATOR permissioin. Thats it. now you will be able to create the database.

Reason: When SharePoint administration website connects SQL database, it uses the account "NT AUTHORITY\NETWORK SERVICE". So this account must have DBCREATEOR permission

hope this helps

Regards,

Ash

|||

It took me a while to find the "SQL Server manager" mentioned in the post above this post.

Eventually I found out that Ash31 meant the "Microsoft SQL Server Management Studio". =)

Hopefully this will help people like me who can't find the SQL Server manager.

|||

The answer you're looking for can be found here:

http://blogs.msdn.com/sqlexpress/archive/2006/11/15/sql-express-sp2-and-windows-vista-uac.aspx

SQL Server Express security works differently from the other versions - by default local admins are not part of the sysadmin role unless specifically set up that way during installation. You can do this post-install by using the SQL Server Surface Area Configuration tool as described in the aforementioned article.

HTH

cannot create database error in sql express 2005

hi..

i have a pc that is on a domain with domain user rights and i installed a sql server express 2005..

when trying to create a new database am encountering an error:

create database permission denied in database 'master' (microsoft sql server error:262)

could anyone help how to go about this..am new to sql express.

thanks

So it seems that your are not logged in with a Windows account which has sufficient priviliedge "Create Database" to perform this action. If you have an account that is local administrator, try to login with this one and execute your DDL Actions.

HTH, Jens Suessmeyer.|||

what do you mean by an account that is local admin? an account outside the domain?

what if i still want to work within the domain? what probably the best sufficient priviledge that i could use? domain admin account?

pls. clarify

thanks

|||By default the local admin group is in in the group of the server administrators, so the domain admin are usally also members of the local admin group and therefore sa′s. YOu just have to login with a user with more permissions than the current one you are trying with.

HTH, Jens Suessmeyer.|||

btw, am using windows authentication mode and not sql authentication mode.. will that be ok...and also a check with my privileges the user am currently using is also a member of administrator built in group.. but not domain admin.

thanks

|||what am trying to achieve here is that.. clients pc can use sql server express without giving them full priveleges to access others pc's folders except for those folders that are shared..|||You could create a group on the local machine and add your user to that group. Then in SQL Server give that group the permissions you want.|||

am having this error when trying to create a diagram. (you are not logged on as database owner or system administrator. you might not be able to save changes to tables that you do not own in sql server express...certain edits require create table permission)

i would greatly appreaciate helping me how to give permissions.. if possible the most step by step guide pls.)

thanks

|||

Hi

THIS WORKED!!!!

Go to SQL Server manager >> Security >> Logins and find an account named "NT AUTHORITY\NETWORK SERVICE"

Open this and in the SERVER ROLE tab, give it DBCREATOR permissioin. Thats it. now you will be able to create the database.

Reason: When SharePoint administration website connects SQL database, it uses the account "NT AUTHORITY\NETWORK SERVICE". So this account must have DBCREATEOR permission

hope this helps

Regards,

Ash

|||

It took me a while to find the "SQL Server manager" mentioned in the post above this post.

Eventually I found out that Ash31 meant the "Microsoft SQL Server Management Studio". =)

Hopefully this will help people like me who can't find the SQL Server manager.

cannot create database error in sql express 2005

hi..

i have a pc that is on a domain with domain user rights and i installed a sql server express 2005..

when trying to create a new database am encountering an error:

create database permission denied in database 'master' (microsoft sql server error:262)

could anyone help how to go about this..am new to sql express.

thanks

So it seems that your are not logged in with a Windows account which has sufficient priviliedge "Create Database" to perform this action. If you have an account that is local administrator, try to login with this one and execute your DDL Actions.

HTH, Jens Suessmeyer.|||

what do you mean by an account that is local admin? an account outside the domain?

what if i still want to work within the domain? what probably the best sufficient priviledge that i could use? domain admin account?

pls. clarify

thanks

|||By default the local admin group is in in the group of the server administrators, so the domain admin are usally also members of the local admin group and therefore sa′s. YOu just have to login with a user with more permissions than the current one you are trying with.

HTH, Jens Suessmeyer.|||

btw, am using windows authentication mode and not sql authentication mode.. will that be ok...and also a check with my privileges the user am currently using is also a member of administrator built in group.. but not domain admin.

thanks

|||what am trying to achieve here is that.. clients pc can use sql server express without giving them full priveleges to access others pc's folders except for those folders that are shared..|||You could create a group on the local machine and add your user to that group. Then in SQL Server give that group the permissions you want.|||

am having this error when trying to create a diagram. (you are not logged on as database owner or system administrator. you might not be able to save changes to tables that you do not own in sql server express...certain edits require create table permission)

i would greatly appreaciate helping me how to give permissions.. if possible the most step by step guide pls.)

thanks

|||

Hi

THIS WORKED!!!!

Go to SQL Server manager >> Security >> Logins and find an account named "NT AUTHORITY\NETWORK SERVICE"

Open this and in the SERVER ROLE tab, give it DBCREATOR permissioin. Thats it. now you will be able to create the database.

Reason: When SharePoint administration website connects SQL database, it uses the account "NT AUTHORITY\NETWORK SERVICE". So this account must have DBCREATEOR permission

hope this helps

Regards,

Ash

|||

It took me a while to find the "SQL Server manager" mentioned in the post above this post.

Eventually I found out that Ash31 meant the "Microsoft SQL Server Management Studio". =)

Hopefully this will help people like me who can't find the SQL Server manager.

|||

The answer you're looking for can be found here:

http://blogs.msdn.com/sqlexpress/archive/2006/11/15/sql-express-sp2-and-windows-vista-uac.aspx

SQL Server Express security works differently from the other versions - by default local admins are not part of the sysadmin role unless specifically set up that way during installation. You can do this post-install by using the SQL Server Surface Area Configuration tool as described in the aforementioned article.

HTH

cannot create database error in sql express 2005

hi..

i have a pc that is on a domain with domain user rights and i installed a sql server express 2005..

when trying to create a new database am encountering an error:

create database permission denied in database 'master' (microsoft sql server error:262)

could anyone help how to go about this..am new to sql express.

thanks

So it seems that your are not logged in with a Windows account which has sufficient priviliedge "Create Database" to perform this action. If you have an account that is local administrator, try to login with this one and execute your DDL Actions.

HTH, Jens Suessmeyer.|||

what do you mean by an account that is local admin? an account outside the domain?

what if i still want to work within the domain? what probably the best sufficient priviledge that i could use? domain admin account?

pls. clarify

thanks

|||By default the local admin group is in in the group of the server administrators, so the domain admin are usally also members of the local admin group and therefore sa′s. YOu just have to login with a user with more permissions than the current one you are trying with.

HTH, Jens Suessmeyer.|||

btw, am using windows authentication mode and not sql authentication mode.. will that be ok...and also a check with my privileges the user am currently using is also a member of administrator built in group.. but not domain admin.

thanks

|||what am trying to achieve here is that.. clients pc can use sql server express without giving them full priveleges to access others pc's folders except for those folders that are shared..|||You could create a group on the local machine and add your user to that group. Then in SQL Server give that group the permissions you want.|||

am having this error when trying to create a diagram. (you are not logged on as database owner or system administrator. you might not be able to save changes to tables that you do not own in sql server express...certain edits require create table permission)

i would greatly appreaciate helping me how to give permissions.. if possible the most step by step guide pls.)

thanks

|||

Hi

THIS WORKED!!!!

Go to SQL Server manager >> Security >> Logins and find an account named "NT AUTHORITY\NETWORK SERVICE"

Open this and in the SERVER ROLE tab, give it DBCREATOR permissioin. Thats it. now you will be able to create the database.

Reason: When SharePoint administration website connects SQL database, it uses the account "NT AUTHORITY\NETWORK SERVICE". So this account must have DBCREATEOR permission

hope this helps

Regards,

Ash

|||

It took me a while to find the "SQL Server manager" mentioned in the post above this post.

Eventually I found out that Ash31 meant the "Microsoft SQL Server Management Studio". =)

Hopefully this will help people like me who can't find the SQL Server manager.

|||

The answer you're looking for can be found here:

http://blogs.msdn.com/sqlexpress/archive/2006/11/15/sql-express-sp2-and-windows-vista-uac.aspx

SQL Server Express security works differently from the other versions - by default local admins are not part of the sysadmin role unless specifically set up that way during installation. You can do this post-install by using the SQL Server Surface Area Configuration tool as described in the aforementioned article.

HTH

Cannot connect to SQL Server from localhost (no problem from any xp client)

Hi ng!
The facts:
SQL Server 2005 is installed on a Windows 2003 server within a domain. Every
XP-Clients can connect to SQL Server via ODBC without any problems.
The problem
From the localhost I cannot connect to SQL-Server, AND from any (2) other
W2K
Server in the same domain I cannot connect to SQL Server.
Here is the original error message, in german:
SQLState: '01000'
SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
[Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
Have you any hints for me? I worked since 5 Days on this Problem...
The solution: :)
THX
Markus
PS: my german is much better...
Sorry for dubbleposting,I have not seen this ng bevor.For local, perhaps Shared Memory driver is disabled? See server config
manager, sql server 2005 network configuration tab.
For remote win2K, check surface area config for Remote Connections - are
both tcp and named pipes enables?
Also you can go to the win2K machines and set up aliases using ODBC or
native client managers.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
> Hi ng!
> The facts:
> SQL Server 2005 is installed on a Windows 2003 server within a domain.
> Every
> XP-Clients can connect to SQL Server via ODBC without any problems.
> The problem
> From the localhost I cannot connect to SQL-Server, AND from any (2) other
> W2K
> Server in the same domain I cannot connect to SQL Server.
>
> Here is the original error message, in german:
> SQLState: '01000'
> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>
> Have you any hints for me? I worked since 5 Days on this Problem...
> The solution: :)
> THX
> Markus
> PS: my german is much better...
> Sorry for dubbleposting,I have not seen this ng bevor.
>
>|||Shared Memory is disabled.
3 Clients are XP, there are all works fine
3 Servers 2K3 (2 of this are TS): nobody can connect the database
I am only use ODBC, no native client, only tcp is activ
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krh3qgfmd58d8@.corp.supernews.com...
> For local, perhaps Shared Memory driver is disabled? See server config
> manager, sql server 2005 network configuration tab.
> For remote win2K, check surface area config for Remote Connections - are
> both tcp and named pipes enables?
> Also you can go to the win2K machines and set up aliases using ODBC or
> native client managers.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a domain.
>> Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2) other
>> W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>|||Local connections on same box will attempt to use Shared Mem IIRC, so try
with it enabled.
You say you use only ODBC, but built-in sql server tools such as QA or SSMS
use whatever their default is set up to be, which could be named pipes. Try
forcibly setting the connection mechanism to tcp and see if it works.
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
> Shared Memory is disabled.
> 3 Clients are XP, there are all works fine
> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
> I am only use ODBC, no native client, only tcp is activ
> Markus
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server config
>> manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections - are
>> both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a domain.
>> Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2)
>> other W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>|||Hi Kevin!
SSMS with tcp/ip works.
I have try to connect via MSSMS to connect from a w2k3 serve to the other
w2k3 Server (SQL Server), this works.
The only thing is, I cannot connect via ODBC from local host or any other
W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
Workstion without problems.
The ODBC - Driver Config is the same on XP ans W2k3. I think the only
differnt ist the ODBC Driver Version:
On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
on W2K3 : 2000.86.3959.00
I am not use the native client, shared memory and tcp/ip is on, the rest
off, SQL Native Client: all is off
\\sqlserver\myprog is always map to s:\
myprog.exe and myprog.ini is always the same
My connection string looks like this (with and without integratet security):
DSN=MYPROG_MSSQL;Database=MYPROG
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password;Trusted_Connection=No;Encrypt=No;
Any Ideas?
THX in advanced
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krpmsnuutd460@.corp.supernews.com...
> Local connections on same box will attempt to use Shared Mem IIRC, so try
> with it enabled.
> You say you use only ODBC, but built-in sql server tools such as QA or
> SSMS use whatever their default is set up to be, which could be named
> pipes. Try forcibly setting the connection mechanism to tcp and see if it
> works.
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Shared Memory is disabled.
>> 3 Clients are XP, there are all works fine
>> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
>> I am only use ODBC, no native client, only tcp is activ
>> Markus
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server config
>> manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections - are
>> both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a domain.
>> Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2)
>> other W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>>
>|||Sorry - I have exhausted my ideas on this one. Time to give MS Support a
call!
--
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi Kevin!
> SSMS with tcp/ip works.
>
> I have try to connect via MSSMS to connect from a w2k3 serve to the other
> w2k3 Server (SQL Server), this works.
> The only thing is, I cannot connect via ODBC from local host or any other
> W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
> Workstion without problems.
> The ODBC - Driver Config is the same on XP ans W2k3. I think the only
> differnt ist the ODBC Driver Version:
> On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
> on W2K3 : 2000.86.3959.00
> I am not use the native client, shared memory and tcp/ip is on, the rest
> off, SQL Native Client: all is off
>
> \\sqlserver\myprog is always map to s:\
> myprog.exe and myprog.ini is always the same
> My connection string looks like this (with and without integratet
> security):
> DSN=MYPROG_MSSQL;Database=MYPROG
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password;Trusted_Connection=No;Encrypt=No;
>
> Any Ideas?
> THX in advanced
> Markus
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krpmsnuutd460@.corp.supernews.com...
>> Local connections on same box will attempt to use Shared Mem IIRC, so try
>> with it enabled.
>> You say you use only ODBC, but built-in sql server tools such as QA or
>> SSMS use whatever their default is set up to be, which could be named
>> pipes. Try forcibly setting the connection mechanism to tcp and see if
>> it works.
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Shared Memory is disabled.
>> 3 Clients are XP, there are all works fine
>> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
>> I am only use ODBC, no native client, only tcp is activ
>> Markus
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server config
>> manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections -
>> are both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a domain.
>> Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2)
>> other W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>>
>>
>|||Hi Kevin,
when I set my Programm "compatible with XP" (in Programm properties), then
the connection works!
But its not a real solution, so I have to connect from 2 Servers and the
property dialog for compatible mode is only availible on a local drive.
Any Ideas?
Thx
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13kui5qdav3mqed@.corp.supernews.com...
> Sorry - I have exhausted my ideas on this one. Time to give MS Support a
> call!
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
>> Hi Kevin!
>> SSMS with tcp/ip works.
>>
>> I have try to connect via MSSMS to connect from a w2k3 serve to the other
>> w2k3 Server (SQL Server), this works.
>> The only thing is, I cannot connect via ODBC from local host or any other
>> W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
>> Workstion without problems.
>> The ODBC - Driver Config is the same on XP ans W2k3. I think the only
>> differnt ist the ODBC Driver Version:
>> On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
>> on W2K3 : 2000.86.3959.00
>> I am not use the native client, shared memory and tcp/ip is on, the rest
>> off, SQL Native Client: all is off
>>
>> \\sqlserver\myprog is always map to s:\
>> myprog.exe and myprog.ini is always the same
>> My connection string looks like this (with and without integratet
>> security):
>> DSN=MYPROG_MSSQL;Database=MYPROG
>> -or-
>> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password
>> -or-
>> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;PWD=password;Trusted_Connection=No;Encrypt=No;
>>
>> Any Ideas?
>> THX in advanced
>> Markus
>>
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krpmsnuutd460@.corp.supernews.com...
>> Local connections on same box will attempt to use Shared Mem IIRC, so
>> try with it enabled.
>> You say you use only ODBC, but built-in sql server tools such as QA or
>> SSMS use whatever their default is set up to be, which could be named
>> pipes. Try forcibly setting the connection mechanism to tcp and see if
>> it works.
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>> Shared Memory is disabled.
>> 3 Clients are XP, there are all works fine
>> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
>> I am only use ODBC, no native client, only tcp is activ
>> Markus
>>
>> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
>> news:13krh3qgfmd58d8@.corp.supernews.com...
>> For local, perhaps Shared Memory driver is disabled? See server
>> config manager, sql server 2005 network configuration tab.
>> For remote win2K, check surface area config for Remote Connections -
>> are both tcp and named pipes enables?
>> Also you can go to the win2K machines and set up aliases using ODBC or
>> native client managers.
>>
>> --
>> Kevin G. Boles
>> TheSQLGuru
>> Indicium Resources, Inc.
>>
>> "Markus" <satmax (at) gmx.at> wrote in message
>> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>> Hi ng!
>> The facts:
>> SQL Server 2005 is installed on a Windows 2003 server within a
>> domain. Every
>> XP-Clients can connect to SQL Server via ODBC without any problems.
>> The problem
>> From the localhost I cannot connect to SQL-Server, AND from any (2)
>> other W2K
>> Server in the same domain I cannot connect to SQL Server.
>>
>> Here is the original error message, in german:
>> SQLState: '01000'
>> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
>> Driver][SharedMemory]ConnectionOpen(SECDoClientHandshake())-
>> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
>> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL
>> Sicherheitsfehler
>>
>> Have you any hints for me? I worked since 5 Days on this Problem...
>> The solution: :)
>> THX
>> Markus
>> PS: my german is much better...
>> Sorry for dubbleposting,I have not seen this ng bevor.
>>
>>
>>
>>
>>
>

Cannot connect to SQL Server from localhost (no problem from any xp client)

Hi ng!
The facts:
SQL Server 2005 is installed on a Windows 2003 server within a domain. Every
XP-Clients can connect to SQL Server via ODBC without any problems.
The problem
From the localhost I cannot connect to SQL-Server, AND from any (2) other
W2K
Server in the same domain I cannot connect to SQL Server.
Here is the original error message, in german:
SQLState: '01000'
SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
Driver]& #91;SharedMemory]ConnectionOpen(SECDoCli
entHandshake())-
Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
[Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherheits
fehler
Have you any hints for me? I worked since 5 Days on this Problem...
The solution:
THX
Markus
PS: my german is much better...
Sorry for dubbleposting,I have not seen this ng bevor.For local, perhaps Shared Memory driver is disabled? See server config
manager, sql server 2005 network configuration tab.
For remote win2K, check surface area config for Remote Connections - are
both tcp and named pipes enables?
Also you can go to the win2K machines and set up aliases using ODBC or
native client managers.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
> Hi ng!
> The facts:
> SQL Server 2005 is installed on a Windows 2003 server within a domain.
> Every
> XP-Clients can connect to SQL Server via ODBC without any problems.
> The problem
> From the localhost I cannot connect to SQL-Server, AND from any (2) other
> W2K
> Server in the same domain I cannot connect to SQL Server.
>
> Here is the original error message, in german:
> SQLState: '01000'
> SQL Server-Fehler: 772[Microsoft][ODBC SQL Server
> Driver]& #91;SharedMemory]ConnectionOpen(SECDoCli
entHandshake())-
> Fehler bei der Verbindung: SQLState: '08001' SQL Server-Fehler: 18
> [Microsoft][ODBC SQL Server Driver][SharedMemory]SSL Sicherhei
tsfehler
>
> Have you any hints for me? I worked since 5 Days on this Problem...
> The solution:
> THX
> Markus
> PS: my german is much better...
> Sorry for dubbleposting,I have not seen this ng bevor.
>
>|||Shared Memory is disabled.
3 Clients are XP, there are all works fine
3 Servers 2K3 (2 of this are TS): nobody can connect the database
I am only use ODBC, no native client, only tcp is activ
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krh3qgfmd58d8@.corp.supernews.com...
> For local, perhaps Shared Memory driver is disabled? See server config
> manager, sql server 2005 network configuration tab.
> For remote win2K, check surface area config for Remote Connections - are
> both tcp and named pipes enables?
> Also you can go to the win2K machines and set up aliases using ODBC or
> native client managers.
>
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH4FyTfMIHA.2000@.TK2MSFTNGP05.phx.gbl...
>|||Local connections on same box will attempt to use Shared Mem IIRC, so try
with it enabled.
You say you use only ODBC, but built-in sql server tools such as QA or SSMS
use whatever their default is set up to be, which could be named pipes. Try
forcibly setting the connection mechanism to tcp and see if it works.
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
> Shared Memory is disabled.
> 3 Clients are XP, there are all works fine
> 3 Servers 2K3 (2 of this are TS): nobody can connect the database
> I am only use ODBC, no native client, only tcp is activ
> Markus
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krh3qgfmd58d8@.corp.supernews.com...
>|||Hi Kevin!
SSMS with tcp/ip works.
I have try to connect via MSSMS to connect from a w2k3 serve to the other
w2k3 Server (SQL Server), this works.
The only thing is, I cannot connect via ODBC from local host or any other
W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
Workstion without problems.
The ODBC - Driver Config is the same on XP ans W2k3. I think the only
differnt ist the ODBC Driver Version:
On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
on W2K3 : 2000.86.3959.00
I am not use the native client, shared memory and tcp/ip is on, the rest
off, SQL Native Client: all is off
\\sqlserver\myprog is always map to s:\
myprog.exe and myprog.ini is always the same
My connection string looks like this (with and without integratet security):
DSN=MYPROG_MSSQL;Database=MYPROG
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password
-or-
DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password;Trusted_Connection=No;E
ncrypt=No;
Any Ideas?
THX in advanced
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13krpmsnuutd460@.corp.supernews.com...
> Local connections on same box will attempt to use Shared Mem IIRC, so try
> with it enabled.
> You say you use only ODBC, but built-in sql server tools such as QA or
> SSMS use whatever their default is set up to be, which could be named
> pipes. Try forcibly setting the connection mechanism to tcp and see if it
> works.
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:OH35HwfMIHA.5208@.TK2MSFTNGP04.phx.gbl...
>|||Sorry - I have exhausted my ideas on this one. Time to give MS Support a
call!
Kevin G. Boles
TheSQLGuru
Indicium Resources, Inc.
"Markus" <satmax (at) gmx.at> wrote in message
news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
> Hi Kevin!
> SSMS with tcp/ip works.
>
> I have try to connect via MSSMS to connect from a w2k3 serve to the other
> w2k3 Server (SQL Server), this works.
> The only thing is, I cannot connect via ODBC from local host or any other
> W2k3 Server to my W2k3 Server with SQL 2005. I can connect from any XP
> Workstion without problems.
> The ODBC - Driver Config is the same on XP ans W2k3. I think the only
> differnt ist the ODBC Driver Version:
> On XP I use the follwing ODBC Driver: SQL Server V2000.85.1117.00
> on W2K3 : 2000.86.3959.00
> I am not use the native client, shared memory and tcp/ip is on, the rest
> off, SQL Native Client: all is off
>
> \\sqlserver\myprog is always map to s:\
> myprog.exe and myprog.ini is always the same
> My connection string looks like this (with and without integratet
> security):
> DSN=MYPROG_MSSQL;Database=MYPROG
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password
> -or-
> DSN=MYPROG_MSSQL;Database=MYPROG;UID=sa;
PWD=password;Trusted_Connection=No
;Encrypt=No;
>
> Any Ideas?
> THX in advanced
> Markus
>
>
> "TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
> news:13krpmsnuutd460@.corp.supernews.com...
>|||Hi Kevin,
when I set my Programm "compatible with XP" (in Programm properties), then
the connection works!
But its not a real solution, so I have to connect from 2 Servers and the
property dialog for compatible mode is only availible on a local drive.
Any Ideas?
Thx
Markus
"TheSQLGuru" <kgboles@.earthlink.net> schrieb im Newsbeitrag
news:13kui5qdav3mqed@.corp.supernews.com...
> Sorry - I have exhausted my ideas on this one. Time to give MS Support a
> call!
> --
> Kevin G. Boles
> TheSQLGuru
> Indicium Resources, Inc.
>
> "Markus" <satmax (at) gmx.at> wrote in message
> news:%23z4vCloMIHA.4712@.TK2MSFTNGP04.phx.gbl...
>

Cannot Connect to SQL Server 2000 Using Domain Account

Hi folks:
I'm new here so please bear with me. I have a problem that is totally
driving me crazy, and it seems like it should be simple but for the life of
me I can't figure it out.
My question is simple: How do I connect to a Microsoft SQL 2000 server using
a domain account? Let me run through what I've done and what I'm trying to do.
I go to Enterprise Manager, expand my server, and click on
SECURITY...LOGINS. I create a new Login. I want to use Windows
Authentication, so I select that. Selecting that prompts me to select my
domain name, which I do. Let's suppose that the domain is named MCD. OK,
now I type in the name of the account, WHICH MATCHES THE DOMAIN ACCOUNT
IDENTICALLY! So, for example, I type in TestAccount, which combined with the
domain name is now MCD\TestAccount. I grant the account access to the
database and make it a full system administrator. I click OK, and the
account looks great.
HOWEVER, when I try to login using Query Analyzer or OSQL, I get "Login
failed for user MCD\TestAccount." Why?! I must just be missing something, but
I have no idea what it could be. I can authenticate to other resources using
that account just fine. For example, I created a network share on another
server and granted just that test account permissions to it. I can connect
to it using that domain account with no problem, so I know the domain account
is OK.
Any ideas?Are you logged into the client machine using that TestAccount, SqlServer
will pass on the credential of the logged in user.
if you are logged in as MCD\NormK and trying to connect to the sql server
using MCD\TestAccount that is not possible, (at least not from query
analyzer), You can connect to Network Share using different account.
(different username )
HTH
--
Rakesh Ajwani
MCSD, MCSD.NET
"NormK" wrote:
> Hi folks:
> I'm new here so please bear with me. I have a problem that is totally
> driving me crazy, and it seems like it should be simple but for the life of
> me I can't figure it out.
> My question is simple: How do I connect to a Microsoft SQL 2000 server using
> a domain account? Let me run through what I've done and what I'm trying to do.
> I go to Enterprise Manager, expand my server, and click on
> SECURITY...LOGINS. I create a new Login. I want to use Windows
> Authentication, so I select that. Selecting that prompts me to select my
> domain name, which I do. Let's suppose that the domain is named MCD. OK,
> now I type in the name of the account, WHICH MATCHES THE DOMAIN ACCOUNT
> IDENTICALLY! So, for example, I type in TestAccount, which combined with the
> domain name is now MCD\TestAccount. I grant the account access to the
> database and make it a full system administrator. I click OK, and the
> account looks great.
> HOWEVER, when I try to login using Query Analyzer or OSQL, I get "Login
> failed for user MCD\TestAccount." Why?! I must just be missing something, but
> I have no idea what it could be. I can authenticate to other resources using
> that account just fine. For example, I created a network share on another
> server and granted just that test account permissions to it. I can connect
> to it using that domain account with no problem, so I know the domain account
> is OK.
> Any ideas?

Cannot Connect to SQL Server 2000 Using Domain Account

Hi folks:
I'm new here so please bear with me. I have a problem that is totally
driving me crazy, and it seems like it should be simple but for the life of
me I can't figure it out.
My question is simple: How do I connect to a Microsoft SQL 2000 server using
a domain account? Let me run through what I've done and what I'm trying to d
o.
I go to Enterprise Manager, expand my server, and click on
SECURITY...LOGINS. I create a new Login. I want to use Windows
Authentication, so I select that. Selecting that prompts me to select my
domain name, which I do. Let's suppose that the domain is named MCD. OK,
now I type in the name of the account, WHICH MATCHES THE DOMAIN ACCOUNT
IDENTICALLY! So, for example, I type in TestAccount, which combined with the
domain name is now MCD\TestAccount. I grant the account access to the
database and make it a full system administrator. I click OK, and the
account looks great.
HOWEVER, when I try to login using Query Analyzer or OSQL, I get "Login
failed for user MCD\TestAccount." Why?! I must just be missing something, bu
t
I have no idea what it could be. I can authenticate to other resources usin
g
that account just fine. For example, I created a network share on another
server and granted just that test account permissions to it. I can connect
to it using that domain account with no problem, so I know the domain accoun
t
is OK.
Any ideas?Are you logged into the client machine using that TestAccount, SqlServer
will pass on the credential of the logged in user.
if you are logged in as MCD\NormK and trying to connect to the sql server
using MCD\TestAccount that is not possible, (at least not from query
analyzer), You can connect to Network Share using different account.
(different username )
HTH
--
Rakesh Ajwani
MCSD, MCSD.NET
"NormK" wrote:

> Hi folks:
> I'm new here so please bear with me. I have a problem that is totally
> driving me crazy, and it seems like it should be simple but for the life o
f
> me I can't figure it out.
> My question is simple: How do I connect to a Microsoft SQL 2000 server usi
ng
> a domain account? Let me run through what I've done and what I'm trying to
do.
> I go to Enterprise Manager, expand my server, and click on
> SECURITY...LOGINS. I create a new Login. I want to use Windows
> Authentication, so I select that. Selecting that prompts me to select my
> domain name, which I do. Let's suppose that the domain is named MCD. OK,
> now I type in the name of the account, WHICH MATCHES THE DOMAIN ACCOUNT
> IDENTICALLY! So, for example, I type in TestAccount, which combined with t
he
> domain name is now MCD\TestAccount. I grant the account access to the
> database and make it a full system administrator. I click OK, and the
> account looks great.
> HOWEVER, when I try to login using Query Analyzer or OSQL, I get "Login
> failed for user MCD\TestAccount." Why?! I must just be missing something,
but
> I have no idea what it could be. I can authenticate to other resources us
ing
> that account just fine. For example, I created a network share on another
> server and granted just that test account permissions to it. I can connec
t
> to it using that domain account with no problem, so I know the domain acco
unt
> is OK.
> Any ideas?

Cannot connect to localhost using Windows Security Group as login

I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.

Thanks,

Dave

Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?

1. You have an instance of SQL Server on the laptop

2. You have a user (UserA) in a Windows group (GroupA)

3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account

4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in

5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in

Do I have all that right?

|||

All of that is correct.

Thanks,

-Dave

|||

Then let me ask a few more questions:

1. Is the user a domain Windows user?

2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?

|||

The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.

Thanks,

-Dave

|||

OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?

To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

|||

The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?

Thanks,

Dave

|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||

Hi,

The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.

Thanks,

-Dave

|||

Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.

|||

Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?

Thanks
Laurentiu

|||

Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.

Thanks,

-Dave

Cannot connect to localhost using Windows Security Group as login

I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.

Thanks,

Dave

Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?

1. You have an instance of SQL Server on the laptop

2. You have a user (UserA) in a Windows group (GroupA)

3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account

4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in

5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in

Do I have all that right?

|||

All of that is correct.

Thanks,

-Dave

|||

Then let me ask a few more questions:

1. Is the user a domain Windows user?

2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?

|||

The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.

Thanks,

-Dave

|||

OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?

To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

|||

The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?

Thanks,

Dave

|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||

Hi,

The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.

Thanks,

-Dave

|||

Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.

|||

Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?

Thanks
Laurentiu

|||

Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.

Thanks,

-Dave

Cannot connect to localhost using Windows Security Group as login

I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.

Thanks,

Dave

Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?

1. You have an instance of SQL Server on the laptop

2. You have a user (UserA) in a Windows group (GroupA)

3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account

4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in

5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in

Do I have all that right?

|||

All of that is correct.

Thanks,

-Dave

|||

Then let me ask a few more questions:

1. Is the user a domain Windows user?

2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?

|||

The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.

Thanks,

-Dave

|||

OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?

To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

|||

The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?

Thanks,

Dave

|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||

Hi,

The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.

Thanks,

-Dave

|||

Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.

|||

Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?

Thanks
Laurentiu

|||

Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.

Thanks,

-Dave

Cannot connect to localhost using Windows Security Group as login

I have a test environment set up at home with a small windows server 2003 Active Directory domain. I created a windows security group on the dc and added myself and another user to the group. I then use this group as a login for SQL Server and add the login to the sysadmin server role. This works exactly as I would expect on the Windows Server computer (which is also the Domain Controller) regardless of which computer I use to connect to this Windows Server computer. However, when I set up the exact same login on the local sql server instance of my client laptop running windows xp pro, the I get an error message (Login failed for user MYDOMAIN\dgolds...) when I attempt to connect to the local instance of SQL server, even though I am able to connect to the instance on the domain controller with no problems using this same client laptop under the same user account. The only way I am able to connect locally on the laptop under this account (which does not have local admin privileges on any box, for testing purposes) is to add the user account separately as a login, rather than as part of a group. I'm curious as to why being a member of a security group that is part of the sysadmin server role does not allow me to connect to the local instance of SQL Server on this client laptop. The windows server computer is running SQL2k5 Enterprise, and the client laptop is running SQL2k5 developer. Any insight into this would be appreciated.

Thanks,

Dave

Let's focus on the laptop for a moment, becuase that seems to be where your question is. Is all this true?

1. You have an instance of SQL Server on the laptop

2. You have a user (UserA) in a Windows group (GroupA)

3. The Windows Group (GroupA) has been added as a login to SQL Server as a Windows account

4. When UserA tries to log in to the local instance of SQL Server on the laptop, they can't get in

5. If you add UserA to the local Instance of SQL Server on the laptop, they can get in

Do I have all that right?

|||

All of that is correct.

Thanks,

-Dave

|||

Then let me ask a few more questions:

1. Is the user a domain Windows user?

2. Which service accounts did you use to start SQL Server on the laptop? Are they starting with a user account or the localsystem account?

|||

The user is a domain Windows user. Originally the laptop was using the local system account as its service account, but I thought that might be the problem so I tried using the same service account (a domain user account that I configured specifically as a SQL Server Service Account) that I use on the server, but unfortunately I got the same results.

Thanks,

-Dave

|||

OK - I think we're getting closer. I'm going to assume the laptop is on the domain, since you say you've added that Windows group to SQL Server as a login. Does the account that you are starting SQL Server with on the laptop have the ability to resolve network names?

To help investigate your problem, make sure you check the logs the system creates. You can read more about that here:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

|||

The laptop is definitely on the domain. As far as the account that I am starting SQL Server with on the laptop having the ability to resolve network names, I'm not sure-how would I find that out?

Thanks,

Dave

|||I'm sure there's an easier way, but I normally just log on as that user, create a local group and then try to add someone from the domain to that local group.|||

Hi,

The SQL Server Service Account that I'm using does have the ability to resolve network names on the laptop.

Thanks,

-Dave

|||

Very odd. At this point, it sounds like you're doing everything properly. It has to be something to do with the security policies on that machine, but without access to it I'm afraid it would take a lot of back-and-forth to figure out where it is. I would suggest checking the logs for the system, using the techniques I outline in this guide:

http://www.informit.com/guides/content.asp?g=sqlserver&seqNum=242&rl=1

If that doesn't help point out the issue, then you may have to open a support call so that someone can gain access to your machine. sorry that I couldn't be more help here.

|||

Dave, I don't know if this will help, but could you check the error message for the login failure in the ERRORLOG file and post here the two lines that describe the state and message of the error?

Thanks
Laurentiu

|||

Thanks for all the suggestions. It turns out that there was something going on with this group (I'm not sure what). I created another group in the same Active Directory location with the same users as members and it works fine.

Thanks,

-Dave

Cannot connect to Local after change domain password

I have a Developer copy of Sql Server on my XP workstation, which I use to
access the Domain server's Sql Data and a local (name of my workstation) set
of practice data in a seperate sql server registration.
If I change my password on the domain, I can no longer connect to the local
server.
I'm running mixed mode on both with the sa login and a non-blank password.
I uninstalled my local copy of sql server, deleted the registry files I
could find, re-installed sql to a different drive partition, and then it
immediately showed the domain server registration but logon failure to the
local server registration.
I then changed my domain password back to what it used to be and everything
works fine. Problem is, my domain password is compromised and I need to
change it.
How do I clear all the real data about my install or get it to accept my new
authentication?
Bob Graham
My problem seems to have gone away after changing my network password back
to the same new one a second time.
As though it took several 'hits' to get sql to recognize the password
change.
Bob
"Bob Graham" <rvgtech@.pacbell.net> wrote in message
news:Io8ce.2370$zu.852@.newssvr13.news.prodigy.com. ..
> I have a Developer copy of Sql Server on my XP workstation, which I use
to
> access the Domain server's Sql Data and a local (name of my workstation)
set
> of practice data in a seperate sql server registration.
> If I change my password on the domain, I can no longer connect to the
local
> server.
> I'm running mixed mode on both with the sa login and a non-blank password.
> I uninstalled my local copy of sql server, deleted the registry files I
> could find, re-installed sql to a different drive partition, and then it
> immediately showed the domain server registration but logon failure to the
> local server registration.
> I then changed my domain password back to what it used to be and
everything
> works fine. Problem is, my domain password is compromised and I need to
> change it.
> How do I clear all the real data about my install or get it to accept my
new
> authentication?
> Bob Graham
>

Cannot connect to Local after change domain password

I have a Developer copy of Sql Server on my XP workstation, which I use to
access the Domain server's Sql Data and a local (name of my workstation) set
of practice data in a seperate sql server registration.
If I change my password on the domain, I can no longer connect to the local
server.
I'm running mixed mode on both with the sa login and a non-blank password.
I uninstalled my local copy of sql server, deleted the registry files I
could find, re-installed sql to a different drive partition, and then it
immediately showed the domain server registration but logon failure to the
local server registration.
I then changed my domain password back to what it used to be and everything
works fine. Problem is, my domain password is compromised and I need to
change it.
How do I clear all the real data about my install or get it to accept my new
authentication?
Bob GrahamMy problem seems to have gone away after changing my network password back
to the same new one a second time.
As though it took several 'hits' to get sql to recognize the password
change.
Bob
"Bob Graham" <rvgtech@.pacbell.net> wrote in message
news:Io8ce.2370$zu.852@.newssvr13.news.prodigy.com...
> I have a Developer copy of Sql Server on my XP workstation, which I use
to
> access the Domain server's Sql Data and a local (name of my workstation)
set
> of practice data in a seperate sql server registration.
> If I change my password on the domain, I can no longer connect to the
local
> server.
> I'm running mixed mode on both with the sa login and a non-blank password.
> I uninstalled my local copy of sql server, deleted the registry files I
> could find, re-installed sql to a different drive partition, and then it
> immediately showed the domain server registration but logon failure to the
> local server registration.
> I then changed my domain password back to what it used to be and
everything
> works fine. Problem is, my domain password is compromised and I need to
> change it.
> How do I clear all the real data about my install or get it to accept my
new
> authentication?
> Bob Graham
>

Cannot Connect to Analysis Server-not a member of OLAP Admin

I have set up the the Analysis Service to log on as DOMAIN\administrator.
I have added DOMAIN\administrator as a member of OLAP Adminitration
I initially logged in as DOMAIN\administrator.
Upon trying to connect in Analysis Server, I get the error messge Cannot
connect to SERVER registry or you are not a member of the OLAP
AdministratorGroup
What gives? How do I resolve this?
Are you running the latest service pack for Analysis Services?
Kevin E.
"Diane" <Diane@.discussions.microsoft.com> wrote in message
news:B2888652-78F9-4F32-88B2-F21C03A48A65@.microsoft.com...
>I have set up the the Analysis Service to log on as DOMAIN\administrator.
> I have added DOMAIN\administrator as a member of OLAP Adminitration
> I initially logged in as DOMAIN\administrator.
> Upon trying to connect in Analysis Server, I get the error messge Cannot
> connect to SERVER registry or you are not a member of the OLAP
> AdministratorGroup
> What gives? How do I resolve this?
|||Yes, I am.
"Diane" wrote:

> I have set up the the Analysis Service to log on as DOMAIN\administrator.
> I have added DOMAIN\administrator as a member of OLAP Adminitration
> I initially logged in as DOMAIN\administrator.
> Upon trying to connect in Analysis Server, I get the error messge Cannot
> connect to SERVER registry or you are not a member of the OLAP
> AdministratorGroup
> What gives? How do I resolve this?
|||We had the same problem on some of our installations. Seems like after we
rebooted and then tried to connect it worked fine. Might of had something to
do with MSSQLServerOLAPService not being started until after reboot. Just a
thought.
Kevin
"Diane" <Diane@.discussions.microsoft.com> wrote in message
news:904C6394-D5AE-4BC4-8A45-39B58AA742BD@.microsoft.com...[vbcol=seagreen]
> Yes, I am.
> "Diane" wrote: