'How do I solve the: Failed to load the sqljdbc_auth.dll cause is not in the java path while working in Jboss/SQL Server?

I'm new in stack overflow, I'm new to web programming. So, I'm making a web app using JSP/servlets and I'm using java 6/jboss server. When I try to connect to the server (I'm using the windows authentication, this means integratedSecurity=true in the string path) throws me the exception. I already tried to put the DLL in the bin folder in the JBoss path, in system 32, and nothing seems to work. I'm using NetBeans, by the way.

Thanks for any help.

javasql-server-2008jbossandroid-sqliteandroid-permissionsandroid-fileandroid-11android-storage


Solution 1:[1]

You've not added the path where sqljdbc_auth.dll is present. Find out in the system where the DLL is and add that to your classpath.

And if that also doesn't work, add the folder where the DLL is present (I'm assuming \Microsoft SQL Server JDBC Driver 3.0\sqljdbc_3.0\enu\auth\x86) to your PATH variable.

1) Download the JDBC Driver here.

2) unzip the file and go to sqljdbc_version\fra\auth\x86 or \x64 3) copy the sqljdbc_auth.dll to C:\Program Files\Java\jre_Version\bin 4) Finally restart eclipse

Solution 2:[2]

to resolve this problem try to change the name of dll files like is required in IDE enter image description here

Solution 3:[3]

I have exactly the same problem. Application A creates an SQL database file somewhere, for example as "Music/Bla/mydatabase.db". Now application B must read that file and cannot. So what are the options?

  1. Claim the MANAGE_EXTERNAL_STORAGE PERMISSION and offer your application via F-Droid or downloadable apk, because Google will deny to publish it in Play Store.
  2. Claim target API 29 and legacy access and offer your application via F-Droid or downloadable apk, because Play Store does not allow to publish new application or updates with API 29 or below.
  3. Use the proprietary SAF method to copy the database file to your application's private directory tree and open it from there.
  4. Use iOS.
  5. Maybe more.

Generally Google's file access strategy is a pain for both developers (makes programming complicated) and users (makes programs slow).

PS: Similar problem with .jpg files. Given the path, the files cannot be opened. There is told to be a solution somewhere in the media storage whatever API (Google: "raw file path access for media"), but I could not find it, yet, because the documentation is insufficient and lacks usable examples.

Sources

This article follows the attribution requirements of Stack Overflow and is licensed under CC BY-SA 3.0.

Source: Stack Overflow

Solution Source
Solution 1 Anup Dey
Solution 2 m Piroli
Solution 3

Related Questions