Home » SQL Server » Page 3

SQL Server

SQL Server Error : 10025, Severity: 16. Provider caused a server fault in an ext

SQL Server Error : 10025 Details

SQL Server Error: 10025 Severity: 16 Event Logged or not: No Description: Provider caused a server fault in an external process. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL,
Read the rest

SQL Server Error : 21396, Severity: 16. The value specified for the @type parame

SQL Server Error : 21396 Details

SQL Server Error: 21396 Severity: 16 Event Logged or not: No Description: The value specified for the @type parameter of sp_addsubscriber or the @subscriber_type parameter of sp_addsubscription is not valid. See SQL Server Books Online for a list of valid values. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
Read the rest

SQL Server Error : 1001, Severity: 16. Line %d: Length or precision specificati

SQL Server Error : 1001 Details

SQL Server Error: 1001 Severity: 16 Event Logged or not: No Description: Line %d: Length or precision specification %d is invalid. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1, N'Logging SQL Server messages in file', NULL, NULL, N'asc'
Go

The parameters for XP_READERRRORLOG are:
1. Value … Read the rest

SQL Server Error : 10010, Severity: 16. The data necessary to complete this oper

SQL Server Error : 10010 Details

SQL Server Error: 10010 Severity: 16 Event Logged or not: No Description: The data necessary to complete this operation was not yet available to the provider. Severity 16 Description: Indicates general errors that can be corrected by the user.

This event is logged when the server did not register with DCOM within the required time-out period.

 

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.… Read the rest

SQL Server Error : 161, Severity: 15. Rule contains more than one variable.

SQL Server Error : 161 Details

SQL Server Error: 161 Severity: 15 Event Logged or not: No Description: Rule contains more than one variable. Severity 15 Description: Indicates syntax errors in the Transact-SQL command.

Causes for SQL Srver Error 161

Sql Server Odbc Driver In client Side where we face SQL Server Error: 161 And SQL Server Error: 17

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog
Read the rest

SQL Server Error : 1480, Severity: 10. The mirrored database “%.*ls” is changin

SQL Server Error : 1480 Details

SQL Server Error: 1480 Severity: 10 Event Logged or not: No Description: The mirrored database “%.*ls” is changing roles from “%ls” to “%ls” due to %S_MSG. Severity 10 Description: Informational messages that return status information or report errors that are not severe. For compatibility reasons, the Database Engine converts severity 10 to severity 0 before returning the error information to the calling application.

Cause of Error SQL Server 1480

Availability Group issues – Failover

In a availabillity Group when second server of the Availability Group issues this information message is recorded with error sql server 1480, is that when an availability group fails over there are other actions may need to be performed. A … Read the rest

SQL Server Error : 14151, Severity: 18. Replication-%s: agent %s failed. %s

SQL Server Error : 14151 Details

SQL Server Error: 14151 Severity: 18 Event Logged or not: Yes Description: Replication-%s: agent %s failed. %s Severity 18 Description: Indicates a problem in the Database Engine software, but the statement completes execution, and the connection to the instance of the Database Engine is maintained. The system administrator should be informed every time a message with a severity level of 18 occurs.

Relate errors below:

error 14151, severity: 18, state: 1

event id 14151

replication the last step did not log any message

the process could not execute ‘sp_replcmds’ on source

mssql_repl error number: mssql_repl20011

the process could not execute ‘sp_mspub_adjust_identity

sql replication log reader agent fails

Cause of Error sql server 14151

“SQL … Read the rest

SQL Server Error : 15517, Severity: 16. Cannot execute as the database principal

SQL Server Error : 15517 Details

SQL Server Error: 15517 Severity: 16 Event Logged or not: No Description: 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. Severity 16 Description: Indicates general errors that can be corrected by the user.

Reading sql server error log location from SQL Query

Identifying SQL Server Error Log File used by SQL Server Database Engine can be done by reading SQL Server Error Logs. DBA can execute the XP_READERRORLOG extended stored procedure to read the SQL Server Error Log and search for its location used by the instance of SQL Server.

USE master
Go
xp_readerrorlog 0, 1,
Read the rest