Showing posts with label user. Show all posts
Showing posts with label user. Show all posts

Tuesday, March 27, 2012

Cannot drop user. Can anyone help?

When trying to drop a user I get ' The database principle owns a schema in the database and cannot be dropped'

How Can I get around this? How can I tell which schema the user owns. It is not listed in the properties of the user.

How can I view a list of schema's and who they are owned by and how can I change ownership of schema's?|||

Hi,

Which Version of Sql you are using? I assume that you are using SQL Server 2005 only. First you need to drop the schema to which the user is binded and then drop the user.

1.Open SSMS, Select your data base.

2. Select "Security" folder and expand it.

3. Select "User" folder and expand it.

4. Select and right click the user to be dropped.

5. Select "Properties" command will open "Database User" dialog box.

6. You can view the schemas which are binded to that user in the "Owned Schemas" section.

7. After determining the schema name, just cancel that dialog window.

8. Expand "Schemas" folder and select the schema that you have determined in step-4.

9. Delete/Drop that schema and then drop the user.

Hope this will help you.

Thanks & Regards,

Kiran.Y

|||

in Security->Users->Right click->Properties-> I have "Schema owned by this user" and I have a check box marked on appropriate schema.

you can run too:

use yourDB

go

select schema_name,schema_owner

from information_schema.schemata

|||

For changing ownership of schema see ALTER AUTHORIZATION command in Books Online

|||

i have blogged this with example. See this

http://madhuottapalam.blogspot.com/search?q=Drop+Database+User+who+Owns+Schema

Madhu

Thursday, March 22, 2012

cannot delete user & shrink log file

Hello... I'm facing two problems:
1. When I try to delete a user from a specific database,
it reports that that user cannot be dropped as it owns
objects. The db_owner is 'sa' not this user.
2. When I try to shrink the size of my log file, it
reports, "Cannot shrink log file 2 (cms1_log) because all
logical log files are in use."
Please help. Thanks.1. My guess is that the user own some objects. If you are used to
Enterprise Manager then expand each objects list and see if the user own
anything like "tables", "views", "store procedure", "user defined functions"
...
2. What is your recovery model? Right click server in EM, then click
properties, then options
"Rob" <rhchin@.hotmail.com> wrote in message
news:5d8901c35784$5b35fbf0$a001280a@.phx.gbl...
> Hello... I'm facing two problems:
> 1. When I try to delete a user from a specific database,
> it reports that that user cannot be dropped as it owns
> objects. The db_owner is 'sa' not this user.
> 2. When I try to shrink the size of my log file, it
> reports, "Cannot shrink log file 2 (cms1_log) because all
> logical log files are in use."
> Please help. Thanks.|||Rob,
#1..It could also be that that the user owns other objects like table,
stored procedures etc.Using the below query, you can find out the objects:
SELECT [name]
FROM sysobjects
WHERE uid=USER_ID('<user_name>')
Once there, try to change the ownership to another user, using
sp_changeobjectowner.
#2.Refer
INF: How to Shrink the SQL Server 7.0 Transaction Log
http://support.microsoft.com/support/kb/Articles/q256/6/50.asp
INF: Shrinking the Transaction Log in SQL Server 2000 with DBCC SHRINKFILE
http://support.microsoft.com/support/kb/Articles/q272/3/18.asp
Dinesh.
SQL Server FAQ at
http://www.tkdinesh.com
"Rob" <rhchin@.hotmail.com> wrote in message
news:5d8901c35784$5b35fbf0$a001280a@.phx.gbl...
> Hello... I'm facing two problems:
> 1. When I try to delete a user from a specific database,
> it reports that that user cannot be dropped as it owns
> objects. The db_owner is 'sa' not this user.
> 2. When I try to shrink the size of my log file, it
> reports, "Cannot shrink log file 2 (cms1_log) because all
> logical log files are in use."
> Please help. Thanks.|||Thanks for your response...
>Once there, try to change the ownership to another user,
using
>sp_changeobjectowner.
I can see many objects owned by the user I wish to drop.
However, when I try to use the sp_changeobjectowner sproc,
it tells me that the object does not exist or is not a
valid object for this operation.
Thanks again.

Cannot Delete user

Here's a catch-22 with the new SQL 2005. I've attached some SQL 2000 db's t
o
the new server. When I went into Mgmt Studio I realized that the old
security settings associated with those db's carried over to the new server
when attached. However, they were no good because the user "abc" did not
exist as a valid login on this new server. I tried to delete it but it won'
t
allow it because there is no "login" associated with the user. Of course
there is none. it's a bogus record. For that same reason the Login screen
is grayed out and Mgmt Studio won't let me change it. I see absolutely no
way to remove it now (short of removing the security settings while it's
still in SQL 2000 before moving to 2005). Any suggestions on a way to
cleanup the security info and get it all redefined after moving to 2005?
Thanks
--Perhaps one of these will offer you a clue:
http://www.sqlservercentral.com/col...se
s.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://support.microsoft.com/kb/274188 Troubleshooting Orphan Logins
http://www.support.microsoft.com/?id=240872 Resolve Permission
Issues -Database Is Moved Between SQL Servers
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Spicie Mikie" <Maz@.newsgroups.nospam> wrote in message
news:7B7F056C-5EB2-4548-BB47-4D58F024860B@.microsoft.com...
> Here's a catch-22 with the new SQL 2005. I've attached some SQL 2000 db's
> to
> the new server. When I went into Mgmt Studio I realized that the old
> security settings associated with those db's carried over to the new
> server
> when attached. However, they were no good because the user "abc" did not
> exist as a valid login on this new server. I tried to delete it but it
> won't
> allow it because there is no "login" associated with the user. Of course
> there is none. it's a bogus record. For that same reason the Login
> screen
> is grayed out and Mgmt Studio won't let me change it. I see absolutely no
> way to remove it now (short of removing the security settings while it's
> still in SQL 2000 before moving to 2005). Any suggestions on a way to
> cleanup the security info and get it all redefined after moving to 2005?
> Thanks
> --
>|||That article about orphaned logins was exactly what I needed to read. I'm
still somewhat surprised that the UI gets "caught" by this situation and
cannot be fixed without using a stored procedure. However, this works, so
I'm happy
Thanks
--
Maz
"Arnie Rowland" wrote:

> Perhaps one of these will offer you a clue:
> http://www.sqlservercentral.com/col...
ses.asp
> Moving Users
> http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
> Passwords Between SQL Servers
> http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after a
> Restore
> http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to users
> http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
> Errors After Restoring Dump
> http://support.microsoft.com/kb/274188 Troubleshooting Orphan Logins
> http://www.support.microsoft.com/?id=240872 Resolve Permission
> Issues -Database Is Moved Between SQL Servers
>
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to th
e
> top yourself.
> - H. Norman Schwarzkopf
>
> "Spicie Mikie" <Maz@.newsgroups.nospam> wrote in message
> news:7B7F056C-5EB2-4548-BB47-4D58F024860B@.microsoft.com...
>
>sql

Cannot delete SQL database user

Dear all,
I was trying to delete a user of a SQL database. But it cannot be deleted
and the error message is: "Error 15008: User 'username' does not exist in the
current database."
The database had some problem yesterday and I restored the backup
successfully. But the database user login cannot be deleted. How to solve
this problem?
Thanks in advance.
IvanThere is a big difference between a user and a login. Is this a user or a
login?
On 3/3/05 11:43 PM, in article
80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:
> Dear all,
> I was trying to delete a user of a SQL database. But it cannot be deleted
> and the error message is: "Error 15008: User 'username' does not exist in the
> current database."
> The database had some problem yesterday and I restored the backup
> successfully. But the database user login cannot be deleted. How to solve
> this problem?
> Thanks in advance.
> Ivan|||Hi,
It is a "Database User"
Ivan
"Aaron [SQL Server MVP]" wrote:
> There is a big difference between a user and a login. Is this a user or a
> login?
>
> On 3/3/05 11:43 PM, in article
> 80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
> <Ivan@.discussions.microsoft.com> wrote:
> > Dear all,
> >
> > I was trying to delete a user of a SQL database. But it cannot be deleted
> > and the error message is: "Error 15008: User 'username' does not exist in the
> > current database."
> > The database had some problem yesterday and I restored the backup
> > successfully. But the database user login cannot be deleted. How to solve
> > this problem?
> > Thanks in advance.
> >
> > Ivan
>|||Open Query Analyzer, and with the correct database context, what happens
when you say:
EXEC sp_helpusers
EXEC sp_helpuser 'username'
EXEC sp_helplogins
EXEC sp_helplogin 'username'
?
On 3/3/05 11:59 PM, in article
C33B5F1E-928D-4AF8-A673-996F097B9B6A@.microsoft.com, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:
> Hi,
> It is a "Database User"
> Ivan
> "Aaron [SQL Server MVP]" wrote:
>> There is a big difference between a user and a login. Is this a user or a
>> login?
>>
>> On 3/3/05 11:43 PM, in article
>> 80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
>> <Ivan@.discussions.microsoft.com> wrote:
>> Dear all,
>> I was trying to delete a user of a SQL database. But it cannot be deleted
>> and the error message is: "Error 15008: User 'username' does not exist in
>> the
>> current database."
>> The database had some problem yesterday and I restored the backup
>> successfully. But the database user login cannot be deleted. How to solve
>> this problem?
>> Thanks in advance.
>> Ivan
>>|||Hi,
I tried to stop the SQL server service and started it again, then I could
delete it.
Thanks a lot and your help is greatly appreciated!
Ivan
"Aaron [SQL Server MVP]" wrote:
> Open Query Analyzer, and with the correct database context, what happens
> when you say:
> EXEC sp_helpusers
> EXEC sp_helpuser 'username'
> EXEC sp_helplogins
> EXEC sp_helplogin 'username'
> ?
>
> On 3/3/05 11:59 PM, in article
> C33B5F1E-928D-4AF8-A673-996F097B9B6A@.microsoft.com, "Ivan"
> <Ivan@.discussions.microsoft.com> wrote:
> > Hi,
> >
> > It is a "Database User"
> >
> > Ivan
> >
> > "Aaron [SQL Server MVP]" wrote:
> >
> >> There is a big difference between a user and a login. Is this a user or a
> >> login?
> >>
> >>
> >> On 3/3/05 11:43 PM, in article
> >> 80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
> >> <Ivan@.discussions.microsoft.com> wrote:
> >>
> >> Dear all,
> >>
> >> I was trying to delete a user of a SQL database. But it cannot be deleted
> >> and the error message is: "Error 15008: User 'username' does not exist in
> >> the
> >> current database."
> >> The database had some problem yesterday and I restored the backup
> >> successfully. But the database user login cannot be deleted. How to solve
> >> this problem?
> >> Thanks in advance.
> >>
> >> Ivan
> >>
> >>
>

Cannot delete SQL database user

Dear all,
I was trying to delete a user of a SQL database. But it cannot be deleted
and the error message is: "Error 15008: User 'username' does not exist in the
current database."
The database had some problem yesterday and I restored the backup
successfully. But the database user login cannot be deleted. How to solve
this problem?
Thanks in advance.
Ivan
There is a big difference between a user and a login. Is this a user or a
login?
On 3/3/05 11:43 PM, in article
80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:

> Dear all,
> I was trying to delete a user of a SQL database. But it cannot be deleted
> and the error message is: "Error 15008: User 'username' does not exist in the
> current database."
> The database had some problem yesterday and I restored the backup
> successfully. But the database user login cannot be deleted. How to solve
> this problem?
> Thanks in advance.
> Ivan
|||Hi,
It is a "Database User"
Ivan
"Aaron [SQL Server MVP]" wrote:

> There is a big difference between a user and a login. Is this a user or a
> login?
>
> On 3/3/05 11:43 PM, in article
> 80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
> <Ivan@.discussions.microsoft.com> wrote:
>
>
|||Open Query Analyzer, and with the correct database context, what happens
when you say:
EXEC sp_helpusers
EXEC sp_helpuser 'username'
EXEC sp_helplogins
EXEC sp_helplogin 'username'
?
On 3/3/05 11:59 PM, in article
C33B5F1E-928D-4AF8-A673-996F097B9B6A@.microsoft.com, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
> Hi,
> It is a "Database User"
> Ivan
> "Aaron [SQL Server MVP]" wrote:
|||Hi,
I tried to stop the SQL server service and started it again, then I could
delete it.
Thanks a lot and your help is greatly appreciated!
Ivan
"Aaron [SQL Server MVP]" wrote:

> Open Query Analyzer, and with the correct database context, what happens
> when you say:
> EXEC sp_helpusers
> EXEC sp_helpuser 'username'
> EXEC sp_helplogins
> EXEC sp_helplogin 'username'
> ?
>
> On 3/3/05 11:59 PM, in article
> C33B5F1E-928D-4AF8-A673-996F097B9B6A@.microsoft.com, "Ivan"
> <Ivan@.discussions.microsoft.com> wrote:
>
>

