-
Notifications
You must be signed in to change notification settings - Fork 50
0100 Initial Data Collection and Scoping Questions
- 0100 Initial Data Collection and Scoping Questions
Narrowing the issue as much as possible and having user and machine available at your fingertips will help the troubleshooting process. Note: Not all questions may be applicable to all issues but serve as a list of things to consider.
*** Client Machine
Operating System name, edition, and version (Winver): SQL Server Driver or Provider name and version: Machine Name: IP address: Domain joined to: Application run-time environment (IIS, Windows Forms, Web Sphere, SSIS Job, etc.): Application language: Connection String: What type of authentication is used to connect to the server? NTLM, Kerberos, SQL, AAD, other? If the application is a server/service, does it delegate user credentials to the back-end database? Is constrained delegation being used? Application service account and domain: Physical, virtual, cloud (e.g. IaaS vs Web App vs Web Role vs Power BI, etc.):
- Is the client driver JDBC or running on Linux or Mac? The workflows are more Windows-oriented at the moment.
- Does the issue only affect legacy providers, such as Provider=SQLOLEBD or Driver={SQL Server} and not SQL Native client and newer drivers or vice versa?
- Does the issue only happen in one application or does it occur in multiple or all applications?
- Does a UDL file fail to connect to other SQL Servers or does it only fail to the problem SQL Server?
- Can you remote into the SQL Server and connect Management Studio?
- Does the issue only happen when using the NETBIOS name of the server and not when using the FQDN or vice versa? Does it work using the IP address?
- If the client is Windows 10 Enterprise Edition, is the Credential Guard feature turned on? This will interfere with full delegation scenarios.