Application already exists in the configuration repository error when installing new EAR in WAS admin console.

If we can screw up our enterprise application installation properly, we would reach to a state where we cannot go forward and backward. It is a nice state in which if we try to uninstall the application we would get an error message from WebSphere. Whatever may be the reason we will not be able to uninstall the enterprise project using WAS admin console. Then we will try our luck by installing new enterprise application unluckily WAS wouldn’t allow us to do that also. This time WebSphere Application Server would give a nice error message. “Application already exists in the configuration repository”.

The solution to this issue is to manually delete/uninstall the application by editing the configuration file. Do a search for your ear file in the file system and delete all the occurrences of the XXX.ear folder (You can see one .ear directory in your WAS_INSTALL_DIR/profiles/ /installedApps directory and one in WAS_INSTALL_DIR/profiles/ /config/cells//applications folder). Once we deleted these entire XXX.ear folders, delete all the contents of temp and wstemp folder. Now go to

WAS_INSTALL_DIR\profiles\<profileName>\config\cells\<cellName>\nodes\<nodeName>\

And edit the file serverindex.xml.

In this file we can see an entry for our application within the tag

 
<deployedApplications>xxx.ear</deployedApplications>

Delete this entry. We are done. Now we can install our application using WebSphere admin console without any issues.

Bookmark to

If you enjoyed this post, make sure you subscribe to my RSS feed!