Pb with login name's under sql server 2000

Hello,
I am searching a way to use login names like
SQLAccessGroup{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}
in sql scripts.
Standard sp like sp-changedbowner refuses them.
Thanks for help.
CSHi CS,
As for the "SQLAccessGroup{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}" you
mentioned, do you mean the SID of a certain sqlserver or windows login name
in the SQL Server instance?
If this is the case, I think you need to translate sid into its
corresponding loginname (sql login name or windows account/group name)
first before calling the sp_changedbowner stored procedure. This is because
the "login" parameter of the sq_changedbowner SP must be an already
existing Microsoft SQL Server login or Microsoft Windows NT user(rather
than the raw SID).
#sp_changedbowner
http://msdn.microsoft.com/library/e...0s2.asp?frame=t
rue
If you will only get the SID first in your scenario, I'd suggest you
consider the following options to translate the SID to login name and pass
the login name to the sp_changedbowner:
1. use the "SUSER_SNAME" T-SQL function to translate login sid into login
name
#SUSER_SNAME (Transact-SQL)
http://msdn2.microsoft.com/en-us/library/ms174427.aspx
2. Since all the logins of a SQL server instance is stored in the
syslogins system view, you can manually query it and find the loginname
associated with the certain SID (not quite recommended )
for example:
=======================
declare @.sid nvarchar(100)
set @.sid =
suser_sname(0x0105000000000005150000005D
28F57FD53AD8354354E02A18B20200)
EXEC sp_changedbowner @.sid
=======================
In addition, the format of the SID stored in SQL Server is abit different
from the {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, you'll need to do some
modification before passing them into the certain translate function.
Hope this helps.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.|||In fact, it is MS CRM that has created this login on its installation, and
our dba& complains that it is a non generic way to name login.
Whe have discovered thta it is normal that changedbowner fails because this
lotgin is an ad group and not an AD user.
Thanks anyway.CS
"Steven Cheng[MSFT]" <stcheng@.online.microsoft.com> a crit dans le mess
age
de news: k56sX1CvGHA.5976@.TK2MSFTNGXA01.phx.gbl...
> Hi CS,
> As for the "SQLAccessGroup{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}" you
> mentioned, do you mean the SID of a certain sqlserver or windows login
> name
> in the SQL Server instance?
> If this is the case, I think you need to translate sid into its
> corresponding loginname (sql login name or windows account/group name)
> first before calling the sp_changedbowner stored procedure. This is
> because
> the "login" parameter of the sq_changedbowner SP must be an already
> existing Microsoft SQL Server login or Microsoft Windows NT user(rather
> than the raw SID).
> #sp_changedbowner
> [url]http://msdn.microsoft.com/library/en-us/tsqlref/ts_sp_ca-cz_30s2.asp?frame=t[/ur
l]
> rue
> If you will only get the SID first in your scenario, I'd suggest you
> consider the following options to translate the SID to login name and pass
> the login name to the sp_changedbowner:
> 1. use the "SUSER_SNAME" T-SQL function to translate login sid into login
> name
> #SUSER_SNAME (Transact-SQL)
> http://msdn2.microsoft.com/en-us/library/ms174427.aspx
> 2. Since all the logins of a SQL server instance is stored in the
> syslogins system view, you can manually query it and find the loginname
> associated with the certain SID (not quite recommended )
>
> for example:
> =======================
> declare @.sid nvarchar(100)
> set @.sid =
> suser_sname(0x0105000000000005150000005D
28F57FD53AD8354354E02A18B20200)
> EXEC sp_changedbowner @.sid
> =======================
> In addition, the format of the SID stored in SQL Server is abit different
> from the {xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx}, you'll need to do so
me
> modification before passing them into the certain translate function.
> Hope this helps.
> Sincerely,
> Steven Cheng
> Microsoft MSDN Online Support Lead
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>|||Hi Cs,
Thanks for the followup and let me know how everything is going on.
Sincerely,
Steven Cheng
Microsoft MSDN Online Support Lead
This posting is provided "AS IS" with no warranties, and confers no rights.

Patch SP4 hanging

