Table of Contents
SQL Server Error: 1418
Severity: 16
Event Logged or not: No
Description:
The server network address “%.*ls” can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.
Severity 16 Description:
Indicates general errors that can be corrected by the user.
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
Check whose account is executing the SQL server by going to services.msc. Assign the identical credentials to the sql server and sql server agent services.
In mirroring check following:
Step 1 should be duplicated on the mirror database server. Provide the same credentials as for the primary server. If the user does not exist, create one using the identical credentials on both systems.
Now that you have the principal server, go to Security->Login in SQL Server and create a new login. Assign Sysadmin and public roles to the server. The identical user should be added to the mirror server as well.
SQL Server Error: 1418
Severity: 16
Event Logged or not: No
Description:
The server network address “%.*ls” can not be reached or does not exist. Check the network address name and that the ports for the local and remote endpoints are operational.
Learn about SQL Server detecting logical consistency based issues and how to resolve them.
Learn about SQL Server error 1222 and how to resolve the lock request time out…
Discover the new features of Microsoft SQL Server 2022 and how they compare to previous…
SQL Server Error 1222 lock request time out period exceeded Lock request time out…
SQL Server Error : 427, Severity: 20. Could not load the definition for constraint ID…
SQL Server Error : 204, Severity: 20. Normalization error in node %ls.
This website uses cookies.