Troubleshooting
Problem
Error: LDAP: Error Code 32 (SCI39150)
Symptom
Error: LDAP: Error Code 32
Starting WebSphere
Cause
No Such Object
Another exception thrown frequently by the javax.naming class
is
javax.naming.NameNotFoundException: LDAP: Error code 32 - No Such
Object
Remaining name
?a??ibm-wsnName=
This error occurs when you
do not pass the "java:comp/env" prefix on the
lookup( ) method when you
lookup a datasource name. To remedy this problem,
add the "java:comp/env"
prefix to the parameter string passed to the lookup
( ) method. To ensure
platform neutrality, specify the datasource look up
string in a properties
or environment file. This way, you can have one
version of the datasource
name on distributed and another on z/OS. The z/OS version must contain the
java:comp/env prefix.
More details are on the web site: /design_center/was_zos.pdf
Resolving The Problem
This problem is a configuration problem within WebSphere. The problem is outside of Connect:Enterprise scope.
Historical Number
PRI33668
Product Synonym
[<p><b>]Fact[</b><p>]
CONNECT:Enterprise HTTP
Release 1.3.00 [<br/>] WebSphere [<br/>] SCI39150
Was this topic helpful?
Document Information
More support for:
IBM Sterling Connect:Enterprise for UNIX
Software version:
All
Document number:
437991
Modified date:
17 December 2019
UID
swg21527963