Showing posts with label login. Show all posts
Showing posts with label login. Show all posts

Friday, March 23, 2012

new SQL Server 2005 install giving login error... HELP!

I completely uninstalled 2000 and did a clean install of 2005. I restored m
y
database and users and all seems fine. I am set up with mixed authenticatio
n
(windows and sql server). My username is in security/logins as well as in
database/security/users with connect and select permissions.
I am getting the following error when trying to submit my asp page:
Microsoft OLE DB Provider for SQL Server error '80004005'
Cannot open database "dbName" requested by the login. The login failed.
/AddressSearch/SearchResults.asp, line 40Hi
This sounds like you have orphaned users
121120120" target="_blank">http://support.microsoft.com/defaul...r />
121120120
John
"SharinDenver" wrote:

> I completely uninstalled 2000 and did a clean install of 2005. I restored
my
> database and users and all seems fine. I am set up with mixed authenticat
ion
> (windows and sql server). My username is in security/logins as well as in
> database/security/users with connect and select permissions.
> I am getting the following error when trying to submit my asp page:
>
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Cannot open database "dbName" requested by the login. The login failed.
> /AddressSearch/SearchResults.asp, line 40
>|||You rock! Thank you! Those articles worked perfectly.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This sounds like you have orphaned users
> 20121120120" target="_blank">http://support.microsoft.com/defaul.../>
20121120120
> John
> "SharinDenver" wrote:
>

new SQL Server 2005 install giving login error... HELP!

I completely uninstalled 2000 and did a clean install of 2005. I restored my
database and users and all seems fine. I am set up with mixed authentication
(windows and sql server). My username is in security/logins as well as in
database/security/users with connect and select permissions.
I am getting the following error when trying to submit my asp page:
Microsoft OLE DB Provider for SQL Server error '80004005'
Cannot open database "dbName" requested by the login. The login failed.
/AddressSearch/SearchResults.asp, line 40
Hi
This sounds like you have orphaned users
http://support.microsoft.com/default...21120121120120
John
"SharinDenver" wrote:

> I completely uninstalled 2000 and did a clean install of 2005. I restored my
> database and users and all seems fine. I am set up with mixed authentication
> (windows and sql server). My username is in security/logins as well as in
> database/security/users with connect and select permissions.
> I am getting the following error when trying to submit my asp page:
>
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Cannot open database "dbName" requested by the login. The login failed.
> /AddressSearch/SearchResults.asp, line 40
>
|||You rock! Thank you! Those articles worked perfectly.
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> This sounds like you have orphaned users
> http://support.microsoft.com/default...21120121120120
> John
> "SharinDenver" wrote:

new SQL Server 2005 install giving login error... HELP!

I completely uninstalled 2000 and did a clean install of 2005. I restored my
database and users and all seems fine. I am set up with mixed authentication
(windows and sql server). My username is in security/logins as well as in
database/security/users with connect and select permissions.
I am getting the following error when trying to submit my asp page:
Microsoft OLE DB Provider for SQL Server error '80004005'
Cannot open database "dbName" requested by the login. The login failed.
/AddressSearch/SearchResults.asp, line 40Hi
This sounds like you have orphaned users
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314546#XSLTH3182121121120121120120
John
"SharinDenver" wrote:
> I completely uninstalled 2000 and did a clean install of 2005. I restored my
> database and users and all seems fine. I am set up with mixed authentication
> (windows and sql server). My username is in security/logins as well as in
> database/security/users with connect and select permissions.
> I am getting the following error when trying to submit my asp page:
>
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Cannot open database "dbName" requested by the login. The login failed.
> /AddressSearch/SearchResults.asp, line 40
>|||You rock! Thank you! Those articles worked perfectly.
"John Bell" wrote:
> Hi
> This sounds like you have orphaned users
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q314546#XSLTH3182121121120121120120
> John
> "SharinDenver" wrote:
> > I completely uninstalled 2000 and did a clean install of 2005. I restored my
> > database and users and all seems fine. I am set up with mixed authentication
> > (windows and sql server). My username is in security/logins as well as in
> > database/security/users with connect and select permissions.
> >
> > I am getting the following error when trying to submit my asp page:
> >
> >
> > Microsoft OLE DB Provider for SQL Server error '80004005'
> >
> > Cannot open database "dbName" requested by the login. The login failed.
> >
> > /AddressSearch/SearchResults.asp, line 40
> >

Wednesday, March 21, 2012

new sql login using active directory

I have a sql admin who is not a domain admin and when he selects a new login for sql 2000 using the domain lookup it tells him he has no permission and can't see any user in active directory. He does have active directory users and computers on his desktop and can see them all there. Any suggestions' He is a local admin on the sql server box and can see local users.I would think you can't enumerate users and groups in
Active Directory unless you are given specific rights. I
know this is true for Open LDAP and IBM SecureWay bases
directory services. Ask him to enter NET USERS /DOMAIN
command on DOS command prompt and see if it lists all
users in the Domain. I would suggest you to post this
question to windows 2000 group, or ask your network admin.
This isn't a sql issue, if he is local admin then more
likely he has DBA privileges in server.
>--Original Message--
>I have a sql admin who is not a domain admin and when he
selects a new login for sql 2000 using the domain lookup
it tells him he has no permission and can't see any user
in active directory. He does have active directory users
and computers on his desktop and can see them all there.
Any suggestions' He is a local admin on the sql
server box and can see local users.
>.
>

New SQL Login cannot list DB in EM

I have a SQL Server 2000 instance running sp3 (in a
cluster).
When I create a NEW SQL user, and give that user access to
ONE database (public and DBO) I cannot list ANY databases
from Enterprise Manager when I login with that user. If I
refresh the Enterprise Manager Databases View, eventually
it will display the Databases - but only after about 10
minutes and I get access violation errors in my SQL and NT
logs. Even if I create a 'dummy SQL login' and give it
access to Northwind, the same results - I cannot list
databases in Enterprise Manager. I tried making the
Defalt DB both Master and the actual DB with the same
results
I tried to recreate this problem on another Clustered SQL
Server 2000 Instance - this one running sp3a, and I am NOT
able to recreate this problem.
I can't imagine that this is a Service Pack issue. Does
anyone have any suggestions?
If you remove the guest user in any database a similar problem can occur.
Look at the following article:
http://support.microsoft.com/?kbid=315523
PRB: Removal of Guest Account May Cause Handled Exception Access Violation
in SQL Server
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Thank you very much!!! I ran the script in the KB article and it fixed my problem!
sql

New SQL Login cannot list DB in EM

I have a SQL Server 2000 instance running sp3 (in a
cluster).
When I create a NEW SQL user, and give that user access to
ONE database (public and DBO) I cannot list ANY databases
from Enterprise Manager when I login with that user. If I
refresh the Enterprise Manager Databases View, eventually
it will display the Databases - but only after about 10
minutes and I get access violation errors in my SQL and NT
logs. Even if I create a 'dummy SQL login' and give it
access to Northwind, the same results - I cannot list
databases in Enterprise Manager. I tried making the
Defalt DB both Master and the actual DB with the same
results
I tried to recreate this problem on another Clustered SQL
Server 2000 Instance - this one running sp3a, and I am NOT
able to recreate this problem.
I can't imagine that this is a Service Pack issue. Does
anyone have any suggestions?If you remove the guest user in any database a similar problem can occur.
Look at the following article:
http://support.microsoft.com/?kbid=315523
PRB: Removal of Guest Account May Cause Handled Exception Access Violation
in SQL Server
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank you very much!!! I ran the script in the KB article and it fixed my problem!

New SQL Login cannot list DB in EM

I have a SQL Server 2000 instance running sp3 (in a
cluster).
When I create a NEW SQL user, and give that user access to
ONE database (public and DBO) I cannot list ANY databases
from Enterprise Manager when I login with that user. If I
refresh the Enterprise Manager Databases View, eventually
it will display the Databases - but only after about 10
minutes and I get access violation errors in my SQL and NT
logs. Even if I create a 'dummy SQL login' and give it
access to Northwind, the same results - I cannot list
databases in Enterprise Manager. I tried making the
Defalt DB both Master and the actual DB with the same
results
I tried to recreate this problem on another Clustered SQL
Server 2000 Instance - this one running sp3a, and I am NOT
able to recreate this problem.
I can't imagine that this is a Service Pack issue. Does
anyone have any suggestions?If you remove the guest user in any database a similar problem can occur.
Look at the following article:
http://support.microsoft.com/?kbid=315523
PRB: Removal of Guest Account May Cause Handled Exception Access Violation
in SQL Server
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Thank you very much!!! I ran the script in the KB article and it fixed my
problem!

Monday, March 19, 2012

new server gives login error URGENT

This is on my web page from a log in:
Microsoft OLE DB Provider for SQL Server error '80004005'
Login failed for user 'TGI_Int_Admin_Webapp'. Reason: Not associated with a
trusted SQL Server connection.
/admin/addconn_1.asp, line 7
I have take a new server given it the former IP of the old one, restored the
data from the old one, and done a DTS for transfer of users.
That DTS gives an error, but no details. I can see Error Occured in the
status, and nothing more
Where do I go to next?Hi
Please check out what is sql server's authentication.
Probably you have "windows only" authentication , try to change it to
"mixed"
"__Stephen" <srussell@.transactiongraphics.com> wrote in message
news:eYzSbOgEGHA.140@.TK2MSFTNGP12.phx.gbl...
> This is on my web page from a log in:
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Login failed for user 'TGI_Int_Admin_Webapp'. Reason: Not associated with
> a trusted SQL Server connection.
> /admin/addconn_1.asp, line 7
>
> I have take a new server given it the former IP of the old one, restored
> the data from the old one, and done a DTS for transfer of users.
>
> That DTS gives an error, but no details. I can see Error Occured in the
> status, and nothing more
> Where do I go to next?
>
>|||Thanks, correct that new box was set as Win only. that has been changed to
mixed. DTS package still fails after stop & start of service.
Any other ideas?
I see the UserID in the actual db for the serve and I see the userid in the
security login for that server for all dbs.
Stephen
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ed4jrSgEGHA.1032@.TK2MSFTNGP11.phx.gbl...
> Hi
> Please check out what is sql server's authentication.
> Probably you have "windows only" authentication , try to change it to
> "mixed"
>
> "__Stephen" <srussell@.transactiongraphics.com> wrote in message
> news:eYzSbOgEGHA.140@.TK2MSFTNGP12.phx.gbl...
>|||I didn't see an * properly as an ending char for a PW. I thought that it
was a ".
Thanks again!
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ed4jrSgEGHA.1032@.TK2MSFTNGP11.phx.gbl...
> Hi
> Please check out what is sql server's authentication.
> Probably you have "windows only" authentication , try to change it to
> "mixed"
>
> "__Stephen" <srussell@.transactiongraphics.com> wrote in message
> news:eYzSbOgEGHA.140@.TK2MSFTNGP12.phx.gbl...
>|||Do you call the DTS from a job ?
If you do ,an another option is that you have created a package on your
workstation , i mean the owner of the package is not the same as an acount
that SQL Server Agent running under.
"__Stephen" <srussell@.transactiongraphics.com> wrote in message
news:OV64bZgEGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks, correct that new box was set as Win only. that has been changed
> to mixed. DTS package still fails after stop & start of service.
> Any other ideas?
> I see the UserID in the actual db for the serve and I see the userid in
> the security login for that server for all dbs.
> Stephen
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ed4jrSgEGHA.1032@.TK2MSFTNGP11.phx.gbl...
>|||Stephen,
Make sure that user 'TGI_Int_Admin_Webapp' is added to appropriate
windows group on the new server and that you have granted that windows group
appropriate windows permissions.
"__Stephen" wrote:

> This is on my web page from a log in:
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Login failed for user 'TGI_Int_Admin_Webapp'. Reason: Not associated with
a
> trusted SQL Server connection.
> /admin/addconn_1.asp, line 7
>
> I have take a new server given it the former IP of the old one, restored t
he
> data from the old one, and done a DTS for transfer of users.
>
> That DTS gives an error, but no details. I can see Error Occured in the
> status, and nothing more
> Where do I go to next?
>
>
>|||Thanks Uri, I even went to the cold cellar or server room, and it failed
there as well.
The mixed authentication worked when I fixed the login/pw to be correct. I
hate an old dheap monitor for the server rack!
__Stephen
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ux1XGfgEGHA.2040@.TK2MSFTNGP14.phx.gbl...
> Do you call the DTS from a job ?
> If you do ,an another option is that you have created a package on your
> workstation , i mean the owner of the package is not the same as an
> acount that SQL Server Agent running under.
>
>
> "__Stephen" <srussell@.transactiongraphics.com> wrote in message
> news:OV64bZgEGHA.344@.TK2MSFTNGP11.phx.gbl...
>|||"Pradeep Gharat" <PradeepGharat@.discussions.microsoft.com> wrote in message
news:63A6D7CC-98DA-4759-A39A-58CE46191F82@.microsoft.com...
> Stephen,
> Make sure that user 'TGI_Int_Admin_Webapp' is added to appropriate
> windows group on the new server and that you have granted that windows
> group
> appropriate windows permissions.
Actually I don't want to do that. I added the SQL Authentication and it's
running now.

new server gives login error URGENT

