Embedded LDAP Error
I just installed the Oracle Fusion Middleware server. The server start fines and I can get to the admin console and use it, but once I deploy the console I begin to get exceptions on the server and it pegs the processor at 100%.
The expection is :
<Nov 4, 2009 11:14:00 PM EST> <Critical> <EmbeddedLDAP> <BEA-000000> <java.lang.NegativeArraySizeException
at com.octetstring.vde.EntryChanges.readBytes(EntryChanges.java:274)
at com.octetstring.vde.EntryChanges.<init>(EntryChanges.java:72)
at com.octetstring.vde.replication.BackendChangeLog.getChange(BackendChangeLog.java:548)
at com.octetstring.vde.replication.Replicator.run(Replicator.java:180)
at com.octetstring.vde.replication.Replication.run(Replication.java:339)
The exception is repeated about every second.
I haven't tried to use the LDAP server for anything. How do I fix this?
im having the same error on the WEBLOGIC ADMIN log file:
The NTservice-pstst-WebLogicAdmin.log is fulling up with the same error:
<Nov 20, 2009 8:53:38 AM CST> <Critical> <EmbeddedLDAP> <000000> <java.lang.NegativeArraySizeException
at com.octetstring.vde.EntryChanges.readBytes(EntryChanges.java:274)
at com.octetstring.vde.EntryChanges.<init>(EntryChanges.java:72)
at com.octetstring.vde.replication.BackendChangeLog.getChange(BackendChangeLog.java:548)
at com.octetstring.vde.replication.Replicator.run(Replicator.java:180)
at com.octetstring.vde.replication.Replication.run(Replication.java:339)
Any thoughts to why its written every other min or so...
thx/t
Similar Messages
-
Weblogic.server.ServiceFailureException:com- embedded LDAP error
Hi
While starting teh weblogic server, I am getting error as
weblogic.server.ServiceFailureException: Error initialisng embedded LDAP server - with nested exception
java.lang.ClassCastException:com.octetstring.vde.backend.BackendRoot
the server is not started (I have installed it as a window service in Win2k)
Any help on this ?there are few different ways to fix this. I do this frequently
--Delete the data folder and boot the server it will fix the issue. You will lose all the users information (except admin user) need to recrate any ohter users you created.make sure backup data folder
-- Second get the data folder from domain_bak folder
Hope this will fix your problem
Thanks
ksr
Edited by: ksr11 on Nov 24, 2010 10:33 AM -
WebLogicServer Embedded LDAP Error!!
Hi,
In the weblogic server environment I am facing the below issue while starting the admin server.
<Error> <EmbeddedLDAP> <AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1372840341006> <BEA-171500> <The embedded LDAP Configuration file: 'Oracle\Middleware\wlserver_10.3\server\lib\adaptertypes.prop' was not found and the embedded LDAP server has not been started. To resolve the problem, ensure that weblogic.home is defined correctly (it should have a lib subdirectory that contains this file).>
<Critical> <WebLogicServer> <AdminServer> <main> <<WLS Kernel>> <> <> <1372840341022> <BEA-000386> <Server subsystem failed. Reason: weblogic.ldap.EmbeddedLDAPException: Could not find configuration files - see log file for more information
weblogic.ldap.EmbeddedLDAPException: Could not find configuration files - see log file for more information
at weblogic.ldap.EmbeddedLDAP.validateVDEConfigFiles(EmbeddedLDAP.java:936)
at weblogic.ldap.EmbeddedLDAP.start(EmbeddedLDAP.java:255)
at weblogic.t3.srvr.SubsystemRequest.run(SubsystemRequest.java:64)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:178)
>
The adaptertypes.prop file is not available in the Oracle\Middleware\wlserver_10.3\server\lib location.
Please advise me on how to resolve this issue..
ThanksBEA-171500
Error: The embedded LDAP Configuration file: fileName was not found and the embedded LDAP server has not been started. To resolve the problem, ensure that weblogic.home is defined correctly (it should have a lib subdirectory that contains this file).
Description
The lib directory contains the configuration files required for the embedded LDAP server. If those files are missing or the appropriate directory cannot be found, then the embedded LDAP server cannot initialize.
Cause
The embedded LDAP server cannot find the specified file. This file is installed as part of the installation process. Most likely, the default directory is not the server root directory and the lib subdirectory cannot be found.
Action
Set the default directory to the server root directory or set the location of the embedded LDAP server configuration files via the weblogic.EmbeddedLDAPConfigDirectory system property.
As suggested in the Action plan for error code 171500,try setting up EmbeddedLDAPConfigDirectory system property in the server start-up script or in setDomainEnv.sh script.
You can set the same as JAVA_OPTIONS in the script.
e.g.
JAVA_OPTIONS="-Dweblogic.EmbeddedLDAPConfigDirectory=/home/mwhome1/wlserver_10.3/server/lib ${JAVA_OPTIONS}"
export JAVA_OPTIONS
Hope this helps!!
Thanks,
Vijaya -
How to change password for a user in WLS 7.0 embedded ldap in code?
I asked the similar question before but don't have an answer yet.
I need to change password for a user in my Java code. Any help will be
appreciated.
Here is my stack trace:
c:\Test>java -classpath . testEmbeddedLdap
attribute: uid
attribute: description
attribute: objectclass
attribute: wlsMemberOf
attribute: sn
attribute: cn
javax.naming.NoPermissionException: [LDAP: error code 50 - Insufficient
Access Rights]; remaining name
'uid=myRegularUser,ou=people,ou=myrealm,dc=mydomain'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2872)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2810)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2616)
at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1374)
at
com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDir
Context.java:255)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(Partial
CompositeDirContext.java:172)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(Partial
CompositeDirContext.java:161)
at
javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.
java:146)
at testEmbeddedLdap.main(testEmbeddedLdap.java:30)
Here is my testing code:
<PRE>
import java.util.*;
import javax.naming.*;
import javax.naming.directory.*;
public class testEmbeddedLdap {
public static void main(String[] argv) {
Hashtable env = new Hashtable(11);
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.sun.jndi.ldap.LdapCtxFactory");
env.put(Context.PROVIDER_URL, "ldap://localhost:7001");
env.put(Context.SECURITY_AUTHENTICATION, "simple");
env.put(Context.SECURITY_PRINCIPAL, "uid=myAdministrator, ou=people,
ou=myrealm, dc=mydomain");
env.put(Context.SECURITY_CREDENTIALS, "myAdministrator");
try {
DirContext ctx = new InitialDirContext(env);
String
sUser="uid=myRegularUser,ou=people,ou=myrealm,dc=mydomain";
String sOldPassword="myRegularUser";
String sNewPassword="newpassword";
for (NamingEnumeration ae = ctx.getAttributes(sUser).getAll();
ae.hasMore(); ) {
Attribute attr = (Attribute)ae.next();
System.out.println("attribute: " + attr.getID());
ModificationItem[] mods = new ModificationItem[2];
Attribute mod0 = new BasicAttribute("userpassword",
sOldPassword);
mods[0] = new ModificationItem(DirContext.REMOVE_ATTRIBUTE,
mod0);
Attribute mod1 = new BasicAttribute("userpassword",
sNewPassword);
mods[1] = new ModificationItem(DirContext.ADD_ATTRIBUTE, mod1);
ctx.modifyAttributes(sUser, mods);
ctx.close();
} catch (NamingException e) {
e.printStackTrace();
</PRE>
"Neil Smithline" <[email protected]> wrote in message
news:[email protected]...
Two things. First, I'm not exactly sure what password you are trying to
change. The LDAP server's password or a user's password in the LDAP
server. Second, could you please post a stack trace.
Thanks - Neil
K Wong wrote:
I am using (javax.naming.directory.DirContext.modifyAttributes) to
change
password to our development Weblogic 7.0 embedded LDAP.
I login as the system administrator (a user in the administratorsgroup),
but always gets the javax.naming.NoPermissionException - InsufficientAccess
Rights.
What user should I use? Any help will be appreciated.Hai,
This condition based execution requires - javascript coding.
In miscelleaneous tools bar, you have an option of SCRIPT_ITEM writer tool, drag the tool into your WAD layout, and select the properties , choose the editor option and paste your coding. that's it.
Alternate option :
in your web application design layout , you will fine XHTML coding editor , there you need to write coding and execute the same.
Hope this will help to you.
Assign Points if its really useful.
Cheers !!!
Bye
Regards,
Giri -
Special characters not supported in Embedded LDAP
Hi All,
I had a very hectic time trying to debug this issue.
The requirement was to provide support for + as a special character in the userId.
As the RFC says to escape it using a backslash.I did exactly that.
However, it kept on giving me Naming Violation... LDAP error code 64.
SO, inorder to verify the code which I had writted ... I connected the Apache Directory Server in place.
This time round the code worked.
Can someone help me with the resolution ... as in, does the Embedded LDAP schema needs modification.... apparently it does.
Thanks & Regards
Yukti KauraThanks !
How do we raise a support issue .Is there any Id where I can drop a mail ?
Yukti -
Hi,
I am getting the following error when I try to do a search on an ldap (AD LDS) database:
javax.naming.NameNotFoundException: [LDAP: error code 32 - 0000208D: NameErr: DSID-031522C9, problem 2001 (NO_OBJECT), data 0, best match of:
'DC=AppPartFE,DC=com'
]; remaining name 'cn=Users,dc=AppPartFE,dc=com'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.searchAux(Unknown Source)
at com.sun.jndi.ldap.LdapCtx.c_search(Unknown Source)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_search(Unknown Source)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown Source)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.search(Unknown Source)
at javax.naming.directory.InitialDirContext.search(Unknown Source)
at Test.<init>(Test.java:70)
at Test.main(Test.java:118)
I can bind successfully using either the userPrincipalName (UPN) or the Distinguished Name (DN), however my search is failing.
It is almost as if I am connected to the db tree at the wrong place. Do I need a different search scope?
I appreciate any assistance you can provide.
Here is my code:
import java.util.*;
import static java.lang.System.err;
import javax.naming.Context;
import javax.naming.NamingEnumeration;
import javax.naming.NamingException;
import javax.naming.directory.DirContext;
import javax.naming.directory.SearchControls;
import javax.naming.directory.SearchResult;
import javax.naming.ldap.InitialLdapContext;
import javax.naming.ldap.LdapContext;
public class Test
public Test()
Properties prop = new Properties();
prop.put("java.naming.factory.initial", "com.sun.jndi.ldap.LdapCtxFactory");
prop.put("java.naming.provider.url", "ldap://MyHost.Mydomain.labs.CompanyX.com:50004");
String strProviderUrl = "ldap://MyHost.Mydomain.labs.CompanyX.com:50004";
// Can successfully bind with the userPrincipalName in AD LDS
//prop.put("java.naming.security.principal", "[email protected]");
// Can successfully bind with Distinguished Name
// Note: the string is case insensitive and embedded blank after a comma is not a problem
prop.put("java.naming.security.principal", "cn=tst0001,cn=Users,dc=AppPartFE,dc=com");
prop.put("java.naming.security.credentials", "password");
try {
LdapContext ctx = new InitialLdapContext(prop, null);
System.out.println("Bind successful");
//I am successful to this point....
//now try doing a search on another user
String strFilter = "(&(objectClass=userProxy)(sAMAccountName=tst0001))";
SearchControls searchControls = new SearchControls();
searchControls.setSearchScope(SearchControls.SUBTREE_SCOPE); //works with object class=* to find top partition node
NamingEnumeration<SearchResult> results = ctx.search("cn=Users,dc=AppPartFE,dc=com", strFilter, searchControls);
SearchResult searchResult = null;
if(results.hasMoreElements()) {
searchResult = (SearchResult) results.nextElement();
//make sure there is not another item available, there should be only 1 match
if(results.hasMoreElements()) {
System.err.println("Matched multiple users for the accountName");
catch (NamingException ex) {
ex.printStackTrace();
public static void main(String[] args)
Test ldaptest = new Test();Because you are specifiying a base distinguished name in your ldap url, the ldap context will be rooted at that context and all subsequent objects will be relative to that base distinguished name.//connect to my domain controller
String ldapURL = "ldaps://rhein:636/dc=bodensee,dc=de";andString userName = "CN=verena bit,OU=Lehrer,OU=ASR,DC=bodensee,DC=de";results in an fully distinguished name of:CN=verena bit,OU=Lehrer,OU=ASR,DC=bodensee,DC=de,dc=bodensee,dc=deEither specify your ldap url asString ldapURL = "ldaps://rhein:636";and leave your username as is, or specify the user object relative to the base distinguished name in the ldapurlString userName = "CN=verena bit,OU=Lehrer,OU=ASR"; -
Petstore - unable to connect to embedded LDAP Server
I have installed the Petstore 1.3.1 02 demo on a Weblogic 8.1 server on Windows XP. After running the Configuration wizard, when trying to start the PetStore Administration Sever using the startPetStoreWebLogic.cmd file, I receive the following error message:
The WebLogic Server did not start up properly.
weblogic.security.spi.ProviderInitializationException: [Security:090314]Entitlement Engine unable to connect to the embedded LDAP server
netscape.ldap.LDAPException: error result (50)
An LDAPException with error result 50, according to the API Specification, means insufficient access rights, but as I am doing everything according to the readme, I don't know what the problem is.
Has anybody had the same problem or knows what to do to solve this?
Thanks very much!Hi,
By removing the encrypted 'Credential' for the
EmbeddedLDAP entry in config.xml workaround it,
it went on but the real problem is with the
deployment of the 4 ears inside applications dir.
Would appreciate of anyone could enlighten.
jchintk
####<Jan 28, 2005 2:59:31 PM SGT> <Debug> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 0
Module: customer-ejb.jar Error: [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 2:59:31 PM SGT> <Error> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 0 for the application appsdirpetstore_ear.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 0
Module: customer-ejb.jar Error: [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 0
Module: customer-ejb.jar Error: [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2396)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 2:59:34 PM SGT> <Info> <Application Poller> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149400> <Activating application: appsdirsupplier_ear>
####<Jan 28, 2005 2:59:34 PM SGT> <Info> <Deployer> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149038> <A deployment task with ID 1 for application appsdirsupplier_ear is being initiated.>
####<Jan 28, 2005 2:59:34 PM SGT> <Warning> <DRS> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-002506> <The current version 0 for DataIdentifier DataIdentifierID: 1 does not match with incoming version 1 for a one-phase update.>
####<Jan 28, 2005 2:59:34 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149033> <preparing application appsdirsupplier_ear on myserver>
####<Jan 28, 2005 2:59:34 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149033> <failed application appsdirsupplier_ear on myserver>
####<Jan 28, 2005 2:59:34 PM SGT> <Warning> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149004> <Failures were detected while initiating Deploy task for application appsdirsupplier_ear.>
####<Jan 28, 2005 2:59:34 PM SGT> <Debug> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 1
Module: supplierpo-ejb.jar Error: [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 2:59:34 PM SGT> <Error> <Deployer> <oakley> <myserver> <ExecuteThread: '3' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 1 for the application appsdirsupplier_ear.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 1
Module: supplierpo-ejb.jar Error: [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: Prepare failed. Task Id = 1
Module: supplierpo-ejb.jar Error: [EJB:011025]The XML parser encountered an error in your deployment descriptor. Please ensure that your DOCTYPE is correct. You may wish to compare your deployment descriptors with the WebLogic Server examples to ensure the format is correct. The error was:
PAction[30633251](.ejb-jar.relationships.ejb-relation.ejb-relation-name.) must be a non-empty string.
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2396)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 2:59:38 PM SGT> <Info> <Application Poller> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149400> <Activating application: appsdirpetstoreadmin_ear>
####<Jan 28, 2005 2:59:38 PM SGT> <Info> <Deployer> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149038> <A deployment task with ID 2 for application appsdirpetstoreadmin_ear is being initiated.>
####<Jan 28, 2005 2:59:38 PM SGT> <Warning> <DRS> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-002506> <The current version 0 for DataIdentifier DataIdentifierID: 1 does not match with incoming version 2 for a one-phase update.>
####<Jan 28, 2005 2:59:55 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149033> <preparing application appsdirpetstoreadmin_ear on myserver>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module admin of application appsdirpetstoreadmin_ear is transitioning from unprepared to prepared on server myserver.>
####<Jan 28, 2005 2:59:56 PM SGT> <Warning> <HTTP> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-101304> <Webapp: ServletContext(id=12397950,name=admin,context-path=/admin), the role: administrator defined in web.xml has not been mapped to principals in security-role-assignment in weblogic.xml. Will use the rolename itself as the principal-name.>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149060> <Module admin of application appsdirpetstoreadmin_ear successfully transitioned from unprepared to prepared on server myserver.>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module asyncsender-ejb.jar of application appsdirpetstoreadmin_ear is transitioning from unprepared to prepared on server myserver.>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <EJB> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-010008> <EJB Deploying file: asyncsender-ejb.jar>
####<Jan 28, 2005 2:59:56 PM SGT> <Info> <EJB> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-010087> <The EJB deployment named: asyncsender-ejb.jar is being recompiled within the WebLogic Server. Please consult the server logs if there are any errors. It is also possible to run weblogic.ejbc as a stand-alone tool to generate the required classes. The generated source files will be placed in C:\bea\user_projects\domains\petstore\.\myserver\.wlnotdelete\EJBCompilerCache\283hhgsoep72.>
####<Jan 28, 2005 3:00:00 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149061> <Module asyncsender-ejb.jar of application appsdirpetstoreadmin_ear failed to transition from unprepared to prepared on server myserver.>
####<Jan 28, 2005 3:00:00 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149059> <Module admin of application appsdirpetstoreadmin_ear is transitioning from prepared to unprepared on server myserver.>
####<Jan 28, 2005 3:00:00 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149060> <Module admin of application appsdirpetstoreadmin_ear successfully transitioned from prepared to unprepared on server myserver.>
####<Jan 28, 2005 3:00:00 PM SGT> <Info> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149033> <failed application appsdirpetstoreadmin_ear on myserver>
####<Jan 28, 2005 3:00:02 PM SGT> <Info> <Application Poller> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149400> <Activating application: appsdiropc_ear>
####<Jan 28, 2005 3:00:02 PM SGT> <Info> <Deployer> <oakley> <myserver> <Main Thread> <<WLS Kernel>> <> <BEA-149038> <A deployment task with ID 3 for application appsdiropc_ear is being initiated.>
####<Jan 28, 2005 3:00:00 PM SGT> <Warning> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149004> <Failures were detected while initiating Deploy task for application appsdirpetstoreadmin_ear.>
####<Jan 28, 2005 3:00:06 PM SGT> <Debug> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149078> <Stack trace for message 149004
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for asyncsender-ejb.jar
Module: asyncsender-ejb.jar Error: Exception preparing module: EJBModule(asyncsender-ejb.jar,status=NEW)
Unable to deploy EJB: AsyncSenderEJB from asyncsender-ejb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010174]The resource-ref 'jms/QueueConnectionFactory' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
at weblogic.ejb20.deployer.EnvironmentBuilder.addJMSConnectionFactoryRef(Lweblogic.management.descriptors.ejb11.ResourceRefMBean;Ljava.util.Map;)V(EnvironmentBuilder.java:439)
at weblogic.ejb20.deployer.EnvironmentBuilder.addResourceReferences(Ljava.util.Collection;Ljava.util.Map;)V(EnvironmentBuilder.java:226)
at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(Ljavax.naming.Context;Lweblogic.ejb20.interfaces.BeanInfo;Ljava.lang.String;Ljava.lang.String;)Ljavax.naming.Context;(EJBDeployer.java:379)
at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(Lweblogic.ejb20.interfaces.BeanInfo;Lweblogic.ejb20.interfaces.DeploymentInfo;Lweblogic.management.configuration.EJBComponentMBean;Ljavax.naming.Context;)Ljavax.naming.Context;(EJBDeployer.java:1172)
at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(Lweblogic.management.configuration.EJBComponentMBean;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;)V(EJBDeployer.java:943)
at weblogic.ejb20.deployer.EJBDeployer.prepare(Lweblogic.utils.jars.VirtualJarFile;Ljava.lang.ClassLoader;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;Ljava.util.Map;)V(EJBDeployer.java:1345)
at weblogic.ejb20.deployer.EJBModule.prepare(Ljava.lang.ClassLoader;)V(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.j2ee.J2EEApplicationContainer$Component;Z)V(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules([Lweblogic.j2ee.J2EEApplicationContainer$Component;Ljava.lang.String;Z)V(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare([Lweblogic.j2ee.J2EEApplicationContainer$Component;[Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(Ljava.lang.String;[Lweblogic.management.configuration.ComponentMBean;[Ljava.lang.String;)V(J2EEApplicationContainer.java:1070)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer()V(SlaveDeployer.java:2513)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2463)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
>
####<Jan 28, 2005 3:00:06 PM SGT> <Error> <Deployer> <oakley> <myserver> <ExecuteThread: '4' for queue: 'weblogic.kernel.System'> <<WLS Kernel>> <> <BEA-149201> <Failed to complete the deployment task with ID 2 for the application appsdirpetstoreadmin_ear.
weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for asyncsender-ejb.jar
Module: asyncsender-ejb.jar Error: Exception preparing module: EJBModule(asyncsender-ejb.jar,status=NEW)
Unable to deploy EJB: AsyncSenderEJB from asyncsender-ejb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010174]The resource-ref 'jms/QueueConnectionFactory' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
at weblogic.ejb20.deployer.EnvironmentBuilder.addJMSConnectionFactoryRef(Lweblogic.management.descriptors.ejb11.ResourceRefMBean;Ljava.util.Map;)V(EnvironmentBuilder.java:439)
at weblogic.ejb20.deployer.EnvironmentBuilder.addResourceReferences(Ljava.util.Collection;Ljava.util.Map;)V(EnvironmentBuilder.java:226)
at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(Ljavax.naming.Context;Lweblogic.ejb20.interfaces.BeanInfo;Ljava.lang.String;Ljava.lang.String;)Ljavax.naming.Context;(EJBDeployer.java:379)
at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(Lweblogic.ejb20.interfaces.BeanInfo;Lweblogic.ejb20.interfaces.DeploymentInfo;Lweblogic.management.configuration.EJBComponentMBean;Ljavax.naming.Context;)Ljavax.naming.Context;(EJBDeployer.java:1172)
at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(Lweblogic.management.configuration.EJBComponentMBean;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;)V(EJBDeployer.java:943)
at weblogic.ejb20.deployer.EJBDeployer.prepare(Lweblogic.utils.jars.VirtualJarFile;Ljava.lang.ClassLoader;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;Ljava.util.Map;)V(EJBDeployer.java:1345)
at weblogic.ejb20.deployer.EJBModule.prepare(Ljava.lang.ClassLoader;)V(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.j2ee.J2EEApplicationContainer$Component;Z)V(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules([Lweblogic.j2ee.J2EEApplicationContainer$Component;Ljava.lang.String;Z)V(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare([Lweblogic.j2ee.J2EEApplicationContainer$Component;[Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(Ljava.lang.String;[Lweblogic.management.configuration.ComponentMBean;[Ljava.lang.String;)V(J2EEApplicationContainer.java:1070)
at weblogic.management.deploy.slave.SlaveDeployer$ComponentActivateTask.prepareContainer()V(SlaveDeployer.java:2513)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2463)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.createContainer()Z(SlaveDeployer.java:2467)
at weblogic.management.deploy.slave.SlaveDeployer$ActivateTask.prepare()V(SlaveDeployer.java:2379)
at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(Lweblogic.management.deploy.OamVersion;Lweblogic.management.runtime.DeploymentTaskRuntimeMBean;Z)V(SlaveDeployer.java:866)
at weblogic.management.deploy.slave.SlaveDeployer.prepareDelta(Lweblogic.management.deploy.OamDelta;Lweblogic.management.deploy.OamVersion;ZLjava.lang.StringBuffer;)Z(SlaveDeployer.java:594)
at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(Ljava.util.ArrayList;Z)V(SlaveDeployer.java:508)
at weblogic.drs.internal.SlaveCallbackHandler$1.execute(Lweblogic.kernel.ExecuteThread;)V(SlaveCallbackHandler.java:25)
at weblogic.kernel.ExecuteThread.execute(Lweblogic.kernel.ExecuteRequest;)V(ExecuteThread.java:219)
at weblogic.kernel.ExecuteThread.run()V(ExecuteThread.java:178)
at java.lang.Thread.startThreadFromVM(Ljava.lang.Thread;)V(Unknown Source)
--------------- nested within: ------------------
weblogic.management.ManagementException: - with nested exception:
[weblogic.management.ApplicationException:
Exception:weblogic.management.ApplicationException: prepare failed for asyncsender-ejb.jar
Module: asyncsender-ejb.jar Error: Exception preparing module: EJBModule(asyncsender-ejb.jar,status=NEW)
Unable to deploy EJB: AsyncSenderEJB from asyncsender-ejb.jar:
[EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment.
weblogic.deployment.EnvironmentException: [EJB:010174]The resource-ref 'jms/QueueConnectionFactory' declared in the ejb-jar.xml descriptor has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor.
at weblogic.ejb20.deployer.EnvironmentBuilder.addJMSConnectionFactoryRef(Lweblogic.management.descriptors.ejb11.ResourceRefMBean;Ljava.util.Map;)V(EnvironmentBuilder.java:439)
at weblogic.ejb20.deployer.EnvironmentBuilder.addResourceReferences(Ljava.util.Collection;Ljava.util.Map;)V(EnvironmentBuilder.java:226)
at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentContext(Ljavax.naming.Context;Lweblogic.ejb20.interfaces.BeanInfo;Ljava.lang.String;Ljava.lang.String;)Ljavax.naming.Context;(EJBDeployer.java:379)
at weblogic.ejb20.deployer.EJBDeployer.setupEnvironmentFor(Lweblogic.ejb20.interfaces.BeanInfo;Lweblogic.ejb20.interfaces.DeploymentInfo;Lweblogic.management.configuration.EJBComponentMBean;Ljavax.naming.Context;)Ljavax.naming.Context;(EJBDeployer.java:1172)
at weblogic.ejb20.deployer.EJBDeployer.setupBeanInfos(Lweblogic.management.configuration.EJBComponentMBean;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;)V(EJBDeployer.java:943)
at weblogic.ejb20.deployer.EJBDeployer.prepare(Lweblogic.utils.jars.VirtualJarFile;Ljava.lang.ClassLoader;Lweblogic.management.descriptors.toplevel.EJBDescriptorMBean;Ljavax.naming.Context;Ljava.util.Map;)V(EJBDeployer.java:1345)
at weblogic.ejb20.deployer.EJBModule.prepare(Ljava.lang.ClassLoader;)V(EJBModule.java:498)
at weblogic.j2ee.J2EEApplicationContainer.prepareModule(Lweblogic.utils.classloaders.GenericClassLoader;Lweblogic.j2ee.J2EEApplicationContainer$Component;Z)V(J2EEApplicationContainer.java:3142)
at weblogic.j2ee.J2EEApplicationContainer.prepareModules([Lweblogic.j2ee.J2EEApplicationContainer$Component;Ljava.lang.String;Z)V(J2EEApplicationContainer.java:1583)
at weblogic.j2ee.J2EEApplicationContainer.prepare([Lweblogic.j2ee.J2EEApplicationContainer$Component;[Ljava.lang.String;Ljava.lang.String;Ljava.lang.String;)V(J2EEApplicationContainer.java:1227)
at weblogic.j2ee.J2EEApplicationContainer.prepare(Ljava.lang.String;[Lweblogic.ma -
BIP 10.1.3.4 with WLS Embedded LDAP
Hi All,
Details of my setup.
1. BIP installed in weblogic
2. BIP Security model setup to point to LDAP (wls embedded). The following details I specified:
a. cn=Admin/passwd
b. Distinguished Name for Users:
ou=people,ou=myrealm,dc=base_domainname
c. Distinguished Name for Groups
ou=groups,ou=myrealm,dc=base_domainname
d. Rest all left blank.
3. I created the XMLP_* (all 5 groups to in the wls myrealm).
4. I created the users and assigned them the above 5 groups as well as all other groups that were present.
5. I did create the Super User also.
I am able to login using the LDAP users but I am not able to see the Reports (as well as Admin tab etc), whenever I click on the Shared folders I get an "Unauthorized Access: Contact Admin" error.
I suspect BIP is not able to resolve the groups for the users.
Could anyone tell me where I am wrong and what needs to be done. I think I have not provided the group details like search filter, group attribute name etc.
I am a bit new to weblogic and not sure what are the details that I should provide for the embedded ldap in BIP.
Any help is much appreciated.
ThanksThis information is available in the "Certification" tab in My Oracle Support. One assumes that this verification is done before you actually perform the database upgrade
HTH
Srini -
[Security:090314]Entitlement Engine unable to connect to the embedded LDAP server
I rebuilt the server and I still can't start cluster server but got a different
error message. Any thoughts? (Migrating from Weblogic 6.1 to 8.1)
=============================================================================
LD_LIBRARY_PATH is:
/usr/openwin/lib
/usr/dt/lib
/usr/lib
/usr/local/lib
/export/opt/weblogic/8.1_SP2/weblogic81/server/lib/solaris
/export/opt/weblogic/8.1_SP2/weblogic81/server/lib/solaris
/export/opt/weblogic/8.1_SP2/weblogic81/server/lib/solaris/oci920_8
/opt/rv/lib
/bin/Solaris <not found>
/opt/BPARun1.0_A0/lib
=============================================================================
CLASSPATH is:
/export/opt/weblogic/8.1_SP2/weblogic81/server
/opt/rv/java/rvjpro.jar
/opt/rv/java/ssmbrvclient.jar
/opt/rv/java/tibrvj.jar
/export/opt/weblogic/8.1_SP2/weblogic81/server/lib/weblogic_sp.jar
/export/opt/weblogic/8.1_SP2/weblogic81/server/lib/weblogic.jar
/xenv/iona/sun4/5.x/6.0/asp/6.0/lib/asp-corba.jar
/work2/gx80747/src/Orbix6_config/etc/domains/GFINetEnv
:$
at weblogic.security.service.RoleManager.<init>(RoleManager.java:98)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doRole(SecurityServiceManagerDelegateImpl.jav
a:512)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManagerDelegat
eImpl.java:408)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelegateImpl.
java:697)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManagerDelega
teImpl.java:730)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl
.java:873)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:719)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:820)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
at weblogic.Server.main(Server.java:32)
Reason: weblogic.security.spi.ProviderInitializationException: [Security:090314]Entitlement
Engine unable to connect
to the embedded LDAP server
Cannot instantiate weblogic.entitlement.data.ldap.EData
null
I rebuilt the server and I still can't start cluster server but got a different
error message. Any thoughts? (Migrating from Weblogic 6.1 to 8.1)
=============================================================================
LD_LIBRARY_PATH is:
/usr/openwin/lib
/usr/dt/lib
/usr/lib
/usr/local/lib
/export/opt/weblogic/8.1_SP2/weblogic81/server/lib/solaris
/export/opt/weblogic/8.1_SP2/weblogic81/server/lib/solaris
/export/opt/weblogic/8.1_SP2/weblogic81/server/lib/solaris/oci920_8
/opt/rv/lib
/bin/Solaris <not found>
/opt/BPARun1.0_A0/lib
=============================================================================
CLASSPATH is:
/export/opt/weblogic/8.1_SP2/weblogic81/server
/opt/rv/java/rvjpro.jar
/opt/rv/java/ssmbrvclient.jar
/opt/rv/java/tibrvj.jar
/export/opt/weblogic/8.1_SP2/weblogic81/server/lib/weblogic_sp.jar
/export/opt/weblogic/8.1_SP2/weblogic81/server/lib/weblogic.jar
/xenv/iona/sun4/5.x/6.0/asp/6.0/lib/asp-corba.jar
/work2/gx80747/src/Orbix6_config/etc/domains/GFINetEnv
:$
at weblogic.security.service.RoleManager.<init>(RoleManager.java:98)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.doRole(SecurityServiceManagerDelegateImpl.jav
a:512)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealm(SecurityServiceManagerDelegat
eImpl.java:408)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.loadRealm(SecurityServiceManagerDelegateImpl.
java:697)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initializeRealms(SecurityServiceManagerDelega
teImpl.java:730)
at weblogic.security.service.SecurityServiceManagerDelegateImpl.initialize(SecurityServiceManagerDelegateImpl
.java:873)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:719)
at weblogic.t3.srvr.T3Srvr.initializeHere(T3Srvr.java:820)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:664)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:342)
at weblogic.Server.main(Server.java:32)
Reason: weblogic.security.spi.ProviderInitializationException: [Security:090314]Entitlement
Engine unable to connect
to the embedded LDAP server
Cannot instantiate weblogic.entitlement.data.ldap.EData
null
-
What is the WLS 7.0 embedded ldap admin account and password?
I am using (javax.naming.directory.DirContext.modifyAttributes) to change
password to our development Weblogic 7.0 embedded LDAP.
I login as the system administrator (a user in the administrators group),
but always gets the javax.naming.NoPermissionException - Insufficient Access
Rights.
What user should I use? Any help will be appreciated.I need to change password for a user. Any help will be appreciated.
Here is my stack trace:
c:\Test>java -classpath . testEmbeddedLdap
attribute: uid
attribute: description
attribute: objectclass
attribute: wlsMemberOf
attribute: sn
attribute: cn
javax.naming.NoPermissionException: [LDAP: error code 50 - Insufficient
Access Rights]; remaining name
'uid=myRegularUser,ou=people,ou=myrealm,dc=mydomain'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2872)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2810)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2616)
at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1374)
at
com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDir
Context.java:255)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(Partial
CompositeDirContext.java:172)
at
com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(Partial
CompositeDirContext.java:161)
at
javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.
java:146)
at testEmbeddedLdap.main(testEmbeddedLdap.java:30)
Here is my testing code:
<PRE>
import java.util.*;
import javax.naming.*;
import javax.naming.directory.*;
public class testEmbeddedLdap {
public static void main(String[] argv) {
Hashtable env = new Hashtable(11);
env.put(Context.INITIAL_CONTEXT_FACTORY,
"com.sun.jndi.ldap.LdapCtxFactory");
env.put(Context.PROVIDER_URL, "ldap://localhost:7001");
env.put(Context.SECURITY_AUTHENTICATION, "simple");
env.put(Context.SECURITY_PRINCIPAL, "uid=myAdministrator, ou=people,
ou=myrealm, dc=mydomain");
env.put(Context.SECURITY_CREDENTIALS, "myAdministrator");
try {
DirContext ctx = new InitialDirContext(env);
String
sUser="uid=myRegularUser,ou=people,ou=myrealm,dc=mydomain";
String sOldPassword="myRegularUser";
String sNewPassword="newpassword";
for (NamingEnumeration ae = ctx.getAttributes(sUser).getAll();
ae.hasMore(); ) {
Attribute attr = (Attribute)ae.next();
System.out.println("attribute: " + attr.getID());
ModificationItem[] mods = new ModificationItem[2];
Attribute mod0 = new BasicAttribute("userpassword",
sOldPassword);
mods[0] = new ModificationItem(DirContext.REMOVE_ATTRIBUTE,
mod0);
Attribute mod1 = new BasicAttribute("userpassword",
sNewPassword);
mods[1] = new ModificationItem(DirContext.ADD_ATTRIBUTE, mod1);
ctx.modifyAttributes(sUser, mods);
ctx.close();
} catch (NamingException e) {
e.printStackTrace();
</PRE>
"Neil Smithline" <[email protected]> wrote in message
news:[email protected]...
Two things. First, I'm not exactly sure what password you are trying to
change. The LDAP server's password or a user's password in the LDAP
server. Second, could you please post a stack trace.
Thanks - Neil
K Wong wrote:
I am using (javax.naming.directory.DirContext.modifyAttributes) to
change
password to our development Weblogic 7.0 embedded LDAP.
I login as the system administrator (a user in the administratorsgroup),
but always gets the javax.naming.NoPermissionException - InsufficientAccess
Rights.
What user should I use? Any help will be appreciated. -
Embedded LDAP exception during startup
Hi,
I'm getting the following exception during startup on my server:
"Server failed during initialization.
Exception:weblogic.security.spi.ProviderInitializationException:
Entitlement Engine unable to connect to the embedded LDAP server"
The full stack trace is below..
What's strange about this, is that it only happens on one of the boxes
I've tried this one. Every other box (_exact_ copy of the
configuration) works fine.
This is Weblogic 7.0 running on Redhat Linux.
======== full error log with embedded ldap debugging at level 11
===========
####<May 1, 2003 4:02:09 PM PDT> <Debug> <EmbeddedLDAP> <s1> <mserver>
<main> <kernel identity> <> <000000> <binding as root user: cn=admin>
####<May 1, 2003 4:02:09 PM PDT> <Debug> <EmbeddedLDAP> <s1> <mserver>
<main> <kernel identity> <> <000000> <Creating LDAP Connection
delegate, useSSL is false>
####<May 1, 2003 4:02:09 PM PDT> <Debug> <EmbeddedLDAP> <s1> <mserver>
<main> <kernel identity> <> <000000> <Initializing LDAP Connection
delegate>
####<May 1, 2003 4:02:09 PM PDT> <Debug> <EmbeddedLDAP> <s1> <mserver>
<main> <kernel identity> <> <000000> <Connecting delegate to :14102>
####<May 1, 2003 4:02:09 PM PDT> <Critical> <WebLogicServer> <s1>
<mserver> <main> <kernel identity> <> <000364> <Server failed during
initialization. Exception:weblogic.security.spi.ProviderInitializationException:
Entitlement Engine unable to connect to the embedded LDAP server>
weblogic.security.spi.ProviderInitializationException: Entitlement
Engine unable to connect to the embedded LDAP server
at weblogic.security.providers.authorization.DefaultAuthorizationUtils.getEngine(DefaultAuthorizationUtils.java:160)
at weblogic.security.providers.authorization.DefaultRoleMapperProviderImpl.initialize(DefaultRoleMapperProviderImpl.java:121)
at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
at weblogic.security.service.RoleManager.initialize(RoleManager.java:152)
at weblogic.security.service.RoleManager.<init>(RoleManager.java:97)
at weblogic.security.service.SecurityServiceManager.doRole(SecurityServiceManager.java:1511)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
at weblogic.Server.main(Server.java:32)
####<May 1, 2003 4:02:10 PM PDT> <Emergency> <WebLogicServer> <s1>
<mserver> <main> <kernel identity> <> <000342> <Unable to initialize
the server: Fatal initialization exception
Throwable: weblogic.security.spi.ProviderInitializationException:
Entitlement Engine unable to connect to the embedded LDAP server
weblogic.security.spi.ProviderInitializationException: Entitlement
Engine unable to connect to the embedded LDAP server
at weblogic.security.providers.authorization.DefaultAuthorizationUtils.getEngine(DefaultAuthorizationUtils.java:160)
at weblogic.security.providers.authorization.DefaultRoleMapperProviderImpl.initialize(DefaultRoleMapperProviderImpl.java:121)
at weblogic.security.service.SecurityServiceManager.createSecurityProvider(SecurityServiceManager.java:1820)
at weblogic.security.service.RoleManager.initialize(RoleManager.java:152)
at weblogic.security.service.RoleManager.<init>(RoleManager.java:97)
at weblogic.security.service.SecurityServiceManager.doRole(SecurityServiceManager.java:1511)
at weblogic.security.service.SecurityServiceManager.initializeRealm(SecurityServiceManager.java:1365)
at weblogic.security.service.SecurityServiceManager.loadRealm(SecurityServiceManager.java:1315)
at weblogic.security.service.SecurityServiceManager.initializeRealms(SecurityServiceManager.java:1432)
at weblogic.security.service.SecurityServiceManager.initialize(SecurityServiceManager.java:1157)
at weblogic.t3.srvr.T3Srvr.initialize1(T3Srvr.java:697)
at weblogic.t3.srvr.T3Srvr.initialize(T3Srvr.java:589)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:277)
at weblogic.Server.main(Server.java:32)"Ryan D'Silva" <[email protected]> wrote in message
news:[email protected]..
Hi,
I'm getting the following exception during startup on my server:
"Server failed during initialization.
Exception:weblogic.security.spi.ProviderInitializationException:
Entitlement Engine unable to connect to the embedded LDAP server"
Make sure the config.xml has the following
<EmbeddedLDAP Credential="..."/>
It should be generated if it is not there. Is the config.xml read-only or
copied from a master config.xml without an EmbeddedLDAP credential? -
WLP Embedded LDAP dependency in 10.3 ?
Hi,
what's the party line on the embedded LDAP dependency in 10.3 ? Since the WLS version is now up to 10.3 is the dependency gone?
I tried creating a domain with an RDBMS security store but got a weird security related error when trying to deploy a portal app. Verified configuration with a regular webapp that deployed/worked fine.
Thanks,
PetriHi Petri,
I hope you are doing well.
For WLP 10.3, only the authorization and role mapper providers which utilize the embedded LDAP are supported by WLP. The next version of WLP is planned to work with the rdbms-based providers.
Brad -
LDAP Error 17 when synchronizing E-Bus suite with OID
Hi all,
I have followed the instructions in Metalink note 233436.1 with a brand-new 11i instance and brand-new 10.1.4 identity management instance (on Linux). I also have followed the instructions in note 417706.1 to fix the issue where the ODISRV would not start up. Now, ODISRV is running, and provisioning events are coming from apps to oid (I used the appstooid profile - only want new e-bus users to create oid users and not vice-versa).
My problem is that the ODISRV is not applying changes. The log is full of these:
Trace Log Started at Wed Apr 18 18:13:54 BST 2007
javax.naming.directory.InvalidAttributeIdentifierException: [LDAP: error code 17 - Attribute orclodipprofilemetric is not supported in schema.]; remaining name 'cn=ApplicationToOID,orclODIPProfileName=2E5F85211462727DE040110A95011C03_2E666B8BFB63B961E040110A95014142,cn=provisioning profiles,cn=changelog subscriber,cn=oracle internet directory'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3057)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2934)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2740)
at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1440)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:255)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:172)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:161)
at javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.java:146)
at oracle.ldap.odip.engine.ProvProfile.updateExecStatus(ProvProfile.java:970)
at oracle.ldap.odip.prov.ProvAppToOIDSync_2_0.updateStatus(ProvAppToOIDSync_2_0.java:522)
at oracle.ldap.odip.prov.ProvAppToOIDSync_2_0.sync(ProvAppToOIDSync_2_0.java:484)
at oracle.ldap.odip.engine.ProvThread.runOldVersion(ProvThread.java:564)
at oracle.ldap.odip.engine.ProvThread.run(ProvThread.java:182)I can find nothing on the web/metalink/forums/etc pertaining to the orclodipprofilemetric.
Anyone seen this before?
Thanks and regards,
JohnJohn,
I think I am having a similar problem. In my case, I receive LDAP Error 17 when trying to build new attributes, under attributetypes. oidadmin seems to indicate that there is such a thing as "attributetypes", attempting to modify subschemasubentry, adding attribute "attributetypes" returns the LDAP error 17.
Isn't this error telling us that your "orclodipprofilemetric" isn't in the schema anywhere and you have to recreate it? Or could this be a case of misspelling in a script somewhere, where "orclodiprofilemetric" (only one "p") is meant, but fat-fingered.
r,
Gus -
Synchronization errors with AD: LDAP error code 65 : orclObjectSid
I'm trying to get synchronization working - importing data from Microsoft AD.
The bootstrap seemed to go ok, and the synchronization is up and running - but I still get errors in the profile's trace file as follows at the end of this post.
The error always seem to complain about the orclObjectSid attribute
Do I need to do anything to the OID schema?
Or is this a mapping problem?
Either way, how would I correct this error?
Thanks!!
Howard Dickins
Here's an example of the errors I'm getting:
DN : dc=connectutilities,dc=co,dc=uk
Normalized DN : dc=connectutilities,dc=co,dc=uk
Processing modifyRadd Operation ..
Proceeding with checkNReplace..
Performing checkNReplace..
Naming attribute: dc
Naming attribute value: dc
Naming attribute value: orclObjectSID
Adding Attribute in OID : orclObjectSID
Naming attribute value: orclobjectguid
Adding Attribute in OID : orclobjectguid
Total # of Mod Items : 2
Exception Modifying Entry : javax.naming.directory.SchemaViolationException: [LDAP: error code 65 - Failed to find orclobjectsid in mandatory or optional attribute list.]; remaining name 'dc=connectutilities,dc=co,dc=uk'
javax.naming.directory.SchemaViolationException: [LDAP: error code 65 - Failed to find orclobjectsid in mandatory or optional attribute list.]; remaining name 'dc=connectutilities,dc=co,dc=uk'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3019)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2934)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2740)
at com.sun.jndi.ldap.LdapCtx.c_modifyAttributes(LdapCtx.java:1440)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_modifyAttributes(ComponentDirContext.java:255)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:172)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.modifyAttributes(PartialCompositeDirContext.java:161)
at javax.naming.directory.InitialDirContext.modifyAttributes(InitialDirContext.java:146)
at oracle.ldap.odip.gsi.LDAPWriter.checkNReplace(LDAPWriter.java:839)
at oracle.ldap.odip.gsi.LDAPWriter.modifyRadd(LDAPWriter.java:717)
at oracle.ldap.odip.gsi.LDAPWriter.writeChanges(LDAPWriter.java:310)
at oracle.ldap.odip.engine.AgentThread.mapExecute(AgentThread.java:581)
at oracle.ldap.odip.engine.AgentThread.execMapping(AgentThread.java:306)
at oracle.ldap.odip.engine.AgentThread.run(AgentThread.java:186)
[LDAP: error code 65 - Failed to find orclobjectsid in mandatory or optional attribute list.]
Entry Not Found. Converting to an ADD op..
Processing Insert Operation ..
Performing createEntry..
Exception creating Entry : javax.naming.directory.SchemaViolationException: [LDAP: error code 65 - Failed to find orclobjectsid in mandatory or optional attribute list.]; remaining name 'dc=connectutilities,dc=co,dc=uk'
[LDAP: error code 65 - Failed to find orclobjectsid in mandatory or optional attribute list.]
javax.naming.directory.SchemaViolationException: [LDAP: error code 65 - Failed to find orclobjectsid in mandatory or optional attribute list.]; remaining name 'dc=connectutilities,dc=co,dc=uk'
at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:3019)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2934)
at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2740)
at com.sun.jndi.ldap.LdapCtx.c_createSubcontext(LdapCtx.java:777)
at com.sun.jndi.toolkit.ctx.ComponentDirContext.p_createSubcontext(ComponentDirContext.java:319)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:248)
at com.sun.jndi.toolkit.ctx.PartialCompositeDirContext.createSubcontext(PartialCompositeDirContext.java:236)
at javax.naming.directory.InitialDirContext.createSubcontext(InitialDirContext.java:176)
at oracle.ldap.odip.gsi.LDAPWriter.createEntry(LDAPWriter.java:1031)
at oracle.ldap.odip.gsi.LDAPWriter.insert(LDAPWriter.java:386)
at oracle.ldap.odip.gsi.LDAPWriter.modifyRadd(LDAPWriter.java:725)
at oracle.ldap.odip.gsi.LDAPWriter.writeChanges(LDAPWriter.java:310)
at oracle.ldap.odip.engine.AgentThread.mapExecute(AgentThread.java:581)
at oracle.ldap.odip.engine.AgentThread.execMapping(AgentThread.java:306)
at oracle.ldap.odip.engine.AgentThread.run(AgentThread.java:186)
DIP_LDAPWRITER_ERROR_CREATE
Error in executing mapping DIP_LDAPWRITER_ERROR_CREATE
DIP_LDAPWRITER_ERROR_CREATE
at oracle.ldap.odip.engine.AgentThread.mapExecute(AgentThread.java:722)
at oracle.ldap.odip.engine.AgentThread.execMapping(AgentThread.java:306)
at oracle.ldap.odip.engine.AgentThread.run(AgentThread.java:186)
DIP_LDAPWRITER_ERROR_CREATE
AD_OID_Import:Error in Mapping EngineDIP_LDAPWRITER_ERROR_CREATE
DIP_LDAPWRITER_ERROR_CREATE
at oracle.ldap.odip.engine.AgentThread.mapExecute(AgentThread.java:741)
at oracle.ldap.odip.engine.AgentThread.execMapping(AgentThread.java:306)
at oracle.ldap.odip.engine.AgentThread.run(AgentThread.java:186)
AD_OID_Import:about to Update exec status
Updated Attributes
orclodipLastExecutionTime: 20090617062658
orclodipConDirLastAppliedChgNum: 12242192
orclOdipSynchronizationStatus: Mapping Failure, Agent Execution Not Attempted
orclOdipSynchronizationErrors:
Sleeping for 1secs
LDAP URL : (inexus-srv01:389 oracleextract
Specifying binary attributes: mpegvideo objectguid objectsid guid usercertificate orclodipcondirlastappliedchgnum
LDAP Connection success
Applied ChangeNum : 12242192Available chg num = 12245972
Reader Initialised !!
LDAP URL : (inexus-srv34:389 cn=odisrv+orclhostname=inexus-srv34,cn=registered instances,cn=directory integration platform,cn=products,cn=oraclecontext
Specifying binary attributes: mpegvideo objectguid objectsid guid usercertificate orclodipcondirlastappliedchgnum
LDAP Connection success
Writer Initialised!!
Writer proxy connection initialised!!
MapEngine Initialised!!
Filter Initialised!!
searchF :
CHGLOGFILTER : (&(USNChanged>=12242193)(USNChanged<=12242692))
Search Time 0
Search Successful till # 12242692
Search Changes Done
Changenumber uSNChanged: 12242193
targetdn distinguishedName: DC=connectutilities,DC=co,DC=uk
ChangeRecord : ----------
Changetype: ADDRMODIFY
ChangeKey: dc=connectutilities,dc=co,dc=uk
Attributes:
Class: null Name: objectGUID Type: null ChgType: REPLACE Value: [[B@1c999c4]
Class: null Name: objectSid Type: null ChgType: REPLACE Value: [[B@8e5360]
Class: null Name: dc Type: null ChgType: REPLACE Value: [connectutilities]
Class: null Name: objectClass Type: nonbinary ChgType: REPLACE Value: [top, domain, domainDNS]
-----------I found a solution - I added the offending attribute orclObjectSid to the domain objectClass as an optional attribute.
It was a bit of a "clutching at straws" solution - but it does seem to have worked.
I'm not sure why the data being imported had such a value, but the synchronization hasn't thrown up any further errors since then.
Thanks for your help everyone.
Howard -
Error while create user in LDAP - LDAP: error code 1
Hi Guy's, I am getting below error while creating user in LDAP MS AD.
cn=3001,ou=sAP_IDM,dc=springswf,dc=comcn<mx:TEXT>putNextEntry failed storingOU=SAP_IDM,DC=springswf,DC=com</mx:TEXT>
<mx:LTEXT>Exception from Add operation:javaxnaming.NamingException: {LDAP: error code 1 = 00000000: LdapErr: DSID-OC090AE2, coment: In order to perform this operation a successful bind must be completed on the connection.,data0,vece
Steps I am following:
1. create a job through wizard and pick from (IC->jobs->Active Directory->Create Active Directory User)
2. Destination tab values that I am passing:
dn: cn=Dummyuser,ou=SAP_IDM,dc=<main domain>,dc=com
objectClass: top|person|organizationalPerson|user
sn: Surname
givenName: GivenName
displayName: Dummy user displayname
Under <main domain> an OU has been created called SAP_IDM for testing user creation from IDM.
Admin user account created called <XYZ> and has full control over SAP_IDM OU.
I am passing <XYZ> credentials into my job for user creation.
Thanks for you help!Farhan,
Based on the error message presented,
In order to perform this operation a successful bind must be completed on the connection
Make sure that you're using the correct information to do the AD Bind. User name should be something like cn=administrator,cn=users,dc=xxx,dc=xxx and the proper password.
Matt
Maybe you are looking for
-
My reader will not open a PDF file that I have downloaded from a government web site (an application form) - it states that the file is not good. I can open on the web site but not from my mac computer.
-
How to revive a dead 9600/300 and 8500/120 Powermac
I now have a 9600/300 and a 8500/120 Powermac. Both ran perfect when I bought them used for a day after I updated their system software to 8.6 for many hours. After shutting them down both would not restart (completely dead). I did the usual procedur
-
Why lumia is very bad os then ever
No photo upload on web directly no Bluetooth sharing for video network connection is very bad no more app than android why all apps are working in sand box video sharing not allowed in WhatsApp or any app some time automatically restart 3g network is
-
MC$6 (Vendor Analysis)
Hi All, I would like to know if anyone is aware of any link which explains this analysis in brief. I have a brief idea, but would like to have a better knowledge. Await inputs Vivek
-
Absolete FM for ECC 6.0
Hi Guys, i have the Function Modules DATA_INPUT_CUSTOMIZE FI_DOCUMENT_ARCH_READ_NEXT I want absolete for ECC 6.0