Letysite.ru

IT Новости с интернет пространства
0 просмотров
Рейтинг статьи
1 звезда2 звезды3 звезды4 звезды5 звезд
Загрузка...

Password does not meet security requirements

Password does not meet security requirements

Question

I tried to install an ALLDATA database which run with SQL Server 2005 express edition. The data base fails to install becase of the following code that come up which is related to AS password requirement. The error that come up is:

The sa password must meet SQL Server password policy requirements. For strong password guidelines, see Authentication Mode, in SQL Server Books Online.

I am trying to install this database in a network server operating under Windows Server 2003 R2 with SP2. If anyone knows how to solve this problem, please let me.

Answers

You should contact the ALLDATA database vendor to determine what effects will have on their application if you were to either choose a strong password for the ‘sa’ account, or to use Windows security and lock out the ‘sa’ account.

And I’m sure they have encountered this question before and will have some suggestions.

All replies

You should contact the ALLDATA database vendor to determine what effects will have on their application if you were to either choose a strong password for the ‘sa’ account, or to use Windows security and lock out the ‘sa’ account.

And I’m sure they have encountered this question before and will have some suggestions.

I’ve got the same problem, did you ever find a solution to this?

Several simple solution steps:

1*. Go to Administrative Tools / Domain Security Policy :: Security Settings | Account Policies | Password Policy

2*. Ensure «Minimum password length» and «Password must meet complexity requirements» set to «Not Defined» state.

Читать еще:  Как исправить ошибки в word

* Skip this steps if you don’t have domain controller.

3. Go to Administrative Tools / Local Security Policy :: Security Settings | Account Policies | Password Policy

4. Turn «Minimum password length» to zero and «Password must meet complexity requirements» to «Disable»

5. Go to SQL Installation window and press «Retry».

6. After installation successfully done, turn changed security settings from steps 1-4 back.

I recently ran into the same problem with a vendor who created a custom install package with their application.

1st — Remove the machine from the domain (if not on the domain proceed to step 2 anyways)

2nd — make sure the local security policy is set to not require complex passwords

3rd — run your install, then change the application password once complete

4th — put the machine back on the domain.

* Let me first caveate this by saying I thought I had a strong grasp on SQL 2005 (regardless of iteration), but once again a small feature change snuck up and bit me.

— Microsoft has modified SQL 2005 (and supposedly 2000 was capable with the proper OS, but I never saw the behaviour) to inherit Password policy from the OS. So if the machine is on the domain and you have a password policy requiring complex passwords (as you should do at a very minimum) you will indeed see this problem with an incorrectly setup application.

the application in my case is «DocuShare Express» from Xerox. It is used by the MultiFunction printers to provide some advanced features. It turns out that the installer does not prompt the user for an SQL password when installing, it then proceeds to install SQL Express and set the password to *null*. Now that I have strong feelings about security, actually I do, if you are going to provide a tool and this tools provides web based access to scanned documents and it secures that access. WHY then would you use the «SA» account and then even WORSE. why would you use a blank password.

Читать еще:  Vba word combobox

I have to stop here or my Soapbox will be taken away.

I hope this helps you or someone else in your situation.

Ссылка на основную публикацию
Adblock
detector