The Domino Server
plug-in might fail to load on an IBM i system
Error
messages in the Domino console can indicate more detailed
error messages in the Notes® spool files. For example,
if you see the following error message on your Domino console,
perform the following steps:
Sample error message:
01/05/2006 13:28:56 HTTP Server:
Failed to load DSAPI module
/QSYS.LIB/QWAS8.LIB/LIBDOMINOH.SRVPGM
- From a CL command prompt, enter the Work with Spool Files (WRKSPLF) command:
WRKSPLF QNOTES
- Use option 5 to open the applicable spool
file for your notes server.
You might have to stop your Domino server
to view the spool file.
- Inspect the output to find applicable error messages. For example,
suppose that the following entry is in the log:
ERROR: lib_sxp: sxpCreate: Can't open
'/QIBM/UserData/webas5/base/rb5025test/config
/cells/plugin-cfg.xml', OS Err: 3401
ERROR: ws_config_parser: configParserParse:
Failed to create the sxpParser object for
profile_root/config/plugin-cfg.xml
ERROR: ws_common: websphereUpdateConfig:
Failed parsing plugin config file:
ERROR: profile_root/config/plugin-cfg.xml
ERROR: The above file may not have correct authorities.
ERROR: Do WRKLNK, Opt 9 on above file. ERROR: Check that QTMHHTTP and QNOTES have correct authorities:
ERROR: QTMHHTTP *RX ERROR: QNOTES *RX ERROR: ws_common: websphereInit:
Failed to load the config file
ERROR: domino5_plugin: FilterInit:
Failed to initialize WebSphere
The Domino Server
plug-in might fail to configure on a Solaris platform
If
this occurs during installation, a
dsapi_stderr.txt file
is created in the logs directory and you get the following error messages:
lotus.notes.NotesException: Could not load dll for system name SUNOS
at lotus.notes.NotesThread.load(NotesThread.java:210)
at lotus.notes.NotesThread.<clinit>(NotesThread.java:24)
java.lang.UnsatisfiedLinkError: NnotesInitThread
at lotus.notes.NotesThread.NnotesInitThread(Native Method)
at lotus.notes.NotesThread.initThread(NotesThread.java:99)
at lotus.notes.NotesThread.run(NotesThread.java:133)
You
can configure the WebSphere Application Server
or Domino Server plug-in manually using the Domino Server
Web Administration tool. Use the following procedures:
- Start the Domino Server.
- Enter the URL for the Domino Server Web Administration
site using a browser. For example, http://host_name/names.nsf.
Enter the administrator user name and password.
- Double-click Server-Servers.
- Double-click WebServer to configure.
- Double-click Edit Server.
- Double-click Internet Protocol.
- Add the WebSphere Application Server DSAPI plug-in
to the DSAPI field. For example, app_server_root/bin/libdomino5_http.so
If
there are already DSAPI filter files specified, use a space to delimit
the WebSphere Application Server plug-in file.
- Double-click Save and Close.
- Restart the Domino Server.
Avoiding a DSAPI
filter-loading error when the Lotus Domino Server
starts
On operating systems such as AIX® or Linux®,
if the Lotus Domino Web Server starts using
a nonroot user, you are likely to generate a DSAPI filter-loading
error when the Lotus Domino Server starts:
Error loading DSAPI filter.
Filter not loaded: app_server_root/bin/libdomino6_http.a
Manually
change the WebSphere Application Server bin directory
permissions from 750 to 755 to
run Lotus Domino Server as a nonroot user
and not generate the error.
You must also change permissions
on the WebSphere Application Server logs directory
to 777 to allow Lotus Domino Server
to write to the log. However, this change poses a security risk.
If
the Lotus Domino Server is started as root,
the problem does not occur.