SP4 installation hangs. I used windows login to do the patch, a message
saying that it is not a valid user. I selected "retry" then used "sa". It
started hanging when "...MDAC" message disappeared.
I checked c:\winnt\sqlsp.log file. It is different from the files on the
other normal patched servers.
The last 2 lines in the file are:
End: Installpkgs(ID_INSTALLMDAC)
**** Starting open OP in write mode ****
What is the cause? How to fix it?
Hi Julia
You may want to try using the MDAC component checker to see if you have a
consistent installation of MDAC and possibly loading MDAC MDAC 2.8 SP1 if on
Windows 2000 or MDAC 2.8 SP2 if on XP/Windows 2003 before installing the
service pack.
http://www.microsoft.com/downloads/r...splayLang= en
John
"Julia" <Julia@.discussions.microsoft.com> wrote in message
news:686DFD79-5223-4A80-BF1B-99469046BF5D@.microsoft.com...
> SP4 installation hangs. I used windows login to do the patch, a message
> saying that it is not a valid user. I selected "retry" then used "sa".
> It
> started hanging when "...MDAC" message disappeared.
> I checked c:\winnt\sqlsp.log file. It is different from the files on the
> other normal patched servers.
> The last 2 lines in the file are:
> End: Installpkgs(ID_INSTALLMDAC)
> **** Starting open OP in write mode ****
> What is the cause? How to fix it?

Patch SP4 hanging

SP4 installation hangs. I used windows login to do the patch, a message
saying that it is not a valid user. I selected "retry" then used "sa". It
started hanging when "...MDAC" message disappeared.
I checked c:\winnt\sqlsp.log file. It is different from the files on the
other normal patched servers.
The last 2 lines in the file are:
End: Installpkgs(ID_INSTALLMDAC)
**** Starting open OP in write mode ****
What is the cause? How to fix it?Hi Julia
You may want to try using the MDAC component checker to see if you have a
consistent installation of MDAC and possibly loading MDAC MDAC 2.8 SP1 if on
Windows 2000 or MDAC 2.8 SP2 if on XP/Windows 2003 before installing the
service pack.
http://www.microsoft.com/downloads/results.aspx?productID=&freetext=mdac&DisplayLang=en
John
"Julia" <Julia@.discussions.microsoft.com> wrote in message
news:686DFD79-5223-4A80-BF1B-99469046BF5D@.microsoft.com...
> SP4 installation hangs. I used windows login to do the patch, a message
> saying that it is not a valid user. I selected "retry" then used "sa".
> It
> started hanging when "...MDAC" message disappeared.
> I checked c:\winnt\sqlsp.log file. It is different from the files on the
> other normal patched servers.
> The last 2 lines in the file are:
> End: Installpkgs(ID_INSTALLMDAC)
> **** Starting open OP in write mode ****
> What is the cause? How to fix it?

Patch SP4 hanging

SP4 installation hangs. I used windows login to do the patch, a message
saying that it is not a valid user. I selected "retry" then used "sa". It
started hanging when "...MDAC" message disappeared.
I checked c:\winnt\sqlsp.log file. It is different from the files on the
other normal patched servers.
The last 2 lines in the file are:
End: Installpkgs(ID_INSTALLMDAC)
**** Starting open OP in write mode ****
What is the cause? How to fix it?Hi Julia
You may want to try using the MDAC component checker to see if you have a
consistent installation of MDAC and possibly loading MDAC MDAC 2.8 SP1 if on
Windows 2000 or MDAC 2.8 SP2 if on XP/Windows 2003 before installing the
service pack.
http://www.microsoft.com/downloads/...La
ng=en
John
"Julia" <Julia@.discussions.microsoft.com> wrote in message
news:686DFD79-5223-4A80-BF1B-99469046BF5D@.microsoft.com...
> SP4 installation hangs. I used windows login to do the patch, a message
> saying that it is not a valid user. I selected "retry" then used "sa".
> It
> started hanging when "...MDAC" message disappeared.
> I checked c:\winnt\sqlsp.log file. It is different from the files on the
> other normal patched servers.
> The last 2 lines in the file are:
> End: Installpkgs(ID_INSTALLMDAC)
> **** Starting open OP in write mode ****
> What is the cause? How to fix it?

passwrd

Hi
i am new in mssql7.Using sp_password i put login password
for the server.How can i put a password for a particular
database in the server.
Thank you.
Passwords & Logins are specific to Servers. Databases simply have users. So,
there is no such thing as passwords for database users.
Anith

Passwords not case sensitive?

