Moving SQL Auth Logins from SQL 2000 to SQL 2005

I have been able to transfer over the majority of SQL Authenticated logins
from my SQL 2000 servers to SQL 2005 servers using the sp 'sp_help_revlogin'
as described in the Microsoft article ID: 246133. However several of the
logins fail to be created with the following error:
Invalid value given for parameter PASSWORD. Specify a valid parameter value.
and on each of these login creations the password value is the same:
CONVERT (varbinary(256),
0x09003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F00)
The same logins with same password values work fine for creating logins on
SQL 2000 but fail on 2005.
Does anyone know what is going on with this certain password value?
Thanx for any help on this......
--
Jeff Carrington
Mgr. IT Operations
NPD GroupHi Jeff
"Jeff Carrington" <JeffCarrington@.discussions.microsoft.com> wrote in
message news:95D56897-BF78-4D67-B448-18F991F050C1@.microsoft.com...
>I have been able to transfer over the majority of SQL Authenticated logins
> from my SQL 2000 servers to SQL 2005 servers using the sp
> 'sp_help_revlogin'
> as described in the Microsoft article ID: 246133. However several of the
> logins fail to be created with the following error:
> Invalid value given for parameter PASSWORD. Specify a valid parameter
> value.
> and on each of these login creations the password value is the same:
> CONVERT (varbinary(256),
> 0x09003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F00)
> The same logins with same password values work fine for creating logins on
> SQL 2000 but fail on 2005.
> Does anyone know what is going on with this certain password value?
> Thanx for any help on this......
> --
> Jeff Carrington
> Mgr. IT Operations
> NPD Group
Have you tried changing the password on SQL 2000 before transfering them or
using CHECK_POLICY = OFF option when creating a login (if you have the
version that uses CREATE LOGIN)?
Also check out the version at
http://blogs.msdn.com/lcris/archive/2006/04/03/567680.aspx
John|||John,
First thanx for the response.
I have tried executing the command with CHECK_POLICY = OFF but got same
results. As for changing the password itself, that is something I am trying
to not do. I am coming into this after years of programming have already
been in place. So if I go changing passwords, who knows what will break. I
am a victim of bad and lack of documentation on the programmers part.
Jeff
--
Jeff Carrington
Mgr. IT Operations
NPD Group
"John Bell" wrote:
> Hi Jeff
> "Jeff Carrington" <JeffCarrington@.discussions.microsoft.com> wrote in
> message news:95D56897-BF78-4D67-B448-18F991F050C1@.microsoft.com...
> >I have been able to transfer over the majority of SQL Authenticated logins
> > from my SQL 2000 servers to SQL 2005 servers using the sp
> > 'sp_help_revlogin'
> > as described in the Microsoft article ID: 246133. However several of the
> > logins fail to be created with the following error:
> > Invalid value given for parameter PASSWORD. Specify a valid parameter
> > value.
> >
> > and on each of these login creations the password value is the same:
> > CONVERT (varbinary(256),
> > 0x09003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F003F00)
> >
> > The same logins with same password values work fine for creating logins on
> > SQL 2000 but fail on 2005.
> >
> > Does anyone know what is going on with this certain password value?
> >
> > Thanx for any help on this......
> > --
> > Jeff Carrington
> > Mgr. IT Operations
> > NPD Group
> Have you tried changing the password on SQL 2000 before transfering them or
> using CHECK_POLICY = OFF option when creating a login (if you have the
> version that uses CREATE LOGIN)?
> Also check out the version at
> http://blogs.msdn.com/lcris/archive/2006/04/03/567680.aspx
> John
>
>