We are seeing the following error on one of our SQL 2008 always on boxes (2008 R2):
DESCRIPTION: SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. The logon attempt failed [CLIENT: 10.165.2.103]
I couldn't find anything useful online and the client IP listed (10.165.2.103) is not a valid IP address on our network.
The SQL resource says all we need to do is manually register the SPN, but I have my doubts about the validity of this statement. This is an error that Argent detected, but I can't get them to actually identify what the actual problem is (the spn is the symptom). I don't want to re-register an SPN and restarting the MSSQLSERVER service if there isn't an actual problem.
I have written a PowerShell script to "walk" the security structure of each SQL instance to find:
Each Login (Windows or SQL)
* Its Server Roles
* Every database to which the login is mapped
* The associated "Database User" for this …
This lesson discusses how to use a Mainform + Subforms in Microsoft Access to find and enter data for payments on orders. The sample data comes from a custom shop that builds and sells movable storage structures that are delivered to your property. …