question

Noonies avatar image
Noonies asked

Invalid value given for parameter PASSWORD.

I wanted to test CREATE LOGIN script which was generated for creating a login on another SQL Instance. I'm receiving an error: CREATE LOGIN [ACCOUNTNAME] WITH PASSWORD = 0x01005CD1F6C15FC43A1F66EF350878DF58313F438372F3AD366C HASHED, SID = 0x019F68B303BCFC43B092FB603A134136, DEFAULT_DATABASE = [master], CHECK_POLICY = OFF, CHECK_EXPIRATION = OFF I can run the CREATE login on a different SQL Server just fine but on my new SQL Instance this does not work. Any ideas why this would work on one SQL instance but not another? This is a SQL account and the SQL Server that it is failing on is part of a workgroup until we migrate databases. I'm just trying to test the script prior to project start time.
sql-server-2008-r2securitylogin
3 comments
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

JohnM avatar image JohnM commented ·
What's the error?
0 Likes 0 ·
Tim avatar image Tim commented ·
Sweet, glad the issue was due to the domain vs workgroup. I nailed that one.
0 Likes 0 ·
Noonies avatar image Noonies commented ·
Yes you def nailed it with the domain vs. workgroup for sure! Thank you both for your help and feedback!
0 Likes 0 ·

1 Answer

·
Tim avatar image
Tim answered
Are both instances SQL 2008R2 and both in the same workgroup? If one is in workgroup and it is working, but not on a server that may be in a domain, it is probably related to the password complexity requirements of the instance in the domain. If that is not the case, do both instances support SQL authentication?
11 comments
10 |1200
Toggle Comment visibility. Current Visibility: Viewable by all users

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Noonies avatar image Noonies commented ·
No we are not! The vendor we had implementing the VM did not want us to use P2V due to some issues they had seen on their end. So they suggested we move to VM manually. So I built the SQL VM box, prepped all the scripts I need and have all files for SSIS and SSRS that I have created saved to a shared location. CheckList is done and now I just wait for the move. :) (not going lie...with my fingers crossed.) I would have also thought P2V would be best!
1 Like 1 ·
Noonies avatar image Noonies commented ·
That actually can be the case causing this. One I'm testing where it works is on the domain and the other is in the workgroup. I will follow up once I have the SQL server on the domain.
0 Likes 0 ·
Tim avatar image Tim commented ·
Any update? When are you planning to move it into the domain?
0 Likes 0 ·
Noonies avatar image Noonies commented ·
Looks like this will be scheduled for early AM saturday. I'm moving from physical server to VM on all databases. The server name needs to be the same as the physical that is why it is in a workgroup right now. I didnt want to rename the SQL instance when the "switch" was to be made.
0 Likes 0 ·
Tim avatar image Tim commented ·
Makes sense to me. Are you performing an OS upgrade as well? Why not just do a physical to virtual conversion? P2V
0 Likes 0 ·
Show more comments

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.