0

I have a strange issue using a UDL file. I can't connect with the UDL file to SQL Server 2016 with a specific user (login) but when I'm trying to connect with the same user via SSMS, it works without problems.

A Diffrent user can connect both ways without issues.

What's wrong with my user/UDL file?

bumped to the homepage by Community 21 hours ago

This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.

  • 1
    I think you are going to need to show us the content of the UDL file - open it in notepad, change the server name/database name/user name/password to protect your security, but don't change anything else. – Mister Magoo Jun 24 '18 at 11:47
0

I found what caused it - UDL connections doesn't allow using a different Windows NT authentication other than the current user. The "Custom user" is only for SQL authentication.

  • This is the case for all Windows authenticated connections, not just UDLs. Windows authentication uses the identity of the current process (e.g. logged in user). – Dan Guzman Jun 24 '18 at 12:35
  • @DanGuzman yeah but you can run them as a different user. that's how I manage to connect with this user using ssms. – Igal Drayerman Jun 24 '18 at 13:07
  • Right, Run As changes the process identity. – Dan Guzman Jun 24 '18 at 13:19

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.