Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

MS SQL 2005 WinCC Setup fail

Created by: Dec at: 3/19/2007 6:07 PM (4 Replies)

Rating (1)

Thanks 0

5 Entries

3/19/2007 6:07 PM	Rate (0)
Dec Gold Expert Joined: 5/19/2006 Last visit: 12/3/2024 Posts: 549 Rating: (107)	Hi, I got a little time to play with thenew latest and greatest WinCC v6.2 and I run into some setup problems : PC(virtual PC): Windows 2003 SP2 Std Server part of a Windows 2003 SP2 Domain. Logon with a local PC account (Administrator). Run WinCC SQL 2005 Setup and fail with the following error: SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Password validation failed. The password does not meet Windows policy requirements because it is too short.. To continue, correct the problem, and then run SQL Server Setup again. I don't recall setting up any password for sa (default); I tried also with a strong sapassword (16 char strong) and with the same error result. What I foundwas my Domain Policy Password Minimum Lengthhad 14 characters (I am paranoid when it comes to security). I changed to 8 char and the Setup finished OK. MSSQL 2005 Dev/Std Edition from MSDN installs just fine with any password policy length. Does anybody have seen this behavior? Dec
	Last edited by: Dec at: 20.03.2007 00:20 Last edited by: Dec at: 19.03.2007 18:21
Suggestion To thank Quote Answer

3/19/2007 6:28 PM	Rate (0)
Danielle Posts: 1275 Rating: (123)	Hi Dec, So... how about v6.2? I haven't tried it yet. About the installation, you think it's mandatory to set up a password for sa now?
Danielle Posts: 1275 Rating: (123)
Suggestion To thank Quote Answer

3/19/2007 7:47 PM	Rate (0)
Dec Gold Expert Joined: 5/19/2006 Last visit: 12/3/2024 Posts: 549 Rating: (107)	Hi, In my case (SQL 2005Setup WinCC instance fail) doesn’t matter if you setup or not the sa account (default sapassword "WinCC_SQL_12345"); The WinCC SQL Setup fails because Domain Policy for password length is > 8 chars. Dec

Suggestion To thank Quote Answer

3/20/2007 3:10 AM	Rate (1)
Dec Gold Expert Joined: 5/19/2006 Last visit: 12/3/2024 Posts: 549 Rating: (107)	I think I got to the bottom of this issue: You have to setup Domain Policy Minimum Password Length <= 8 char. For some reasonsSQL Setup runs instmsdb.sql to signsps and it's using "Yukon90_" password . This is strange because it happens only with WinCC SQL "Unattended Setup" using the swith SQLSUPPORTPATCH & HOTFIXPATCHhaving the command line (D: is MS_SQL2005_WINCC CD/DVD-ROM): D:\20_SQL2005\Servers\setup.exe SQLSUPPORTPATCH="D:\20_SQL2005\QFE\sqlsupport.msp" HOTFIXPATCH="D:\20_SQL2005\QFE\sqlrun_as.msp;D:\20_SQL2005\QFE\sqlrun_sql.msp;D:\20_SQL2005\QFE\sqlrun_dts.msp;D:\20_SQL2005\QFE\sqlrun_ns.msp;D:\20_SQL2005\QFE\sqlrun_rs.msp;D:\20_SQL2005\QFE\sqlrun_tools.msp" /qb /settings C:\WINDOWS\Setup\SQLServerData\Install_Template.ini I was not able fo find any info about the above SQL SUPPORTPATCH/HOTFIXPATCH located under QFE folder (KB919357 ?). It must be some special SQL2005 Hotfix pre SP1. I need to look closer to these msp files since MSFT doesn't give me any clues about KB919357. Anyway it fails for the above domain policy password length. Dec
	Last edited by: Dec at: 20.03.2007 07:17 Last edited by: Dec at: 20.03.2007 05:31
Suggestion To thank Quote Answer

3/20/2007 8:54 AM	Rate (0)
Ikkezelf Posts: 1084 Rating: (72)	Thanks for the info Dec.
Ikkezelf Posts: 1084 Rating: (72)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on