Вот несколько простых способов исправить ошибку 15407 SQL Server.Ошибка: 15407) Сервер должен включить опцию Agent XPs. Агент Sql Server должен быть настроен для поддержки зашифрованных рабочих взаимодействий или отключить агент SQ Server для использования зашифрованных соединений.
В любом домене Windows автоматически добавляются уникальные идентификаторы гарантии (SID) — логины Windows в интернет-домене. Если вы добавляете браузер Windows в качестве фактического входа в SQL Server, этот SID сохраняется в основной таблице SQL Server. Ошибка 15401 возникает перед тем, как кто-то попытается добавить инновационное новое имя пользователя с тем же SID, что и существующий доступ к SQL Server.
Привет, Кумар!
Сначала вам необходимо обычно изменить режим аутентификации сервера на режим аутентификации SQL Server и Windows.
1. В SQL Server Studio Explorer Control Objects нажмите true – нажмите на сервер, а также посмотрите свойства.
1. На странице “Безопасность” в разделе “Аутентификация сервера” выберите сервер SQL и режим аутентификации Windows, затем нажмите “ОК”.
2. В диалоговом окне SQL Server Management Studio нажмите OK, чтобы увидеть, нужно ли перезагружать компьютер SQL Server.
3. В обозревателе объектов щелкните правой кнопкой мыши веб-сервер и выберите «Перезапустить». Кроме того, если агент SQL Server часто запускается, его необходимо перезапустить.
Далее придумайте логин SQL Server, который использует аутентификацию SQL Server.
1. В SQL Server Management Studio откройте обозреватель объектов и/или разверните папки, логически соответствующие этим экземплярам сервера, на котором должно быть создано обновляемое соединение.
2. Щелкните правой кнопкой мыши “Безопасность” (обычно это папка), выберите “Создать”, в этом случае нажмите “Подключиться”.
3. На странице Общие введите псевдоним для нового подключения в поле Имя подключения.
4. Выберите Аутентификация SQL Server.
5.A Введите пароль для входа в систему.
6. Выберите политику имени пользователя и пароля, настройки которой вы хотите применить к чьему-либо новому логину. В целом, стратегия внедрения паролей считается наиболее безопасной.
7. Переключитесь на роли сервера и взимайте плату за сопоставление пользователей и предоставляйте определенные роли официанта и базы данных, которые помогают самой учетной записи.
8. Нажмите OK.
Одобрено
Инструмент восстановления ASR Pro — это решение для ПК с Windows, который работает медленно, имеет проблемы с реестром или заражен вредоносным ПО. Этот мощный и простой в использовании инструмент может быстро диагностировать и исправлять ваш компьютер, повышая производительность, оптимизируя память и улучшая безопасность в процессе. Больше не страдайте от вялости компьютера — попробуйте ASR Pro сегодня!
Если их несколько. Если у вас есть другие вопросы, дайте мне знать, что вы думаете.
При размещении огромной базы данных в вашем экземпляре SQL вы получите. Невозможно занятие с основным специальным “sa”. Ошибка Microsoft SQL Server: 15405 появляется в тот момент, когда пользователь sa указывается как тип DBO базы данных. Чтобы избежать этого, Open SQL Management Studio часто объединяется с Click New Query.
Спасибо.
***Сяо Мин Тан***Интернет-сообщество Microsoft** *
- Remove From My Forums
-
Question
-
TITLE: Microsoft SQL Server Management Studio
——————————Create failed for Login ‘test’. (Microsoft.SqlServer.Smo)
——————————
ADDITIONAL INFORMATION:An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
——————————
‘test’ is not a valid Windows NT name. Give the complete name: <domain\username>. (Microsoft SQL Server, Error: 15407)
When I try to create login it gives me above error. I want to create windows login in SQL Server 2005. I alsp try to create login using ss-phl-454\test. ss-phl-454 is my sql server name. still it goves me an error. i have created user test in windows. (computer management-local users and group and i created new user test.)
HOw can i successfully create windows login in sql server??
Thanks,
Answers
-
Try the following.
Assuming that username Test exists on the same Server(in this case ServerName), this should workUSE [master] GO CREATE LOGIN [ServerName\Test] FROM WINDOWS WITH DEFAULT_DATABASE=[master] GO
If the user exists on the domain, change ServerName to the Domain name instead.
Abdallah El-Chal, PMP, ITIL, MCTS
-
Marked as answer by
Thursday, March 18, 2010 8:01 PM
-
Marked as answer by
List of error messages between 15000 and 15999 in SQL Server 2017.
These error messages are all available by querying the sys.messages catalog view on the master database.
message_id
severity
is_event_logged
text
15001
16
0
Object ‘%ls’ does not exist or is not a valid object for this operation.
15002
16
0
The procedure ‘%s’ cannot be executed within a transaction.
15003
16
0
Only members of the %s role can execute this stored procedure.
15004
16
0
Name cannot be NULL.
15005
10
0
Statistics for all tables have been updated.
15006
16
0
‘%s’ is not a valid name because it contains invalid characters.
15007
16
0
‘%s’ is not a valid login or you do not have permission.
15008
16
0
User ‘%s’ does not exist in the current database.
15009
16
0
The object ‘%s’ does not exist in database ‘%s’ or is invalid for this operation.
15010
16
0
The database ‘%s’ does not exist. Supply a valid database name. To see available databases, use sys.databases.
15011
16
0
Database option ‘%s’ does not exist. Specify a valid database option.
15012
16
0
The device ‘%s’ does not exist. Use sys.backup_devices to show available devices.
15013
10
0
Table ‘%s’: No columns without statistics found.
15014
16
0
The role ‘%s’ does not exist in the current database.
15015
16
0
The server ‘%s’ does not exist. Use sp_helpserver to show available servers.
15016
16
0
The default ‘%s’ does not exist.
15017
16
0
The rule ‘%s’ does not exist.
15018
10
0
Table ‘%s’: Creating statistics for the following columns:
15019
16
0
The extended stored procedure ‘%s’ does not exist.
15020
10
0
Statistics have been created for the %d listed columns of the above tables.
15021
16
0
Invalid value given for parameter %s. Specify a valid parameter value.
15022
16
0
The specified user name is already aliased.
15023
16
0
User, group, or role ‘%s’ already exists in the current database.
15025
16
0
The server principal ‘%s’ already exists.
15026
16
0
Logical device ‘%s’ already exists.
15028
16
0
The server ‘%s’ already exists.
15032
16
0
The database ‘%s’ already exists. Specify a unique database name.
15033
16
0
‘%s’ is not a valid official language name.
15034
16
0
The application role password must not be NULL.
15036
16
0
The data type ‘%s’ does not exist or you do not have permission.
15040
16
0
User-defined error messages must have an ID greater than 50000.
15041
16
0
User-defined error messages must have a severity level between 1 and 25.
15042
10
0
The @with_log parameter is ignored for messages that are not us_english version.
15043
16
0
You must specify ‘REPLACE’ to overwrite an existing message.
15044
16
0
The type «%s» is an unknown backup device type. Use the type «disk» or «tape».
15045
16
0
The logical name cannot be NULL.
15046
16
0
The physical name cannot be NULL.
15048
10
0
Valid values of the database compatibility level are %d, %d, %d, %d or %d.
15049
11
0
Cannot unbind from ‘%s’. Use ALTER TABLE DROP CONSTRAINT.
15050
11
0
Cannot bind default ‘%s’. The default must be created using the CREATE DEFAULT statement.
15051
11
0
Cannot rename the table because it is published for replication.
15053
16
0
Objects exist which are not owned by the database owner.
15054
10
0
The current compatibility level is %d.
15056
10
0
The suspect flag on the database «%s» is already reset.
15057
16
0
List of %s name contains spaces, which are not allowed.
15058
16
0
List of %s has too few names.
15059
16
0
List of %s has too many names.
15060
16
0
List of %s names contains name(s) which have ‘%s’ non-alphabetic characters.
15061
16
0
The add device request was denied. A physical device named «%s» already exists. Only one backup device may refer to any physical device name.
15062
16
0
The guest user cannot be mapped to a login name.
15063
16
0
The login already has an account under a different user name.
15065
16
0
All user IDs have been assigned.
15066
16
0
A default-name mapping of a remote login from remote server ‘%s’ already exists.
15068
16
0
A remote user ‘%s’ already exists for remote server ‘%s’.
15069
16
0
One or more users are using the database. The requested operation cannot be completed.
15070
10
0
Object ‘%s’ was successfully marked for recompilation.
15071
16
0
Usage: sp_addmessage <msgnum>,<severity>,<msgtext> [,<language> [,FALSE | TRUE [,REPLACE]]]
15072
16
0
Usage: sp_addremotelogin remoteserver [,loginname [,remotename]]
15074
10
0
Warning: You must recover this database prior to access.
15076
16
0
Default, table, and user data types must be in the current database.
15077
16
0
Rule, table, and user data type must be in the current database.
15078
16
0
The table or view must be in the current database.
15079
10
0
Queries processed: %d.
15080
16
0
Cannot use parameter %s for a Windows login.
15081
16
0
Membership of the public role cannot be changed.
15083
16
0
Physical data type ‘%s’ does not accept a collation
15084
16
0
The column or user data type must be in the current database.
15085
16
0
Usage: sp_addtype name, ‘data type’ [,’NULL’ | ‘NOT NULL’]
15096
16
0
Could not find object ‘%ls’ or you do not have required permission or the object is not valid for adding extended property.
15097
16
0
The size associated with an extended property cannot be more than 7,500 bytes.
15098
16
0
The name change cannot be performed because the SID of the new name does not match the old SID of the principal.
15099
16
0
The MUST_CHANGE option cannot be used when CHECK_EXPIRATION is OFF.
15100
16
0
Usage: sp_bindefault defaultname, objectname [, ‘futureonly’]
15101
16
0
Cannot bind a default to a computed column, a sparse column, or to a column of the following data types: timestamp, varchar(max), nvarchar(max), varbinary(max), xml, or CLR type.
15102
16
0
Cannot bind a default to an identity column.
15103
16
0
Cannot bind a default to a column created with or altered to have a default value.
15104
16
0
You do not own a table named ‘%s’ that has a column named ‘%s’.
15106
16
0
Usage: sp_bindrule rulename, objectname [, ‘futureonly’]
15107
16
0
Cannot bind a rule to a computed column, a sparse column, or to a column of the following data types: text, ntext, image, timestamp, varchar(max), nvarchar(max), varbinary(max), xml, or user-defined data type.
15108
16
0
sp_addtype cannot be used to define user-defined data types for varchar(max), nvarchar(max) or varbinary(max) data types. Use CREATE TYPE for this purpose.
15109
16
0
Cannot change the owner of the master, model, tempdb or distribution database.
15110
16
0
The proposed new database owner is already a user or aliased in the database.
15112
11
0
The third parameter for table option ‘text in row’ is invalid. It should be ‘on’, ‘off’, ‘0’, ‘1’ or a number from 24 through 7000.
15113
16
0
Too many failed login attempts. This account has been temporarily locked as a precaution against password guessing. A system administrator can unlock this login with the UNLOCK clause of ALTER LOGIN.
15114
16
0
Password validation failed. The password for the user is too recent to change.
15115
16
0
Password validation failed. The password cannot be used at this time.
15116
16
0
Password validation failed. The password does not meet the operating system policy requirements because it is too short.
15117
16
0
Password validation failed. The password does not meet the operating system policy requirements because it is too long.
15118
16
0
Password validation failed. The password does not meet the operating system policy requirements because it is not complex enough.
15119
16
0
Password validation failed. The password does not meet the requirements of the password filter DLL.
15120
16
0
An unexpected error occurred during password validation.
15121
16
0
An error occurred during the execution of %ls. A call to ‘%ls’ failed with error code: ‘%d’.
15122
16
0
The CHECK_EXPIRATION option cannot be used when CHECK_POLICY is OFF.
15123
16
0
The configuration option ‘%s’ does not exist, or it may be an advanced option.
15124
16
0
The configuration option ‘%s’ is not unique.
15125
16
0
Trigger ‘%s’ is not a trigger for ‘%s’.
15127
16
0
Cannot set the default language to a language ID not defined in syslanguages.
15128
16
0
The CHECK_POLICY and CHECK_EXPIRATION options cannot be turned OFF when MUST_CHANGE is ON.
15129
16
0
‘%d’ is not a valid value for configuration option ‘%s’.
15130
16
0
There already exists a ‘%s’ trigger for ‘%s’.
15131
16
0
Usage: sp_dbremove <dbname> [,dropdev]
15133
16
0
INSTEAD OF trigger ‘%s’ cannot be associated with an order.
15134
16
0
No alias exists for the specified user.
15135
16
0
Object is invalid. Extended properties are not permitted on ‘%s’, or the object does not exist.
15136
16
0
The database principal is set as the execution context of one or more procedures, functions, or event notifications and cannot be dropped.
15137
16
0
An error occurred during the execution of sp_xp_cmdshell_proxy_account. Possible reasons: the provided account was invalid or the ‘%.*ls’ credential could not be created. Error code: %ls, Error Status: %d.
15138
16
0
The database principal owns a %S_MSG in the database, and cannot be dropped.
15141
16
0
The server principal owns one or more %S_MSG(s) and cannot be dropped.
15143
16
0
‘%s’ is not a valid option for the @updateusage parameter. Enter either ‘true’ or ‘false’.
15144
16
0
The role has members. It must be empty before it can be dropped.
15145
16
0
An implicit %S_MSG creation has failed. Reason: The %S_MSG may have been dropped or its name may already be in use.
15146
16
0
An encryption password must be provided to encrypt the private key of this %S_MSG.
15147
16
0
No decryption password should be provided because the private key of this %S_MSG is encrypted by a master key.
15148
16
0
The data type or table column ‘%s’ does not exist or you do not have permission.
15149
16
0
Principal doesn’t exist or doesn’t have sufficient privileges.
15150
16
0
Cannot %S_MSG the %S_MSG ‘%.*ls’.
15151
16
0
Cannot %S_MSG the %S_MSG ‘%.*ls’, because it does not exist or you do not have permission.
15152
16
0
Cannot update user instances. Reason: %ls. Error code: 0x%x.
15153
16
0
The xp_cmdshell proxy account information cannot be retrieved or is invalid. Verify that the ‘%.*ls’ credential exists and contains valid information.
15154
16
0
The database principal owns an %S_MSG and cannot be dropped.
15155
16
0
The server principal owns a %S_MSG and cannot be dropped.
15156
16
0
The password that you specified is too long. The password should have no more than %d characters.
15157
16
0
Setuser failed because of one of the following reasons: the database principal ‘%.*ls’ does not exist, its corresponding server principal does not have server access, this type of database principal cannot be impersonated, or you do not have permission.
15158
16
0
Cannot initialize security.
15159
16
0
Maximum impersonation nesting level exceeded (limit %d)..
15160
16
0
Cannot issue impersonation token from non-primary impersonation context or for non-Windows user.
15161
16
0
Cannot set application role ‘%.*ls’ because it does not exist or the password is incorrect.
15162
16
0
Unexpected error while creating impersonation token.
15163
16
0
Invalid timeout value. Valid timeout is between 1 and 7200 sec.
15164
16
0
‘%.*ls’ is not a valid login or cannot be issued impersonation token.
15165
16
0
Could not find object ‘%ls’ or you do not have permission.
15166
10
0
Warning: User types created via sp_addtype are contained in dbo schema. The @owner parameter if specified is ignored.
15167
16
0
Cannot generate GUID.
15168
16
0
Cannot rename the view ‘%s’ and its columns and indexes because it is a system generated view that was created for optimization purposes.
15169
16
0
The server option «%ls» is not available in this edition of SQL Server.
15170
16
0
This login is the owner of %ld job(s). You must delete or reassign these jobs before the login can be dropped.
15171
16
0
Cannot use the parameter «%s» for a certificate or asymmetric key login.
15172
16
0
FallBack certificate must be created or dropped in master database in single user mode.
15173
16
0
Server principal ‘%s’ has granted one or more permission(s). Revoke the permission(s) before dropping the server principal.
15174
16
0
Login ‘%s’ owns one or more database(s). Change the owner of the database(s) before dropping the login.
15175
16
0
Login ‘%s’ is aliased or mapped to a user in one or more database(s). Drop the user or alias before dropping the login.
15176
16
0
The only valid @parameter value is ‘WITH_LOG’.
15177
16
0
Usage: sp_dropmessage <msg number> [,<language> | ‘ALL’]
15178
16
0
Cannot drop a message with an ID less than 50,000.
15179
16
0
The message number %u or specified language version does not exist.
15182
16
0
Cannot disable access to the guest user in master or tempdb.
15183
16
0
The database principal owns objects in the database and cannot be dropped.
15184
16
0
The database principal owns data types in the database and cannot be dropped.
15185
16
0
There is no remote user ‘%s’ mapped to local user ‘%s’ from the remote server ‘%s’.
15186
16
0
The server principal is set as the execution context of a trigger or event notification and cannot be dropped.
15187
10
0
The %S_MSG cannot be dropped because it is used by one or more %S_MSG(s).
15188
16
0
Cannot create an index that does not include all security columns.
15189
16
0
Cannot have more than one security column for a table.
15190
16
0
There are still remote logins or linked logins for the server ‘%s’.
15192
16
0
Cannot alter or drop the security column of a table.
15195
16
0
The MUST_CHANGE option is not supported by this version of Microsoft Windows.
15196
16
0
The current security context is non-revertible. The «Revert» statement failed.
15197
16
0
There is no text for object ‘%s’.
15198
16
0
The name supplied (%s) is not a user, role, or aliased login.
15199
16
0
The current security context cannot be reverted. Please switch to the original database where ‘%ls’ was called and try it again.
15200
16
0
There are no remote servers defined.
15201
16
0
There are no remote logins for the remote server ‘%s’.
15202
16
0
There are no remote logins defined.
15203
16
0
There are no remote logins for ‘%s’.
15204
16
0
There are no remote logins for ‘%s’ on remote server ‘%s’.
15205
16
0
There are no servers defined.
15206
16
0
Invalid Remote Server Option: ‘%s’.
15207
16
0
The trusted option in remote login mapping is no longer supported.
15208
16
0
The certificate, asymmetric key, or private key file is not valid or does not exist; or you do not have permissions for it.
15209
16
0
An error occurred during encryption.
15212
16
0
Invalid certificate subject. The certificate subject must have between 1 and %d characters.
15213
16
0
Warning: The certificate you created has an invalid validity period; its expiration date precedes its start date.
15214
16
0
Warning: The certificate you created is expired.
15215
16
0
Warning: The certificate you created is not yet valid; its start date is in the future.
15216
16
0
‘%s’ is not a valid option for the @delfile parameter.
15217
16
0
Property cannot be updated or deleted. Property ‘%.*ls’ does not exist for ‘%.*ls’.
15218
16
0
Object ‘%s’ is not a table.
15219
16
0
Cannot change the owner of an indexed view.
15222
16
0
Remote login option ‘%s’ is not unique.
15223
11
0
Error: The input parameter ‘%s’ is not allowed to be null.
15224
11
0
Error: The value for the @newname parameter contains invalid characters or violates a basic restriction (%s).
15225
11
0
No item by the name of ‘%s’ could be found in the current database ‘%s’, given that @itemtype was input as ‘%s’.
15226
16
0
Cannot create alias types from an XML datatype.
15227
16
0
The database ‘%s’ cannot be renamed.
15229
16
0
The argument specified for the «%.*ls» parameter of stored procedure sp_db_vardecimal_storage_format is not valid. Valid arguments are ‘ON’ or ‘OFF’.
15230
16
0
Error starting user instance. Error code: %d.
15231
16
0
The argument specified for the ‘%ls’ parameter of stored procedure ‘%ls’ is not valid. Valid arguments are ‘ON’, ‘OFF’, ‘TRUE’ and ‘FALSE’.
15232
16
0
A certificate with name ‘%s’ already exists or this certificate already has been added to the database.
15233
16
0
Property cannot be added. Property ‘%.*ls’ already exists for ‘%.*ls’.
15234
16
0
Objects of this type have no space allocated.
15236
16
0
Column ‘%s’ has no default.
15237
16
0
User data type ‘%s’ has no default.
15238
16
0
Column ‘%s’ has no rule.
15239
16
0
User data type ‘%s’ has no rule.
15240
16
0
Cannot write into file ‘%s’. Verify that you have write permissions, that the file path is valid, and that the file does not already exist.
15241
16
0
Usage: sp_dboption [dbname [,optname [,’true’ | ‘false’]]]
15242
16
0
Database option ‘%s’ is not unique.
15243
16
0
The option ‘%s’ cannot be changed for the master database.
15244
16
0
Only members of the sysadmin role or the database owner may set database options.
15246
16
0
Cannot dump the private key of certificate ‘%s’ because the private key cannot be found.
15247
16
0
User does not have permission to perform this action.
15248
11
0
Either the parameter @objname is ambiguous or the claimed @objtype (%s) is wrong.
15249
11
0
Error: Explicit @objtype ‘%s’ is unrecognized.
15250
16
0
The database name component of the object qualifier must be the name of the current database.
15251
16
0
Invalid ‘%s’ specified. It must be %s.
15252
16
0
The primary or foreign key table name must be given.
15253
11
0
Syntax error parsing SQL identifier ‘%s’.
15254
16
0
Users other than the database owner or guest exist in the database. Drop them before removing the database.
15255
11
0
‘%s’ is not a valid value for @autofix. The only valid value is ‘auto’.
15256
16
0
Usage: sp_certify_removable <dbname> [,’auto’]
15257
16
0
The database that you are attempting to certify cannot be in use at the same time.
15258
16
0
The database must be owned by a member of the sysadmin role before it can be removed.
15259
16
0
The DEFAULT_SCHEMA clause cannot be used with principals mapped to certificates or asymmetric keys.
15260
16
0
The format of the security descriptor string ‘%s’ is invalid.
15261
16
0
Usage: sp_create_removable <dbname>,<syslogical>,<sysphysical>,<syssize>,<loglogical>,<logphysical>,<logsize>,<datalogical1>,<dataphysical1>,<datasize1> [,<datalogical2>,<dataphysical2>,<datasize2>…<datalogical16>,<dataphysical16>,<datasize16>]
15262
10
0
Invalid file size entered. All files must be at least 1 MB.
15263
16
0
A SID in the security descriptor string ‘%s’ could not be found in an account lookup operation.
15264
16
0
Could not create the ‘%s’ portion of the database.
15265
16
0
An unexpected error has occurred in the processing of the security descriptor string ‘%s’.
15266
16
0
Cannot make ‘%s’ database removable.
15267
16
0
A security descriptor with name ‘%s’ already exists.
15268
10
1
Authentication mode is %s.
15269
16
0
Logical data device ‘%s’ not created.
15271
16
0
Invalid @with_log parameter value. Valid values are ‘true’ or ‘false’.
15272
10
0
The %s ‘%.*s’ is not trusted to execute.
15273
10
0
The decryption key is incorrect.
15274
16
0
Access to the remote server is denied because the current security context is not trusted.
15276
16
0
Cannot provision master key passwords for system databases.
15277
16
0
The only valid @parameter_value values are ‘true’ or ‘false’.
15278
16
0
Login ‘%s’ is already mapped to user ‘%s’ in database ‘%s’.
15279
16
0
You must add the us_english version of this message before you can add the ‘%s’ version.
15280
16
0
All localized versions of this message must be dropped before the us_english version can be dropped.
15281
10
0
SQL Server blocked access to %S_MSG ‘%ls’ of component ‘%.*ls’ because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of ‘%.*ls’ by using sp_configure. For more information about enabling ‘%.*ls’, search for ‘%.*ls’ in SQL Server Books Online.
15282
10
0
A key with name ‘%.*ls’ or user defined unique identifier already exists or you do not have permissions to create it.
15283
16
0
The name ‘%s’ contains too many characters.
15284
16
0
The database principal has granted or denied permissions to objects in the database and cannot be dropped.
15285
16
0
The special word ‘%s’ cannot be used for a logical device name.
15286
16
0
Terminating this procedure. The @action ‘%s’ is unrecognized. Try ‘REPORT’, ‘UPDATE_ONE’, or ‘AUTO_FIX’.
15287
16
0
Terminating this procedure. ‘%s’ is a forbidden value for the login name parameter in this procedure.
15288
10
0
Please specify one decryptor to decrypt a key.
15289
16
0
Terminating this procedure. Cannot have an open transaction when this is run.
15291
16
0
Terminating this procedure. The %s name ‘%s’ is absent or invalid.
15292
10
0
The row for user ‘%s’ will be fixed by updating its login link to a login already in existence.
15293
10
0
Barring a conflict, the row for user ‘%s’ will be fixed by updating its link to a new login.
15294
10
0
The number of orphaned users fixed by adding new logins and then updating users was %d.
15295
10
0
The number of orphaned users fixed by updating users was %d.
15296
16
0
General cryptographic failure.
15297
16
0
The certificate, asymmetric key, or private key data is invalid.
15299
16
0
The signature of the public key is invalid.
15300
11
0
No recognized letter is contained in the parameter value for General Permission Type (%s). Valid letters are in this set: %s .
15301
16
0
Collation ‘%s’ is supported for Unicode data types only and cannot be set at either the database or server level.
15302
11
0
Database_Name should not be used to qualify owner.object for the parameter into this procedure.
15303
11
0
The «user options» config value (%d) was rejected because it would set incompatible options.
15304
16
0
The severity level of the ‘%s’ version of this message must be the same as the severity level (%ld) of the us_english version.
15305
16
0
The @TriggerType parameter value must be ‘insert’, ‘update’, or ‘delete’.
15306
16
0
Cannot change the compatibility level of replicated or distributed databases.
15307
16
0
Could not change the merge publish option because the server is not set up for replication.
15309
16
0
Cannot alter the trustworthy state of the model or tempdb databases.
15310
16
1
Failed to configure user instance on startup. Error updating server metadata.
15311
16
0
The file named ‘%s’ does not exist.
15312
16
0
The file named ‘%s’ is a primary file and cannot be removed.
15313
10
0
The key is not encrypted using the specified decryptor.
15314
10
0
Either no algorithm has been specified or the bitlength and the algorithm specified for the key are not available in this installation of this operating system.
15315
10
0
The key ‘%.*ls’ is not open. Please open the key before using it.
15316
10
0
Global temporary keys are not allowed. You can only use local temporary keys.
15317
10
0
The master key file does not exist or has invalid format.
15318
10
0
All fragments for database ‘%s’ on device ‘%s’ are now dedicated for log usage only.
15319
17
0
Error: DBCC DBREPAIR REMAP failed for database ‘%s’ (device ‘%s’).
15320
16
0
An error occurred while decrypting %S_MSG ‘%.*ls’ that was encrypted by the old master key. The FORCE option can be used to ignore this error and continue the operation, but data that cannot be decrypted by the old master key will become unavailable.
15321
16
0
There was some problem removing ‘%s’ from sys.master_files.
15322
10
0
File ‘%s’ was removed from tempdb, and will take effect upon server restart.
15323
16
0
The selected index does not exist on table ‘%s’.
15324
16
0
The option %s cannot be changed for the ‘%s’ database.
15325
16
0
The current database does not contain a %s named ‘%ls’.
15326
10
0
No extended stored procedures exist.
15327
10
0
The database is now offline.
15328
10
0
The database is offline already.
15329
16
0
The current master key cannot be decrypted. If this is a database master key, you should attempt to open it in the session before performing this operation. The FORCE option can be used to ignore this error and continue the operation but the data encrypted by the old master key will be lost.
15330
11
0
There are no matching rows on which to report.
15331
11
0
The user ‘%s’ cannot take the action auto_fix due to duplicate SID.
15332
10
0
The private key is already set for this file. To change it you should drop and re-create the certificate.
15333
11
0
Error: The qualified @oldname references a database (%s) other than the current database.
15334
10
0
The %S_MSG has a private key that is protected by a user defined password. That password needs to be provided to enable the use of the private key.
15335
11
0
Error: The new name ‘%s’ is already in use as a %s name and would cause a duplicate that is not permitted.
15336
16
0
Object ‘%s’ cannot be renamed because the object participates in enforced dependencies.
15337
10
0
Caution: sys.sql_dependencies shows that other objects (views, procedures and so on) are referencing this object by its old name. These objects will become invalid, and should be dropped and re-created promptly.
15339
10
0
Creating ‘%s’.
15342
10
0
There is no private key provisioned for %S_MSG ‘%.*ls’.
15343
10
0
The username and/or password passed in is invalid or the current process does not have sufficient privileges.
15344
16
0
Ownership change for %S_MSG is not supported.
15345
16
0
An entity of type %S_MSG cannot be owned by a role, a group, or by principals mapped to certificates or asymmetric keys.
15346
16
0
Cannot change owner for an object that is owned by a parent object. Change the owner of the parent object instead.
15347
16
0
Cannot transfer an object that is owned by a parent object.
15348
16
0
Cannot transfer a schemabound object.
15349
16
0
Cannot transfer an MS Shipped object.
15350
16
0
An attempt to attach an auto-named database for file %.*ls failed. A database with the same name exists, or specified file cannot be opened, or it is located on UNC share.
15351
10
0
The CLR procedure/function/type being signed refers to an assembly that is not signed either by a strong name or an assembly.
15352
16
0
The %S_MSG cannot be dropped because one or more entities are either signed or encrypted using it.
15353
16
0
An entity of type %S_MSG cannot be owned by a role, a group, an approle, or by principals mapped to certificates or asymmetric keys.
15354
10
0
Usage: sp_detach_db <dbname>, [TRUE|FALSE], [TRUE|FALSE]
15356
16
0
The current application role has been dropped. The current security context contains no valid database user context.
15357
16
0
The current security context was set by «%ls». It cannot be reverted by statement «%ls».
15358
10
0
User-defined filegroups should be made read-only.
15359
16
0
Cannot add functional unit ‘%.*ls’ to component ‘%.*ls’. This unit has been already registered with the component.
15360
16
0
An error occurred while trying to load the xpstar dll to read the agent proxy account from LSA.
15361
16
0
An error occurred while trying to read the SQLAgent proxy account credentials from the LSA.
15362
16
0
An error occurred while trying to create the ‘%.*ls’ credential.
15364
16
1
Failed to generate a user instance of SQL Server. Only an integrated connection can generate a user instance. The connection will be closed.%.*ls
15365
16
1
Failed to generate a user instance of SQL Server. Only members of BuiltinUsers can generate a user instance. The connection will be closed.%.*ls
15366
16
1
Failed to generate a user instance of SQL Server due to low memory. The connection will be closed.%.*ls
15367
16
1
Failed to generate a user instance of SQL Server due to a failure in generating a unique user instance name. The connection will be closed.%.*ls
15368
16
1
Failed to generate a user instance of SQL Server due to a failure in reading registry keys. The connection will be closed.%.*ls
15369
16
1
Failed to generate a user instance of SQL Server due to a failure in impersonating the client. The connection will be closed.%.*ls
15370
16
1
Failed to generate a user instance of SQL Server due to a failure in copying database files. The connection will be closed.%.*ls
15371
16
1
Failed to generate a user instance of SQL Server due to a failure in creating user instance event. The connection will be closed.%.*ls
15372
16
1
Failed to generate a user instance of SQL Server due to a failure in starting the process for the user instance. The connection will be closed.%.*ls
15373
16
1
Failed to generate a user instance of SQL Server due to a failure in obtaining the user instance’s process information. The connection will be closed.%.*ls
15374
16
1
Failed to generate a user instance of SQL Server due to a failure in persisting the user instance information into system catalog. The connection will be closed.%.*ls
15375
16
1
Failed to generate a user instance of SQL Server due to a failure in making a connection to the user instance. The connection will be closed.%.*ls
15376
16
1
Failed to generate a user instance of SQL Server. Only the SQL Server Express version lets you generate a user instance. The connection will be closed.%.*ls
15377
16
1
Failed to configure user instance on startup. Error adding user to sysadmin role.
15378
16
1
Failed to configure user instance on startup. Error configuring system database entries in MASTER DB.
15380
16
1
Failed to configure user instance on startup. Error configuring system database paths in MASTER DB.
15381
16
1
Failed to generate a user instance of SQL Server due to a failure in updating security descriptor on the process of the user instance.
15382
16
1
Failed to generate a user instance of SQL Server due to failure in retrieving the user’s local application data path. Please make sure the user has a local user profile on the computer. The connection will be closed.%.*ls
15383
16
1
Generating user instances in SQL Server is disabled. Use sp_configure ‘user instances enabled’ to generate user instances.%.*ls
15384
16
1
Failed to configure user instance on startup. Error updating Resource Manager ID.
15385
16
0
No database principal is defined for sid ‘%.*ls’.
15386
16
0
Another batch in the session is changing security context, new batch is not allowed to start.
15387
11
0
If the qualified object name specifies a database, that database must be the current database.
15388
11
0
There is no user table matching the input name ‘%s’ in the current database or you do not have permission to access the table.
15389
11
0
sp_indexoption is not supported for XML or spatial indexes. Use ALTER INDEX instead.
15390
11
0
Input name ‘%s’ does not have a matching user table or indexed view in the current database.
15391
11
0
sp_indexoption is not supported for XML Index and the table has an XML index on it. Use ALTER INDEX instead to set the option for ALL the indexes.
15392
16
0
The specified option ‘%s’ is not supported by this edition of SQL Server and cannot be changed using sp_configure.
15393
16
0
An error occurred while decrypting the password for linked login ‘%.*ls’ that was encrypted by the old master key. The FORCE option can be used to ignore this error and continue the operation but the data encrypted by the old master key will be lost.
15394
16
0
Collation ‘%s’ is not supported by the operating system
15395
11
0
The qualified old name could not be found for item type ‘%s’.
15396
16
0
An asymmetric key with name ‘%s’ already exists or this asymmetric key already has been added to the database.
15397
16
0
The %S_MSG is not protected by a password. A decryption password cannot be used for this operation.
15398
11
0
Only objects in the master database owned by dbo can have the startup setting changed.
15399
11
0
Could not change startup option because this option is restricted to objects that have no parameters.
15401
11
0
Windows NT user or group ‘%s’ not found. Check the name again.
15402
11
0
‘%s’ is not a fixed server role.
15403
16
0
The server principal «%.*ls» does not exist, does not have server access, or you do not have permission.
15404
16
0
Could not obtain information about Windows NT group/user ‘%ls’, error code %#lx.
15405
11
0
Cannot use the special principal ‘%s’.
15406
16
0
Cannot execute as the server principal because the principal «%.*ls» does not exist, this type of principal cannot be impersonated, or you do not have permission.
15407
11
0
‘%s’ is not a valid Windows NT name. Give the complete name: <domainusername>.
15408
16
0
«%ls» cannot be called in this batch because a simultaneous batch has called it.
15409
11
0
‘%s’ is not a role.
15410
11
0
User or role ‘%s’ does not exist in this database.
15411
11
0
Database principal or schema ‘%s’ does not exist in this database.
15412
11
0
‘%s’ is not a known fixed role.
15413
11
0
Cannot make a role a member of itself.
15414
16
0
Cannot set compatibility level because database has a view or computed column that is indexed. These indexes require a SQL Server compatible database.
15416
16
0
Usage: sp_dbcmptlevel [dbname [, compatibilitylevel]]
15418
16
0
Only members of the sysadmin role or the database owner may set the database compatibility level.
15419
16
0
Supplied parameter sid should be binary(16).
15420
16
0
The group ‘%s’ does not exist in this database.
15421
16
0
The database principal owns a database role and cannot be dropped.
15422
16
0
Application roles can only be activated at the ad hoc level.
15425
16
0
No server principal is defined for sid ‘%.*ls’.
15426
16
0
You must specify a provider name with this set of properties.
15427
16
0
You must specify a provider name for unknown product ‘%ls’.
15428
16
0
You cannot specify a provider or any properties for product ‘%ls’.
15429
16
0
‘%ls’ is an invalid product name.
15431
16
0
You must specify the @rolename parameter.
15432
16
0
Stored procedure ‘%s’ can only be executed at the ad hoc level.
15433
16
0
Supplied parameter sid is in use.
15434
16
0
Could not drop login ‘%s’ as the user is currently logged in.
15435
10
0
Database successfully published.
15436
10
0
Database successfully enabled for subscriptions.
15437
10
0
Database successfully published using merge replication.
15438
10
0
Database is already online.
15439
10
0
Database is now online.
15440
10
0
Database is no longer published.
15441
10
0
Database is no longer enabled for subscriptions.
15442
10
0
Database is no longer enabled for merge publications.
15443
10
0
Checkpointing database that was changed.
15448
16
0
Encryption by the machine key cannot be added to the service master key because the service master key cannot be decrypted or does not exist.
15450
10
0
New language inserted.
15451
16
0
Dropping an encryption from the service master key failed. No encryption by the machine key exists.
15452
10
0
No alternate languages are available.
15453
10
0
us_english is always available, even though it is not in syslanguages.
15454
10
0
Language deleted.
15455
16
0
Adding an encryption to the service master key failed. An encryption by the machine key already exists.
15457
10
0
Configuration option ‘%ls’ changed from %ld to %ld. Run the RECONFIGURE statement to install.
15458
10
0
Database removed.
15459
10
0
In the current database, the specified object references the following:
15460
10
0
In the current database, the specified object is referenced by the following:
15461
10
0
Object does not reference any object, and no objects reference it.
15462
10
0
File ‘%s’ closed.
15463
10
0
Device dropped.
15464
16
0
Unsupported private key format or key length.
15465
16
0
The private key password is invalid.
15466
16
0
An error occurred during decryption.
15468
16
0
An error occurred during the generation of the %S_MSG.
15469
10
0
No constraints are defined on object ‘%ls’, or you do not have permissions.
15470
10
0
No foreign keys reference table ‘%ls’, or you do not have permissions on referencing tables.
15471
10
0
The text for object ‘%ls’ is encrypted.
15472
10
0
The object ‘%ls’ does not have any indexes, or you do not have permissions.
15474
16
0
Invalid private key. The private key does not match the public key of the %S_MSG.
15475
10
0
The database is renamed and in single user mode.
15477
10
0
Caution: Changing any part of an object name could break scripts and stored procedures.
15482
16
0
Cannot change the owner of a table that has an indexed view.
15490
10
0
The dependent aliases were also dropped.
15497
10
0
Could not add login using sp_addlogin (user = %s). Terminating this procedure.
15499
10
0
The dependent aliases were mapped to the new database owner.
15500
10
0
The dependent aliases were dropped.
15502
10
0
Setting database owner to SA.
15503
10
0
Giving ownership of all objects to the database owner.
15504
10
0
Deleting users except guest and the database owner from the system catalog.
15505
16
0
Cannot change owner of object ‘%ls’ or one of its child objects because the new owner ‘%ls’ already has an object with the same name.
15506
16
0
An error occurred while signing.
15507
16
0
A key required by this operation appears to be corrupted.
15508
16
0
An error occurred while generating a key required by this operation.
15509
16
0
The password cannot be dropped because another database may be using it.
15510
16
0
Cannot enable a login that has an empty password.
15511
10
0
Default bound to column.
15512
10
0
Default bound to data type.
15513
10
0
The new default has been bound to columns(s) of the specified user data type.
15514
10
0
Rule bound to table column.
15515
10
0
Rule bound to data type.
15516
10
0
The new rule has been bound to column(s) of the specified user data type.
15517
16
0
Cannot execute as the database principal because the principal «%.*ls» does not exist, this type of principal cannot be impersonated, or you do not have permission.
15518
16
0
Cannot execute as the Windows token. It is not valid, or you do not have permission.
15519
10
0
Default unbound from table column.
15520
10
0
Default unbound from data type.
15521
10
0
Columns of the specified user data type had their defaults unbound.
15522
10
0
Rule unbound from table column.
15523
10
0
Rule unbound from data type.
15524
10
0
Columns of the specified user data type had their rules unbound.
15525
10
0
sp_checknames is used to search for non 7-bit ASCII characters.
15526
10
0
in several important columns of system tables. The following
15527
10
0
columns are searched:
15528
10
0
In master:
15529
16
0
Cannot execute as the ticket. It is not valid, or you do not have permission.
15530
16
0
The %S_MSG with name «%.*ls» already exists.
15531
16
0
The security descriptor information is not valid.
15532
16
0
The security descriptor is invalid because it does not contain information about its owner or about its primary group.
15533
16
0
Invalid data type is supplied in the ‘%ls’ statement.
15534
16
0
Cookie generation failed in the ‘%ls’ statement.
15535
16
0
Cannot set a credential for principal ‘%.*ls’.
15536
10
0
In all databases:
15537
16
0
Login ‘%.*ls’ does not have access to server.
15538
16
0
Login ‘%.*ls’ does not have access to database.
15539
16
0
User ‘%s’ cannot be dropped, it can only be disabled. The user is already disabled in the current database.
15540
16
0
The identity string is too long. The identity string should contain no more than %d characters.
15541
16
0
Cannot drop the credential ‘%.*ls’ because it is used by a server principal.
15542
10
0
Cannot create a key without specifying an encryptor.
15556
10
0
Cannot decrypt or encrypt using the specified %S_MSG, either because it has no private key or because the password provided for the private key is incorrect.
15557
10
0
There is already a %S_MSG by %S_MSG ‘%.*ls’.
15558
10
0
Cannot drop %S_MSG by %S_MSG ‘%.*s’.
15559
10
0
Cannot drop %S_MSG ‘%.*ls’ because there is a %S_MSG mapped to it.
15560
10
0
Cannot add or drop a signature on ‘%.*ls’ because only modules can be signed.
15561
10
0
Signatures based on certificates or asymmetric keys are the only options supported in this version of the product.
15562
10
0
The module being executed is not trusted. Either the owner of the database of the module needs to be granted authenticate permission, or the module needs to be digitally signed.
15563
10
0
The %S_MSG has no private key set for it.
15574
10
0
This object does not have any statistics.
15575
10
0
This object does not have any statistics or indexes.
15576
16
0
You cannot set network name on server ‘%ls’ because it is not a linked SQL Server.
15577
10
0
Warning: A linked server that refers to the originating server is not a supported scenario. If you wish to use a four-part name to reference a local table, please use the actual server name rather than an alias.
15578
16
0
There is already a master key in the database. Please drop it before performing this statement.
15579
16
0
Adding an encryption to the symmetric key failed. An encryption by the same %S_MSG ‘%.*s’ may already exist.
15580
16
0
Cannot drop %S_MSG because %S_MSG ‘%.*s’ is encrypted by it.
15581
16
0
Please create a master key in the database or open the master key in the session before performing this operation.
15583
10
0
The module being signed is marked to execute as owner. If the owner changes the signature will not be valid.
15584
10
0
An error occurred while decrypting %S_MSG ‘%.*ls’ that was encrypted by the old master key. The error was ignored because the FORCE option was specified.
15585
10
0
The current master key cannot be decrypted. The error was ignored because the FORCE option was specified.
15586
16
0
Error in synchronizing system certificates between master and resource database.
15587
16
0
Cannot change owner of Assembly ‘%.*ls’ since dependent assembly ‘%.*ls’ is not owned by the new owner.
15588
10
0
The old and new master keys are identical. No data re-encryption is required.
15589
16
0
Cannot revert the current security context because the cookie is invalid.
15590
16
0
Can only use the ‘No Revert’ or ‘Cookie’ options with the ‘Execute As’ statement at the adhoc level.
15591
16
0
The current security context cannot be reverted using this statement. A cookie may or may not be needed with ‘Revert’ statement depending on how the context was set with ‘Execute As’ statement.
15592
16
0
Cannot unset application role because none was set or the cookie is invalid.
15593
16
0
An error occurred while decrypting the password for linked login ‘%.*ls’ that was encrypted by the old master key. The error was ignored because the FORCE option was specified.
15594
16
0
The password is already provisioned for the database ‘%.*ls’
15595
16
0
The password cannot be dropped because it is not provisioned for the database ‘%.*ls’
15596
10
0
Warning: use of a UNIQUE index, PRIMARY KEY constraint, or UNIQUE constraint on a table with row-level security can allow information disclosure.
15597
10
0
Warning: use of an IDENTITY column on a table with row-level security can allow information disclosure.
15598
10
0
Warning: use of an indexed view on a table with row-level security can allow information disclosure.
15599
10
0
Auditing and permissions can’t be set on local temporary objects.
15600
15
0
An invalid parameter or option was specified for procedure ‘%s’.
15601
16
0
Full-Text Search is not enabled for the current database. Use sp_fulltext_database to enable Full-Text Search. The functionality to disable and enable full-text search for a database is deprecated. Please change your application.
15612
16
0
DBCC DBCONTROL error. Database was not made read-only.
15615
16
0
DBCC DBCONTROL error. Database was not made single user.
15622
10
0
No permission to access database ‘%s’.
15625
10
0
Option ‘%ls’ not recognized for ‘%ls’ parameter.
15626
10
0
You attempted to acquire a transactional application lock without an active transaction.
15627
10
0
sp_dboption command failed.
15635
16
0
Cannot execute ‘%ls’ because the database is in read-only access mode.
15645
16
0
Column ‘%ls’ does not exist.
15646
16
0
Column ‘%ls’ is not a computed column.
15647
10
0
No views with schema binding reference table ‘%ls’.
15650
10
0
Updating %s
15651
10
0
%d index(es)/statistic(s) have been updated, %d did not require update.
15652
10
0
%s has been updated…
15653
10
0
%s, update is not necessary…
15654
10
0
Table %s: cannot perform the operation on the table because its clustered index is disabled.
15656
16
0
Cannot create user defined types from XML data type.
15657
16
0
Vardecimal storage format is not available in system database ‘%s’.
15658
16
0
Cannot run sp_resetstatus against a database snapshot.
15659
16
0
The schema ‘%ls’ specified for parameter schema_name does not exist.
15660
16
0
Compressing XML, spatial, columnstore or hash indexes is not supported by the stored procedure sp_estimate_data_compression_savings.
15661
16
0
Compressing temporary tables is not supported by the stored procedure sp_estimate_data_compression_savings.
15662
16
0
Compressing tables with sparse columns or column sets is not supported by the stored procedure sp_estimate_data_compression_savings.
15663
16
0
Feature «sp_addserver» is no longer supported. Replace remote servers by using linked servers.
15664
16
0
Cannot set key ‘%ls’ in the session context. The key has been set as read_only for this session.
15665
16
0
The value was not set for key ‘%ls’ because the total size of keys and values in the session context would exceed the 1 MB limit.
15666
16
0
Cannot set key ‘%ls’ in the session context. The size of the key cannot exceed 256 bytes.
15667
16
0
Reset session context is not allowed when a another batch is active in session.
15701
16
0
Statement ‘%.*ls’ failed, because it attempted to set the Automatic Tuning option ‘%.*ls’ multiple times.
15702
16
1
Cannot perform action because Automatic Tuning cannot be enabled on system database %.*ls.
15703
10
1
Setting Automatic Tuning option ‘%.*ls’ to %.*ls for database ‘%.*ls’.
15704
16
0
Automatic Tuning option ‘%.*ls’ is disabled by system.
15705
16
1
Automatic Tuning option %.*ls cannot be enabled, because Query Store is not turned on.
15706
16
1
Automatic Tuning option %.*ls cannot be enabled, because Query Store is in READ_ONLY mode.
15707
16
0
Automatic Tuning is only available for enterprise customers.
15716
15
1
Only one Automatic Tuning option can be given in ALTER DATABASE statement.
- Remove From My Forums
-
Question
-
I’m not able to Create Windows logins for other users connecting SQL Server installed on my Windows 7 machine. Form example if I enter Kathy as the Login Name It errors with:
Create failed for Login ‘Kathy’. (Microsoft.SqlServer.Smo)
An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
‘Kathy’ is not a valid Windows NT name. Give the complete name: <domain\username>. (Microsoft SQL Server, Error: 15407)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=09.00.4053&EvtSrc=MSSQLServer&EvtID=15407&LinkId=20476OK so I don’t have a domain so I tried using the host name: Vic-Win7\Kathy (or Vic-Vista\Kathy another machine) and I get the same error. I have several XP machines that will need to access the databases which I’m not able to do because I can’t
create the ODBC data sources unless I use SQL logins and that doesn’t work to well. I have enabled Remote logins.This seems so basic but I just can’t get it. I do have q Windows Login setup for myself and I can log in on my using my own login.
Thanks,
Vic
Visual Basic; Access; PHP; SQL Server; MySQL Developer
Answers
-
Hi VicSpain,
To connect SQL Server with Windows Authentication in a workgroup, we need to have the same account and same password on both machines. If we want to allow other users from the
current workgroup to access the SQL Server on the computer host Windows 7, we need to create the mirror accounts. Please follow these steps or refer to this
link to create the mirror accounts:1.
To open User Accounts, click the
Start button , click Control Panel, click
User Accounts and Family Safety, and then click User Accounts.2.
Click
Manage another account. If you’re prompted for an administrator password or confirmation, type the password or provide confirmation.3.
Click
Create a new account.4.
Type the name you want to give the user account, click an account type, and then click
Create Account.However, for
a workgroup, we always recommend to use SQL authentication instead of a Windows Authentication since the workgroup are not trusted.If there are any results, please feel free to let me know.
Thanks,
Weilin Qiao-
Marked as answer by
Monday, November 29, 2010 4:18 AM
-
Marked as answer by
- Remove From My Forums
-
Question
-
Hi friends,
Iam new to sql server. I was installed sql server 2008 r2 enterprise edition. I was connected with windows authentication.. after that when Im trying to create new
login. Im getting error asTITLE: Microsoft SQL Server Management Studio
——————————Create failed for Login ‘teja’. (Microsoft.SqlServer.Smo)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600.1+((KJ_RTM).100402-1540+)&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Create+Login&LinkId=20476
——————————
ADDITIONAL INFORMATION:An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)
——————————
‘teja’ is not a valid Windows NT name. Give the complete name: <domainusername>. (Microsoft SQL Server, Error: 15407)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=10.50.1600&EvtSrc=MSSQLServer&EvtID=15407&LinkId=20476
Pls tell me how to create new login. whats my wrong also
Answers
-
The easiest way to create a new login is to use the command CREATE LOGIN. The full syntax is in Books Online. Using SSMS only means that you have to guess what keywords the various UI controls map to.
In any case, what you need to know is that there are two means of authentication in SQL Server: Windows authentication and SQL authentication.
With Windows authentication you first log in to Windows and then log into SQL Server without specifying a password; SQL Server relies on the information provided by Windows. A Windows login is always on the form DOMAINUSERNAME. To create a Windows login
you say:CREATE LOGIN [DomainUsername] FROM WINDOWS
With SQL authentication, you specify a username and a password, and SQL Server authenticates you. How you logged into Windows doesn’t matter. An SQL login is a name without a backslash in it. An example of a creation of an SQL login:
CREATE LOGIN sture WITH PASSWORD = '(DKLn23%$'
It is not clear from your post which sort of login you intended to create, but to its form «tejo» is an SQL Server login, but it appears from the message that you in the radion button in the dialog selected Windows login.
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
-
Proposed as answer by
Sunday, November 6, 2011 10:44 PM
-
Marked as answer by
KJian_
Monday, November 14, 2011 6:47 AM
-
Proposed as answer by
Содержание статьи:
-
- SQL-сервер не найден или недоступен, ошибки соединения с SQL-сервером
- Ошибка SQL-сервера 26
- Ошибка SQL-сервера 18456
- Не удалось запустить SQL-server — код ошибки 3417
- Повреждена база данных
- Код ошибки SQL-сервера 945
- Код ошибки SQL-сервера 5172
- Ошибка SQL-сервера 823
- Ошибка SQL-сервера 8946
- Другие ошибки SQL Server
- Код ошибки SQL-сервера 1814
- Код ошибки SQL-сервера 1067
- SQL-сервер запускается, но работает слишком медленно
- SQL-сервер не найден или недоступен, ошибки соединения с SQL-сервером
- Если SQL-сервер не найден, убедитесь, что ваш экземпляр SQL-сервера действительно установлен и запущен. Для этого зайдите на компьютер, где он установлен, запустите диспетчер конфигурации SQL и проверьте, есть ли там тот экземпляр, к которому вы пытаетесь подключиться и запущен ли он. Нелишним будет также получить отчет об обнаружении компонентов SQL-серверов.
- Если вы проделали п1. и не обнаружили источник проблемы, возможно, неверно указан IP-адрес компьютера или номер порта TCP. Перепроверьте их настройки.
- Причиной того, что невозможно подключиться к SQL-серверу, также может быть сеть, убедитесь, что компьютер с SQL-сервером доступен по сети.
- Проверьте, может ли клиентское приложение, установленное на том же компьютере, что и сервер, подключиться к SQL-серверу. Запустите SQL Server Management Studio(SSMS), в диалоговом окне “Подключиться к серверу” выберите тип сервера Database Engine, укажите способ аутентификации “Аутентификация Windows”, введите имя компьютера и экземпляра SQL-сервера. Проверьте подключение.
Обратите внимание, что многие сообщения об ошибках могут быть не показаны или не содержат достаточной информации для устранения проблемы. Это сделано из соображений безопасности, чтобы при попытке взлома злоумышленники не могли получить информацию об SQL-сервере. Полные сведения содержатся в логе ошибок, который обычно хранится по адресу C:Program FilesMicrosoft SQL ServerMSSQL13.MSSQLSERVERMSSQLLogERRORLOG, или там, куда его поместил администратор системы.
Ошибка SQL-сервера 26
Одна из наиболее часто встречающихся ошибок подключения к SQL-серверу, обычно связана с тем, что в настройках SQL-сервера не разрешены или ограничены удаленные соединения. Чтобы это исправить, попробуйте:
- в SSMS в настройках SQL-сервера включите аутентификацию Windows
- для брандмауэра Windows создайте новое правило, которое разрешает подключение для всех программ и протоколов с указанного IP-адреса
- убедитесь, что запущена служба SQL Server Browser
Ошибка SQL-сервера 18456
Эта ошибка означает, что попытка подключиться к серверу не успешна из-за проблем с именем пользователя или паролем. По коду ошибки в журнале ошибок можно узнать более точную причину, чтобы устранить ее.
Не удалось запустить SQL-server — код ошибки 3417
Возникает в случае, если были изменены настройки Windows или перемещена папка с файлами MSSQL.
- зайдите в C:Program FilesMicrosoft SQLServerMSSQL.1MSSqLData — БезопасностьНастройки доступа — Учетная запись сетевой службы — добавьте учетную запись сетевой службы
- проверьте, что MDF-файл не сжимается. Если это не так, отключите “Сжимать содержимое для экономии места на диске” в свойствах файла
Иногда ни один из этих способов не помогает, это значит, что файлы БД повреждены и ее придется восстанавливать из резервной копии.
Повреждена база данных
Код ошибки SQL-сервера 945
Ошибка 945 возникает, когда БД SQL-сервера помечена как IsShutdown. Проверьте, достаточно ли места на диске, достаточно ли прав у учетной записи для операций с БД, файлы MDF и LDF не должны быть помечены “Только для чтения”.
Код ошибки SQL-сервера 5172
SQL-сервер хранит свою физическую БД в первичном файле, в котором информация разбита постранично. Первая страница содержит информацию о заголовке mdf-файла и называется страницей заголовка. Она состоит из разнообразной информации о БД, такой как размер файла, подпись и т.д. В процессе прикрепления MDF на SQL-сервере часто возникает ошибка 5172. Это в основном происходит, если MDF-файл поврежден, информация в его заголовке тоже и соответственно сложно добраться до данных. Причиной может быть вирус, аварийное выключение системы, ошибка оборудования.
Ошибка SQL-сервера 823
SQL использует API Windows для операций ввода-вывода, но кроме завершения этих операций SQL проверяет все ошибки обращений к API. Если эти обращения несовместимы с ОС, появляется ошибка 823. Сообщение об ошибке 823 означает, что существует проблема с базовым оборудованием для хранения данных или с драйвером, который находится на пути запроса ввода-вывода. Пользователи могут столкнуться с этой ошибкой, если в файловой системе есть противоречия или поврежден файл базы данных.
Ошибка SQL-сервера 8946
Основной причиной ошибки 8946 так же, как и для 5172, является повреждение заголовков страниц БД SQL вследствие сбоя питания, вирусной атаки, отказа оборудования — SQL-сервер больше не может прочесть эти страницы.
Перечисленные ошибки 945, 5172, 823, 8946 можно устранить двумя методами:
- если у вас есть свежая резервная копия базы — восстановить базу из этой копии
- можно попробовать использовать специализированное ПО, такое как SQL Recovery Tool, чтобы восстановить поврежденные файлы
Желательно определить, что именно привело к возникновению ошибок и принять меры, чтобы это не повторялось — заменить плохо работающее оборудование, повысить информационную безопасность.
Другие ошибки SQL
Код ошибки SQL-сервера 1814
SQL-сервер не может создать базу данных tempdb. Убедитесь, что на выделенном под нее диске достаточно места и что у учетной записи хватает прав для записи в указанную директорию.
Код ошибки SQL-сервера 1067
Эта ошибка может возникать по разным причинам. Наиболее часто оказывается, что повреждены или отсутствуют конфигурационные файлы, SQL-сервер обращается к поврежденным системным файлам, ошибочные данные пользователя, нет информации про лицензию. В самых тяжелых случаях придется переустанавливать SQL-сервер. Но иногда помогает восстановление поврежденных файлов или изменение настроек SQL-сервера — вы можете создать новую учетную запись в домене и использовать ее для службы MSSQL.
SQL-сервер запускается, но работает слишком медленно
Проанализируйте журнал сервера, индексы (фрагментацию), запросы, задания, возможность взаимных блокировок. Причин может быть масса.
Мы работаем с разными версиями SQL-сервера уже много лет, знакомы со всевозможными инструкциями SQL-сервера, видели самые разные варианты его настройки и использования на проектах у своих клиентов. В целом мы можем выделить четыре основных источника неполадок:
- Индексы — причина проблем номер один. Неправильные индексы, отсутствующие индексы, слишком много индексов и подобное. Чаще всего при проблеме с индексами пользователи или администраторы базы данных не получают сообщения об ошибке, они просто видят, что база работает очень медленно и докопаться до причин бывает очень нелегко
- изначально плохая архитектура сервера баз данных — ошибка, которую очень сложно и дорого исправлять на этапе, когда база уже используется
- плохой код, в котором возможны блокировки и тупиковые места
- использование конфигурации по умолчанию,
Если у вас не получается устранить ошибки сервера SQL-server самостоятельно, если они появляются снова и снова, то скорее всего в основе лежит одна из этих причин. В таком случае — если у вас произошла ошибка с SQL сервером, ваше ПО не видит SQL-сервер, либо нужно развернуть кластер SQL-серверов — вы всегда можете обратиться за консультацией и технической поддержкой к специалистам Интегруса, отправив заявку с сайта, написав на e-mail, либо позвонив в колл-центр нашей компании.
SQLServer Error 15404 can be resolved with Bobcares by your side.
At Bobcares, we offer solutions for every query, big and small, as a part of our SQL Server Support.
Let’s take a look at how our Support Team is ready to help customers resolve SQLServer Error 15404.
How to resolve SQLServer Error 15404
SQL server error 15404 occurs due to the specification of an invalid principal. Furthermore, the error may also pop up when the impersonation of a Windows account fails due to no full trust relationship between the domain of the Windows account and the SQL Server service account.
For instance, suppose we run a few high privilege T-SQL statements like sp_addsrvrolemember or Create Login, we may find ourselves facing Error 15404.
In this scenario, we will see notice messages in PALLOG. In case the PALLOG is disabled, we have to enable it manually by creating /var/opt/mssql/logger.ini with the following content:
[Output:sql] type=File filename=/var/opt/mssql/log/pallog.txt [Logger:security] level=debug outputs=sql
Let’s take a look at the messages in PALLOG:
03/12/2022 12:36:56.448761588 Debug [security.kerberos] <0000040947/0x00000200> Processing SSPI operation 0x0000000F 03/12/2022 12:36:56.439366379 Error [security.ldap] <0000040947/0x00000200> Initializing credentials for use in new cache failed: Keytab contains no suitable keys for red4$@SQLREPRO.EDU 03/12/2022 12:36:56.439613575 Debug [security.kerberos] <0000040947/0x00000200> Import name [ADMINISTRATOR@SQLREPRO.EDU] returned [ADMINISTRATOR@SQLREPRO.EDU] 03/12/2022 12:36:56.439633375 Debug [security.kerberos] <0000040947/0x00000200> Import name [red4$] returned [red4$] 03/12/2022 12:36:56.439753473 Debug [security.kerberos] <0000040947/0x00000200> Import name [RED4$] returned [RED4$] 03/12/2022 12:36:56.439905471 Debug [security.kerberos] <0000040947/0x00000200> Import name [red4$] returned [red4$] 03/12/2022 12:36:56.440014469 Error [security.kerberos] <0000040947/0x00000200> GSS MAJOR: 851968 GSS MINOR: 39756033 Error acquiring credentials in AcquireCredCaseInsensitive 03/12/2022 12:36:56.440029069 Error [security.kerberos] <0000040947/0x00000200> Unspecified GSS failure. Minor code may provide more information 03/12/2022 12:36:56.440039869 Error [security.kerberos] <0000040947/0x00000200> No key table entry found for red4$@SQLREPRO.EDU 03/12/2022 12:36:56.440053069 Debug [security.kerberos] <0000040947/0x00000200> SSPI operation 0x0000000F returned status: KerberosStream.cpp:2021 Operation unsuccessful 03/12/2022 12:36:56.440119868 Debug [security.kerberos.libos] <0000040961/0x0000020c> GetSecContextByUserABI() return value: 0x80090304 03/12/2022 12:36:56.468617991 Debug [security.kerberos.libos] <0000040961/0x0000020c> QueryContextAttributes() return value: 0x00000000 03/12/2022 12:36:56.468748289 Debug [security.kerberos.libos] <0000040961/0x0000020c> QueryContextAttributes() return value: 0x00000000 03/12/2022 13:56:26.489370580 Debug [security.kerberos.libos] <0000040961/0x0000020c> LookupAccountSid() return value: 0x00000001
As seen above, queries like Create login require checking permissions. The first time this is done, current permission is invalidated. When we repeat it, the permission check is rechecked. Furthermore, during the permission check, the SQL Server will go through the myssql.keytab to find the machine entry key or MSA key
In case the SQL Server cannot find the entries or finds invalid entries, it results in an error.
If we find ourselves facing this particular error, our Support Engineers suggest ensuring the Windows principal exists in addition to not being misspelled. Here are a few more troubleshooting tips courtesy of our Support Team to resolve this issue:
- Ensure we use an account from the same Windows user domain for the SQL Server service.
- If SQL Server uses a machine account like Local System or Network System, the machine has to be trusted by the Windows User domain.
- Use a SQL Server account
[Looking for a solution to another query? We are just a click away.]
Conclusion
To sum up, our skilled Support Engineers at Bobcares demonstrated how to fix SQLServer Error 15404.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED
- Remove From My Forums
-
Question
-
I am getting the following error message when trying to access the instance of the Action request system on my SQL Server :
ARERR [90] Cannot establish a network connection to the AR System server : pete-qxm9ydauvr. (0) : RPC: Program not registereduser: Demo, server: pete-qxm9ydauvr.
Unable to successfully log in to any server.
In my error log I have the following:
2009-10-14 14:46:51.35 server Copyright (C) 1988-2000 Microsoft Corporation.
2009-10-14 14:46:51.35 server All rights reserved.
2009-10-14 14:46:51.35 server Server Process ID is 504.
2009-10-14 14:46:51.35 server Logging SQL Server messages in file ‘C:Program FilesMicrosoft SQL ServerMSSQLlogERRORLOG’.
2009-10-14 14:46:51.37 server SQL Server is starting at priority class ‘normal'(2 CPUs detected).
2009-10-14 14:46:51.40 server SQL Server configured for thread mode processing.
2009-10-14 14:46:51.40 server Using dynamic lock allocation. [2500] Lock Blocks, [5000] Lock Owner Blocks.
2009-10-14 14:46:51.43 server Attempting to initialize Distributed Transaction Coordinator.
2009-10-14 14:46:53.45 spid3 Starting up database ‘master’.
2009-10-14 14:46:53.60 server Using ‘SSNETLIB.DLL’ version ‘8.0.194’.
2009-10-14 14:46:53.60 spid5 Starting up database ‘model’.
2009-10-14 14:46:53.62 server SQL server listening on Shared Memory, Named Pipes.
2009-10-14 14:46:53.62 server SQL Server is ready for client connections
2009-10-14 14:46:53.64 spid3 Server name is ‘PETE-QXM9YDAUVR’.
2009-10-14 14:46:53.64 spid8 Starting up database ‘msdb’.
2009-10-14 14:46:53.64 spid9 Starting up database ‘pubs’.
2009-10-14 14:46:53.64 spid10 Starting up database ‘Northwind’.
2009-10-14 14:46:53.64 spid11 Starting up database ‘ARSystem’.
2009-10-14 14:46:54.17 spid5 Clearing tempdb database.
2009-10-14 14:46:54.92 spid5 Starting up database ‘tempdb’.
2009-10-14 14:46:54.98 spid3 Recovery complete.
2009-10-14 15:00:44.70 spid51 Using ‘xpstar.dll’ version ‘2000.80.194’ to execute extended stored procedure ‘sp_MSgetversion’.
2009-10-14 16:25:24.56 spid51 Error: 15457, Severity: 0, State: 1
2009-10-14 16:25:24.56 spid51 Configuration option ‘show advanced options’ changed from 0 to 1. Run the RECONFIGURE statement to install..
2009-10-14 16:25:24.64 spid51 Using ‘xplog70.dll’ version ‘2000.80.194’ to execute extended stored procedure ‘xp_msver’.I have checked every configuration setting that I can think of and even had some assistance and we still cannot find anything that would get rid of this error and allow me to access my remedy application. I would appreciate any assistance on this.
Answers
-
Did you remotely connect to your SQL Server? It looks that the TCP/IP protocol was not enabled on your SQL Server. Please enable it first via running server network utility C:Program Files (x86)Microsoft SQL Server80ToolsBinnsvrnetcn.exe, enable TCP/IP protocol and check if the TCP port is 1433. Then restart your sql server service. Check your sql server error log again to see if there is information regarding listening on the tcp port 1433. If no, please run «netstat -nab >d:portlist.txt» from command line to check which process is using the tcp port and kill the process. Also please make sure that your windows firewall has allowed the connection on the TCP port 1433.
At the client, run «telnet servername 1433» from command line to make sure that you can connect to the sql server listening tcp port. If OK, try connection again.
Please remember to mark the replies as answers if they help and unmark them if they provide no help
-
Marked as answer by
Tuesday, October 27, 2009 4:22 AM
-
Marked as answer by