You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running Windows 10 Enterprise with MSSQL Server 15.0.4326.1. SSMC shows Windows Auth
Installed the JDBC driver with the auth file in the class path (bottom line contains the JDBC auth directory (click the black bar for fullscreen)
using these instructions
The database is "DB2_Mothership"
Since it's Windows Auth, no need to enter credentials. You can see the IP:Port. I can successfully ping this IP address, but I'm not sure if that means MSSQL Server is listening on that IP:PORT combo (I believe it does, but can always be schooled)
The popup says it's not configured for integrated authentication contrary to the JDBC driver instructions. I restarted WR to see if that might work, but no joy. Same with SSMS (though I did not stop/restart the database itself). Note the console has an earlier auth error not related (had the wrong folder name).
Running Windows 10 Enterprise with MSSQL Server 15.0.4326.1. SSMC shows Windows Auth
Installed the JDBC driver with the auth file in the class path (bottom line contains the JDBC auth directory (click the black bar for fullscreen)
using these instructions
The database is "DB2_Mothership"
Since it's Windows Auth, no need to enter credentials. You can see the IP:Port. I can successfully ping this IP address, but I'm not sure if that means MSSQL Server is listening on that IP:PORT combo (I believe it does, but can always be schooled)
The popup says it's not configured for integrated authentication contrary to the JDBC driver instructions. I restarted WR to see if that might work, but no joy. Same with SSMS (though I did not stop/restart the database itself). Note the console has an earlier auth error not related (had the wrong folder name).
Troubleshooting JDBC/MSSQL Server connectivity issues:
https://learn.microsoft.com/en-us/sql/connect/jdbc/troubleshooting-connectivity?view=sql-server-ver16
I'm able to get WR to work with SAS tables just fine, btw.
The text was updated successfully, but these errors were encountered: