Error: "C:\Lotus\Domino\nlsxbe.dll: The specified procedure could not be found"

(Last modified: 19Jul2004)

This document (10093640) is provided subject to the disclaimer at the end of this document.

fact

Nsure Identity Manager 2.0

Novell Lotus Notes Driver

Microsoft Windows 2000 Server

Microsoft Windows Server 2003 Enterprise Edition

symptom

Error: "C:\Lotus\Domino\nlsxbe.dll: The specified procedure could not be found"

Message = Exception caused by SubscriptionShim.init()

java.lang.UnsatisfiedLinkError: C:\Lotus\Domino\nlsxbe.dll: The specified procedure could not be found

Notes driver fails to start and throws this error right after reading the environment information.

The problem happens on a server with a current version of Notes that has been upgraded to a newer version.

If you upgraded to Domino server 6.5 sometimes the nlsxbe.dll library doesn't get registered properly. You need to do so by running regsvr32 nlsxbe.dll.

Another symptom of the problem might be that you will get problems trying to register the library if you don't specify the full path when running regsvr32 (that means you would need to type regsvr32 C:\Lotus\Domino\nlsxbe.dll in order to register the library correctly)

You may also get the error: java.lang.UnsatisfiedLinkError: C:\Lotus\Domino\nlsxbe.dll: The operating system cannot run lassLoader$NativeLibrary.load(Native Method)

cause

Some modules of the previous installation are still present on the WINNT\SYSTEM32 or WINNT directories. Because they are first in the search path, the outdated dlls are loaded first and some functionality gets broken.

fix

Verify that the most recent modules are always loaded. You may do so by ensuring that the PATH and java.library.path always refer to the Lotus\Domino directory before they point to the WINNT\SYSTEM32 or WINNT directories.

It is also recommendable that you clean up your system properly to work with the version of Notes you are currently running. Compare the dlls present in the Lotus\Domino directory and make sure to have the same version if the dll is present in any of the system directories.

This error in particular was given because of an incorrect version of the JS32.DLL file. IBM (as per document #1087014) recommends that if you have problems with this you also check for these files: NLSCCSTR.DLL, NSTRINGS.DLL and NNOTES.DLL.

note

Note that this error is essentially different to the following one: java.lang.UnsatisfiedLinkError: no nlsxbe in shared library path.

This error tells you that the nlsxbe.dll library could not be located. Most likely this indicates that the system wide PATH variable doesn't contain the C:\Lotus\Domino path on it, that the server hasn't been rebooted after adjusting the environment variable or that there is a typo in the setting of the PATH variable.

document

Document Title:	Error: "C:\Lotus\Domino\nlsxbe.dll: The specified procedure could not be found"
Document ID:	10093640
Solution ID:	NOVL97834
Creation Date:	15Jul2004
Modified Date:	19Jul2004
Novell Product Class:	DirXML

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.