This is on my web page from a log in:
Microsoft OLE DB Provider for SQL Server error '80004005'
Login failed for user 'TGI_Int_Admin_Webapp'. Reason: Not associated with a
trusted SQL Server connection.
/admin/addconn_1.asp, line 7
I have take a new server given it the former IP of the old one, restored the
data from the old one, and done a DTS for transfer of users.
That DTS gives an error, but no details. I can see Error Occured in the
status, and nothing more
Where do I go to next?
Hi
Please check out what is sql server's authentication.
Probably you have "windows only" authentication , try to change it to
"mixed"
"__Stephen" <srussell@.transactiongraphics.com> wrote in message
news:eYzSbOgEGHA.140@.TK2MSFTNGP12.phx.gbl...
> This is on my web page from a log in:
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Login failed for user 'TGI_Int_Admin_Webapp'. Reason: Not associated with
> a trusted SQL Server connection.
> /admin/addconn_1.asp, line 7
>
> I have take a new server given it the former IP of the old one, restored
> the data from the old one, and done a DTS for transfer of users.
>
> That DTS gives an error, but no details. I can see Error Occured in the
> status, and nothing more
> Where do I go to next?
>
>
|||Thanks, correct that new box was set as Win only. that has been changed to
mixed. DTS package still fails after stop & start of service.
Any other ideas?
I see the UserID in the actual db for the serve and I see the userid in the
security login for that server for all dbs.
Stephen
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ed4jrSgEGHA.1032@.TK2MSFTNGP11.phx.gbl...
> Hi
> Please check out what is sql server's authentication.
> Probably you have "windows only" authentication , try to change it to
> "mixed"
>
> "__Stephen" <srussell@.transactiongraphics.com> wrote in message
> news:eYzSbOgEGHA.140@.TK2MSFTNGP12.phx.gbl...
>
|||I didn't see an * properly as an ending char for a PW. I thought that it
was a ".
Thanks again!
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ed4jrSgEGHA.1032@.TK2MSFTNGP11.phx.gbl...
> Hi
> Please check out what is sql server's authentication.
> Probably you have "windows only" authentication , try to change it to
> "mixed"
>
> "__Stephen" <srussell@.transactiongraphics.com> wrote in message
> news:eYzSbOgEGHA.140@.TK2MSFTNGP12.phx.gbl...
>
|||Do you call the DTS from a job ?
If you do ,an another option is that you have created a package on your
workstation , i mean the owner of the package is not the same as an acount
that SQL Server Agent running under.
"__Stephen" <srussell@.transactiongraphics.com> wrote in message
news:OV64bZgEGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks, correct that new box was set as Win only. that has been changed
> to mixed. DTS package still fails after stop & start of service.
> Any other ideas?
> I see the UserID in the actual db for the serve and I see the userid in
> the security login for that server for all dbs.
> Stephen
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ed4jrSgEGHA.1032@.TK2MSFTNGP11.phx.gbl...
>
|||Stephen,
Make sure that user 'TGI_Int_Admin_Webapp' is added to appropriate
windows group on the new server and that you have granted that windows group
appropriate windows permissions.
"__Stephen" wrote:

> This is on my web page from a log in:
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Login failed for user 'TGI_Int_Admin_Webapp'. Reason: Not associated with a
> trusted SQL Server connection.
> /admin/addconn_1.asp, line 7
>
> I have take a new server given it the former IP of the old one, restored the
> data from the old one, and done a DTS for transfer of users.
>
> That DTS gives an error, but no details. I can see Error Occured in the
> status, and nothing more
> Where do I go to next?
>
>
>
|||Thanks Uri, I even went to the cold cellar or server room, and it failed
there as well.
The mixed authentication worked when I fixed the login/pw to be correct. I
hate an old dheap monitor for the server rack!
__Stephen
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ux1XGfgEGHA.2040@.TK2MSFTNGP14.phx.gbl...
> Do you call the DTS from a job ?
> If you do ,an another option is that you have created a package on your
> workstation , i mean the owner of the package is not the same as an
> acount that SQL Server Agent running under.
>
>
> "__Stephen" <srussell@.transactiongraphics.com> wrote in message
> news:OV64bZgEGHA.344@.TK2MSFTNGP11.phx.gbl...
>
|||"Pradeep Gharat" <PradeepGharat@.discussions.microsoft.com> wrote in message
news:63A6D7CC-98DA-4759-A39A-58CE46191F82@.microsoft.com...
> Stephen,
> Make sure that user 'TGI_Int_Admin_Webapp' is added to appropriate
> windows group on the new server and that you have granted that windows
> group
> appropriate windows permissions.
Actually I don't want to do that. I added the SQL Authentication and it's
running now.

new server gives login error URGENT