Cannot delete SQL database user

Dear all,
I was trying to delete a user of a SQL database. But it cannot be deleted
and the error message is: "Error 15008: User 'username' does not exist in th
e
current database."
The database had some problem yesterday and I restored the backup
successfully. But the database user login cannot be deleted. How to solve
this problem?
Thanks in advance.
IvanThere is a big difference between a user and a login. Is this a user or a
login?
On 3/3/05 11:43 PM, in article
80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:

> Dear all,
> I was trying to delete a user of a SQL database. But it cannot be deleted
> and the error message is: "Error 15008: User 'username' does not exist in
the
> current database."
> The database had some problem yesterday and I restored the backup
> successfully. But the database user login cannot be deleted. How to solve
> this problem?
> Thanks in advance.
> Ivan|||Hi,
It is a "Database User"
Ivan
"Aaron [SQL Server MVP]" wrote:

> There is a big difference between a user and a login. Is this a user or a
> login?
>
> On 3/3/05 11:43 PM, in article
> 80C03227-032B-45D7-B821-6EFE7D89A54B@.microsoft.com, "Ivan"
> <Ivan@.discussions.microsoft.com> wrote:
>
>|||Open Query Analyzer, and with the correct database context, what happens
when you say:
EXEC sp_helpusers
EXEC sp_helpuser 'username'
EXEC sp_helplogins
EXEC sp_helplogin 'username'
?
On 3/3/05 11:59 PM, in article
C33B5F1E-928D-4AF8-A673-996F097B9B6A@.microsoft.com, "Ivan"
<Ivan@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
> Hi,
> It is a "Database User"
> Ivan
> "Aaron [SQL Server MVP]" wrote:
>|||Hi,
I tried to stop the SQL server service and started it again, then I could
delete it.
Thanks a lot and your help is greatly appreciated!
Ivan
"Aaron [SQL Server MVP]" wrote:

> Open Query Analyzer, and with the correct database context, what happens
> when you say:
> EXEC sp_helpusers
> EXEC sp_helpuser 'username'
> EXEC sp_helplogins
> EXEC sp_helplogin 'username'
> ?
>
> On 3/3/05 11:59 PM, in article
> C33B5F1E-928D-4AF8-A673-996F097B9B6A@.microsoft.com, "Ivan"
> <Ivan@.discussions.microsoft.com> wrote:
>
>sql

Tuesday, March 20, 2012

Cannot create user on Report Server 2005

Hi, we installed SQL Server 2005 & Reporting Services on a box that had been
running 2000.
I launched the reports website.
When I try to do New System Role Assignment, I type in a domain user and
select a role and click OK, nothing at all happens. No error message, no
response, nothing.
Does anyone have any idea what might be going on?What I tend to do is create a local group and add my domain users to the
local group. Two things to try. Did you put the domain in front of the user?
I.e. MyDomain\Username
Second, are you in the local administrators group. Perhaps you don't have
rights to be doing this.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"RebeccaTS" <RebeccaTS@.discussions.microsoft.com> wrote in message
news:730D7944-B019-4E7A-8B9C-EA7EEB33486A@.microsoft.com...
> Hi, we installed SQL Server 2005 & Reporting Services on a box that had
> been
> running 2000.
> I launched the reports website.
> When I try to do New System Role Assignment, I type in a domain user and
> select a role and click OK, nothing at all happens. No error message, no
> response, nothing.
> Does anyone have any idea what might be going on?

Sunday, March 11, 2012

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. Wink

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. Wink

|||

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. Wink

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. Wink

|||

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. Wink

|||

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

Thursday, March 8, 2012

Cannot create a connection to data source !!!!!!!

I cannot get this error resolve either for myself or any users, and I'm actually part of the Admin group! Furthermore, a user with whom I'm tring allow to view this report keeps getting prompted for their windows username and password. I thought that since this datasource was set to Windows Authentification that it would just pass it through?

I'm pulling my hair out at this point:

Screen Shots:

http://www.webfound.net/datasource_connection.jpg

http://www.webfound.net/datasource_connection2.jpg

