Troubleshooting Database Mirroring Error 1418

[@kishoreevani5813]

well explained each small thing in the video. Awesome sir.

[@giribabu7009]

Nice video thank you for giving end to end clarification

[@RamanaVenki-g9z]

Thanks very good explanation

[@goguladhananjineyulu3174]

THANK YOU SO MUCH ANNA 😍🥰

[@helloRChere]

Hi Chandu, Do you provide DBA Training

[@Gabriel-kx4qv]

Nice vídeo, ty

[@giribabu7009]

Suggested to upload more videos and share knowledge replications, migration, performance issues etc.,

[@chandustechnet4214]

Sure, thanks for the feedback

[@ShubhenduKumarKundu]

After successful synchronized, secondary database shown restoring mode. How do I get back in normal mode with synchroinized?

[@chandustechnet4214]

Need to look into the logs to understand the issue. But just a couple of generic checks, make sure both principal and mirror are on the same build/version. Please check the algorithm you're using and make sure it's AES but not RC4 algorithm.

[@FardinNoman-p7v]

When I will implement database mirroring in 2 different server then what are the things I have to mention in service accounts? There are 2 options one is principle & another one is mirroring. Whether i have to put server name or anything else just clear this part. Thanks.

[@chandustechnet4214]

Service accounts should be domain accounts.

[@ArokiyaAnandKumar]

Thank you Mr. Chandu, Your explanation was fantastic. But My issue is I have 2 different system, in both system have [NT Authority/System] . I have tried the below Script GRANT CONNECT ON ENDPOINT:: MIRRORING to [NT AUTHORITY\SYSTEM] But after if I executing the mirroring Same 1418 error is coming I try to check in sp_readerrorlog 2024-11-28 11:11:52.060 Logon Database Mirroring login attempt by user 'NT AUTHORITY\ANONYMOUS LOGON.' failed with error: 'Connection handshake failed. The login 'NT AUTHORITY\ANONYMOUS LOGON' does not have CONNECT permission on the endpoint. State 84.'. [CLIENT: 172.16.29.110] NT AUTHORITY\ANONYMOUS LOGON Can you please guide me where I have to fix this issue.

[@merjt14]

I was having the same problem, the only thing i came up was to create NT AUTHORITY\ANONYMOUS LOGON login and give it CONNECT permission on both servers, i don't know if it is something that can be done but it worked for me, even though i'm still looking for another way to solve it

[@merjt14]

Oh, another solution i found was to use .\Administrator instead of NT Service\MSSQL$SERVER01 for Log On As i both servers, i think it can work by using another windows account but keeping the same passwords in both servers. I didn't went for this because i was using a SCADA database and didn't wanna move something that may alter the application

[@chandustechnet4214]

Is it your test machine or your personal laptop and learning? Is SQl service running under the default account and/or the local system account? Please give sysadmin to the SQL service account (create both service accounts if different) and check. If it's a domain computers, suggest you to use the domain logins and fix SPNs if any.

[@chandustechnet4214]

I still recommend to use domain accounts. If you're using admin accounts. Then you need to add admin login both the servers. Ex: Server1/administrator and server2/administrator with required permissions

[@VeeVeeSarathi]

Hi Guys It Worked. But i cannot Open the Mirrored Database after the mirroring process. it Says The database TestMirror is not accessible. (ObjectExplorer) any Solutions?

[@chandustechnet4214]

What do you mean "you cannot open the mirrored database", you cannot access the mirrored database because it's always in restoring state. You can access only the principal.

[@prashantbhosale5635]

Please show how to configure on domain server

[@chandustechnet4214]

You mean to configure database mirroring on cluster environment?

[@JSunilKumar0508]

How to troubleshoot 927 error in Database Mirroring ?

[@chandustechnet4214]

What's the SQL version? Please check if you've any pending logs to be restored. It's not an error or issue, if the LSN should be in sync with the primary. Make sure that no log backup jobs running on primary while configuring mirroring. Restore necessary logs and then configure.

[@JSunilKumar0508]

Principle Server: SQL 2017 Developer Edition Mirror Server: SQL 2019 Developer Edition. Took one Full & one Transaction log backups from Principle Server, same Restored in Mirror server. Then configured. Observed 927 error.

[@chandustechnet4214]

Please share the error message and check if any logs pending to restore. To isolate the issue, you can create a test database and try to configure. **Make sure that database mirroring endpoint encryption algorithm configured with AES but not RC4.