This is on my web page from a log in:
Microsoft OLE DB Provider for SQL Server error '80004005'
Login failed for user 'TGI_Int_Admin_Webapp'. Reason: Not associated with a
trusted SQL Server connection.
/admin/addconn_1.asp, line 7
I have take a new server given it the former IP of the old one, restored the
data from the old one, and done a DTS for transfer of users.
That DTS gives an error, but no details. I can see Error Occured in the
status, and nothing more :(
Where do I go to next?Do you have mixed authentication mode on that server?
right click the server-->properties-->security and take a look, is
windows only checked?|||Hi
Please check out what is sql server's authentication.
Probably you have "windows only" authentication , try to change it to
"mixed"
"__Stephen" <srussell@.transactiongraphics.com> wrote in message
news:eYzSbOgEGHA.140@.TK2MSFTNGP12.phx.gbl...
> This is on my web page from a log in:
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Login failed for user 'TGI_Int_Admin_Webapp'. Reason: Not associated with
> a trusted SQL Server connection.
> /admin/addconn_1.asp, line 7
>
> I have take a new server given it the former IP of the old one, restored
> the data from the old one, and done a DTS for transfer of users.
>
> That DTS gives an error, but no details. I can see Error Occured in the
> status, and nothing more :(
> Where do I go to next?
>
>|||Seems that your are not using mixed authentication. Try to set the
server to mixed authentication.
HTH, jens Suessmeyer.|||Thanks, correct that new box was set as Win only. that has been changed to
mixed. DTS package still fails after stop & start of service.
Any other ideas?
I see the UserID in the actual db for the serve and I see the userid in the
security login for that server for all dbs.
Stephen
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ed4jrSgEGHA.1032@.TK2MSFTNGP11.phx.gbl...
> Hi
> Please check out what is sql server's authentication.
> Probably you have "windows only" authentication , try to change it to
> "mixed"
>
> "__Stephen" <srussell@.transactiongraphics.com> wrote in message
> news:eYzSbOgEGHA.140@.TK2MSFTNGP12.phx.gbl...
>> This is on my web page from a log in:
>> Microsoft OLE DB Provider for SQL Server error '80004005'
>> Login failed for user 'TGI_Int_Admin_Webapp'. Reason: Not associated with
>> a trusted SQL Server connection.
>> /admin/addconn_1.asp, line 7
>>
>> I have take a new server given it the former IP of the old one, restored
>> the data from the old one, and done a DTS for transfer of users.
>>
>> That DTS gives an error, but no details. I can see Error Occured in the
>> status, and nothing more :(
>> Where do I go to next?
>>
>>
>|||Thanks, correct that new box was set as Win only. that has been changed to
mixed. DTS package still fails after stop & start of service.
Any other ideas?
I see the UserID in the actual db for the serve and I see the userid in the
security login for that server for all dbs.
Stephen
"SQL" <denis.gobo@.gmail.com> wrote in message
news:1136471412.242368.94270@.f14g2000cwb.googlegroups.com...
> Do you have mixed authentication mode on that server?
> right click the server-->properties-->security and take a look, is
> windows only checked?
>|||Thanks
I wasn't using mixed authentication as well as confusing * with " on a fuzzy
server monitor!!
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1136471757.457363.194350@.g14g2000cwa.googlegroups.com...
> Seems that your are not using mixed authentication. Try to set the
> server to mixed authentication.
> HTH, jens Suessmeyer.
>|||I didn't see an * properly as an ending char for a PW. I thought that it
was a ".
Thanks again!
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ed4jrSgEGHA.1032@.TK2MSFTNGP11.phx.gbl...
> Hi
> Please check out what is sql server's authentication.
> Probably you have "windows only" authentication , try to change it to
> "mixed"
>
> "__Stephen" <srussell@.transactiongraphics.com> wrote in message
> news:eYzSbOgEGHA.140@.TK2MSFTNGP12.phx.gbl...
>> This is on my web page from a log in:
>> Microsoft OLE DB Provider for SQL Server error '80004005'
>> Login failed for user 'TGI_Int_Admin_Webapp'. Reason: Not associated with
>> a trusted SQL Server connection.
>> /admin/addconn_1.asp, line 7
>>
>> I have take a new server given it the former IP of the old one, restored
>> the data from the old one, and done a DTS for transfer of users.
>>
>> That DTS gives an error, but no details. I can see Error Occured in the
>> status, and nothing more :(
>> Where do I go to next?
>>
>>
>|||I didn't see an * properly as an ending char for a PW. I thought that it
was a ".
Thanks again!
"SQL" <denis.gobo@.gmail.com> wrote in message
news:1136471412.242368.94270@.f14g2000cwb.googlegroups.com...
> Do you have mixed authentication mode on that server?
> right click the server-->properties-->security and take a look, is
> windows only checked?
>|||Do you call the DTS from a job ?
If you do ,an another option is that you have created a package on your
workstation , i mean the owner of the package is not the same as an acount
that SQL Server Agent running under.
"__Stephen" <srussell@.transactiongraphics.com> wrote in message
news:OV64bZgEGHA.344@.TK2MSFTNGP11.phx.gbl...
> Thanks, correct that new box was set as Win only. that has been changed
> to mixed. DTS package still fails after stop & start of service.
> Any other ideas?
> I see the UserID in the actual db for the serve and I see the userid in
> the security login for that server for all dbs.
> Stephen
>
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:ed4jrSgEGHA.1032@.TK2MSFTNGP11.phx.gbl...
>> Hi
>> Please check out what is sql server's authentication.
>> Probably you have "windows only" authentication , try to change it to
>> "mixed"
>>
>> "__Stephen" <srussell@.transactiongraphics.com> wrote in message
>> news:eYzSbOgEGHA.140@.TK2MSFTNGP12.phx.gbl...
>> This is on my web page from a log in:
>> Microsoft OLE DB Provider for SQL Server error '80004005'
>> Login failed for user 'TGI_Int_Admin_Webapp'. Reason: Not associated
>> with a trusted SQL Server connection.
>> /admin/addconn_1.asp, line 7
>>
>> I have take a new server given it the former IP of the old one, restored
>> the data from the old one, and done a DTS for transfer of users.
>>
>> That DTS gives an error, but no details. I can see Error Occured in the
>> status, and nothing more :(
>> Where do I go to next?
>>
>>
>>
>|||Stephen,
Make sure that user 'TGI_Int_Admin_Webapp' is added to appropriate
windows group on the new server and that you have granted that windows group
appropriate windows permissions.
"__Stephen" wrote:
> This is on my web page from a log in:
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Login failed for user 'TGI_Int_Admin_Webapp'. Reason: Not associated with a
> trusted SQL Server connection.
> /admin/addconn_1.asp, line 7
>
> I have take a new server given it the former IP of the old one, restored the
> data from the old one, and done a DTS for transfer of users.
>
> That DTS gives an error, but no details. I can see Error Occured in the
> status, and nothing more :(
> Where do I go to next?
>
>
>|||Thanks Uri, I even went to the cold cellar or server room, and it failed
there as well.
The mixed authentication worked when I fixed the login/pw to be correct. I
hate an old dheap monitor for the server rack!
__Stephen
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ux1XGfgEGHA.2040@.TK2MSFTNGP14.phx.gbl...
> Do you call the DTS from a job ?
> If you do ,an another option is that you have created a package on your
> workstation , i mean the owner of the package is not the same as an
> acount that SQL Server Agent running under.
>
>
> "__Stephen" <srussell@.transactiongraphics.com> wrote in message
> news:OV64bZgEGHA.344@.TK2MSFTNGP11.phx.gbl...
>> Thanks, correct that new box was set as Win only. that has been changed
>> to mixed. DTS package still fails after stop & start of service.
>> Any other ideas?
>> I see the UserID in the actual db for the serve and I see the userid in
>> the security login for that server for all dbs.
>> Stephen
>>
>> "Uri Dimant" <urid@.iscar.co.il> wrote in message
>> news:ed4jrSgEGHA.1032@.TK2MSFTNGP11.phx.gbl...
>> Hi
>> Please check out what is sql server's authentication.
>> Probably you have "windows only" authentication , try to change it to
>> "mixed"
>>
>> "__Stephen" <srussell@.transactiongraphics.com> wrote in message
>> news:eYzSbOgEGHA.140@.TK2MSFTNGP12.phx.gbl...
>> This is on my web page from a log in:
>> Microsoft OLE DB Provider for SQL Server error '80004005'
>> Login failed for user 'TGI_Int_Admin_Webapp'. Reason: Not associated
>> with a trusted SQL Server connection.
>> /admin/addconn_1.asp, line 7
>>
>> I have take a new server given it the former IP of the old one,
>> restored the data from the old one, and done a DTS for transfer of
>> users.
>>
>> That DTS gives an error, but no details. I can see Error Occured in
>> the status, and nothing more :(
>> Where do I go to next?
>>
>>
>>
>>
>|||"Pradeep Gharat" <PradeepGharat@.discussions.microsoft.com> wrote in message
news:63A6D7CC-98DA-4759-A39A-58CE46191F82@.microsoft.com...
> Stephen,
> Make sure that user 'TGI_Int_Admin_Webapp' is added to appropriate
> windows group on the new server and that you have granted that windows
> group
> appropriate windows permissions.
Actually I don't want to do that. I added the SQL Authentication and it's
running now.

Monday, March 12, 2012

new login, EXECUTE permissions

I'm a newbie to the admin side of SqlServer. I created a new login:
<code>
CREATE LOGIN pmd_app
WITH PASSWORD='********'
</code>
I then used the "Server Management Studio Express" to create a new user in
my DB with the same name, then give the logical permissions, at least
logical to me. I can read and write table data with this new user, but I'm
getting EXECUTE permission errors when calling sprocs. I know how to grant
permissions to a user on a per object basis, but what role memberships
should I be using to give them EXECUTE permissions to all new sprocs that I
create?
I'm looking over BOL to see if I can find the answer, but so far not coming
up with anything.
Also, if anyone knows a good place to find an article covering SQLServer
security, role, permission, schemas, etc that would be awesome ;)
Thanks for any help,
Steve> getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships
If the user is an owner of the object he/she has an EXECUTE permissions
automatically.
Who is the owner of the object?
"sklett" <sklett@.mddirect.com> wrote in message
news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but
> I'm getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships should I be using to give them EXECUTE permissions to all new
> sprocs that I create?
> I'm looking over BOL to see if I can find the answer, but so far not
> coming up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>|||That's a 2000 way of thinking. The new way is to associate everything via
schemas.
Create a schema, grant your users execute permissions in the schema, create
all you new procs under that schema...easy!
"sklett" wrote:
> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but I'm
> getting EXECUTE permission errors when calling sprocs. I know how to grant
> permissions to a user on a per object basis, but what role memberships
> should I be using to give them EXECUTE permissions to all new sprocs that I
> create?
> I'm looking over BOL to see if I can find the answer, but so far not coming
> up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>
>|||oooh, uncharted territory! - scary and exciting :)
So it sounds like I need to put my tools down and read the manual. I will
do some Schema research and figure just how they work and what they do.
Thanks for the tip!
"mulhall" <mulhall@.discussions.microsoft.com> wrote in message
news:C6F5B46D-52D0-4EC2-9782-A72A53774A26@.microsoft.com...
> That's a 2000 way of thinking. The new way is to associate everything via
> schemas.
> Create a schema, grant your users execute permissions in the schema,
> create
> all you new procs under that schema...easy!
> "sklett" wrote:
>> I'm a newbie to the admin side of SqlServer. I created a new login:
>> <code>
>> CREATE LOGIN pmd_app
>> WITH PASSWORD='********'
>> </code>
>>
>> I then used the "Server Management Studio Express" to create a new user
>> in
>> my DB with the same name, then give the logical permissions, at least
>> logical to me. I can read and write table data with this new user, but
>> I'm
>> getting EXECUTE permission errors when calling sprocs. I know how to
>> grant
>> permissions to a user on a per object basis, but what role memberships
>> should I be using to give them EXECUTE permissions to all new sprocs that
>> I
>> create?
>> I'm looking over BOL to see if I can find the answer, but so far not
>> coming
>> up with anything.
>> Also, if anyone knows a good place to find an article covering SQLServer
>> security, role, permission, schemas, etc that would be awesome ;)
>> Thanks for any help,
>> Steve
>>|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uBW9KT4NGHA.1460@.TK2MSFTNGP10.phx.gbl...
>> getting EXECUTE permission errors when calling sprocs. I know how to
>> grant permissions to a user on a per object basis, but what role
>> memberships
> If the user is an owner of the object he/she has an EXECUTE permissions
> automatically.
> Who is the owner of the object?
I don't know :)
if the full name of the object is any indicator ("dbo.usp_MySprocName") I
would have to guess 'dbo' - but I could be wrong. Schemas are brand new to
me, I don't know whay they are or how they work.
Looking at the already defined schemas in my DB, I don't see any obvious
ones that would indicate EXECUTE permissions, I may need to make my own?
Sounds like schemas are my solution, I need to learn about them. Thanks for
the post!
-Steve
>
> "sklett" <sklett@.mddirect.com> wrote in message
> news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
>> I'm a newbie to the admin side of SqlServer. I created a new login:
>> <code>
>> CREATE LOGIN pmd_app
>> WITH PASSWORD='********'
>> </code>
>>
>> I then used the "Server Management Studio Express" to create a new user
>> in my DB with the same name, then give the logical permissions, at least
>> logical to me. I can read and write table data with this new user, but
>> I'm getting EXECUTE permission errors when calling sprocs. I know how to
>> grant permissions to a user on a per object basis, but what role
>> memberships should I be using to give them EXECUTE permissions to all new
>> sprocs that I create?
>> I'm looking over BOL to see if I can find the answer, but so far not
>> coming up with anything.
>> Also, if anyone knows a good place to find an article covering SQLServer
>> security, role, permission, schemas, etc that would be awesome ;)
>> Thanks for any help,
>> Steve
>

Friday, March 9, 2012

new login, EXECUTE permissions

I'm a newbie to the admin side of SqlServer. I created a new login:
<code>
CREATE LOGIN pmd_app
WITH PASSWORD='********'
</code>
I then used the "Server Management Studio Express" to create a new user in
my DB with the same name, then give the logical permissions, at least
logical to me. I can read and write table data with this new user, but I'm
getting EXECUTE permission errors when calling sprocs. I know how to grant
permissions to a user on a per object basis, but what role memberships
should I be using to give them EXECUTE permissions to all new sprocs that I
create?
I'm looking over BOL to see if I can find the answer, but so far not coming
up with anything.
Also, if anyone knows a good place to find an article covering SQLServer
security, role, permission, schemas, etc that would be awesome ;)
Thanks for any help,
Steve
> getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships
If the user is an owner of the object he/she has an EXECUTE permissions
automatically.
Who is the owner of the object?
"sklett" <sklett@.mddirect.com> wrote in message
news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but
> I'm getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships should I be using to give them EXECUTE permissions to all new
> sprocs that I create?
> I'm looking over BOL to see if I can find the answer, but so far not
> coming up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>
|||That's a 2000 way of thinking. The new way is to associate everything via
schemas.
Create a schema, grant your users execute permissions in the schema, create
all you new procs under that schema...easy!
"sklett" wrote:

> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but I'm
> getting EXECUTE permission errors when calling sprocs. I know how to grant
> permissions to a user on a per object basis, but what role memberships
> should I be using to give them EXECUTE permissions to all new sprocs that I
> create?
> I'm looking over BOL to see if I can find the answer, but so far not coming
> up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>
>
|||oooh, uncharted territory! - scary and exciting
So it sounds like I need to put my tools down and read the manual. I will
do some Schema research and figure just how they work and what they do.
Thanks for the tip!
"mulhall" <mulhall@.discussions.microsoft.com> wrote in message
news:C6F5B46D-52D0-4EC2-9782-A72A53774A26@.microsoft.com...[vbcol=seagreen]
> That's a 2000 way of thinking. The new way is to associate everything via
> schemas.
> Create a schema, grant your users execute permissions in the schema,
> create
> all you new procs under that schema...easy!
> "sklett" wrote:
|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uBW9KT4NGHA.1460@.TK2MSFTNGP10.phx.gbl...
> If the user is an owner of the object he/she has an EXECUTE permissions
> automatically.
> Who is the owner of the object?
I don't know
if the full name of the object is any indicator ("dbo.usp_MySprocName") I
would have to guess 'dbo' - but I could be wrong. Schemas are brand new to
me, I don't know whay they are or how they work.
Looking at the already defined schemas in my DB, I don't see any obvious
ones that would indicate EXECUTE permissions, I may need to make my own?
Sounds like schemas are my solution, I need to learn about them. Thanks for
the post!
-Steve

>
> "sklett" <sklett@.mddirect.com> wrote in message
> news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
>

new login, EXECUTE permissions

I'm a newbie to the admin side of SqlServer. I created a new login:
<code>
CREATE LOGIN pmd_app
WITH PASSWORD='********'
</code>
I then used the "Server Management Studio Express" to create a new user in
my DB with the same name, then give the logical permissions, at least
logical to me. I can read and write table data with this new user, but I'm
getting EXECUTE permission errors when calling sprocs. I know how to grant
permissions to a user on a per object basis, but what role memberships
should I be using to give them EXECUTE permissions to all new sprocs that I
create?
I'm looking over BOL to see if I can find the answer, but so far not coming
up with anything.
Also, if anyone knows a good place to find an article covering SQLServer
security, role, permission, schemas, etc that would be awesome ;)
Thanks for any help,
Steve> getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships
If the user is an owner of the object he/she has an EXECUTE permissions
automatically.
Who is the owner of the object?
"sklett" <sklett@.mddirect.com> wrote in message
news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but
> I'm getting EXECUTE permission errors when calling sprocs. I know how to
> grant permissions to a user on a per object basis, but what role
> memberships should I be using to give them EXECUTE permissions to all new
> sprocs that I create?
> I'm looking over BOL to see if I can find the answer, but so far not
> coming up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>|||That's a 2000 way of thinking. The new way is to associate everything via
schemas.
Create a schema, grant your users execute permissions in the schema, create
all you new procs under that schema...easy!
"sklett" wrote:

> I'm a newbie to the admin side of SqlServer. I created a new login:
> <code>
> CREATE LOGIN pmd_app
> WITH PASSWORD='********'
> </code>
>
> I then used the "Server Management Studio Express" to create a new user in
> my DB with the same name, then give the logical permissions, at least
> logical to me. I can read and write table data with this new user, but I'
m
> getting EXECUTE permission errors when calling sprocs. I know how to gran
t
> permissions to a user on a per object basis, but what role memberships
> should I be using to give them EXECUTE permissions to all new sprocs that
I
> create?
> I'm looking over BOL to see if I can find the answer, but so far not comin
g
> up with anything.
> Also, if anyone knows a good place to find an article covering SQLServer
> security, role, permission, schemas, etc that would be awesome ;)
> Thanks for any help,
> Steve
>
>|||oooh, uncharted territory! - scary and exciting
So it sounds like I need to put my tools down and read the manual. I will
do some Schema research and figure just how they work and what they do.
Thanks for the tip!
"mulhall" <mulhall@.discussions.microsoft.com> wrote in message
news:C6F5B46D-52D0-4EC2-9782-A72A53774A26@.microsoft.com...[vbcol=seagreen]
> That's a 2000 way of thinking. The new way is to associate everything via
> schemas.
> Create a schema, grant your users execute permissions in the schema,
> create
> all you new procs under that schema...easy!
> "sklett" wrote:
>|||"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uBW9KT4NGHA.1460@.TK2MSFTNGP10.phx.gbl...
> If the user is an owner of the object he/she has an EXECUTE permissions
> automatically.
> Who is the owner of the object?
I don't know
if the full name of the object is any indicator ("dbo.usp_MySprocName") I
would have to guess 'dbo' - but I could be wrong. Schemas are brand new to
me, I don't know whay they are or how they work.
Looking at the already defined schemas in my DB, I don't see any obvious
ones that would indicate EXECUTE permissions, I may need to make my own?
Sounds like schemas are my solution, I need to learn about them. Thanks for
the post!
-Steve

