Application already exists in the configuration repository
If you are getting this error it means that you have screwed you Websphere Application Server application to a very good extend that now you cannot deploy or un-deploy that particular application.
In order to fix this issue we need to do a manual process of deleting the application
Steps:
- Stop the Websphere Application Server
- Do a search for your ear file in the file system and delete all the occurrences of the XXX.ear folder
- Once we deleted these entire XXX.ear folders, delete all the contents of temp and wstemp folder.
- Now go to WAS_INSTALL_DIRprofiles<profileName>defaultconfigcells<cellName>nodes<nodeName>
- Edit the file serverindex.xml for an entry for our application within the tag
<deployedApplications>xxx.ear</deployedApplications> - Restart the Websphere Application Server
- Redeploy the application to the Websphere Application Server
This isthe biggest pointless pieces of crappy software that exists on this planet. WEBSPHERE MUST DIE, piece of crap rational.
Ddd you should get the nobel prize for for keeping the good in our fragile world and for Obliterate the evil
sometimes delete all *.ear folders may make the server “page not found” while trying to restart.
you may try to delete all “last modified” files (not folders) in those *.ear folders.
obviously it will include *.jar files of the last installation.
it works for me.
Thanks! I think at-least I am getting started with the process to get Noble prize with you voting for me :). Thanks for stopping by, reading my blog and taking time to comment.
This isthe biggest pointless pieces of crappy software that exists on this planet. WEBSPHERE MUST DIE, piece of crap rational.
This isthe biggest pointless pieces of crappy software that exists on this planet. WEBSPHERE MUST DIE, piece of crap rational.
this is good artical and helped me resolve the problem..
this is good artical and helped me resolve the problem..
this is good artical and helped me resolve the problem..
Fantastic help, worked perfectly, thanks heaps!
Fantastic help, worked perfectly, thanks heaps!
Fantastic help, worked perfectly, thanks heaps!
thanks a lot. Very much useful piece of information.
I am glad that it is still helpful after so many years.
thanks a lot. Very much useful piece of information.
I am glad that it is still helpful after so many years.
This is great information.
Cel, Thanks. I am glad it helped.
This is great information. I’ve been deploying ear files for years and encountered this problem for the first time, now sure how. And, this helped, THANKS!!!
Cel, Thanks. I am glad it helped.
Good old WebSphere…. where you have to hack your way through the files!! Thanks – this helped me!!
Thanks for posting such useful article…It worked perfectly:)
Thanks Raja
Thanks a lot. This issue ruined my enitre morning session
Ahmed
I am glad to hear that this helped. When I wrote this blog many years ago I never knew this will be useful even after years. I remember I spent few weeks before I was able to find this solution. I am glad this was of some help.
Hi,
I tried the above method but still getting error. Can u please help
Parinita
I apologize for the late reply. Do you still have the issue?
Thanks
Rohit
Yes..the problem still persists. I tried it many times but the same issue.Please help
Hi Parineeta, I hope by this time you were able to solve this. I have been out of the tech development world for sometime and unable to help you more on this. Thanks for understanding me.
You must be canonized =O
Hi Luis
Why do you think so :), seems you were in a lot of pain when you reached here. I am glad it worked.
Thanks
Rohit
You must be canonized =O
Worked like charm! Million thanks!
I am glad it is of help even after so many years. Thanks for taking time and sending your appreciation.
Cheers
Rohit
I am still facing the same issue, even after following all the steps above.
Hi Akhilesh, I hope by this time you were able to solve this. I have been out of the tech development world for sometime and unable to help you more on this. Thanks for understanding me.
This error can come under following conditions:
Deploying an application and it already exists
Re-Deploying an application whose deployment failed before for some reason
undeployment failed but there is no reference of the application in admin console
For example, you are deploying a large application using wsadmin and got a soap timeout or out of memory before application is saved. Then you change the timeout/heap and try to deploy your applciation… in this case above error can come
NOW This states that the configurations are inconsistent states.
for us it happened while using SOAP (wsadmin).So the best solution is to use the same.
USE wsadmin :
$AdminApp install $ear_fileName -node $nodeName -cell $cellName -server $serverName -appname $appName
$AdminConfig save
Check out for wsadmin for full details.
Jay, Thanks for taking time and replying to this thread.
-Rohit