I have a server that uses specific login/passwords. And through random
testing i noticed that the passwords are not case sensitive. Can this be
changed so that the passwords ARE case sensitive?
thanks,
BenHi,
For a Case insensitive sort order/carecter set it is not possible. If you
have a Case sensitive sortorder/char set then automatically
passwords will be case sensitive.
Thanks
Hari
SQL Server MVP
"Ben" <ben_1_ AT hotmail DOT com> wrote in message
news:0E632896-37E7-4EA0-8022-5AC2D4230F84@.microsoft.com...
>I have a server that uses specific login/passwords. And through random
> testing i noticed that the passwords are not case sensitive. Can this be
> changed so that the passwords ARE case sensitive?
> thanks,
> Ben|||SQL Server 2000 maintains two versions of each login password. One is the
actual password supplied by the user, and the other is the password
converted by to all uppercase letters. This enables case-insensitive
validation of passwords (for case insensitive collations). Although this
behavior is convenient for many users, it makes password-guessing attacks
easier by reducing the number of possible passwords
In SQL 2005 only the actual password is stored. A password entered by a user
must match the password stored in the server (regardless of collation,
however the username can still be in a different case). If a password does
not match the password stored in SQL Server, the login fails. If the precise
case of the password characters is forgotten, the password must be reset.
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
"Ben" <ben_1_ AT hotmail DOT com> wrote in message
news:0E632896-37E7-4EA0-8022-5AC2D4230F84@.microsoft.com...
>I have a server that uses specific login/passwords. And through random
> testing i noticed that the passwords are not case sensitive. Can this be
> changed so that the passwords ARE case sensitive?
> thanks,
> Ben|||Hi,
Actually it because of *Collation setting* look for your collation and
change it accordingly to case sensitive from case insensitive .
Regards
--
Andy Davis
Activecrypt Team
---
SQL Server Encryption Software
http://www.activecrypt.com
"Ben" wrote:

> I have a server that uses specific login/passwords. And through random
> testing i noticed that the passwords are not case sensitive. Can this be
> changed so that the passwords ARE case sensitive?
> thanks,
> Ben

Password's case sensitivity

Hi,
somehow my Sql Server's passwors are not case sensitive. I thought sql
server's login passwords are case sensitive.
Am I worng?
How do I change my SQL Server back to the case sensitive passwords?
Please help..
Thank you
SamHi
Passwords case sensitivity is based on the collation of the installation. If
you install with a non-case sensitive collation, the password will not be
cases sensitive.
Regards
Mike
"sam" wrote:

> Hi,
> somehow my Sql Server's passwors are not case sensitive. I thought sql
> server's login passwords are case sensitive.
> Am I worng?
> How do I change my SQL Server back to the case sensitive passwords?
> Please help..
> Thank you
> Sam|||Password case-sensitivity is determined by the default collation for the SQL
Server instance. It appears you have a case-insensitive collation.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:BDB6FA4B-D047-438F-A850-0E3FD0A8F49B@.microsoft.com...
> Hi,
> somehow my Sql Server's passwors are not case sensitive. I thought sql
> server's login passwords are case sensitive.
> Am I worng?
> How do I change my SQL Server back to the case sensitive passwords?
> Please help..
> Thank you
> Sam|||Thank you for your response. I think the Earlier I used all the SQL servers
which are upgraded from 7.0 to 2K and so the defautl collation of 7.0 was a
case sensitive. (Not usre right now).
But if I want to keep all my client data and other code to be case
-insensitive but all my login passwords to be case sensitive , can I do that
?
How can I do that?
Please let me know..
Thank you again..
Sam
"Dan Guzman" wrote:

> Password case-sensitivity is determined by the default collation for the S
QL
> Server instance. It appears you have a case-insensitive collation.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:BDB6FA4B-D047-438F-A850-0E3FD0A8F49B@.microsoft.com...
>
>|||To change the instance default collation after installation, you'll need to
either reinstall or rebuild the master database. This will create new
master, msdb and model databases.
Although you can run with mixed collations, this can lead to problems. The
tempdb collation will be the instance default so you might get errors due to
collation conflicts when using temp tables.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:96622B87-A747-4E23-8593-27221C2C10BD@.microsoft.com...[vbcol=seagreen]
> Thank you for your response. I think the Earlier I used all the SQL
> servers
> which are upgraded from 7.0 to 2K and so the defautl collation of 7.0 was
> a
> case sensitive. (Not usre right now).
> But if I want to keep all my client data and other code to be case
> -insensitive but all my login passwords to be case sensitive , can I do
> that?
> How can I do that?
> Please let me know..
> Thank you again..
> Sam
> "Dan Guzman" wrote:
>|||Thanks Dan,
But I think I did not put my question clearly. My Apologies.
I want to keep the collation of all the DBs on the server same as what I
have at present (case in-sensitive) but only all my login passwords should b
e
case sensitive.
Can I do that?
How?
Thank you
Sam
"Dan Guzman" wrote:

> To change the instance default collation after installation, you'll need t
o
> either reinstall or rebuild the master database. This will create new
> master, msdb and model databases.
> Although you can run with mixed collations, this can lead to problems. Th
e
> tempdb collation will be the instance default so you might get errors due
to
> collation conflicts when using temp tables.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:96622B87-A747-4E23-8593-27221C2C10BD@.microsoft.com...
>
>|||Running mixed collations is the only way to have case-sensitive passwords
and case-insensitive user database collations. The default collation of
your existing databases will not be changed after you reattach following a
master database rebuild or SQL Server reinstall.
However, as I mentioned in my previous response, mixed collations will have
other consequences. If you feel compelled to try this, be sure to
thoroughly test your applications before implementing this in production.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:B4EB814F-DCAD-4AF1-AB66-11C821BFD09D@.microsoft.com...[vbcol=seagreen]
> Thanks Dan,
> But I think I did not put my question clearly. My Apologies.
> I want to keep the collation of all the DBs on the server same as what I
> have at present (case in-sensitive) but only all my login passwords should
> be
> case sensitive.
> Can I do that?
> How?
> Thank you
> Sam
> "Dan Guzman" wrote:
>|||I understand your concern and thank you for your response.
Bu insterad of rebuilding my master database, Can I change the collation of
the password column of the sysxlogin table?
This is just a guess. I think you must have thought of this but I still want
to ask you this question.
"Dan Guzman" wrote:

> Running mixed collations is the only way to have case-sensitive passwords
> and case-insensitive user database collations. The default collation of
> your existing databases will not be changed after you reattach following a
> master database rebuild or SQL Server reinstall.
> However, as I mentioned in my previous response, mixed collations will hav
e
> other consequences. If you feel compelled to try this, be sure to
> thoroughly test your applications before implementing this in production.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:B4EB814F-DCAD-4AF1-AB66-11C821BFD09D@.microsoft.com...
>
>|||> Bu insterad of rebuilding my master database, Can I change the collation
> of
> the password column of the sysxlogin table?
Changing system table schema is not supported so you would this is at your
own risk. The supported method is a mixed collation environment with a
case-sensitive instance default collation and case-insensitive collation for
user databases. Of course, mixed collation caveats apply.
Hope this helps.
Dan Guzman
SQL Server MVP
"sam" <sam@.discussions.microsoft.com> wrote in message
news:D516F2B3-79BF-414E-B005-88AB683F5DD5@.microsoft.com...[vbcol=seagreen]
>I understand your concern and thank you for your response.
> Bu insterad of rebuilding my master database, Can I change the collation
> of
> the password column of the sysxlogin table?
> This is just a guess. I think you must have thought of this but I still
> want
> to ask you this question.
> "Dan Guzman" wrote:
>|||Thank you Dan,
I will try this in the development environment and then see how it works
before changing the collation for any thing else.
Thank you once again for your time and response.
Sam
"Dan Guzman" wrote:

> Changing system table schema is not supported so you would this is at your
> own risk. The supported method is a mixed collation environment with a
> case-sensitive instance default collation and case-insensitive collation f
or
> user databases. Of course, mixed collation caveats apply.
> --
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "sam" <sam@.discussions.microsoft.com> wrote in message
> news:D516F2B3-79BF-414E-B005-88AB683F5DD5@.microsoft.com...
>
>

password storage

hai all!
i am going to store my user details to login from vb.net in a user table in sql.i would like to disguise the password column with dots or stars.how do i do that?kindly help.its urgent.i also need to compare the password right.so it should be readable by the program

Quote:

Originally Posted by pangsans

hai all!
i am going to store my user details to login from vb.net in a user table in sql.i would like to disguise the password column with dots or stars.how do i do that?kindly help.its urgent.i also need to compare the password right.so it should be readable by the program

i doubt if you can revert back to the original string from "dots or stars", what you could is to use an encrypting function...you may create your own or find one on the net|||

Quote:

Originally Posted by ck9663

i doubt if you can revert back to the original string from "dots or stars", what you could is to use an encrypting function...you may create your own or find one on the net

thanks yaar
give me some more info yaar|||That would depend on how you want to encrypt it. one way or 2 way?
and syntax will differ from language to language :)
cheers

password sql 2005

I am creating an db login called test to test some sripts. When I try to set
that password it says password validation failed. The password does not meet
windows policy requirenments because it is too short.
In sql 2005 is the password policy based on your windwows policy?
stoney wrote:
> I am creating an db login called test to test some sripts. When I try to set
> that password it says password validation failed. The password does not meet
> windows policy requirenments because it is too short.
> In sql 2005 is the password policy based on your windwows policy?
>
It can be, but doesn't HAVE to be. Study the options that are available
when you create a new login.
Tracy McKibben
MCDBA
http://www.realsqlguy.com
|||I think that this is the behvior if the OS is windows 2003. In any
case you can use the option CHECK_POLICY = OFF when you create the
login. Here is an example:
CREATE LOGIN MyLogin WITH PASSWORD = 'MyPass', CHECK_POLICY = OFF
Adi
stoney wrote:
> I am creating an db login called test to test some sripts. When I try to set
> that password it says password validation failed. The password does not meet
> windows policy requirenments because it is too short.
> In sql 2005 is the password policy based on your windwows policy?

password sql 2005

I am creating an db login called test to test some sripts. When I try to se
t
that password it says password validation failed. The password does not mee
t
windows policy requirenments because it is too short.
In sql 2005 is the password policy based on your windwows policy?stoney wrote:
> I am creating an db login called test to test some sripts. When I try to
set
> that password it says password validation failed. The password does not m
eet
> windows policy requirenments because it is too short.
> In sql 2005 is the password policy based on your windwows policy?
>
It can be, but doesn't HAVE to be. Study the options that are available
when you create a new login.
Tracy McKibben
MCDBA
http://www.realsqlguy.com|||I think that this is the behvior if the OS is windows 2003. In any
case you can use the option CHECK_POLICY = OFF when you create the
login. Here is an example:
CREATE LOGIN MyLogin WITH PASSWORD = 'MyPass', CHECK_POLICY = OFF
Adi
stoney wrote:
> I am creating an db login called test to test some sripts. When I try to
set
> that password it says password validation failed. The password does not m
eet
> windows policy requirenments because it is too short.
> In sql 2005 is the password policy based on your windwows policy?

Password question

Morning,
Yesterday I got a call from a developer, telling me that the MSSQL Login
(for a application) that I set up for him on ServerA was not letting him
login. This exact same MSSQL Login was also set up on ServerB and it works
fine. After, a bit of time, of looking into it I stumbled on the problem and
fix. The fix was the password length for the SQL Server login account.
According to BOL, the password can be from 1 to 128 & alpha-numeric. The
password was a 19 alpha-numeric character password. This worked with no
problems on ServerB but failed on ServerA.
ServerB is a Windows 2000 server while ServerA is NT4 SP6.
So, I'm thinking that even though this was a MSSQL login and not a OS login,
the OS layer is playing a role in the authentication process. Does anyone
know if this is so and what are the limitations of NT4 password length?
Thanks for you time,I forgot to add, both are SQL2000 SP3.
"JoeyDBA" <JoeyDBA@.yahoo.com> wrote in message
news:uQErEJmbEHA.716@.TK2MSFTNGP11.phx.gbl...
> Morning,
> Yesterday I got a call from a developer, telling me that the MSSQL Login
> (for a application) that I set up for him on ServerA was not letting him
> login. This exact same MSSQL Login was also set up on ServerB and it works
> fine. After, a bit of time, of looking into it I stumbled on the problem
and
> fix. The fix was the password length for the SQL Server login account.
> According to BOL, the password can be from 1 to 128 & alpha-numeric. The
> password was a 19 alpha-numeric character password. This worked with no
> problems on ServerB but failed on ServerA.
> ServerB is a Windows 2000 server while ServerA is NT4 SP6.
> So, I'm thinking that even though this was a MSSQL login and not a OS
login,
> the OS layer is playing a role in the authentication process. Does anyone
> know if this is so and what are the limitations of NT4 password length?
> Thanks for you time,
>|||If it's a SQL login account we don't interact with the OS.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||As Kevin already pointed out, a SQL Login doesn't interact
with the OS.
One possibility, If the server uses a case-sensitive
collation, then your passwords are case sensitive as well.
-Sue
On Tue, 20 Jul 2004 09:02:59 -0500, "JoeyDBA"
<JoeyDBA@.yahoo.com> wrote:

>Morning,
>Yesterday I got a call from a developer, telling me that the MSSQL Login
>(for a application) that I set up for him on ServerA was not letting him
>login. This exact same MSSQL Login was also set up on ServerB and it works
>fine. After, a bit of time, of looking into it I stumbled on the problem an
d
>fix. The fix was the password length for the SQL Server login account.
>According to BOL, the password can be from 1 to 128 & alpha-numeric. The
>password was a 19 alpha-numeric character password. This worked with no
>problems on ServerB but failed on ServerA.
>ServerB is a Windows 2000 server while ServerA is NT4 SP6.
>So, I'm thinking that even though this was a MSSQL login and not a OS login
,
>the OS layer is playing a role in the authentication process. Does anyone
>know if this is so and what are the limitations of NT4 password length?
>Thanks for you time,
>|||ok - thanks for the feed back. I'll go back and play with it again.
"Kevin McDonnell [MSFT]" <kevmc@.online.microsoft.com> wrote in message
news:8SC7MkobEHA.2924@.cpmsftngxa06.phx.gbl...
> If it's a SQL login account we don't interact with the OS.
> Thanks,
> Kevin McDonnell
> Microsoft Corporation
> This posting is provided AS IS with no warranties, and confers no rights.
>
>

Password problem

Hi to all.

I'm trying to add a new login to SQL Server Express, using SQL Management Studio...

I create the user, select "SQL Server authentication", and type the password, wich is strong enough. I click OK, and, for now, everything's fine. The problem arises when I access that login's properties: the password is different (it has different length), so I can't login with that account.

Any help would be greatly appreciated...

Thanks,

Alberto.

Hi,

the length of the password doesn′t have to do anything with the password itself, even if you put in a blank password (if this is made possible) you will get a bunch of stars / points presented there. That is just a hint that in there is a secret (password) stored in there.

HTH, jens Suessmeyer.

http://www.sqlserver2005.de
|||

mmhh...it seems reasonable (with the help of some kind of weird logic)...thanks a lot!

password issue assigning role to login

