Searched on Google with the first line of a JAVA stack trace?

We can recommend more relevant solutions and speed up debugging when you paste your entire stack trace with the exception message. Try a sample exception.

Recommended solutions based on your search

Solutions on the web

via Oracle Community by 3004, 1 year ago
The DataSource with the JNDI name: ImeDS could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
via Coderanch by Ronak Parekh, 1 year ago
The DataSource with the JNDI name: java:comp/env/ejb/Organization could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
via Google Groups by Ronak Parekh, 7 months ago
The DataSource with the JNDI name: java:comp/env/ejb/Organization could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
via Oracle Community by 3004, 1 year ago
The DataSource with the JNDI name: java:comp/env/ejb/Organization could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
via Oracle Community by 3004, 1 year ago
The DataSource with the JNDI name: java:comp/env/ejb/Organization could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
via Google Groups by ronak, 7 months ago
The DataSource with the JNDI name: Organization could not be located. Please ensure that the DataSource has been deployed successfully and that the JNDI name in your EJB Deployment descriptor is correct.
weblogic.ejb20.WLDeploymentException: The DataSource with the JNDI name: ImeDS
could not be located. Please ensure that the DataSource has been deployed successfully
and that the JNDI name in your EJB Deployment descriptor is correct.	at weblogic.ejb20.cmp.rdbms.RDBMSPersistenceManager.setup(RDBMSPersistenceManager.java:138)	at weblogic.ejb20.manager.BaseEntityManager.setupPM(BaseEntityManager.java:211)	at weblogic.ejb20.manager.BaseEntityManager.setup(BaseEntityManager.java:181)	at weblogic.ejb20.manager.DBManager.setup(DBManager.java:162)	at weblogic.ejb20.deployer.ClientDrivenBeanInfoImpl.activate(ClientDrivenBeanInfoImpl.java:945)	at weblogic.ejb20.deployer.EJBDeployer.activate(EJBDeployer.java:1296)	at weblogic.ejb20.deployer.EJBModule.activate(EJBModule.java:349)	at weblogic.j2ee.J2EEApplicationContainer.activateModule(J2EEApplicationContainer.java:1592)	at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1029)	at weblogic.j2ee.J2EEApplicationContainer.activate(J2EEApplicationContainer.java:1016)	at weblogic.management.deploy.slave.SlaveDeployer.processPrepareTask(SlaveDeployer.java:1112)	at weblogic.management.deploy.slave.SlaveDeployer.prepareUpdate(SlaveDeployer.java:732)	at weblogic.drs.internal.SlaveCallbackHandler$1.execute(SlaveCallbackHandler.java:24)	at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:153)	at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:134)