>
> "sklett" <sklett@.mddirect.com> wrote in message
> news:ePmSgM1NGHA.3732@.TK2MSFTNGP10.phx.gbl...
>

New Login with Trusted Connection

I have my development machine connected to my SQL 2000 server using trusted connection.

I want to setup another machine for testing purposes.

How do I setup SQL for another user? I can't get pass the Domain, when I setup a new login using trusted connection. It only shows the admin and my account on the sql server machine.

Once that is completed, how to I setup a w2k pc for trusted connection?

Thanks,
MikeD

Can you be a little more clear on what the error is that you're getting? Can you tell me exactly what steps you took to get you to where you're stuck?

Is your SQL Installation enabled for windows authentication?
Is your machine part of a domain?

|||

Greg,
Not getting an error, just could not complete the new login without a Domain.

What I ended up doing was adding a Local User Account to the server, using the same username and pwd as on the client pc.

I could then add the user login to SQL and use Windows Authentication, not SQL Server Authentication. I tried the new deployment and the win2k machine connected right up.

I don't have a domain controller. I have a small network with a server, 4 pcs, a router(broadband) and a lynksys hub that I uplink to the router.

My SQL2000 server is enabled for windows authentication. I enabled my XPpro a while back but forgot the steps. I thought it was somewhat obscure if I remember correctly.

Do you happen to have links to instructions on how to setup the different os
Thanks,
Mike

|||

Mike, I"m completely confused. What are you trying to do, create a new login using SQL Server Authentication? Not sure what an OS has to do with this.

|||Greg,

I have an application I'm developing that I'm using Windows Authentication for the SQL login instead of SQL Server Authentication.

Since I'm not using a Domain controller, I think things are a bit different.

Additionally I'm trying to setup the SQL Server for Windows Authentication.
1. Do you normally have to setup a Local User/Groups account on the server for each SQL login?. This is what I had to do to be able pick from a domain in the SQL Login setup window.

I'm trying to setup the best way to use Windows Authentication from different PC client OS's with SQL server.
2. On XPpro / home, is there anything special that has to be done?

Thanks,
Mike

New Login Question

Hello,
I have been programming with Sql Server 2000 for 2-3 years
now. But I am just now starting out with having to also
be the DBA of Sql Server 2000. My question is about
creating new Logins.
I noticed that at the bottom of the New login dialog there
are 2 dropdown boxes. One selects a database to log in to
and the other is the language. The database login
dropdown always has master listed. If I leave that alone
and then go to the Database access tab where I select what
database the new login can access I leave master in that
dialog unchecked but I check some other database. If a
user creates a connection with a tool like MS Access 2002
adp, the user can connect to master but can't access
anything because I did not check master in the Database
access tab of the New Login dialog. So my question is -
what is the significance of the database dropdown on the
first dialog of the Login dialog? If I change the
database dropdown from Master to just the desired
database, then the user cannot connect to master in
addition to not being able to access any objects in
master. But does master contain login information? If
the user is only going to be creating ODBC connections to
the desired Sql DB, does the user need to be able to
connect to master?
Thanks,
RonI see your dilemma. The answer to whether the user needs to be able to
connect to master, I don't know. But the syslogins table does exist there.
So any underlying tables that are affected by it will not show if you don't
choose it from the dropdown. I'm sure there are other system tables in maste
r
like sysobjects, sysdatabases etc that require a reference as well...
SELECT name, [password], dbname, language, sid,
'skip_encryption', loginname
FROM master..syslogins
"Ron" wrote:

> Hello,
> I have been programming with Sql Server 2000 for 2-3 years
> now. But I am just now starting out with having to also
> be the DBA of Sql Server 2000. My question is about
> creating new Logins.
> I noticed that at the bottom of the New login dialog there
> are 2 dropdown boxes. One selects a database to log in to
> and the other is the language. The database login
> dropdown always has master listed. If I leave that alone
> and then go to the Database access tab where I select what
> database the new login can access I leave master in that
> dialog unchecked but I check some other database. If a
> user creates a connection with a tool like MS Access 2002
> adp, the user can connect to master but can't access
> anything because I did not check master in the Database
> access tab of the New Login dialog. So my question is -
> what is the significance of the database dropdown on the
> first dialog of the Login dialog? If I change the
> database dropdown from Master to just the desired
> database, then the user cannot connect to master in
> addition to not being able to access any objects in
> master. But does master contain login information? If
> the user is only going to be creating ODBC connections to
> the desired Sql DB, does the user need to be able to
> connect to master?
> Thanks,
> Ron
>|||The default database option is just that, a default database to connect to
if one is not specified in the connection string/DSN. More often than not
when a user creates a DSN or a connection string they will specify a
database. All logins have access to the master database via the guest user
(a special database user account that cannot be removed from master) and do
not need to be explicitly granted access to that database. When setting up a
new login via Enterprise Manager, you simply need to select which databases
the login can access and also what permissions that user has access to with
the database.When you grant access to a database for a login, they are added
to the public role, however this role generally has no access to user
database objects (and not should it). Generally you would create a new role
in the database and grant the required permissions to that role. THen you
can simply add the user to that role. At the login level, you should be
using groups to access SQL Server so that when a new user needs access to an
existing database you can simply add them to a Windows group and not have to
touch the SQL Server at all.
HTH
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
I support PASS - the definitive, global
community for SQL Server professionals -
http://www.sqlpass.org
"Ron" <anonymous@.discussions.microsoft.com> wrote in message
news:100301c53aba$a7a56690$a501280a@.phx.gbl...
> Hello,
> I have been programming with Sql Server 2000 for 2-3 years
> now. But I am just now starting out with having to also
> be the DBA of Sql Server 2000. My question is about
> creating new Logins.
> I noticed that at the bottom of the New login dialog there
> are 2 dropdown boxes. One selects a database to log in to
> and the other is the language. The database login
> dropdown always has master listed. If I leave that alone
> and then go to the Database access tab where I select what
> database the new login can access I leave master in that
> dialog unchecked but I check some other database. If a
> user creates a connection with a tool like MS Access 2002
> adp, the user can connect to master but can't access
> anything because I did not check master in the Database
> access tab of the New Login dialog. So my question is -
> what is the significance of the database dropdown on the
> first dialog of the Login dialog? If I change the
> database dropdown from Master to just the desired
> database, then the user cannot connect to master in
> addition to not being able to access any objects in
> master. But does master contain login information? If
> the user is only going to be creating ODBC connections to
> the desired Sql DB, does the user need to be able to
> connect to master?
> Thanks,
> Ron

New login problem

Hi,

When i create a new login on my sql server 2005, i have a default database role selected. Is there a way to remove it or to modify it ?

Thanks

Zahir

Hi,

do you mean the public role ? This role cannot be removed or disabled.

Try to make the role secure an grant not that many rights to it.


HTH, Jens Suessmeyer.


http://www.sqlserver2005.de
-

New login permissions - too broad

Hi,

I created a new sql server login, but didn't assign it any permissions in any databases.

When I login with this new login, it logs into the master database, and is able to select tables from the system databases, such as master, msdb.

This seems very wrong to me. How can I turn these default permissions off for new logins? I thought it might have something to do with the guest account, but not sure how to best handle this.

Thanks

This is normal, default behavior, and it is considered a best practice to leave the behavior the way it is. If don't like it, you can always manually deny a specific user permissions to SELECT on specific tables in the master and msdb databases.

|||

Ok.

Do you have any links where I can read up more on this? I'd like to find out exactly what permissions new logins have by default in these system databases.

I know that you can't disable the guest account in master or tempdb, as they are needed there.

Thanks

|||

That is because, by default VIEW DEFINITION has been granted to public. If you want this and all subsequent logins to not be able to view metadata in the system databases, then execute the following:

REVOKE VIEW DEFINITION FROM public

GO

That will prevent them from seeing any metadata i.e. the databases will "appear" to be blank to them. They will still be able to do things like SELECT * FROM sys.databases. So, to prevent them from selecting from any of the DMVs, execute the following:

REVOKE SELECT ON DATABASE::master FROM public

new login ID issue

I migrated a SQL 2005 db from our development server to our QA server. I created a new ID for the application to use on the QA SQL server. The problem I'm facing is, I can't connect using the ID I created or even the ID that was already in the db on the test server. I did a backup of the DB on the test server, did a restore on the QA server and the ID's will not connect. I keep getting 'login failed for username'

The username is under the security tab of SQL, and I have it pointing to the DB that it will be connected to, but no success.

Any ideas on what could be causing this to fail?

Sorry, I accidently posted my reply as a new post :-(

For the existing ID, the reason is does not work is probably due to the fact it is an "orphan". Userid information in SQL exists in 2 places, the system database master, and in the application database. So, when you restored the application database, the userid does not have a corresponding entry in the master system database, so it is an orphan. Go here to read more http://support.microsoft.com/kb/274188/

The issue with the newly-created account is more likely due to something you did wrong. Here are some things to check:

1. verify the default database for the userid is correct

2. check the "user mapping" for the userid - does it have at least the public role on the database?

It should have db_datareader also, and maybe db_datawriter, depending on its intended use

3. test your odbc connection, there is a test button to verify it is working

good luck.

|||

I've done all of that.

I even backed up the db and restored it to a fresh SQL server that had no Db's or ID's on it. And I still can't connect to it. I'm only able to connect to the database on the SQL server it was created on.

|||

This does seem strange. Lets ignore the old Login for now as we'd expect that not to be able to access the new database due to the orphaned user issue mentioned previously.


Could you confirm how you created the new login/user? Is the new login enabled (check status tab in SSMS) and double check the new password :-)

If all that looks fine, would you possibly be able to script out the CREATE LOGIN statement from SSMS and also the CREATE USER statement from SSMS and post them here. Might help troubleshoot.

|||

I got it to work, but only after I added the domain username by using SQL Auth and I dont want that. I want to use my windows id and password so its like

domain\username;password

when i do that I get [username] not associated with a trusted connection.

|||

How are you trying to connect to sql server? Via SSMS or through an application? If through an app, what is your connection string?

|||

