Unable to execute stored Procs

Anonymous
2023-04-18T08:58:01.12+00:00

Hi, Everyone in our office who recently upgraded their devices to Windows 11 have been experiencing issues with apps SQL connections. NT authority anonymous logon error, it however works when downgrading to Windows 10. Example apps fulling data from SQL received this error and when trying to execute a stored procedure. Any suggestions ?

Windows for business Windows Client for IT Pros User experience Other
0 comments No comments
{count} votes

Accepted answer
  1. Daniel 80 Reputation points
    2023-04-25T08:52:42.84+00:00

    Hi,

    have the same issue and more details:
    I use runas.exe to start SSMS with different user credentials.

    Till Windows 10 22H2 this was no issue and working fine.
    Since the update to Windows 11 22H2 this doesn't work anymore.

    If no credentials saved and you start ssms with:
    *C:\Windows\System32\runas.exe /savecred /user:"DOMAIN\USER" "C:\Program Files (x86)\Microsoft SQL Server Management Studio 19\Common7\IDE\Ssms.exe"
    *
    The console ask for the password and it will be saved in the Windows Webcredentials.
    After SSMS opened it is possible to login to the SQL Instance with the different user

    After closing ssms and open the comand above again, it will not ask for the credentials again (because of the /savecred parameter), ssms open and it is not able to connect to the sql server again.
    Follow error message is showing up

    ***Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.


    With using the command C:\Windows\System32\runas.exe /user:"DOMAIN\USER" "C:\Program Files (x86)\Microsoft SQL Server Management Studio 19\Common7\IDE\Ssms.exe" (without the /savecred parameter) you need to enter the password everytime but the ssms session works and will connect to the SQL Server with the right credentials.
    Best Regards

    1 person found this answer helpful.
    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. Olaf Helper 47,436 Reputation points
    2023-04-18T09:09:12.38+00:00

    With that less information it's difficult to give a suggestion. Which error messages do you see in the SQL Server ErrorLog? My guess: Local auth change from domain to Azure auth.

    0 comments No comments

  2. ZoeHui-MSFT 41,491 Reputation points
    2023-04-19T06:56:51.1166667+00:00

    Hi @Anonymous ,

    From your description, it seems the issue is more related with Windows 11 22h2 version.

    Report a problem with Windows updates:

    To report an issue to Microsoft at any time, use the Feedback Hub app. To learn more, see Send feedback to Microsoft with the Feedback Hub app

    Check it out here: https://learn.microsoft.com/en-us/windows/release-health/status-windows-11-22h2#report-a-problem-with-windows-updates

    Regards,

    Zoe Hui


    If the answer is helpful, please click "Accept Answer" and upvote it.

    0 comments No comments

  3. AdamStefanowski-5825 0 Reputation points
    2023-10-19T02:03:37.34+00:00

    I have the same problem running SSMS with different user credentials.

    Till Windows 10 22H2 this was no issue and working fine.
    Since the update to Windows 11 22H2 this doesn't work anymore.

    If no credentials are saved and you start ssms with:
    *C:\Windows\System32\runas.exe /savecred /user:"DOMAIN\USER" "C:\Program Files (x86)\Microsoft SQL Server Management Studio 19\Common7\IDE\Ssms.exe"
    *
    The console ask for the password and it will be saved in the Windows Credentials
    After SSMS opened it is possible to login to the SQL Instance with the different user

    After closing ssms and open the comand above again, it will not ask for the credentials again (because of the /savecred parameter), ssms open and it is not able to connect to the sql server again.
    Follow error message is showing up

    ***Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'.

    I can delete credentials with credential manager and then that will work again, but i need to enter the password again.

    we had the same issue with rdc to remote computer

    for rdc the workaround is to delete the credentials from windows credentials and to reenter the credentials using credential manager by adding a general credential; for SSMS that woraround does not work

    0 comments No comments

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.