i am running into a strange thing...at least to me
in enterprise mgr-security-logins
i double click the user, go to the server roles tab and then check the role
i want to add to that user
when i click okay, it prompts me for a confirmation password..that seems odd
to me
i am not certain what password its looking for so i have
entered my AD password, and the SA password, and this logins
password..doesn't matter everytime it tells me the password is incorrect
anyone know what is going on?I am running into a strange thing...at least to
me
in enterprise mgr-security-logins
I double click the user, go to the server roles tab and then check the role
I want to add to that user
when I click okay, it prompts me for a confirmation password..that seems odd
to me
I am not certain what password its looking for so I have
entered my AD password, and the SA password, and this logins
password..doesn't matter every time it tells me the password is incorrect
anyone know what is going on?What version of SQL server and service pack you are running?
--
Thanks & Rate the Postings.
-Ravi-
"jason" wrote:
> i am running into a strange thing...at least to me
> in enterprise mgr-security-logins
> i double click the user, go to the server roles tab and then check the role
> i want to add to that user
> when i click okay, it prompts me for a confirmation password..that seems odd
> to me
> i am not certain what password its looking for so i have
> entered my AD password, and the SA password, and this logins
> password..doesn't matter everytime it tells me the password is incorrect
> anyone know what is going on?I am running into a strange thing...at least to
> me
> in enterprise mgr-security-logins
> I double click the user, go to the server roles tab and then check the role
> I want to add to that user
> when I click okay, it prompts me for a confirmation password..that seems odd
> to me
> I am not certain what password its looking for so I have
> entered my AD password, and the SA password, and this logins
> password..doesn't matter every time it tells me the password is incorrect
> anyone know what is going on?|||2000
sp3a
ms03031
on a cluster
"Ravi" wrote:
> What version of SQL server and service pack you are running?
> --
> Thanks & Rate the Postings.
> -Ravi-
>
> "jason" wrote:
> > i am running into a strange thing...at least to me
> >
> > in enterprise mgr-security-logins
> > i double click the user, go to the server roles tab and then check the role
> > i want to add to that user
> >
> > when i click okay, it prompts me for a confirmation password..that seems odd
> > to me
> > i am not certain what password its looking for so i have
> > entered my AD password, and the SA password, and this logins
> > password..doesn't matter everytime it tells me the password is incorrect
> >
> > anyone know what is going on?I am running into a strange thing...at least to
> > me
> >
> > in enterprise mgr-security-logins
> > I double click the user, go to the server roles tab and then check the role
> > I want to add to that user
> >
> > when I click okay, it prompts me for a confirmation password..that seems odd
> > to me
> > I am not certain what password its looking for so I have
> > entered my AD password, and the SA password, and this logins
> > password..doesn't matter every time it tells me the password is incorrect
> >
> > anyone know what is going on?|||This is becuase of the security patch MS03-031 you installed on the server.
Every time you change the property of the login account you have to enter the
password (Password of the login account) and confirm the password.
Workaroung to avoid this is, use the system stored procedures to modify the
login accounts
E.g
use the stored procedure sp_addsrvrolemember to add a login to the server
role.
Thanks & Rate the Postings.
-Ravi-
"jason" wrote:
> 2000
> sp3a
> ms03031
> on a cluster
> "Ravi" wrote:
> > What version of SQL server and service pack you are running?
> > --
> > Thanks & Rate the Postings.
> > -Ravi-
> >
> >
> > "jason" wrote:
> >
> > > i am running into a strange thing...at least to me
> > >
> > > in enterprise mgr-security-logins
> > > i double click the user, go to the server roles tab and then check the role
> > > i want to add to that user
> > >
> > > when i click okay, it prompts me for a confirmation password..that seems odd
> > > to me
> > > i am not certain what password its looking for so i have
> > > entered my AD password, and the SA password, and this logins
> > > password..doesn't matter everytime it tells me the password is incorrect
> > >
> > > anyone know what is going on?I am running into a strange thing...at least to
> > > me
> > >
> > > in enterprise mgr-security-logins
> > > I double click the user, go to the server roles tab and then check the role
> > > I want to add to that user
> > >
> > > when I click okay, it prompts me for a confirmation password..that seems odd
> > > to me
> > > I am not certain what password its looking for so I have
> > > entered my AD password, and the SA password, and this logins
> > > password..doesn't matter every time it tells me the password is incorrect
> > >
> > > anyone know what is going on?|||i entered that password and it still didn't do it
and i doubled checked that i was entering it correctly
is this something that was fixed with sp4?
"Ravi" wrote:
> This is becuase of the security patch MS03-031 you installed on the server.
> Every time you change the property of the login account you have to enter the
> password (Password of the login account) and confirm the password.
> Workaroung to avoid this is, use the system stored procedures to modify the
> login accounts
> E.g
> use the stored procedure sp_addsrvrolemember to add a login to the server
> role.
>
> --
> Thanks & Rate the Postings.
> -Ravi-
>
> "jason" wrote:
> > 2000
> > sp3a
> > ms03031
> >
> > on a cluster
> >
> > "Ravi" wrote:
> >
> > > What version of SQL server and service pack you are running?
> > > --
> > > Thanks & Rate the Postings.
> > > -Ravi-
> > >
> > >
> > > "jason" wrote:
> > >
> > > > i am running into a strange thing...at least to me
> > > >
> > > > in enterprise mgr-security-logins
> > > > i double click the user, go to the server roles tab and then check the role
> > > > i want to add to that user
> > > >
> > > > when i click okay, it prompts me for a confirmation password..that seems odd
> > > > to me
> > > > i am not certain what password its looking for so i have
> > > > entered my AD password, and the SA password, and this logins
> > > > password..doesn't matter everytime it tells me the password is incorrect
> > > >
> > > > anyone know what is going on?I am running into a strange thing...at least to
> > > > me
> > > >
> > > > in enterprise mgr-security-logins
> > > > I double click the user, go to the server roles tab and then check the role
> > > > I want to add to that user
> > > >
> > > > when I click okay, it prompts me for a confirmation password..that seems odd
> > > > to me
> > > > I am not certain what password its looking for so I have
> > > > entered my AD password, and the SA password, and this logins
> > > > password..doesn't matter every time it tells me the password is incorrect
> > > >
> > > > anyone know what is going on?|||Did you enter the password in the first tab?
--
Thanks & Rate the Postings.
-Ravi-
"jason" wrote:
> i entered that password and it still didn't do it
> and i doubled checked that i was entering it correctly
> is this something that was fixed with sp4?
> "Ravi" wrote:
> > This is becuase of the security patch MS03-031 you installed on the server.
> > Every time you change the property of the login account you have to enter the
> > password (Password of the login account) and confirm the password.
> >
> > Workaroung to avoid this is, use the system stored procedures to modify the
> > login accounts
> > E.g
> > use the stored procedure sp_addsrvrolemember to add a login to the server
> > role.
> >
> >
> > --
> > Thanks & Rate the Postings.
> > -Ravi-
> >
> >
> > "jason" wrote:
> >
> > > 2000
> > > sp3a
> > > ms03031
> > >
> > > on a cluster
> > >
> > > "Ravi" wrote:
> > >
> > > > What version of SQL server and service pack you are running?
> > > > --
> > > > Thanks & Rate the Postings.
> > > > -Ravi-
> > > >
> > > >
> > > > "jason" wrote:
> > > >
> > > > > i am running into a strange thing...at least to me
> > > > >
> > > > > in enterprise mgr-security-logins
> > > > > i double click the user, go to the server roles tab and then check the role
> > > > > i want to add to that user
> > > > >
> > > > > when i click okay, it prompts me for a confirmation password..that seems odd
> > > > > to me
> > > > > i am not certain what password its looking for so i have
> > > > > entered my AD password, and the SA password, and this logins
> > > > > password..doesn't matter everytime it tells me the password is incorrect
> > > > >
> > > > > anyone know what is going on?I am running into a strange thing...at least to
> > > > > me
> > > > >
> > > > > in enterprise mgr-security-logins
> > > > > I double click the user, go to the server roles tab and then check the role
> > > > > I want to add to that user
> > > > >
> > > > > when I click okay, it prompts me for a confirmation password..that seems odd
> > > > > to me
> > > > > I am not certain what password its looking for so I have
> > > > > entered my AD password, and the SA password, and this logins
> > > > > password..doesn't matter every time it tells me the password is incorrect
> > > > >
> > > > > anyone know what is going on?|||that "fixed" it with my test account where i knew the password
but i am not going to know peoples password when i add some security to
their login
i guess i will have to use the workaround till this bug is fixed.
thanks for bringing some clarity to this issue
"Ravi" wrote:
> Did you enter the password in the first tab?
> --
> Thanks & Rate the Postings.
> -Ravi-
>
> "jason" wrote:
> > i entered that password and it still didn't do it
> > and i doubled checked that i was entering it correctly
> >
> > is this something that was fixed with sp4?
> >
> > "Ravi" wrote:
> >
> > > This is becuase of the security patch MS03-031 you installed on the server.
> > > Every time you change the property of the login account you have to enter the
> > > password (Password of the login account) and confirm the password.
> > >
> > > Workaroung to avoid this is, use the system stored procedures to modify the
> > > login accounts
> > > E.g
> > > use the stored procedure sp_addsrvrolemember to add a login to the server
> > > role.
> > >
> > >
> > > --
> > > Thanks & Rate the Postings.
> > > -Ravi-
> > >
> > >
> > > "jason" wrote:
> > >
> > > > 2000
> > > > sp3a
> > > > ms03031
> > > >
> > > > on a cluster
> > > >
> > > > "Ravi" wrote:
> > > >
> > > > > What version of SQL server and service pack you are running?
> > > > > --
> > > > > Thanks & Rate the Postings.
> > > > > -Ravi-
> > > > >
> > > > >
> > > > > "jason" wrote:
> > > > >
> > > > > > i am running into a strange thing...at least to me
> > > > > >
> > > > > > in enterprise mgr-security-logins
> > > > > > i double click the user, go to the server roles tab and then check the role
> > > > > > i want to add to that user
> > > > > >
> > > > > > when i click okay, it prompts me for a confirmation password..that seems odd
> > > > > > to me
> > > > > > i am not certain what password its looking for so i have
> > > > > > entered my AD password, and the SA password, and this logins
> > > > > > password..doesn't matter everytime it tells me the password is incorrect
> > > > > >
> > > > > > anyone know what is going on?I am running into a strange thing...at least to
> > > > > > me
> > > > > >
> > > > > > in enterprise mgr-security-logins
> > > > > > I double click the user, go to the server roles tab and then check the role
> > > > > > I want to add to that user
> > > > > >
> > > > > > when I click okay, it prompts me for a confirmation password..that seems odd
> > > > > > to me
> > > > > > I am not certain what password its looking for so I have
> > > > > > entered my AD password, and the SA password, and this logins
> > > > > > password..doesn't matter every time it tells me the password is incorrect
> > > > > >
> > > > > > anyone know what is going on?