On the second part of your explanation, it seems like you are trying to use Windows credentials (domain\login;passwordWink as part of the connection string. If my assumption is correct, then it would explain the “not associated with a trusted connection” error.

Windows authentication uses the Windows credentials used to establish the connection, if you need to switch to a different set of credentials (i.e. run as a different user), you will need to impersonate the Windows user first (i.e. using runas).

For the invalid ID issue, I am also surprised that the suggestion by z-on didn’t work. We will need more information in order to help.

· What is the error message that you are getting back

· Does it fail when connecting using sqlcmd as well?

· Does it fail on connections made on the same machine?

· Assuming the user Is the a Windows principal (please correct me if I am wrong)

· Is it a domain or a local machine Windows user

o If it I s a domain user, does the new system has access to the domain

o Does the service account used for SQL Server has proper permissions on the domain

· Does it have access to the system via Windows role membership (i.e. member of sysadmin group) or directly.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

new login ID issue

I migrated a SQL 2005 db from our development server to our QA server. I created a new ID for the application to use on the QA SQL server. The problem I'm facing is, I can't connect using the ID I created or even the ID that was already in the db on the test server. I did a backup of the DB on the test server, did a restore on the QA server and the ID's will not connect. I keep getting 'login failed for username'

The username is under the security tab of SQL, and I have it pointing to the DB that it will be connected to, but no success.

Any ideas on what could be causing this to fail?

Sorry, I accidently posted my reply as a new post :-(

For the existing ID, the reason is does not work is probably due to the fact it is an "orphan". Userid information in SQL exists in 2 places, the system database master, and in the application database. So, when you restored the application database, the userid does not have a corresponding entry in the master system database, so it is an orphan. Go here to read more http://support.microsoft.com/kb/274188/

The issue with the newly-created account is more likely due to something you did wrong. Here are some things to check:

1. verify the default database for the userid is correct

2. check the "user mapping" for the userid - does it have at least the public role on the database?

It should have db_datareader also, and maybe db_datawriter, depending on its intended use

3. test your odbc connection, there is a test button to verify it is working

good luck.

|||

I've done all of that.

I even backed up the db and restored it to a fresh SQL server that had no Db's or ID's on it. And I still can't connect to it. I'm only able to connect to the database on the SQL server it was created on.

|||

This does seem strange. Lets ignore the old Login for now as we'd expect that not to be able to access the new database due to the orphaned user issue mentioned previously.


Could you confirm how you created the new login/user? Is the new login enabled (check status tab in SSMS) and double check the new password :-)

If all that looks fine, would you possibly be able to script out the CREATE LOGIN statement from SSMS and also the CREATE USER statement from SSMS and post them here. Might help troubleshoot.

|||

I got it to work, but only after I added the domain username by using SQL Auth and I dont want that. I want to use my windows id and password so its like

domain\username;password

when i do that I get [username] not associated with a trusted connection.

|||

How are you trying to connect to sql server? Via SSMS or through an application? If through an app, what is your connection string?

|||

On the second part of your explanation, it seems like you are trying to use Windows credentials (domain\login;passwordWink as part of the connection string. If my assumption is correct, then it would explain the “not associated with a trusted connection” error.

Windows authentication uses the Windows credentials used to establish the connection, if you need to switch to a different set of credentials (i.e. run as a different user), you will need to impersonate the Windows user first (i.e. using runas).

For the invalid ID issue, I am also surprised that the suggestion by z-on didn’t work. We will need more information in order to help.

· What is the error message that you are getting back

· Does it fail when connecting using sqlcmd as well?

· Does it fail on connections made on the same machine?

· Assuming the user Is the a Windows principal (please correct me if I am wrong)

· Is it a domain or a local machine Windows user

o If it I s a domain user, does the new system has access to the domain

o Does the service account used for SQL Server has proper permissions on the domain

· Does it have access to the system via Windows role membership (i.e. member of sysadmin group) or directly.

Thanks,

-Raul Garcia

SDE/T

SQL Server Engine

New login cannot retrieve data from db

Hello all. I created the "student2" user account and set the password to
"student2". I then
went to Enterprise Manager and in the class_mgr database and in its
customers table, I gave this student2 user account access to the database
and set all permissions to the table. But when I log in to SQL Server using
this new userlogin, I can access the SQL Server Query Analyzer OK but when I
run the select * from customers; query I get
http://www.jimwrichards.com/images/student2_1.gif"

.. What have I done wrong or overlooked doing right? Thanks in advance for
any help, Jim.
Jim Richards wrote:

> Hello all. I created the "student2" user account and set the password to
> "student2". I then
> went to Enterprise Manager and in the class_mgr database and in its
> customers table, I gave this student2 user account access to the database
> and set all permissions to the table. But when I log in to SQL Server using
> this new userlogin, I can access the SQL Server Query Analyzer OK but when I
> run the select * from customers; query I get
> http://www.jimwrichards.com/images/student2_1.gif"
> . What have I done wrong or overlooked doing right? Thanks in advance for
> any help, Jim.

What is the default database context for the new user? If it is not
the class_mgr database, then maybe your query is trying to access a
different table of the same name, but which isn't allowed to your user?
Joe Weinstein at BEA
|||"Jim Richards" <JWRichards@.satx.rr.com> wrote in message
news:6AXCd.483$q4.168@.fe1.texas.rr.com...
> Hello all. I created the "student2" user account and set the password to
> "student2". I then
> went to Enterprise Manager and in the class_mgr database and in its
> customers table, I gave this student2 user account access to the database
> and set all permissions to the table. But when I log in to SQL Server
> using
> this new userlogin, I can access the SQL Server Query Analyzer OK but when
> I
> run the select * from customers; query I get
> http://www.jimwrichards.com/images/student2_1.gif"
> . What have I done wrong or overlooked doing right? Thanks in advance for
> any help, Jim.

No idea, but what are the current permissions on the table? You can use
sp_helprotect to find out (see Books Online for more details):

exec sp_helprotect 'dbo.customers'

Also, did you DENY permissions on that table to student2 or a role which
student2 is in; a DENY takes precedence over a GRANT.

Simon|||Thanks Joe. I set the default database to "class_mgr" which contains the
table "customers" which contains just two rows (customers). As soon as I
access the SQL Query Analyzer using this student2 login the current database
is automatically set to "class_mgr" instead of the usual "master" database.

"Joe Weinstein" <joeNOSPAM@.bea.com> wrote in message
news:41DC46D5.5040701@.bea.com...
>
> Jim Richards wrote:
>> Hello all. I created the "student2" user account and set the password to
>> "student2". I then
>> went to Enterprise Manager and in the class_mgr database and in its
>> customers table, I gave this student2 user account access to the database
>> and set all permissions to the table. But when I log in to SQL Server
>> using
>> this new userlogin, I can access the SQL Server Query Analyzer OK but
>> when I
>> run the select * from customers; query I get
>> http://www.jimwrichards.com/images/student2_1.gif"
>>
>> . What have I done wrong or overlooked doing right? Thanks in advance for
>> any help, Jim.
> What is the default database context for the new user? If it is not
> the class_mgr database, then maybe your query is trying to access a
> different table of the same name, but which isn't allowed to your user?
> Joe Weinstein at BEA
>>
>|||Thanks Simon. I have a snapshot of the current permissions:
http://www.jimwrichards.com/images/student2_2.gif.

I did NOT deny any permissions, see snapshot:
http://www.jimwrichards.com/images/student2_3.gif.

What now, Sir? Jim.

"Simon Hayes" <sql@.hayes.ch> wrote in message
news:41dc4a08$1_1@.news.bluewin.ch...
> "Jim Richards" <JWRichards@.satx.rr.com> wrote in message
> news:6AXCd.483$q4.168@.fe1.texas.rr.com...
>> Hello all. I created the "student2" user account and set the password to
>> "student2". I then
>> went to Enterprise Manager and in the class_mgr database and in its
>> customers table, I gave this student2 user account access to the database
>> and set all permissions to the table. But when I log in to SQL Server
>> using
>> this new userlogin, I can access the SQL Server Query Analyzer OK but
>> when I
>> run the select * from customers; query I get
>> http://www.jimwrichards.com/images/student2_1.gif"
>>
>> . What have I done wrong or overlooked doing right? Thanks in advance for
>> any help, Jim.
>>
>>
> No idea, but what are the current permissions on the table? You can use
> sp_helprotect to find out (see Books Online for more details):
> exec sp_helprotect 'dbo.customers'
> Also, did you DENY permissions on that table to student2 or a role which
> student2 is in; a DENY takes precedence over a GRANT.
> Simon|||"Jim Richards" <JWRichards@.satx.rr.com> wrote in message
news:QEYCd.502$q4.238@.fe1.texas.rr.com...
> Thanks Simon. I have a snapshot of the current permissions:
> http://www.jimwrichards.com/images/student2_2.gif.
> I did NOT deny any permissions, see snapshot:
> http://www.jimwrichards.com/images/student2_3.gif.
> What now, Sir? Jim.

Good question - everything seems to be correct, unless I've missed something
somewhere. Is student2 in any roles?

exec sp_helpuser 'student2'

If student2 is in the db_denydatareader role for some reason, then that
would explain what you're seeing. If not, then I'd try dropping and
recreating the user again (and running DBCC CHECKDB wouldn't hurt either,
just in case there is some database corruption).

Simon