System information:
- Operating system (distribution) and version: Windows 10
- DBeaver version: 7.0.1.202003211804
- Additional extensions: None
Connection specification:
- Database name and version: Oracle 18c
- Driver name: jdbc driver
- Do you use tunnels or proxies (SSH, SOCKS, etc)? no
Describe the problem you’re observing:
After update to version 7.0.1 DBeaver decided to redownload Oracle drivers, but for some reason cannot do that and throws an error:
Error resolving dependencies
Maven artifact 'maven:/com.oracle.database.xml:xmlparserv2::RELEASE' not found
Is this somehow related to #8182?
Steps to reproduce, if exist:
Update to version 7.0.1 and try to download drivers for Oracle.
Include any warning/errors/backtraces from the logs
dbeaver-debug.log:
> Start Equinox Provisioning Platform Update Support [org.eclipse.equinox.p2.ui.sdk 1.1.500.v20191016-0512]
> Start Core Compare Support [org.eclipse.compare.core 3.6.700.v20191122-2107]
> Start Compare Support [org.eclipse.compare 3.7.800.v20191122-2107]
> Start Equinox Security Default UI [org.eclipse.equinox.security.ui 1.2.500.v20191003-0536]
2020-03-23 12:39:05.679 - Error resolving library 'com.oracle.database.jdbc:ojdbc8::RELEASE' dependencies
java.io.IOException: Maven artifact 'maven:/com.oracle.database.jdbc:ojdbc8::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
2020-03-23 12:39:05.681 - Error resolving library 'com.oracle.database.nls:orai18n::RELEASE' dependencies
java.io.IOException: Maven artifact 'maven:/com.oracle.database.nls:orai18n::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
2020-03-23 12:39:05.682 - Error resolving library 'com.oracle.database.xml:xdb6::RELEASE' dependencies
java.io.IOException: Maven artifact 'maven:/com.oracle.database.xml:xdb6::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
2020-03-23 12:39:05.684 - Error resolving library 'com.oracle.database.xml:xmlparserv2::RELEASE' dependencies
java.io.IOException: Maven artifact 'maven:/com.oracle.database.xml:xmlparserv2::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
2020-03-23 12:39:05.717 - org.jkiss.dbeaver.DBException: Error resolving dependencies
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:91)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
Caused by: java.io.IOException: Maven artifact 'maven:/com.oracle.database.xml:xmlparserv2::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
... 3 more
2020-03-23 12:40:09.782 - Error resolving library 'com.oracle.database.jdbc:ojdbc8::RELEASE' dependencies
java.io.IOException: Maven artifact 'maven:/com.oracle.database.jdbc:ojdbc8::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
2020-03-23 12:40:09.783 - Error resolving library 'com.oracle.database.nls:orai18n::RELEASE' dependencies
java.io.IOException: Maven artifact 'maven:/com.oracle.database.nls:orai18n::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
2020-03-23 12:40:09.785 - Error resolving library 'com.oracle.database.xml:xdb6::RELEASE' dependencies
java.io.IOException: Maven artifact 'maven:/com.oracle.database.xml:xdb6::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
2020-03-23 12:40:09.787 - Error resolving library 'com.oracle.database.xml:xmlparserv2::RELEASE' dependencies
java.io.IOException: Maven artifact 'maven:/com.oracle.database.xml:xmlparserv2::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
2020-03-23 12:40:09.817 - org.jkiss.dbeaver.DBException: Error resolving dependencies
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:91)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
Caused by: java.io.IOException: Maven artifact 'maven:/com.oracle.database.xml:xmlparserv2::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
... 3 more
2020-03-23 12:40:18.323 - Error resolving library 'com.oracle.database.jdbc:ojdbc8::RELEASE' dependencies
java.io.IOException: Maven artifact 'maven:/com.oracle.database.jdbc:ojdbc8::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
2020-03-23 12:40:18.325 - Error resolving library 'com.oracle.database.nls:orai18n::RELEASE' dependencies
java.io.IOException: Maven artifact 'maven:/com.oracle.database.nls:orai18n::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
2020-03-23 12:40:18.327 - Error resolving library 'com.oracle.database.xml:xdb6::RELEASE' dependencies
java.io.IOException: Maven artifact 'maven:/com.oracle.database.xml:xdb6::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
2020-03-23 12:40:18.333 - Error resolving library 'com.oracle.database.xml:xmlparserv2::RELEASE' dependencies
java.io.IOException: Maven artifact 'maven:/com.oracle.database.xml:xmlparserv2::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
2020-03-23 12:40:18.356 - org.jkiss.dbeaver.DBException: Error resolving dependencies
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:91)
at org.jkiss.dbeaver.ui.dialogs.driver.DriverDependenciesTree.lambda$1(DriverDependenciesTree.java:120)
at org.jkiss.dbeaver.runtime.RunnableContextDelegate.lambda$0(RunnableContextDelegate.java:39)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
Caused by: java.io.IOException: Maven artifact 'maven:/com.oracle.database.xml:xmlparserv2::RELEASE' not found
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.resolveLocalVersion(DriverLibraryMavenArtifact.java:297)
at org.jkiss.dbeaver.registry.driver.DriverLibraryMavenArtifact.getDependencies(DriverLibraryMavenArtifact.java:203)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:107)
at org.jkiss.dbeaver.registry.driver.DriverDependencies.resolveDependencies(DriverDependencies.java:57)
... 3 more
Содержание
- Dbeaver: Error resolving driver dependencies mssql-jdbc_auth
- All 11 comments
- Error resolving dependencies #10026
- Comments
- System information:
- Connection specification:
- Describe the problem you’re observing:
- Steps to reproduce, if exist:
- Include any warning/errors/backtraces from the logs
- Error resolving driver dependencies mssql-jdbc_auth #8251
- Comments
Dbeaver: Error resolving driver dependencies mssql-jdbc_auth
Hello, after 7.0.1 update ( from 6.* release) mssql auth library is missing and it was not possible to connect to mssql db anymore .
Error:
Error resolving dependencies Maven artifact ‘maven:/com.microsoft.sqlserver:mssql-jdbc_auth:RELEASE’ not found Maven artifact ‘maven:/com.microsoft.sqlserver:mssql-jdbc_auth:RELEASE’ not found
under %appdata%DBeaverDatadriversdriversmssqlauthx64 I’ve an old sqljdbc_auth.dll that worked well before 7.* release.
I’ve manually downloaded the new dll: https://mvnrepository.com/artifact/com.microsoft.sqlserver/mssql-jdbc_auth/8.2.1.x64 and added it to driver to libraries files and with this workaround it works. but everytime that I try to connect to a mssql db I get the error of missing dependencies.
I’m using home dsl , no proxy authentication , no VPN enabled.
OS: windows 7
Dbeaver version: 7.0.1
Try to reset driver settings.
From connection settings dialog click Edit Driver Settings -> Reset to Defaults (at the bottom).
Then dbeaver should ask for driver jars/dlls re-download.
Try to reset driver settings.
From connection settings dialog click Edit Driver Settings -> Reset to Defaults (at the bottom).
Then dbeaver should ask for driver jars/dlls re-download.
I’ve reset to default mssql driver settings and re-downloaded latest driver version, this solved the problem of auth library dependency, thanks!
access to mssql database with SQL server authentication works well.
access to mssql database with windows authentication give me this error:
no mssql-jdbc_auth-8.2.1.x64 in java.library.path: [C:Program FilesDBeaver, C:WINDOWSSunJavabin, C:WINDOWSsystem32, C:WINDOWS, C:/Program Files/DBeaver/jre/bin/server, C:/Program Files/DBeaver/jre/bin, C:WINDOWSsystem32, C:WINDOWS, C:WINDOWSSystem32Wbem, C:WINDOWSSystem32WindowsPowerShellv1.0, C:Program Files (x86)QuickTimeQTSystem, C:Program Files (x86)IBMClient AccessEmulator, C:Program Files (x86)IBMClient AccessShared, C:Program Files (x86)IBMClient Access, c:Program FilesMicrosoft Data Protection ManagerDPMbinVDDKbin, C:Program Files (x86)Microsoft SQL Server150DTSBinn, C:Program FilesDBeaver, ., .]
this problem was raised because libraries versions where a little bit different by default after resetting driver settings
mssql-jdbc : 8.2.1
mssql-jdbc_auth: 8.2.0
As I learned from your post I’ve forced auth library to 8.2.1 version, because libraries must have the same versions, and this fixed the problem. I’m reporting this because some people may face the same situation if they don’t know about new required version dependency, because dbeaver allow you to have different library versions.
I can confirm that the issue still prevails after resetting when windows authentication is used to connect to MS SQL and different library versions exist. I get the same error as P4Ks.
Reset to default works incorrectly 
Hello,
I have the same issue. I am not able to connect using Windows Authentication, but using ‘SQL server authentication’ it works well.
I tried to reset to default and download again, but it is still the same thing.
I did not understand how I can manage this issue. Maybe there will be a fix soon anyway?
Thanks for your help
@flocoolb just choose the same version manually for both files when you download drivers 
Thank you very much @uslss
I am not used to change things like those. I understood with your last screenshot. Thanks!
By the way, there is the 8.2.2 since yesterday.
Have a good day
«Reset to default» fixed
I have the same error «no mssql-jdbc_auth-8.2.0.x64 in java library path: » .
I use MacOS Catalina. Both mssql-jdbc and mssql-jdbc_auth are version 8.2.0. 
However, the «download/update» window only have mssql-jdbc, no JDBC_auth. 
I also manually downloaded the auth-8.2.0.x64.dll and put it in the maven-central/com.microsoft.sqlserver folder. This didn’t work either.
Источник
Error resolving dependencies #10026
First Installation of DBeaver to use Postgre
System information:
- W10 1903
- DBeaver version 7.2.2.202010041557
- Java version 8 update 101
- Additional extensions : none
Connection specification:
Describe the problem you’re observing:
unabble to access to https://dbeaver.io/files/jdbc
to get files
Steps to reproduce, if exist:
Include any warning/errors/backtraces from the logs
Maven artifact ‘maven:/net.postgis:postgis-jdbc:RELEASE’ not found
The text was updated successfully, but these errors were encountered:
Have the same on Kubuntu 20.
It worked previous week but today I found it not working at all. It stop working on its own (how is it possible?)
Any clues what happened and how to resolve/workaround it?
I resolved my issue by:
- removing files from snap
- restarting dbeaver
- creating new postgresql database or importing project (all connections)
However once I import configuration (Import General/Preferences) the issue is back. I’m really not aware about changes I made to config which would affect libraries. I can provide the preferences file if it could help you debugging the problem.
PS. At this stage I’m not sure it’s the same issue as OP has. but still looks similar.
Do you use a proxy to access the internet?
No. I tried various connection types (inlc hotspot from my mobile). No changes.
HA.. I did another experiment.
- I exported Preferences from working DBeaver
- I imported «broken» config which causes the issue. DBeaver asked for its restart, After that the issue appeared as expected
- I imported config exported at beginning of this test case. After restart DBeaver remains broken
As a workaround, you can download the driver manually from here:
https://jdbc.postgresql.org/download.html
(use version 42.2.14 specifically, if you need SSH Tunnel working)
Probably nailed it down to the download path which points to snap directory. This path is being stored in exported preferences but might change (in stored prefs I had snap/dbeaver-ce/79/. while currently such path doesn’t exist any more. There is 81 instead of 79.
Maybe question is why imported «bad» preferences cannot be fixed by importing preferences exported second ago. But it needs more testing
Ah. and changing the path doesn’t help immediately. Restart of DBeaver is needed. After that DBeaver asks for downloading something but this time it works.
Thank you for answers !
To solve :
- DL postgresql-42.2.17.jar from https://jdbc.postgresql.org/download.html ( Yoni : 👍 ))
- copy file to C:Users%username%AppDataRoamingDBeaverDatadrivers ( or some where else . ) (unlock if necessary)
- Databases/ driverManager PostgreSQL / Edit / Add a file : select the copied file below
It’s error about SSL cerificate of repository you use. I used repo1.maven.org and insalled their certificate. You must save cert file from repo and import it in java cacerts:
keytool -import -alias maven_repo -keystore (your jdk home path)libsecuritycacerts -file maven_repo.cer
default password: changeit
And before use you system wide java, turn off Beaver local jdk, rename jdk folder to something another, e.g. jdk.bak
Initially my proxy was not set ..so it failed to download the driver. But then it said that the RELEASE file is not available from maven. I restarted dbeaver and it worked for me.
for those who may still struggle with downloading drivers — check your settings. I had the same problem and recognized, that the default location on Linux is set to /usr/share/dbeaver — a location, where normal users may not have access to. So, I solved my issue by setting the download location to /home/myuser/.dbeaver_drivers (or whatever you may choose). After that I reset all drivers to default and was able to download and update them. Worked like a charme.
Probably nailed it down to the download path which points to snap directory. This path is being stored in exported preferences but might change (in stored prefs I had snap/dbeaver-ce/79/. while currently such path doesn’t exist any more. There is 81 instead of 79.
Maybe question is why imported «bad» preferences cannot be fixed by importing preferences exported second ago. But it needs more testing
Ah. and changing the path doesn’t help immediately. Restart of DBeaver is needed. After that DBeaver asks for downloading something but this time it works.
I just had the same problem and this helped me. A snap update was applied while I was using the dbeaver and the drivers location folder was not updated to the new location. I had to manually fix it at the preferences dialog.
It got it solved by Downloading from https://jdbc.postgresql.org/download.html 
and then went to driver settings, deleted everything else and add the file I downloaded ( the folder location didn’t seem to matter 
Probably nailed it down to the download path which points to snap directory. This path is being stored in exported preferences but might change (in stored prefs I had snap/dbeaver-ce/79/. while currently such path doesn’t exist any more. There is 81 instead of 79.
Maybe question is why imported «bad» preferences cannot be fixed by importing preferences exported second ago. But it needs more testing
Ah. and changing the path doesn’t help immediately. Restart of DBeaver is needed. After that DBeaver asks for downloading something but this time it works.
I just had the same problem and this helped me. A snap update was applied while I was using the dbeaver and the drivers location folder was not updated to the new location. I had to manually fix it at the preferences dialog.
Great! This is the best way!
I am adjusted the path, restart dbeaver, and all works.
Thank you so much @leobasilio and @michalk-k 
For me, fixed this issue by importing maven website cert into dbeaver jre cacerts which is under folder Application/DBeaver/Contents/eclipse/jre/Contents/Home/lib/security, this is Mac path, Windows could be different
Probably nailed it down to the download path which points to snap directory. This path is being stored in exported preferences but might change (in stored prefs I had snap/dbeaver-ce/79/. while currently such path doesn’t exist any more. There is 81 instead of 79.
Maybe question is why imported «bad» preferences cannot be fixed by importing preferences exported second ago. But it needs more testing
Ah. and changing the path doesn’t help immediately. Restart of DBeaver is needed. After that DBeaver asks for downloading something but this time it works.
This fixed it for me. For everyone as inexperienced with DBeaver as me:
The dialogue to change this can be found under Window > Preferences > Connections > Drivers , then change the path under the section Drivers location , labeled Local folder to the one with the path with newest version. (In my case the path that worked was /home/ /snap/dbeaver/current/.local/share/DBeaverData/drivers , with the change being that current previously was a number)
Then as mentioned in the original post, restart DBeaver and it should work.
Источник
Error resolving driver dependencies mssql-jdbc_auth #8251
Hello, after 7.0.1 update ( from 6.* release) mssql auth library is missing and it was not possible to connect to mssql db anymore .
Error:
Error resolving dependencies Maven artifact ‘maven:/com.microsoft.sqlserver:mssql-jdbc_auth:RELEASE’ not found Maven artifact ‘maven:/com.microsoft.sqlserver:mssql-jdbc_auth:RELEASE’ not found
This issue probably it’s linked to #8054
under %appdata%DBeaverDatadriversdriversmssqlauthx64 I’ve an old sqljdbc_auth.dll that worked well before 7.* release.
I’ve manually downloaded the new dll: https://mvnrepository.com/artifact/com.microsoft.sqlserver/mssql-jdbc_auth/8.2.1.x64 and added it to driver to libraries files and with this workaround it works. but everytime that I try to connect to a mssql db I get the error of missing dependencies.
I’m using home dsl , no proxy authentication , no VPN enabled.
OS: windows 7
Dbeaver version: 7.0.1
The text was updated successfully, but these errors were encountered:
Try to reset driver settings.
From connection settings dialog click Edit Driver Settings -> Reset to Defaults (at the bottom).
Then dbeaver should ask for driver jars/dlls re-download.
I’ve reset to default mssql driver settings and re-downloaded latest driver version, this solved the problem of auth library dependency, thanks!
access to mssql database with SQL server authentication works well.
access to mssql database with windows authentication give me this error:
no mssql-jdbc_auth-8.2.1.x64 in java.library.path: [C:Program FilesDBeaver, C:WINDOWSSunJavabin, C:WINDOWSsystem32, C:WINDOWS, C:/Program Files/DBeaver/jre/bin/server, C:/Program Files/DBeaver/jre/bin, C:WINDOWSsystem32, C:WINDOWS, C:WINDOWSSystem32Wbem, C:WINDOWSSystem32WindowsPowerShellv1.0, C:Program Files (x86)QuickTimeQTSystem, C:Program Files (x86)IBMClient AccessEmulator, C:Program Files (x86)IBMClient AccessShared, C:Program Files (x86)IBMClient Access, c:Program FilesMicrosoft Data Protection ManagerDPMbinVDDKbin, C:Program Files (x86)Microsoft SQL Server150DTSBinn, C:Program FilesDBeaver, ., .]
this problem was raised because libraries versions where a little bit different by default after resetting driver settings
mssql-jdbc : 8.2.1
mssql-jdbc_auth: 8.2.0
As I learned from your post I’ve forced auth library to 8.2.1 version, because libraries must have the same versions, and this fixed the problem. I’m reporting this because some people may face the same situation if they don’t know about new required version dependency, because dbeaver allow you to have different library versions.
I can confirm that the issue still prevails after resetting when windows authentication is used to connect to MS SQL and different library versions exist. I get the same error as P4Ks.
Reset to default works incorrectly
Источник
Introduction
This is an article where the main focus is just to solve an error message exist. The error message actually exist upon executing DBeaver. It is a software for database tool. It exist in the following link. Upon executing the DBeaver tool for connecting to MySQL database server, the following pop-up window dialog box appear :
The above image is from an article exist as also the main focus of the content where it exist is in this link. So, the main problem is connecting to MySQL database server require a database driver. By default DBeaver do not have it already after the installation process is finished. So, it is using ‘maven’ tool installed to get and download the database driver.
So, in order to solve the error message as appear in the title of this article, the following are the steps :
-
Just make sure that maven tool is available. Type ‘mvn’ on the command prompt to check whether the maven path location in the environment variable path. If it is exist, it will make the maven execution tool is possible in every path and for every other tool which need it.
-
After that, also check the maven tool configuration is currently support HTTPS connection. The configuration is available in an article exist in this link. Normally, just add the following configuration to the maven/conf directory in a file with the name settings.conf :
<mirror> <id>central-secure</id> <url>https://repo.maven.apache.org/maven2</url> <mirrorOf>central</mirrorOf> </mirror>
The reason for why the maven repository itself cannot be found, the main one is because there is no maven tool available in the machine. Use existing maven such as the one available in an IDE like NetBeans and other type of available IDE. Another way is by manually download the maven and have it independently. Do not forget to make maven available for the execution in every path and for every tool. Just declare the path in the environment variable. In that case, DBeaver can use it to download the mysql-connector-java using the help from maven tool.
DBException: IO error while resolving dependencies
DBException: IO error while resolving dependencies
DBEaver 3.5.2
Windows 7 x64
Java 1.8
PostgreSQL 9.3
I had to run several times with cleaning.
Now , when you connect to the database beyond the error:
After this error when closing a window — works
new driver here (It was downloaded at first start)
C:Usersuser.dbeaver.metadata.pluginsorg.jkiss.dbeaver.coredriverspostgresqlpostgresql-9.1-901.jdbc4.jar
- ems2811
- Posts: 16
- Joined: Fri Sep 12, 2014 10:59 am
Re: DBException: IO error while resolving dependencies
by Serge » Tue Oct 27, 2015 9:49 am
It is a bug in 3.5.2. I’ll release fixed version shortly.
Solution: Go to driver editor («Edit Driver») and remove old maven reference «maven:/org.postgresql:postgresql:[.*jdbc4]»
Thanks for report.
- Serge
- Posts: 1526
- Joined: Sat Feb 26, 2011 8:24 pm
- Location: SPb
-
- Website
Re: DBException: IO error while resolving dependencies
by Serge » Tue Oct 27, 2015 10:39 am
In driver editor (second screen).
You can just click on «Reset to Defaults».
- Serge
- Posts: 1526
- Joined: Sat Feb 26, 2011 8:24 pm
- Location: SPb
-
- Website
Re: DBException: IO error while resolving dependencies
by Serge » Tue Oct 27, 2015 10:53 am
Re-download 3.5.2 version (I just published fix).
After clicking on Reset restart DBeaver.
- Serge
- Posts: 1526
- Joined: Sat Feb 26, 2011 8:24 pm
- Location: SPb
-
- Website
Re: DBException: IO error while resolving dependencies
by ems2811 » Tue Oct 27, 2015 11:04 am
I downloaded again.
Do this: After clicking on Reset restart DBeaver
nothing changes
- ems2811
- Posts: 16
- Joined: Fri Sep 12, 2014 10:59 am
Re: DBException: IO error while resolving dependencies
by ems2811 » Tue Oct 27, 2015 11:27 am
I downloaded again . all cleared . everything is working. thank
- ems2811
- Posts: 16
- Joined: Fri Sep 12, 2014 10:59 am
Return to Support
Who is online
Users browsing this forum: Google [Bot] and 37 guests
Я использую внутренний репозиторий maven / artifactory в своей сети.
Я пытаюсь инициализировать соединение Oracle с помощью DBeaver 7.1.0. (не плагин eclipse, отдельная программа)
При каждой инициализации не удается загрузить драйверы. с ошибкой
Error Resolving Dependencies
Maven artifact 'maven:/com.oracle.database.xml:xmlparserv2:RELEASE' not found
Я предполагаю, что это связано с тем, что прокси-сервер блокирует внешний доступ для загрузки файлов.
Зная содержимое моего ~ / .m2 / settings.xml
<proxies>
<proxy>
<host>myproxy.foo</host>
<port>80</port>
</proxy>
<proxies>
<profiles>
<profile>
...
<repositories>
<repository>
<id>foobar</id>
<name>mystuff</id>
<url>https://my-interal-maven.foo/artifactory/mystuff</url>
Как правильно настроить соединение, чтобы оно могло загружать файлы?
РЕДАКТИРОВАТЬ : я обошел использование maven и вручную скопировал JAR-файлы в настройки, как и ответ @FeodorG
По сути, при попытке заставить драйвер работать он сломается, когда в настройках драйвера -> «Загрузить» выдает ошибку при разрешении зависимостей … Ошибка при разрешении зависимостей Maven artifact ‘maven: /com.oracle.database.nls: orai18n: RELEASE’ not нашел
Поэтому я бы взял эту банку в mvnRepository: и повторил бы для каждой другой записи, которая не удалась при загрузке
https://mvnrepository.com/artifact/com.oracle.database.nls/orai18n/12.2.0.1
https://mvnrepository.com/artifact/com.oracle.database.xml/xmlparserv2/12.2.0.1
https://mvnrepository.com/artifact/com.oracle.database.xml/xdb6/12.2.0.1
https://mvnrepository.com/artifact/com.oracle.database.nls/orai18n/12.2.0.1
После замены всех записей в моей файловой системе на JAR … соединение сработало!
3 ответа
Лучший ответ
Ну, у меня была такая же проблема (всевозможные проблемы с настройками безопасности в корпоративных сетях мешали мне установить драйвер). Мое обходное решение заключалось в том, чтобы каким-то образом получить файлы jar драйвера Oracle на моем локальном диске, затем я определил свой собственный драйвер Oracle, перейдя в Database -> Driver manager в DBeaver. Оттуда я определил новый драйвер, добавив файл в качестве указателя на драйвер файла jar Oracle на моем локальном диске, а затем щелкнул «Найти класс». Он нашел класс, а затем я просто ввел некоторые детали для порта по умолчанию и т. Д. Затем я создал новое соединение с драйвером, который я только что создал, ввел имя пользователя и пароль, и он сработал. Короче говоря, я просто перенес файлы jar на свой локальный диск и создал новый драйвер и новое соединение.
4
FeodorG
24 Фев 2021 в 12:29
В моем случае у меня есть прокси и частный репозиторий, и мне удалось определить URL-адрес частного репозитория в качестве нового источника данных в Windows-> Preferences-> Connections-> Drivers-> maven и щелкнуть Add.
1
Blackcoat77
21 Окт 2021 в 08:07
На этот раз я использую Windows 10 и использую прокси. На самом деле проблема заключалась не в его настройке (для загрузки прокси) или URL-адресе репозитория Maven (который мог быть написан с ошибкой).
Проблема заключалась в разрешениях папки, которые не могли принять драйвер для сохранения в папке %userprofile%AppDataRoamingDBeaverDatadriversmavenmaven-central.
Я просто рекурсивно даю полное разрешение всем в папке DBeaverData, но это не самая безопасная установка. Вместо этого вы можете изменить «Все» только на своего пользователя. Это сработало.
takeown /f %userprofile%AppDataRoamingDBeaverData* /r
icacls %userprofile%AppDataRoamingDBeaverData /grant Everyone:F /t
0
bad_coder
2 Сен 2021 в 03:04
Try to reset driver settings.
From connection settings dialog click Edit Driver Settings -> Reset to Defaults (at the bottom).
Then dbeaver should ask for driver jars/dlls re-download.
I’ve reset to default mssql driver settings and re-downloaded latest driver version, this solved the problem of auth library dependency, thanks!
access to mssql database with SQL server authentication works well.
access to mssql database with windows authentication give me this error:
no mssql-jdbc_auth-8.2.1.x64 in java.library.path: [C:Program FilesDBeaver, C:WINDOWSSunJavabin, C:WINDOWSsystem32, C:WINDOWS, C:/Program Files/DBeaver/jre/bin/server, C:/Program Files/DBeaver/jre/bin, C:WINDOWSsystem32, C:WINDOWS, C:WINDOWSSystem32Wbem, C:WINDOWSSystem32WindowsPowerShellv1.0, C:Program Files (x86)QuickTimeQTSystem, C:Program Files (x86)IBMClient AccessEmulator, C:Program Files (x86)IBMClient AccessShared, C:Program Files (x86)IBMClient Access, c:Program FilesMicrosoft Data Protection ManagerDPMbinVDDKbin, C:Program Files (x86)Microsoft SQL Server150DTSBinn, C:Program FilesDBeaver, ., .]
this problem was raised because libraries versions where a little bit different by default after resetting driver settings
mssql-jdbc : 8.2.1
mssql-jdbc_auth: 8.2.0
As I learned from your post I’ve forced auth library to 8.2.1 version, because libraries must have the same versions, and this fixed the problem. I’m reporting this because some people may face the same situation if they don’t know about new required version dependency, because dbeaver allow you to have different library versions.
Thanks @serge-rider !
I can confirm that the issue still prevails after resetting when windows authentication is used to connect to MS SQL and different library versions exist. I get the same error as P4Ks.
Reset to default works incorrectly
Hello,
I have the same issue. I am not able to connect using Windows Authentication, but using ‘SQL server authentication’ it works well.
I tried to reset to default and download again, but it is still the same thing.
I did not understand how I can manage this issue. Maybe there will be a fix soon anyway?
Thanks for your help
@flocoolb just choose the same version manually for both files when you download drivers
Thank you very much @uslss
I am not used to change things like those. I understood with your last screenshot. Thanks!
By the way, there is the 8.2.2 since yesterday.
Have a good day
I have the same error «no mssql-jdbc_auth-8.2.0.x64 in java library path: » .
I use MacOS Catalina. Both mssql-jdbc and mssql-jdbc_auth are version 8.2.0.
However, the «download/update» window only have mssql-jdbc, no JDBC_auth.
I also manually downloaded the auth-8.2.0.x64.dll and put it in the maven-central/com.microsoft.sqlserver folder. This didn’t work either.
verified.
Fixed in scope of 7.0.2 release.
Could be tested in EA version (https://dbeaver.io/files/ea/)