Bug report #16190
Connection MSSQL (not localhost)
|Affected QGIS version:||2.18.3||Regression?:||No|
|Operating System:||Windows||Easy fix?:||No|
|Pull Request or Patch supplied:||No||Resolution:||no timely feedback|
|Crashes QGIS or corrupts data:||No||Copied to github as #:||24100|
I think there is a problem with the MSSQL connector because I have different result if I connect with "Add a MSSQL spatial layer" or with "Add vector layer"/Database/MSSQL !
With a localhost Database, I agree everything works fine. But in this example, I don't use a local database, it is located on a virtual network through VPN (database is on a server, and I connect to this server through a VPN).
- if I connect with "Add vector layer"/Database/MSSQL (host=192.168.0.100\\SQLEXPRESS), I can connect to spatial vectors, it's OK
- if I use the same connection with "Add a MSSQL spatial layer" or with QGIS Browser, I have this error message "[Microsoft][ODBC SQL Server Driver][SQL Server]Échec de l'ouverture de session de l'utilisateur 'XXXXX\\XXXXX'. [Microsoft][Gestionnaire de pilotes ODBC] Échec SQLSetConnectAttr du pilote QODBC3: Unable to connect"
The thing is I need to have access not only to spatial layers, but to the whole database. And without the data connection, I can't.
Thanks for the answer.
#3 Updated by Jürgen Fischer almost 4 years ago
- Resolution set to no timely feedback
- Status changed from Feedback to Closed
Bulk closing 82 tickets in feedback state for more than 90 days affecting an old version. Feel free to reopen if it still applies to a current version and you have more information that clarify the issue.