http://www.webfound.net/datasource_connection3.jpg


Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

  • An error has occurred during report processing.
  • Cannot create a connection to data source 'datasourcename'.
  • For more information about this error navigate to the report server on the local server machine, or enable remote errors
  • no it usues whatever account iis is running under.

    IUSR_something I think.

    if you want use integrated auth you need to use impersonation.

    |||ok....then how do incorporate personalization in Reporting Services! I don't see anything on that...I think you're referring to .NET, I'm talking about Reporting Services 2005|||I posted this in the wrong forum by accident..I'll move it to Reporting Services..sorry
  • Cannot create a connection to data source !!!! SSRS 2005

    I cannot get this error resolve either for myself or any users, and I'm actually part of the Admin group! Furthermore, a user with whom I'm tring allow to view this report keeps getting prompted for their windows username and password. I thought that since this datasource was set to Windows Authentification that it would just pass it through?

    I'm pulling my hair out at this point:

    Screen Shots:

    http://www.webfound.net/datasource_connection.jpg

    http://www.webfound.net/datasource_connection2.jpg

    http://www.webfound.net/datasource_connection3.jpg


    Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

  • An error has occurred during report processing.
  • Cannot create a connection to data source 'datasourcename'.
  • For more information about this error navigate to the report server on the local server machine, or enable remote errors
  • Are the client, RS, and SQL server all on different machines? If so, then you are probably hitting the double-hop problem. This is a limitation of integrated security in environments which don't support kerberos.

    Tudor talks about it a bit in this blog entry:

    http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx

    You might want to check that out and see if the problem described there is what you are experiencing.

    |||

    No, I have gotten this to work fine for my test server which is the server running both RS and SQL Server 2005. RS and SQL Server 2005 are on the same box. The server I'm trying to connect to now is a different server's DB which is where the datasource is pointing to. So there is no double-hop issue here at least!

    So in other words if I change the datasets to use the datasources that piont to ServerA below, my report runs for me ok. If I change the datasets in my report to talk to ServerB, I get the error immediately. The datasets are running stored procs and referencing the data sources for the DB connection in the dataset properties. I am using 3 datasets in my report and around 4 datasources are in my project that are uploaded automatically when I deploy my report to the report serve (TestServerA)

    TestServerA - Has RS and SQL Server 2005. When using Datasources that point to this server's stored procs, it works for me at least the other users still have issues though where it's prompting them for a windows username and password

    ServerB - a production server running SQL Server 2000 (doesn't have Reporting Services on it, we're just runnign stored procs against it for the datasets) in which the dataset (on TestServerA) is trying to run a stored proc off of ServerB. It stil uses ServerA for Reporting services part...whcih is where I'm getting the error from my own client when trying to run the report from the client in Report Manager

    |||Ok, now I tried logging on directly to my TestServerA and ran the report from IE on that server (report Manager) and it works fine. Ok, so how am I getting a double hop issue if I have everything installed on the same server? I don't think hopping is the issue here still!|||scratch my last response...it was working only because my datasets were pointing to the datasources that were pointing to my TestServerA. Once I changed it back to the point where I got the error (for this post) whcih was to chagne teh datasets to point to the datasources that point to ServerB, I still get the error, even when running the report from TestServerA's Report Manager....|||

    Here's a diagram to show you what's going on. Keep in mind, if the datasets aren't using datasources that point to ServerB and are using datasources that point to TestServerA, all works fine...it's just when my report is using datasources trying to talk to ServerB.

    http://www.webfound.net/diagram.jpg

    |||

    Can you check the errors in the report server log files - they are under /Reporting Services/LogFiles/ReportServer*.log

    If you see an error message coming from your data sources server that looks like - login failed for user (null), then it's likely that you are experiencing the Integrated security double-hop issue.

    If that's the case, you can store credentials for the data sources in the report server, or enable Kerberos delegation as shown below:

    http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx

    Thanks,

    Tudor

    |||

    In your second setup (ServerB) you are describing what I would expect to be the symptoms of the double hop problem. You have 3 machines, A->B->C. A is the client machine, B is the machine with reporting services, and C is the machine that has the data you are reporting against. You are trying to pass credentials from machine A all the way to machine C. Unless you have set up your environment to allow kerberos delegation (see the links that I pasted above), then this will fail. If you don't want to (or cannot) enable delegation, then a workaround for you is to store credentials for accessing the datasources in the catalog.

    In your 1st scenario (TestServerA), I am not certain why they are getting prompted for credentials. I suspect it is because your test users don't have access to your machine, are they able to connect when providing their credentials?

    |||my users do have access to the SQL Server databases so I don't know why they would get prompted still. No, when they type in their username and password, it doesn't take.|||

    ,I have missed the same problem once ,the problem is that ur datasource was set ot windows Authentification,(if u pay more attention to ur report'Connection string,u could find the bugs),but ur database has no right for this kind of user,

    u could follow this steps to add a user or a group which the user belong to :

    1.login in database

    2.extend the security node

    3.extend the logins node

    3.right-click logins node,click new login, and then add the user or the group which the user belong to to Database'logins.

    And there is a skill,if ur user is a member of administrator,and u assign permissions to the other user,by default,this kind of user only is a menber of user,dont have the role of administrator,so if u use the windows Authentification to build connection string for ur report,the user who just have a role of user don't have logins to database,u need to follow the steps above to add the user or the group to Database'logins.

    |||Samuel, they definitely already have logins to the database, right down to the permissions of the stored procs being called by the datasets so this is covered! They have read rights as well as datawriter (which isn't really needed). This is why I posted, I have done almost everything.|||

    I believe you are running into a couple of problems which are not necessarily related.

    When you are prompted for credentials in IE with the standard credentials dialog, it is because IIS did not accept the user's token when IE presented it in response to a 401. This usually means that the user is not a valid user on the target machine. Check your IIS logs for 401s.

    The datasource problems are because the user we are trying to access the database with is not allowed access. This can be for any number of reasons, the double-hop issue being a pretty common one when people are trying to pass through Windows credentials.

    |||I have a similar problem to FlavorFlave. Our setup:

    Machine A : client
    Machine B: SSRS 2005
    Machine C: SSAS 2000

    Running reports from Machine B works, running from from A does not - getting the exact error he specified. Logged on to machine A with a limited user account, onto B/C with full admin rights.

    Enabling delegation is not going to be possible on our network. John, i see you say a workaround is to "store credentials for accessing the datasources in the catalog". Not sure what you meant by this.. or where to do this?|||never mind.. ive figured it out :)

    stored the credentials securely within the datasource on the report server itself. works now... though its slower to initialise than when the security is integrated.
    |||talwar, can you explain the steps you took in detail so hopefully I can do the same...thanks

  • Cannot create a connection to data source !!!! SSRS 2005

    I cannot get this error resolve either for myself or any users, and I'm actually part of the Admin group! Furthermore, a user with whom I'm tring allow to view this report keeps getting prompted for their windows username and password. I thought that since this datasource was set to Windows Authentification that it would just pass it through?

    I'm pulling my hair out at this point:

    Screen Shots:

    http://www.webfound.net/datasource_connection.jpg

    http://www.webfound.net/datasource_connection2.jpg

    http://www.webfound.net/datasource_connection3.jpg


    Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

  • An error has occurred during report processing.
  • Cannot create a connection to data source 'datasourcename'.
  • For more information about this error navigate to the report server on the local server machine, or enable remote errors
  • Are the client, RS, and SQL server all on different machines? If so, then you are probably hitting the double-hop problem. This is a limitation of integrated security in environments which don't support kerberos.

    Tudor talks about it a bit in this blog entry:

    http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx

    You might want to check that out and see if the problem described there is what you are experiencing.

    |||

    No, I have gotten this to work fine for my test server which is the server running both RS and SQL Server 2005. RS and SQL Server 2005 are on the same box. The server I'm trying to connect to now is a different server's DB which is where the datasource is pointing to. So there is no double-hop issue here at least!

    So in other words if I change the datasets to use the datasources that piont to ServerA below, my report runs for me ok. If I change the datasets in my report to talk to ServerB, I get the error immediately. The datasets are running stored procs and referencing the data sources for the DB connection in the dataset properties. I am using 3 datasets in my report and around 4 datasources are in my project that are uploaded automatically when I deploy my report to the report serve (TestServerA)

    TestServerA - Has RS and SQL Server 2005. When using Datasources that point to this server's stored procs, it works for me at least the other users still have issues though where it's prompting them for a windows username and password

    ServerB - a production server running SQL Server 2000 (doesn't have Reporting Services on it, we're just runnign stored procs against it for the datasets) in which the dataset (on TestServerA) is trying to run a stored proc off of ServerB. It stil uses ServerA for Reporting services part...whcih is where I'm getting the error from my own client when trying to run the report from the client in Report Manager

    |||Ok, now I tried logging on directly to my TestServerA and ran the report from IE on that server (report Manager) and it works fine. Ok, so how am I getting a double hop issue if I have everything installed on the same server? I don't think hopping is the issue here still!|||scratch my last response...it was working only because my datasets were pointing to the datasources that were pointing to my TestServerA. Once I changed it back to the point where I got the error (for this post) whcih was to chagne teh datasets to point to the datasources that point to ServerB, I still get the error, even when running the report from TestServerA's Report Manager....|||

    Here's a diagram to show you what's going on. Keep in mind, if the datasets aren't using datasources that point to ServerB and are using datasources that point to TestServerA, all works fine...it's just when my report is using datasources trying to talk to ServerB.

    http://www.webfound.net/diagram.jpg

    |||

    Can you check the errors in the report server log files - they are under /Reporting Services/LogFiles/ReportServer*.log

    If you see an error message coming from your data sources server that looks like - login failed for user (null), then it's likely that you are experiencing the Integrated security double-hop issue.

    If that's the case, you can store credentials for the data sources in the report server, or enable Kerberos delegation as shown below:

    http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx

    Thanks,

    Tudor

    |||

    In your second setup (ServerB) you are describing what I would expect to be the symptoms of the double hop problem. You have 3 machines, A->B->C. A is the client machine, B is the machine with reporting services, and C is the machine that has the data you are reporting against. You are trying to pass credentials from machine A all the way to machine C. Unless you have set up your environment to allow kerberos delegation (see the links that I pasted above), then this will fail. If you don't want to (or cannot) enable delegation, then a workaround for you is to store credentials for accessing the datasources in the catalog.

    In your 1st scenario (TestServerA), I am not certain why they are getting prompted for credentials. I suspect it is because your test users don't have access to your machine, are they able to connect when providing their credentials?

    |||my users do have access to the SQL Server databases so I don't know why they would get prompted still. No, when they type in their username and password, it doesn't take.|||

    ,I have missed the same problem once ,the problem is that ur datasource was set ot windows Authentification,(if u pay more attention to ur report'Connection string,u could find the bugs),but ur database has no right for this kind of user,

    u could follow this steps to add a user or a group which the user belong to :

    1.login in database

    2.extend the security node

    3.extend the logins node

    3.right-click logins node,click new login, and then add the user or the group which the user belong to to Database'logins.

    And there is a skill,if ur user is a member of administrator,and u assign permissions to the other user,by default,this kind of user only is a menber of user,dont have the role of administrator,so if u use the windows Authentification to build connection string for ur report,the user who just have a role of user don't have logins to database,u need to follow the steps above to add the user or the group to Database'logins.

    |||Samuel, they definitely already have logins to the database, right down to the permissions of the stored procs being called by the datasets so this is covered! They have read rights as well as datawriter (which isn't really needed). This is why I posted, I have done almost everything.|||

    I believe you are running into a couple of problems which are not necessarily related.

    When you are prompted for credentials in IE with the standard credentials dialog, it is because IIS did not accept the user's token when IE presented it in response to a 401. This usually means that the user is not a valid user on the target machine. Check your IIS logs for 401s.

    The datasource problems are because the user we are trying to access the database with is not allowed access. This can be for any number of reasons, the double-hop issue being a pretty common one when people are trying to pass through Windows credentials.

    |||I have a similar problem to FlavorFlave. Our setup:

    Machine A : client
    Machine B: SSRS 2005
    Machine C: SSAS 2000

    Running reports from Machine B works, running from from A does not - getting the exact error he specified. Logged on to machine A with a limited user account, onto B/C with full admin rights.

    Enabling delegation is not going to be possible on our network. John, i see you say a workaround is to "store credentials for accessing the datasources in the catalog". Not sure what you meant by this.. or where to do this?|||never mind.. ive figured it out :)

    stored the credentials securely within the datasource on the report server itself. works now... though its slower to initialise than when the security is integrated.
    |||talwar, can you explain the steps you took in detail so hopefully I can do the same...thanks

  • Cannot create a connection to data source !!!! SSRS 2005

    I cannot get this error resolve either for myself or any users, and I'm actually part of the Admin group! Furthermore, a user with whom I'm tring allow to view this report keeps getting prompted for their windows username and password. I thought that since this datasource was set to Windows Authentification that it would just pass it through?

    I'm pulling my hair out at this point:

    Screen Shots:

    http://www.webfound.net/datasource_connection.jpg

    http://www.webfound.net/datasource_connection2.jpg

    http://www.webfound.net/datasource_connection3.jpg


    Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

  • An error has occurred during report processing.

  • Cannot create a connection to data source 'datasourcename'.

  • For more information about this error navigate to the report server on the local server machine, or enable remote errors

  • Are the client, RS, and SQL server all on different machines? If so, then you are probably hitting the double-hop problem. This is a limitation of integrated security in environments which don't support kerberos.

    Tudor talks about it a bit in this blog entry:

    http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx

    You might want to check that out and see if the problem described there is what you are experiencing.

    |||

    No, I have gotten this to work fine for my test server which is the server running both RS and SQL Server 2005. RS and SQL Server 2005 are on the same box. The server I'm trying to connect to now is a different server's DB which is where the datasource is pointing to. So there is no double-hop issue here at least!

    So in other words if I change the datasets to use the datasources that piont to ServerA below, my report runs for me ok. If I change the datasets in my report to talk to ServerB, I get the error immediately. The datasets are running stored procs and referencing the data sources for the DB connection in the dataset properties. I am using 3 datasets in my report and around 4 datasources are in my project that are uploaded automatically when I deploy my report to the report serve (TestServerA)

    TestServerA - Has RS and SQL Server 2005. When using Datasources that point to this server's stored procs, it works for me at least the other users still have issues though where it's prompting them for a windows username and password

    ServerB - a production server running SQL Server 2000 (doesn't have Reporting Services on it, we're just runnign stored procs against it for the datasets) in which the dataset (on TestServerA) is trying to run a stored proc off of ServerB. It stil uses ServerA for Reporting services part...whcih is where I'm getting the error from my own client when trying to run the report from the client in Report Manager

    |||Ok, now I tried logging on directly to my TestServerA and ran the report from IE on that server (report Manager) and it works fine. Ok, so how am I getting a double hop issue if I have everything installed on the same server? I don't think hopping is the issue here still!|||scratch my last response...it was working only because my datasets were pointing to the datasources that were pointing to my TestServerA. Once I changed it back to the point where I got the error (for this post) whcih was to chagne teh datasets to point to the datasources that point to ServerB, I still get the error, even when running the report from TestServerA's Report Manager....|||

    Here's a diagram to show you what's going on. Keep in mind, if the datasets aren't using datasources that point to ServerB and are using datasources that point to TestServerA, all works fine...it's just when my report is using datasources trying to talk to ServerB.

    http://www.webfound.net/diagram.jpg

    |||

    Can you check the errors in the report server log files - they are under /Reporting Services/LogFiles/ReportServer*.log

    If you see an error message coming from your data sources server that looks like - login failed for user (null), then it's likely that you are experiencing the Integrated security double-hop issue.

    If that's the case, you can store credentials for the data sources in the report server, or enable Kerberos delegation as shown below:

    http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx

    Thanks,

    Tudor

    |||

    In your second setup (ServerB) you are describing what I would expect to be the symptoms of the double hop problem. You have 3 machines, A->B->C. A is the client machine, B is the machine with reporting services, and C is the machine that has the data you are reporting against. You are trying to pass credentials from machine A all the way to machine C. Unless you have set up your environment to allow kerberos delegation (see the links that I pasted above), then this will fail. If you don't want to (or cannot) enable delegation, then a workaround for you is to store credentials for accessing the datasources in the catalog.

    In your 1st scenario (TestServerA), I am not certain why they are getting prompted for credentials. I suspect it is because your test users don't have access to your machine, are they able to connect when providing their credentials?

    |||my users do have access to the SQL Server databases so I don't know why they would get prompted still. No, when they type in their username and password, it doesn't take.|||

    ,I have missed the same problem once ,the problem is that ur datasource was set ot windows Authentification,(if u pay more attention to ur report'Connection string,u could find the bugs),but ur database has no right for this kind of user,

    u could follow this steps to add a user or a group which the user belong to :

    1.login in database

    2.extend the security node

    3.extend the logins node

    3.right-click logins node,click new login, and then add the user or the group which the user belong to to Database'logins.

    And there is a skill,if ur user is a member of administrator,and u assign permissions to the other user,by default,this kind of user only is a menber of user,dont have the role of administrator,so if u use the windows Authentification to build connection string for ur report,the user who just have a role of user don't have logins to database,u need to follow the steps above to add the user or the group to Database'logins.

    |||Samuel, they definitely already have logins to the database, right down to the permissions of the stored procs being called by the datasets so this is covered! They have read rights as well as datawriter (which isn't really needed). This is why I posted, I have done almost everything.|||

    I believe you are running into a couple of problems which are not necessarily related.

    When you are prompted for credentials in IE with the standard credentials dialog, it is because IIS did not accept the user's token when IE presented it in response to a 401. This usually means that the user is not a valid user on the target machine. Check your IIS logs for 401s.

    The datasource problems are because the user we are trying to access the database with is not allowed access. This can be for any number of reasons, the double-hop issue being a pretty common one when people are trying to pass through Windows credentials.

    |||

    I have a similar problem to FlavorFlave. Our setup:

    Machine A : client
    Machine B: SSRS 2005
    Machine C: SSAS 2000

    Running

    reports from Machine B works, running from from A does not - getting the

    exact error he specified. Logged on to machine A with a limited user

    account, onto B/C with full admin rights.

    Enabling delegation is

    not going to be possible on our network. John, i see you say a

    workaround is to "store credentials for accessing the datasources in

    the catalog". Not sure what you meant by this.. or where to do this?|||never mind.. ive figured it out :)

    stored the credentials securely within the datasource on the report server itself. works now... though its slower to initialise than when the security is integrated.|||talwar, can you explain the steps you took in detail so hopefully I can do the same...thanks

  • Cannot create a connection to data source !!!! SSRS 2005

    I cannot get this error resolve either for myself or any users, and I'm actually part of the Admin group! Furthermore, a user with whom I'm tring allow to view this report keeps getting prompted for their windows username and password. I thought that since this datasource was set to Windows Authentification that it would just pass it through?

    I'm pulling my hair out at this point:

    Screen Shots:

    http://www.webfound.net/datasource_connection.jpg

    http://www.webfound.net/datasource_connection2.jpg

    http://www.webfound.net/datasource_connection3.jpg


    Also As far as I know, I've given sufficient permissions to the right logins and right users on my SQL Databases and related stored procs that the datasets (not datasource) run

  • An error has occurred during report processing.
  • Cannot create a connection to data source 'datasourcename'.
  • For more information about this error navigate to the report server on the local server machine, or enable remote errors
  • Are the client, RS, and SQL server all on different machines? If so, then you are probably hitting the double-hop problem. This is a limitation of integrated security in environments which don't support kerberos.

    Tudor talks about it a bit in this blog entry:

    http://blogs.msdn.com/tudortr/archive/2005/11/03/488731.aspx

    You might want to check that out and see if the problem described there is what you are experiencing.

    |||

    No, I have gotten this to work fine for my test server which is the server running both RS and SQL Server 2005. RS and SQL Server 2005 are on the same box. The server I'm trying to connect to now is a different server's DB which is where the datasource is pointing to. So there is no double-hop issue here at least!

    So in other words if I change the datasets to use the datasources that piont to ServerA below, my report runs for me ok. If I change the datasets in my report to talk to ServerB, I get the error immediately. The datasets are running stored procs and referencing the data sources for the DB connection in the dataset properties. I am using 3 datasets in my report and around 4 datasources are in my project that are uploaded automatically when I deploy my report to the report serve (TestServerA)

    TestServerA - Has RS and SQL Server 2005. When using Datasources that point to this server's stored procs, it works for me at least the other users still have issues though where it's prompting them for a windows username and password

    ServerB - a production server running SQL Server 2000 (doesn't have Reporting Services on it, we're just runnign stored procs against it for the datasets) in which the dataset (on TestServerA) is trying to run a stored proc off of ServerB. It stil uses ServerA for Reporting services part...whcih is where I'm getting the error from my own client when trying to run the report from the client in Report Manager

    |||Ok, now I tried logging on directly to my TestServerA and ran the report from IE on that server (report Manager) and it works fine. Ok, so how am I getting a double hop issue if I have everything installed on the same server? I don't think hopping is the issue here still!|||scratch my last response...it was working only because my datasets were pointing to the datasources that were pointing to my TestServerA. Once I changed it back to the point where I got the error (for this post) whcih was to chagne teh datasets to point to the datasources that point to ServerB, I still get the error, even when running the report from TestServerA's Report Manager....|||

    Here's a diagram to show you what's going on. Keep in mind, if the datasets aren't using datasources that point to ServerB and are using datasources that point to TestServerA, all works fine...it's just when my report is using datasources trying to talk to ServerB.

    http://www.webfound.net/diagram.jpg

    |||

    Can you check the errors in the report server log files - they are under /Reporting Services/LogFiles/ReportServer*.log

    If you see an error message coming from your data sources server that looks like - login failed for user (null), then it's likely that you are experiencing the Integrated security double-hop issue.

    If that's the case, you can store credentials for the data sources in the report server, or enable Kerberos delegation as shown below:

    http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerbdel.mspx

    Thanks,

    Tudor

    |||

    In your second setup (ServerB) you are describing what I would expect to be the symptoms of the double hop problem. You have 3 machines, A->B->C. A is the client machine, B is the machine with reporting services, and C is the machine that has the data you are reporting against. You are trying to pass credentials from machine A all the way to machine C. Unless you have set up your environment to allow kerberos delegation (see the links that I pasted above), then this will fail. If you don't want to (or cannot) enable delegation, then a workaround for you is to store credentials for accessing the datasources in the catalog.

    In your 1st scenario (TestServerA), I am not certain why they are getting prompted for credentials. I suspect it is because your test users don't have access to your machine, are they able to connect when providing their credentials?

    |||my users do have access to the SQL Server databases so I don't know why they would get prompted still. No, when they type in their username and password, it doesn't take.|||

    ,I have missed the same problem once ,the problem is that ur datasource was set ot windows Authentification,(if u pay more attention to ur report'Connection string,u could find the bugs),but ur database has no right for this kind of user,

    u could follow this steps to add a user or a group which the user belong to :

    1.login in database

    2.extend the security node

    3.extend the logins node

    3.right-click logins node,click new login, and then add the user or the group which the user belong to to Database'logins.

    And there is a skill,if ur user is a member of administrator,and u assign permissions to the other user,by default,this kind of user only is a menber of user,dont have the role of administrator,so if u use the windows Authentification to build connection string for ur report,the user who just have a role of user don't have logins to database,u need to follow the steps above to add the user or the group to Database'logins.

    |||Samuel, they definitely already have logins to the database, right down to the permissions of the stored procs being called by the datasets so this is covered! They have read rights as well as datawriter (which isn't really needed). This is why I posted, I have done almost everything.|||

    I believe you are running into a couple of problems which are not necessarily related.

    When you are prompted for credentials in IE with the standard credentials dialog, it is because IIS did not accept the user's token when IE presented it in response to a 401. This usually means that the user is not a valid user on the target machine. Check your IIS logs for 401s.

    The datasource problems are because the user we are trying to access the database with is not allowed access. This can be for any number of reasons, the double-hop issue being a pretty common one when people are trying to pass through Windows credentials.

    |||I have a similar problem to FlavorFlave. Our setup:

    Machine A : client
    Machine B: SSRS 2005
    Machine C: SSAS 2000

    Running reports from Machine B works, running from from A does not - getting the exact error he specified. Logged on to machine A with a limited user account, onto B/C with full admin rights.

    Enabling delegation is not going to be possible on our network. John, i see you say a workaround is to "store credentials for accessing the datasources in the catalog". Not sure what you meant by this.. or where to do this?|||never mind.. ive figured it out :)

    stored the credentials securely within the datasource on the report server itself. works now... though its slower to initialise than when the security is integrated.
    |||talwar, can you explain the steps you took in detail so hopefully I can do the same...thanks

  • Cannot create a connection to data source - SSRS 2005

    I cannot get this error resolve either for myself or any users, and I'm
    actually part of the Admin group! Furthermore, a user with whom I'm
    tring allow to view this report keeps getting prompted for their
    windows username and password. I thought that since this datasource
    was set to Windows Authentification that it would just pass it through?
    I'm pulling my hair out at this point:
    Screen Shots:
    http://www.webfound.net/datasource_connection.jpg
    http://www.webfound.net/datasource_connection2.jpg
    http://www.webfound.net/datasource_connection3.jpg
    Also As far as I know, I've given proper permissions to the right
    logins and right users on my SQL Databases and related stored procs
    that the datasets (not datasource) run
    An error has occurred during report processing.
    Cannot create a connection to data source 'datasourcename'.
    For more information about this error navigate to the report server on
    the local server machine, or enable remote errorsWith windows authentication issue, there is a parameter in Internet
    Explorer which can cause this. Goto Tools|Internet options|Security
    then I think the problem is likely to be the Intranet Zone, but
    depending on your setup it could be one of the others too. Anyway,
    select the Intranet Zone then custom, scroll to the bottom and you
    should see User Authentication, you've probably got it set to Prompt on
    this particular PC. This seems to be the default on Windows 2000
    machines.
    You may also find Active Directory policies can override this setting,
    when they reboot.
    On the data source issue:
    A bit of a long shot this, but try removing the hyphens '-' from the
    datasource names. It's never a good idea to put these sorts of
    characters in SQL related stuff (this is the voice of experience!).
    Also, can you run it from BIDS? If you can, then it would suggest the
    server you are deploying to cannot see the server containing the actual
    datasource.
    Also, it may be worth checking the datasource "file" on the report
    server. Remember, when you deploy a report it won't overwrite a
    datasource if it already exists, and if it's been changed on the server
    in any way the report will use that instead. Having said that, viewing
    your screenshots it doesn't look like this is the case.
    My hunch is your report server can't gain access to the server with the
    data. Maybe describing the server setup a bit more may shed some more
    light on the issue.
    Hope some of this helps.
    Cheers
    Chris
    dba123 wrote:
    > I cannot get this error resolve either for myself or any users, and
    > I'm actually part of the Admin group! Furthermore, a user with whom
    > I'm tring allow to view this report keeps getting prompted for their
    > windows username and password. I thought that since this datasource
    > was set to Windows Authentification that it would just pass it
    > through?
    > I'm pulling my hair out at this point:
    > Screen Shots:
    > http://www.webfound.net/datasource_connection.jpg
    > http://www.webfound.net/datasource_connection2.jpg
    > http://www.webfound.net/datasource_connection3.jpg
    >
    > Also As far as I know, I've given proper permissions to the right
    > logins and right users on my SQL Databases and related stored procs
    > that the datasets (not datasource) run
    > An error has occurred during report processing.
    > Cannot create a connection to data source 'datasourcename'.
    > For more information about this error navigate to the report server on
    > the local server machine, or enable remote errors

    Wednesday, March 7, 2012

    Cannot connect with the Administator account

    Hi.
    I installed Sql Server 2005 with NetworkService user and now
    I can't connect with Management Studio with the Administrator account.
    How can I do?
    Thx! ;-)
    Matteo Migliore
    Blog - http://blogs.ugidotnet.org/matteomiglioreError message?
    Kevin Hill
    IC3 North Texas
    www.ChristianCycling.com
    Please support me in the 2008 MS150:
    http://www.ms150.org/dallas/donate/donate.cfm?id=208000
    "Matteo Migliore" <matteo.migliore.cut@.gmail.com> wrote in message
    news:e4Ateg$RIHA.4752@.TK2MSFTNGP05.phx.gbl...
    > Hi.
    > I installed Sql Server 2005 with NetworkService user and now
    > I can't connect with Management Studio with the Administrator account.
    > How can I do?
    > Thx! ;-)
    > --
    > Matteo Migliore
    > Blog - http://blogs.ugidotnet.org/matteomigliore
    >|||> Error message?
    There aren't errors. The problem is that only NetworkService user can
    connect,
    but not the Administrator account. I suppose that I've to add Administrator
    to users.
    Mmmm... while I was writing, I tried to run Management Studio with "Run As
    Administrator" in Vista,
    and I solved the problem.
    Thx again!
    Matteo Migliore
    Blog - http://blogs.ugidotnet.org/matteomigliore|||That's because Windows Vista' s UAC. Another user experienced the very same
    problem some days ago in the NG if I'm remembering correctly...
    Ekrem nsoy
    "Matteo Migliore" <matteo.migliore.cut@.gmail.com> wrote in message
    news:%23B9PGHASIHA.2000@.TK2MSFTNGP05.phx.gbl...
    > There aren't errors. The problem is that only NetworkService user can
    > connect,
    > but not the Administrator account. I suppose that I've to add
    > Administrator to users.
    > Mmmm... while I was writing, I tried to run Management Studio with "Run As
    > Administrator" in Vista,
    > and I solved the problem.
    > Thx again!
    > --
    > Matteo Migliore
    > Blog - http://blogs.ugidotnet.org/matteomigliore
    >|||> Mmmm... while I was writing, I tried to run Management Studio with "Run As
    > Administrator" in Vista,
    > and I solved the problem.
    Alternatively, you can add the specific user Windows account as a login and
    to the sysadmin server role. This is basically what is done by the the user
    provisioning tool that can be launched at the end of the SQL 2005 SP2
    installation.
    Hope this helps.
    Dan Guzman
    SQL Server MVP
    "Matteo Migliore" <matteo.migliore.cut@.gmail.com> wrote in message
    news:%23B9PGHASIHA.2000@.TK2MSFTNGP05.phx.gbl...
    > There aren't errors. The problem is that only NetworkService user can
    > connect,
    > but not the Administrator account. I suppose that I've to add
    > Administrator to users.
    > Mmmm... while I was writing, I tried to run Management Studio with "Run As
    > Administrator" in Vista,
    > and I solved the problem.
    > Thx again!
    > --
    > Matteo Migliore
    > Blog - http://blogs.ugidotnet.org/matteomigliore
    >

    Cannot connect w/ Java app but can connect w/ .Net app - SQL Server Express 2005

    I'm having a problem connecting with a Java application but I CAN connect using my .Net application - the user name and password are the same for both (using the same database on SQL Server Express 2005).

    The error I get is: "com.microsoft.sqlserver.jdbc.SQLServerException: Cannot open database "CORNERS" requested by the login. The login failed." An interesing note - I get the same message if the database is not running.

    SQL Server Express 2005 is installed in mixed mode.

    Here is my connection string in the .Net appplication: <add key="connectString" value="Server=(local);UID=sa;PWD=myPasswd;Database=CORNERS" />.

    These are my values in my Java app web.xml -

    <init-param>
    <param-name>DBDriver</param-name>
    <param-value>com.microsoft.sqlserver.jdbc.SQLServerDriver</param-value>
    </init-param>
    <init-param>

    <param-name>DBURL</param-name> <param-value>jdbc:sqlserver://localhost\sqlexpress:1055;databaseName=CORNERS</param-value>

    </init-param>
    <init-param>
    <param-name>DBUser</param-name>
    <param-value>sa</param-value>
    </init-param>
    <init-param>
    <param-name>DBPwd</param-name>
    <param-value>myPasswd</param-value>
    </init-param>.

    And yes, the port is 1055 - I checked to find it.

    I am using Microsoft SQL Server 2005 JDBC Driver 1.0 (sqljdbc_1.0.809.102).

    Does anyone have any idea what is wrong so that the login fails in the Java application but works in the .Net application?

    Mostlikely, you have a syntax error in your connection string.

    jdbc:sqlserver://localhost\sqlexpress:1055;databaseName=CORNERS

    please refer to http://msdn2.microsoft.com/en-us/library/ms378428.aspx

    you can try

    jdbc:sqlserver://localhost:1055;databaseName=CORNERS,

    |||I tried your suggestion and it does not work. I get the same error. I tried many different variations of the connection string and none of them have worked.

    I think it is important to note that I get this error even if the database is NOT running.

    This leads me to believe it's a problem with the driver. I have the sqljdbc.jar located in my Tomcat\common\lib directory. Is this incorrect?|||Can you get a trace with FINEST level turned on?|||How do I turn the trace on? And to the finest level? And will this make a difference considering that I get the same message whether or not the database is actually running?|||

    I'm having a similar problem. However I am using context.xml to define the connection pool as:

    <Resource name="jdbc/SqlServerLocal"
    auth="Container"
    type="javax.sql.DataSource"
    username="PortalUser"
    password="********"
    driverClassName="com.microsoft.sqlserver.jdbc.SQLServerDriver"
    url="jdbc:sqlserver://servername\\SQLEXPRESS:1433"
    maxActive="10"
    maxIdle="4"
    maxWait="100" />

    and this works on my Windows development machine... but when I ftp the *.war file to the Linux server, I get the following message:

    Cannot load JDBC driver class 'com.microsoft.sqlserver.jdbc.SQLServerDriver'

    I put the 'sqljdbc.jar' file in the /common/lib path for both installations.

    |||

    Adisciullo,

    Please refer to the following site for information regarding turning tracing on:

    http://msdn2.microsoft.com/en-us/library/ms378517.aspx

    Please post the results so we can further diagnose this.

    Additionally, does this problem also reproduce with the v1.1 driver. You can find it at: http://www.microsoft.com/downloads/details.aspx?FamilyId=6D483869-816A-44CB-9787-A866235EFC7C&displaylang=en

    Thanks,

    Jaaved Mohammed