Перейти к содержимому раздела
TechnologiCS
Форумы TechnologiCS
Вы не вошли. Пожалуйста, войдите или зарегистрируйтесь.
Дерево сообщений Активные темы Темы без ответов
Страницы 1
Чтобы отправить ответ, вы должны войти или зарегистрироваться
#1 17 сентября 2014 15:01:48 (изменено: Антон Мороков, 17 сентября 2014 15:04:02)
- Антон Мороков
- Партнеры
- Неактивен
- Откуда: Самара
- На форуме с 4 апреля 2011
- Сообщений: 209
Тема: Ошибка MS SQL Native Error:15118
Добрый день.
Windows Server 2008 R2
MS SQL 2008 Express Edition
TechnologiCS 6.3.0.0(19094)
Все работало нормально, но в один «прекрасный» момент при попытке входа в Администратор стала выводится следующая ошибка: MS SQL Native Error:15118.
Причем после нажатия кнопки «OK», вход производится.
Может ли это быть связанно с вхождением машины на которой установлен Технолоджикс с SQL в домен? Может быть доменные права влияют? Т.к. локальные настройки все проверили, а вот доменные не можем т.к. настройками домена рулят админы управ-ей компании.
Еще создали нового пользователя, но при попытке входа не пускает, возникает ошибка:
Пароль у пользователя сложный.
Старые пользователи заходят без проблем. Новый пользователь в базе появился.
Post’s attachments
pass-user.jpg 19.07 Кб, файл не был скачан.
pass.jpg 12.81 Кб, файл не был скачан.
You don’t have the permssions to download the attachments of this post.
#2 Ответ от Олег Зырянов 18 сентября 2014 04:44:06
- Олег Зырянов
- Технический руководитель
- Неактивен
- Откуда: Новосибирск
- На форуме с 10 декабря 2008
- Сообщений: 4,246
Re: Ошибка MS SQL Native Error:15118
Может ли это быть связанно с вхождением машины на которой установлен Технолоджикс с SQL в домен?
Скорей всего, но это в первую очередь качается машины, где установлен SQL Server (это его пароли не соответствуют политики безопасности). http://www.technologics.ru/support/faq.html#node02-10.
В этом случае следует привести пароли в соответствие с данной политикой, либо запустить TechnologiCS-администратор и отключить у пользователя использование политик ( но по хорошему лучше привести в порядок пароли). https://help.technologics.ru/6.3/TCSHelp/_496.htm
#3 Ответ от Олег Зырянов 18 сентября 2014 04:51:28
- Олег Зырянов
- Технический руководитель
- Неактивен
- Откуда: Новосибирск
- На форуме с 10 декабря 2008
- Сообщений: 4,246
Re: Ошибка MS SQL Native Error:15118
Что-то не так с этим пользователем. Запустите TechnologiCS-Администратор — если что-то не так, он должен исправить. Если и это не поможет надо смотреть в Managment Studio. Скорей всего пользователь по каким-то причинам заблокирован (вроде такие приколы бывают когда пароль несколько раз ввел неправильно, но точно не скажу).
Сообщения 3
Тему читают: 1 гость
Страницы 1
Чтобы отправить ответ, вы должны войти или зарегистрироваться
Search
You can use the CHECK_POLICY & CHECK_EXPIRATION optional clauses when creating or altering a login. For example:
If you had the user 'sa', that can only alter 'sa' : alter login sa with check_policy = off
— Will fail
CREATE LOGIN [noPwdPolicy] WITH PASSWORD = 'weak' go
— Will succeed
CREATE LOGIN [noPwdPolicy] WITH PASSWORD = 'weak', CHECK_POLICY = OFF go
ALTER LOGIN login_name { <status_option> | WITH <set_option> [ ,... ] | <cryptographic_credential_option> } <status_option> ::= ENABLE | DISABLE <set_option> ::= PASSWORD = 'password' | hashed_password HASHED [ OLD_PASSWORD = 'oldpassword' | <password_option> [<password_option> ] ] | DEFAULT_DATABASE = database | DEFAULT_LANGUAGE = language | NAME = login_name | CHECK_POLICY = { ON | OFF } | CHECK_EXPIRATION = { ON | OFF } | CREDENTIAL = credential_name | NO CREDENTIAL <password_option> ::= MUST_CHANGE | UNLOCK <cryptographic_credentials_option> ::= ADD CREDENTIAL credential_name | DROP CREDENTIAL credential_name
- login_name
- Specifies the name of the SQL Server login that is being changed. Domain logins must be enclosed in brackets in the format [domain\user].
- ENABLE | DISABLE
- Enables or disables this login.
- PASSWORD =‘password‘
- Applies only to SQL Server logins. Specifies the password for the login that is being changed. Passwords are case-sensitive.
- PASSWORD =hashed_password
- Applies to the HASHED keyword only. Specifies the hashed value of the password for the login that is being created.
- HASHED
- Applies to SQL Server logins only. Specifies that the password entered after the PASSWORD argument is already hashed. If this option is not selected, the password is hashed before being stored in the database. This option should only be used for login synchronization between two servers. Do not use the HASHED option to routinely change passwords.
Note This argument only works with hashes generated by SQL Server 2000 or later versions. - OLD_PASSWORD =‘oldpassword‘
- Applies only to SQL Server logins. The current password of the login to which a new password will be assigned. Passwords are case-sensitive.
- MUST_CHANGE
- Applies only to SQL Server logins. If this option is included, SQL Server will prompt for an updated password the first time the altered login is used.
- DEFAULT_DATABASE =database
- Specifies a default database to be assigned to the login.
- DEFAULT_LANGUAGE =language
- Specifies a default language to be assigned to the login.
- NAME = login_name
- The new name of the login that is being renamed. If this is a Windows login, the SID of the Windows principal corresponding to the new name must match the SID associated with the login in SQL Server. The new name of a SQL Server login cannot contain a backslash character (\).
- CHECK_EXPIRATION = { ON | OFF }
- Applies only to SQL Server logins. Specifies whether password expiration policy should be enforced on this login. The default value is OFF.
- CHECK_POLICY = { ON | OFF }
- Applies only to SQL Server logins. Specifies that the Windows password policies of the computer on which SQL Server is running should be enforced on this login. The default value is ON.
- CREDENTIAL = credential_name
- The name of a credential to be mapped to a SQL Server login. The credential must already exist in the server. For more information see Credentials (Database Engine).
- NO CREDENTIAL
- Removes any existing mapping of the login to a server credential. For more information see Credentials (Database Engine).
- UNLOCK
- Applies only to SQL Server logins. Specifies that a login that is locked out should be unlocked.
- ADD CREDENTIAL
- Adds an Extensible Key Management (EKM) provider credential to the login. For more information, see Understanding Extensible Key Management (EKM).
- DROP CREDENTIAL
- Removes an Extensible Key Management (EKM) provider credential to the login. For more information see Understanding Extensible Key Management (EKM).
When CHECK_POLICY is set to ON, the HASHED argument cannot be used.
When CHECK_POLICY is changed to ON, the following behavior occurs:
- CHECK_EXPIRATION is also set to ON, unless it is explicitly set to OFF.
- The password history is initialized with the value of the current password hash.
When CHECK_POLICY is changed to OFF, the following behavior occurs:
- CHECK_EXPIRATION is also set to OFF.
- The password history is cleared.
- The value of lockout_time is reset.
If MUST_CHANGE is specified, CHECK_EXPIRATION and CHECK_POLICY must be set to ON. Otherwise, the statement will fail.
If CHECK_POLICY is set to OFF, CHECK_EXPIRATION cannot be set to ON. An ALTER LOGIN statement that has this combination of options will fail.
Important |
---|
CHECK_EXPIRATION and CHECK_POLICY are only enforced on Windows Server 2003 and later. For more information see Password Policy. |
Important |
---|
A known issue in Windows Server 2003 might prevent the bad password count from resetting after the Account Lockout threshold has been reached. This could cause an immediate lockout on subsequent failed login attempts. You can manually reset the bad password count by briefly setting CHECK_POLICY = OFF, followed by CHECK_POLICY = ON. For more information about the Account Lockout threshold, see Microsoft Knowledge Base article 818078: Your User Account May Be Prematurely Locked Out. |
You cannot use ALTER_LOGIN with the DISABLE argument to deny access to a Windows group. For example, ALTER_LOGIN [domain\group] DISABLE will return the following error message:
“Msg 15151, Level 16, State 1, Line 1
“Cannot alter the login ‘Domain\Group’, because it does not exist or you do not have permission.”
This is by design.
Requires ALTER ANY LOGIN permission.
If the CREDENTIAL option is used, also requires ALTER ANY CREDENTIAL permission.
If the login that is being changed is a member of the sysadmin fixed server role or a grantee of CONTROL SERVER permission, also requires CONTROL SERVER permission when making the following changes:
- Resetting the password without supplying the old password.
- Enabling MUST_CHANGE, CHECK_POLICY, or CHECK_EXPIRATION.
- Changing the login name.
- Enabling or disabling the login.
- Mapping the login to a different credential.
A principal can change the password, default language, and default database for its own login.
A. Enabling a disabled login
The following example enables the login Mary5.
ALTER LOGIN Mary5 ENABLE;
B. Changing the password of a login
The following example changes the password of login Mary5 to a strong password.
ALTER LOGIN Mary5 WITH PASSWORD = '<enterStrongPasswordHere>';
C. Changing the name of a login
The following example changes the name of login Mary5 to John2.
ALTER LOGIN Mary5 WITH NAME = John2;
D. Mapping a login to a credential
The following example maps the login John2 to the credential Custodian04.
ALTER LOGIN John2 WITH CREDENTIAL = Custodian04;
E. Mapping a login to an Extensible Key Management credential
The following example maps the login Mary5 to the EKM credential EKMProvider1.
ALTER LOGIN Mary5 ADD CREDENTIAL EKMProvider1; GO
F. Unlocking a login
To unlock a SQL Server login, execute the following statement, replacing **** with the desired account password.
ALTER LOGIN [Mary5] WITH PASSWORD = '****' UNLOCK ; GO
To unlock a login without changing the password, turn the check policy off and then on again.
ALTER LOGIN [Mary5] WITH CHECK_POLICY = OFF; ALTER LOGIN [Mary5] WITH CHECK_POLICY = ON; GO
G. Changing the password of a login using HASHED
The following example changes the password of the TestUser login to an already hashed value.
ALTER LOGIN TestUser WITH PASSWORD = 0x01000CF35567C60BFB41EBDE4CF700A985A13D773D6B45B90900 HASHED ; GO
About berbagisolusi
Berbagi merupakan sebuah bentuk simbol keikhlasan untuk membantu dan menolong, sedangkan solusi adalah cara menyelesaikan masalah. Setiap manusia pasti mengalami masalah, tetapi kita tidak perlu mengalami masalah yang sama jika orang lain pernah mengalami dan kita tahu hal tersebut.
Step 1 – Solve Microsoft Sql Server Error 15118
Is Microsoft Sql Server Error 15118 appearing? Would you like to safely and quickly eliminate Microsoft Sql Server which additionally can lead to a blue screen of death?
When you manually edit your Windows Registry trying to take away the invalid password validation failed. the password does not meet windows policy requirements keys you’re taking a authentic chance. Unless you’ve got been adequately trained and experienced you’re in danger of disabling your computer system from working at all. You could bring about irreversible injury to your whole operating system. As very little as just 1 misplaced comma can preserve your Pc from even booting every one of the way by!
Troubleshooting sp_addlogin check_policy off Windows XP, Vista, 7, 8 & 10
Simply because this chance is so higher, we hugely suggest that you make use of a trusted registry cleaner plan like CCleaner (Microsoft Gold Partner Licensed). This system will scan and then fix any Microsoft Sql Server Error 15118 complications.
Registry cleaners automate the entire procedure of finding invalid registry entries and missing file references (including the Error error) likewise as any broken hyperlinks inside of your registry.
Issue with sql server password policy
Backups are made immediately prior to each and every scan providing you with the choice of undoing any changes with just one click. This protects you against doable damaging your pc. Another advantage to these registry cleaners is that repaired registry errors will strengthen the speed and performance of one’s procedure drastically.
- https://berbagisolusi.wordpress.com/2011/12/21/password-validation-failed-the-password-does-not-meet-windows-policy-requirements-because-it-is-not-complex-enough-microsoft-sql-server-error-15118/
- https://social.msdn.microsoft.com/Forums/sqlserver/en-US/5786e767-323d-4d74-8fe5-0776869c9532/sql-2005-windows-password-policy?forum=sqlsecurity
- http://www.experts-exchange.com/questions/23090487/Enforcing-Windows-password-policy-on-SQL-accounts.html
- http://www.mytechmantra.com/LearnSQLServer/change-sa-password-in-SQL-Server.html
Cautionary Note: Yet again, for those who are not an state-of-the-art consumer it’s very encouraged that you simply refrain from editing your Windows Registry manually. If you make even the smallest error within the Registry Editor it can result in you some serious issues that may even call for a brand new set up of Windows. Not all difficulties attributable to incorrect Registry Editor use are solvable.
Fixed: sql error 18456
Symptoms of Microsoft Sql Server Error 15118
“Microsoft Sql Server Error 15118” appears and crashes the energetic method window.
Your Personal computer routinely crashes with Microsoft Sql Server Error 15118 when running the exact same system.
“Microsoft Sql Server Error 15118” is shown.
Windows operates sluggishly and responds little by little to mouse or keyboard input.
Your computer periodically “freezes” for the number of seconds in a time.
Will cause of Microsoft Sql Server Error 15118
Corrupt obtain or incomplete set up of Windows Operating System software program.
Corruption in Windows registry from a new Windows Operating System-related application adjust (install or uninstall).
Virus or malware infection which has corrupted Windows method documents or Windows Operating System-related application data files.
Another method maliciously or mistakenly deleted Windows Operating System-related files.
Mistakes this sort of as “Microsoft Sql Server Error 15118” can be brought about by several different elements, so it really is important that you troubleshoot every of the achievable brings about to forestall it from recurring.
Simply click the beginning button.
Variety “command” inside the lookup box… Will not hit ENTER nonetheless!
Although keeping CTRL-Shift in your keyboard, hit ENTER.
You’re going to be prompted that has a authorization dialog box.
Click on Of course.
A black box will open having a blinking cursor.
Variety “regedit” and hit ENTER.
Within the Registry Editor, choose the password validation failed. the password does not meet windows policy requirements connected key (eg. Windows Operating System) you wish to back again up.
Within the File menu, choose Export.
Inside the Preserve In list, pick out the folder in which you wish to save the Windows Operating System backup key.
Inside the File Title box, sort a reputation for the backup file, these types of as “Windows Operating System Backup”.
From the Export Vary box, ensure that “Selected branch” is selected.
Click on Help you save.
The file is then saved by using a .reg file extension.
You now use a backup within your sp_addlogin check_policy off related registry entry.
Solution to your problem
There are actually some manual registry editing measures that can not be talked about in this article due to the high chance involved for your laptop or computer method. If you want to understand more then check out the links below.
Additional Measures:
One. Conduct a Thorough Malware Scan
There’s a probability the Error 15118 Microsoft Server Sql error is relevant to some variety of walware infection. These infections are malicious and ready to corrupt or damage and possibly even delete your ActiveX Control Error files. Also, it’s attainable that your Microsoft Sql Server Error 15118 is actually connected to some element of that malicious plan itself.
2. Clean Disk Cleanup
The a lot more you employ your computer the extra it accumulates junk files. This comes from surfing, downloading packages, and any sort of usual computer system use. When you don’t clean the junk out occasionally and keep your program clean, it could turn into clogged and respond slowly. That is when you can encounter an Error error because of possible conflicts or from overloading your hard drive.
Once you clean up these types of files using Disk Cleanup it could not just remedy Microsoft Sql Server Error 15118, but could also create a dramatic change in the computer’s efficiency.
Tip: While ‘Disk Cleanup’ is definitely an excellent built-in tool, it even now will not completely clean up Sql Server discovered on your PC. There are numerous programs like Chrome, Firefox, Microsoft Office and more, that cannot be cleaned with ‘Disk Cleanup’.
Since the Disk Cleanup on Windows has its shortcomings it is extremely encouraged that you use a specialized sort of challenging drive cleanup and privacy safety application like CCleaner. This system can clean up your full pc. If you run this plan after each day (it could be set up to run instantly) you are able to be assured that your Pc is generally clean, often operating speedy, and always absolutely free of any Microsoft error associated with your temporary files.
How Disk Cleanup can help
1. Click your ‘Start’ Button.
2. Style ‘Command’ into your search box. (no ‘enter’ yet)
3. When holding down in your ‘CTRL-SHIFT’ important go ahead and hit ‘Enter’.
4. You will see a ‘permission dialogue’ box.
5. Click ‘Yes’
6. You will see a black box open up plus a blinking cursor.
7. Variety in ‘cleanmgr’. Hit ‘Enter’.
8. Now Disk Cleanup will start calculating the amount of occupied disk space you will be able to reclaim.
9. Now a ‘Disk Cleanup dialogue box’ seems. There will be a series of checkboxes for you personally to pick. Generally it will likely be the ‘Temporary Files’ that consider up the vast majority of your disk area.
10. Verify the boxes that you want cleaned. Click ‘OK’.
How to repair
3. System Restore can also be a worthwhile device if you ever get stuck and just desire to get back to a time when your computer system was working ideal. It will work without affecting your pics, paperwork, or other crucial information. You can discover this option with your User interface.
Sql Server
Manufacturer
Device
Operating System
Microsoft Sql Server Error 15118
4.5 out of
5
based on
37 ratings.
Hello
are
there
any
well-known
special characters
that
you
can’t
use
in
a
password
for
a
SQL
Server
login?
I
just
tried
using
the
TSQL
«ALTER
LOGIN
[USER NAME]
WITH
PASSWORD
=
‘acegh§1′»
to
change
the
password
for
a
user
and
get
the
error message
that
the
password policy
is
not
met. (
Message
15118,
level
16,
State
1,
line
1
Password validation
failed.
The
password
is
not
complex
enough,
and
does
not meet
Windows policy
requirements
because.
)
It
seems
that the paragraph sign
(§)
is the problem.
Because
as I change it to
a
dollar sign
($) then
the
password
will be
accepted.
I
have
searched all
SQL
Server
documentation
and
various
forums
and
found
nothing
in this regard.
Because
the
above
command runs within
an
application I
would
like to
know
whether
there
are
more
such
illegal
characters
so
I can check/block it
when users are
entering
new Passwords.
Thank
in
advance.
Christian
When you are dealing with Database Master Key and provide encryption password, you have to give strong password there. It uses Windows Complexity Password policy if exist any. In you won’t provide password according to your Windows Complexity Password policy, it won’t accept it and you will greeted with following error.
Msg 15118, Level 16, State 1, Line 1
Password validation failed. The password does not meet Windows policy requirements because it is not complex enough.
Reference: Ritesh Shah
http://www.sqlhub.com
Note: Microsoft Books online is a default reference of all articles but examples and explanations prepared by Ritesh Shah, founder of http://www.SQLHub.com