- 3,715,830 Users
- 2,242,890 Discussions
- 7,845,632 Comments
Forum Stats
Discussions
Categories
- 17 Data
- 362.2K Big Data Appliance
- 7 Data Science
- 1.6K Databases
- 472 General Database Discussions
- 3.7K Java and JavaScript in the Database
- 22 Multilingual Engine
- 487 MySQL Community Space
- 5 NoSQL Database
- 7.6K Oracle Database Express Edition (XE)
- 2.8K ORDS, SODA & JSON in the Database
- 417 SQLcl
- 42 SQL Developer Data Modeler
- 184.9K SQL & PL/SQL
- 21K SQL Developer
- 1.9K Development
- 3 Developer Projects
- 32 Programming Languages
- 135.1K Development Tools
- 9 DevOps
- 3K QA/Testing
- 254 Java
- 6 Java Learning Subscription
- 10 Database Connectivity
- 66 Java Community Process
- 1 Java 25
- 9 Java APIs
- 141.1K Java Development Tools
- 6 Java EE (Java Enterprise Edition)
- 153K Java Essentials
- 135 Java 8 Questions
- 86.2K Java Programming
- 270 Java Lambda MOOC
- 65.1K New To Java
- 1.7K Training / Learning / Certification
- 13.8K Java HotSpot Virtual Machine
- 10 Java SE
- 13.8K Java Security
- 3 Java User Groups
- 22 JavaScript - Nashorn
- 18 Programs
- 125 LiveLabs
- 30 Workshops
- 9 Software
- 3 Berkeley DB Family
- 3.5K JHeadstart
- 5.7K Other Languages
- 2.3K Chinese
- 3 Deutsche Oracle Community
- 11 Español
- 1.9K Japanese
- 2 Portuguese
Create New Connection Error

Hi, This is the first time I am trying the extension, getting this error when trying to create a connection:
Error opening connection 'DBUser.DBService'.Details: Could not load file or assembly 'System.DirectoryServices.Protocols, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'.
The system cannot find the file specified. Any idea what it can be?
Thanks
Answers
-
Usually this happens when you copy a SQLNET.ORA and/or LDAP.ORA from a Windows machine and try to use it on Linux. The issue is that we currently do not support LDAP on Linux.
Please try renaming the LDAP.ORA and remove mention of LDAP from your SQLNET.ORA. Then restart Visual Studio Code.
If that doesn't fix your problem, please post the contents of your SQLNET.ORA file here.
-
I am using Windows 10 machine, not Linux. From my laptop I can successfully make connection from tools like JDeveloper, TOAD etc.
Contents of sqlnet.ora
TRACE_DIRECTORY_CLIENT = c:\temp
LOG_FILE_CLIENT = client.log
LOG_DIRECTORY_CLIENT = c:\temp
TRACE_FILE_CLIENT = client_trace.log
SQLNET.EXPIRE_TIME = 0
NAMES.DIRECTORY_PATH= (LDAP, TNSNAMES)
SQLNET.CRYPTO_SEED = "-1109189660"
DISABLE_OOB=ON
-
FYI - All of the client side connectivity code (SQLNet, etc) is different with this tool than SQLDev and Toad.
As a test, backup sqlnet.ora, then:
Remove LDAP from NAMES.DIRECTORY_PATH
Rename LDAP.ORA
Then save sqlnet.ora and restart Visual Studio Code.
-
I managed to connect to the database.
Instead of changing the sqlnet.ora file, I connected using the "Connect using a TNSNAMES.ORA Connection Alias" method.
Made of copy of the 2 files form %USERPROFILE%\.vscode\extensions\oracle.oracledevtools-19.3.2\sample\network to a desperate location. Updated the tnsnames.ora file to create an entry for the database I was connecting to.
While creating connection selected TNS Alias as connection type, selected alias, entered username / password and it worked fine.
Thanks for the help.
-
I used a combination of the above two comments and it worked.
I took the sqlnet.ora file from %USERPROFILE%\.vscode\extensions\oracle.oracledevtools-XXXXXXXXX\sample\network and replaced my own sqlnet.ora
It worked after that
Thanks guys
-
I am facing the same problem.
I have tried all the above method but its not working for me.
It looks like without LDAP.ORA file it is not possible to connect to the database.
Please help me with this.
-
MananGajjar wrote:I am facing the same problem.I have tried all the above method but its not working for me.It looks like without LDAP.ORA file it is not possible to connect to the database.Please help me with this.
Hello, LDAP does not work with the current tools. We are hoping to fix that in an upcoming release.
Do you require LDAP? If you are not sure, please check with your DBA.
If you do NOT require LDAP, you can avoid this issue by removing references to LDAP from SQLNET.ORA, TNSNAMES.ORA and by renaming LDAP.ORA
-
Support for LDAP is now available in the new 19.3.3 version. Please try it out and let me know what you think.