For the computer that is receiving the connection request, type DisableServerExtendedMasterSecret: REG_DWORD for the name of the DWORD, and then press ENTER.ĥ. On the Edit menu, point to New, and then click DWORD Value.Ĥ. Locate and then click the following subkey in the registry: HKLM\System\CurrentControlSet\Control\SecurityProviders\Schannelģ. This error was caused by a bad update of windows server related to a security configuration/spoofing.Ģ. The following fatal alert was generated: 51. Windows server Event Log has many SChannel errors as below: It isn't specific to SQL 2017, but may be something to look into. Thanks in advance for any guidance you can give me. In the many years I've been a member, I try to fix my own issues, but this one has me stumped. I have searched high and low and I'm not finding much help. The other three instances on this blade are fine, so I don't want to have to do a bulk restore (more of a pain than rebuilding the instance). The repair fails because the process needs to connect. (provider: SSL Provider, error: 0 - The Local Security Authority cannot be contacted) (Microsoft SQL Server, Error: -2146893052) I can NOT connect to the instance with SQL or Windows auth, even locally.Ī connection was successfully established with the server, but then an error occurred during the login process. The SQL service is running, agent is not (the reason is obvious with the error). I've tried a repair, I've tried removing updates (even though the other 5 prod blades are fine, and the Dev/QA clusters are fine also. One of the 2017 instances is in a bad state. Each blade has 4 instances so 4 availability groups of 6 members each. Servers are 2019 datacenter in a cluster. Did patch Tuesday yesterday across 6 UCS blades.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |