Sponsored Content
Full Discussion: Jvm.dll failed to load error
Operating Systems AIX Jvm.dll failed to load error Post 302924816 by achenle on Wednesday 12th of November 2014 01:23:02 PM
Old 11-12-2014
Have any of your environment variables changed, such as LD_LIBRARY_PATH?

What's your OS?

What's the full path of the java executable you're trying to run?

Without any "DLL" environment variables set, what's the output from "ldd -r -v /full/path/to/java"?
 

9 More Discussions You Might Find Interesting

1. HP-UX

Module jk2 failed to load into apache server!!

Hi There, Does anyone knows what could be the problem if my apache server is running but unable to load JK2 module into the server. My HTTPS is running on Apache Server 2.0.49 with ssl enabled and compiled with Mod_ssl on HPUX-11.11i. In fact we have try out the following parameter, ... (4 Replies)
Discussion started by: e_jeffhang
4 Replies

2. Shell Programming and Scripting

Need help in wrting Load Script for a Load-Resume type of load.

hi all need your help. I am wrting a script that will load data into the table. then on another load will append the data into the existing table. Regards Ankit (1 Reply)
Discussion started by: ankitgupta
1 Replies

3. Solaris

boot load failed

I modified the partitions on my Solaris 10 disk using format command in "boot cdrom -s" mode and then tried rebooting with "reboot". It said "Boot load failed". Why does this happen? I have faced this error before:( and I went in for a fresh installation of the OS.Can anyone tell me the reason as... (1 Reply)
Discussion started by: lydiaEd
1 Replies

4. Solaris

pam_unix_cred.so.1 failed to load

My solaris 8 server messages log recored error "Sep 30 21:35:00 bkp1 cron: open_module: /usr/lib/security/pam_unix_cred.so.1 failed: ld.so.1: cron: fatal: libproject.so.1: open failed: No such file or directory" Any idea what is this related to and how to stop? thanks in advance. (2 Replies)
Discussion started by: admin@solaris
2 Replies

5. SuSE

Failed to load HCA driver and Access Layer

Hi All, I got the following errors when i was trying to restart Infiniband service. Loading cxgb3 driver : Loading HCA driver and Access Layer : The command managed to bring up the services, but without RDMA modules loaded from /etc/init.d/openibd status output. Is the missing of RDMA... (0 Replies)
Discussion started by: dchm
0 Replies

6. Solaris

Cygwin X Server error: xdmcp fatal error session failed session 23 failed for display

Hi, i got the following error when i tried to access the cygwin x server from a windows XP PC. "xdmcp fatal error session failed session 23 failed for display" Alternatively, when i tried to access the same Cygwin X Server from another windows XP PC which is on a different LAN... (3 Replies)
Discussion started by: HarishKumarM
3 Replies

7. Solaris

Rpcinfo: can't contact portmapper: RPC: Authentication error; why = Failed (unspecified error)

I have two servers with a fresh install of Solaris 11, and having problems when doing rpcinfo between them. There is no firewall involved, so everything should theoretically be getting through. Does anyone have any ideas? I did a lot of Google searches, and haven't found a working solution yet. ... (2 Replies)
Discussion started by: christr
2 Replies

8. UNIX for Dummies Questions & Answers

VPS has load 200, httpd load no activity, netstat nothing

Hello, on my hostserver i see one VPS of mine got load of 200.00 and netstat nothing (not a single blank line on netstat command) after some time, netstat started showing connections, but i see no excessive IP connections. tail -f /var/log/httpd/access_log shows no activity /var/log/messages ;... (1 Reply)
Discussion started by: postcd
1 Replies

9. Solaris

Fresh Install - Boot Load Failed

I have M10-1. Installation OS 10 from cdrom external. Here message from OK Prompt {0} ok probe-scsi-all /pci@8000/pci@4/pci@0/pci@2/pci@0/usb@4,1/cdrom@1 Unit 0 Removable Read Only device HL-DT-STDVDRAM GP65NB60 PF00 But.. {0} ok boot... (3 Replies)
Discussion started by: mbahjiman
3 Replies
sane-dll(5)						   SANE Scanner Access Now Easy 					       sane-dll(5)

NAME
sane-dll - SANE dynamic backend loader DESCRIPTION
The sane-dll library implements a SANE (Scanner Access Now Easy) backend that provides access to an arbitrary number of other SANE back- ends. These backends may either be pre-loaded at the time the sane-dll library is built or, on systems that support dynamic loading of shared libraries, the backends may be loaded at runtime. In the latter case, adding support for a new backend simply involves installing the relevant library in /usr/lib64/sane and adding an entry to the dll.conf configuration file. In other words, no applications need to be modified or recompiled to add support for new devices. DEVICE NAMES
This backend expects device names of the form: backend:device Where backend is the name of the backend and device is the name of the device in this backend that should be addressed. If the device name does not contain a colon (:), then the entire string is treated as the device string for the default backend. The default backend is the backend listed last in the configuration file (see below) or the first pre-loaded backend (if any). CONFIGURATION
The contents of the dll.conf file is a list of backend names that may be loaded dynamically upon demand. Empty lines are ignored, also everything after a hash mark (#). A sample configuration file is shown below: net # this is a comment pnm mustek It is also possible to add a file in /etc/sane.d/dll.d that contains the list of backends to be added. Backends mentioned in a file included in this directory will be added before any backends listed in dll.conf. Files in /etc/sane.d/dll.d can be freely named. They shall follow the format conventions as apply for dll.conf. Note that backends that were pre-loaded when building this library do not have to be listed in this configuration file. That is, if a backend was preloaded, then that backend will always be present, regardless of whether it's listed in the configuration file or not. The list of preloaded backends is determined by macro PRELOADABLE_BACKENDS in file backend/Makefile.in of the SANE source code distribu- tion. After changing the value of this macro, it is necessary to reconfigure, rebuild, and reinstall SANE for the change to take effect. Aliases are defined in the config file dll.aliases. It can contain entries of the form alias SomeName SaneDeviceName alias "Some Name" SaneDeviceName hide SaneDeviceName For example: alias Epson net:somehost:epson:/dev/sgX alias "Siemens ST400" st400:/dev/sgY hide net:somehost:pnm:0 hide net:somehost:pnm:1 alias "Read from file" pnm:0 hide pnm:1 Aliased device names are automatically hidden. The idea is that users don't have to deal with complicated device names (especially for networked devices), and to hide other exported devices which might confuse them. Note that a hidden device can still be accessed if the device name is known, it just doesn't appear on the list. FILES
/etc/sane.d/dll.aliases The list of aliased or hidden backends. /etc/sane.d/dll.conf The backend configuration file (see also description of SANE_CONFIG_DIR below). /usr/lib64/sane/libsane-dll.a The static library implementing this backend. /usr/lib64/sane/libsane-dll.so The shared library implementing this backend (present on systems that support dynamic loading). ENVIRONMENT
SANE_CONFIG_DIR This environment variable specifies the list of directories that may contain the configuration file. Under UNIX, the directories are separated by a colon (`:'), under OS/2, they are separated by a semi-colon (`;'). If this variable is not set, the configura- tion file is searched in two default directories: first, the current working directory (".") and then in /etc/sane.d. If the value of the environment variable ends with the directory separator character, then the default directories are searched after the explic- itly specified directories. For example, setting SANE_CONFIG_DIR to "/tmp/config:" would result in directories "tmp/config", ".", and "/etc/sane.d" being searched (in this order). SANE_DEBUG_DLL If the library was compiled with debug support enabled, this environment variable controls the debug level for this backend. E.g., a value of 128 requests all debug output to be printed. Smaller levels reduce verbosity. Value Description 0 print severe errors only 1 print normal errors and important messages 2 print normal messages 3 print debugging messages 4 print everything Example: export SANE_DEBUG_DLL=3 SEE ALSO
sane(7), scanimage(1), sane-"backendname"(5) AUTHOR
David Mosberger 13 Jul 2008 sane-dll(5)
All times are GMT -4. The time now is 11:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy