Endeca application already exists with the name CRS use --force option

-
*** info    Thu Jun 06 18:06:31 IST 2013    1370522191743    atg.cim.task.ant.utility.AntLogger    Total time: 0 seconds
**** info    Thu Jun 06 18:06:33 IST 2013    1370522193801    atg.cim.productconfig.endeca.EndecaInitializeTask    Intitializing Endeca Application
**** info    Thu Jun 06 18:06:33 IST 2013    1370522193824    atg.cim.task.ant.utility.AntLogger   
**** info    Thu Jun 06 18:06:33 IST 2013    1370522193824    atg.cim.task.ant.utility.AntLogger    edeca-init.nonwindows:
**** info    Thu Jun 06 18:06:33 IST 2013    1370522193831    atg.cim.task.ant.utility.AntLogger         [exec] Initializing Endeca App
**** info    Thu Jun 06 18:06:36 IST 2013    1370522196128    atg.cim.task.ant.utility.AntLogger         [exec] [06.06.13 18:06:36] SEVERE: An application already exists with the name, "CRS". Please use the '--force' option if you want to replace all existing configuration.
**** info    Thu Jun 06 18:06:36 IST 2013    1370522196156    atg.cim.task.ant.utility.AntLogger   
**** info    Thu Jun 06 18:06:36 IST 2013    1370522196156    atg.cim.task.ant.utility.AntLogger    BUILD FAILED
**** info    Thu Jun 06 18:06:36 IST 2013    1370522196156    atg.cim.task.ant.utility.AntLogger    /home/atgint/ATG/ATG10.2/CIM/plugins/Base/ant/cim-ant.xml:871: exec returned: 1
**** info    Thu Jun 06 18:06:36 IST 2013    1370522196156    atg.cim.task.ant.utility.AntLogger   
**** info    Thu Jun 06 18:06:36 IST 2013    1370522196156    atg.cim.task.ant.utility.AntLogger    Total time: 2 seconds
**** Error    Thu Jun 06 18:06:36 IST 2013    1370522196157    atg.cim.productconfig.endeca.EndecaInitializeTask    ---    /home/atgint/ATG/ATG10.2/CIM/plugins/Base/ant/cim-ant.xml:871: exec returned: 1
**** Error    Thu Jun 06 18:06:36 IST 2013    1370522196157 

Solution 
  
This error basically occurs if we already have a CRS Endeca Provisioned  in your Application.

To know whether you have already an Application Provisioned use the command

eaccmd.sh list-apps/.bat , this will give you a list of applications Provisioned. 

Next use the command  ./runcommand.sh --remove-app/.bat . This will remove all your Provisioned application.Once this is done you can use the above command again to see it actually removed your Provisioned Applications. Ideally this should not list anything.

Next Modify your initialize_rs_feeds.sh/.bat file and remove eveerything from the line below the  word "echo creating fresh record stores " , this will basically delete the old records from the schemas which is created earlier at the time of Provisioning your Endeca Application.

Lastly remove your CRS Endeca Application,For that Remove the Folder CRS which will be usually located under C:\Endeca\Apps\CRS in Windows  or /usr/local/Endeca/Apps/CRS  in Linux Environments.

Now go back to your CIM configuration,Redeploy your CRS Endeca to the Production Server and do the Initialization, Hopefully you will not see the above error this time,once the Initialization has done successfully you can proceed with Indexing . Paste your Logs if you are encountering any issues.

Comments

  1. The MortimerMarch 3, 2014 at 9:13 AM

    Awesome I was stuck on this.. Thanks

    ReplyDelete
  2. The MortimerMarch 3, 2014 at 10:14 AM

    Actually not so awesome get the next error.. Any ideas please?

    **** info Mon Mar 03 10:12:04 PST 2014 1393870324234 atg.cim.task.ant.utility.AntLogger [exec] com.endeca.soleng.eac.toolkit.utility.IFCRUtility execute - Precondition Failed (412): Cannot copy ContentItemWrapper, type=endeca/site, path=/prototype/default, resource=[JcrNodeResource, type=endeca/site, superType=null, path=/prototype/default] to /sites/CRS: destination exists
    **** info Mon Mar 03 10:12:04 PST 2014 1393870324234 atg.cim.task.ant.utility.AntLogger [exec]
    **** info Mon Mar 03 10:12:04 PST 2014 1393870324253 atg.cim.task.ant.utility.AntLogger [exec] Failed to setup EAC application.
    **** info Mon Mar 03 10:12:04 PST 2014 1393870324255 atg.cim.task.ant.utility.AntLogger
    **** info Mon Mar 03 10:12:04 PST 2014 1393870324255 atg.cim.task.ant.utility.AntLogger BUILD FAILED
    **** info Mon Mar 03 10:12:04 PST 2014 1393870324255 atg.cim.task.ant.utility.AntLogger /home/atgdev/ATG/ATG11.0/CIM/plugins/Base/ant/cim-ant.xml:872: exec returned: 1

    ReplyDelete
  3. SebastianMarch 5, 2014 at 8:58 AM

    can you provide me the steps at what point this issue came and are you using endeca with crs and were you seeing any other errors?

    ReplyDelete
  4. The MortimerMarch 10, 2014 at 8:38 AM

    Thanks but the way I found to solve this was to uninstall ToolsAndFrameworks as the site CRS was hanging around there, then reinstall and it got past this error.

    Further errors were that in initialize_services.sh I had to comment out the following before I ran the CIM endeca install.

    # Import sample media. Remove the following step if
    # not using sample application and data.
    #echo "Importing media..."
    #"${WORKING_DIR}/set_media.sh"
    #if [ $? != 0 ]; then
    # exit 1
    #fi
    #echo "Finished importing media"

    As there is no set_media.sh

    ReplyDelete
  5. SebastianMarch 10, 2014 at 8:17 PM

    ok fine , thanks for sharing this information

    ReplyDelete

Post a Comment

Popular posts from this blog

BCC site status inaccessible Agent Production in error state

-
Image
The Error Message showing in BCC T he error logs is showing the below message /atg/epub/DeploymentServer Failed to connect to agent 'Production'. This agent not allowed to be absent for  a deployment. The server will continue attempts to  intialize the connection. Set loggingDebug to true for  continued exception and stacktrace logging. Analysis This happens when the target/Production instance is down for some  reason or the RMI configuration which points to the target/Production instance may not be correct one. Fix If this is happening  due to target/Production instance down  then we can restart the target/Production Server,Other wise  correct the RMI configuration from the BCC agent configuration page and reinitialise. Verify the RMI Port in Configuration.properties file.Usually this file will be located in the path C:\ATG\ATG10.2\home\servers\ATGProduction\localconfig\atg\dynamo\Configuration.properties,make sure the
Read more

Weblogic Issues during EAR Deployment Exception in AppMerge flows progression

-
Unable to access the selected application Exception in AppMerge flows progression Bean already exists "weblogic.j2ee.descriptor.ModuleBeanImpl@..../Modules[weblogic.descriptor.internal.Descriptor.Beankey@....] This issue can happen in many scenarios, may be you need to check your deployment descriptors based on Application Servers used, this generally happens due to issue in XML files related to deployment. I got this issue when i mistakenly added the modules twice in the Manifest file, the module 'Store.Storefront' is added more than once in  'ATG-Required'  of my Manifest.MF file,due to this i am seeing the module 'storedocroot.war' is added twice in my application.xml which is located in the  path ATGProd.ear\META-INF\application.xml.Due to this i am not able to deploy my EAR file. I have removed the duplicate entry and deployed the application and everything working fine. ....... <module>         <web>             <web-uri>atg_
Read more

DUseSunHttpHandler=true weblogic.net.http.SOAPHttpsURLConnection Weblogic/Java HttpHandler issues

-
Verify the issue is happening due to the error throwing  from the weblogic class  SOAPHttpsURLConnection,then you need to inform the Application Server which handler implementation you need to use.  add the following option to JAVA_OPTIONS in   setDomainEnv.sh/setDomainEnv.cmd  on Unix/Windows.   -DUseSunHttpHandler=true.  eg:  set JAVA_PROPERTIES=%JAVA_PROPERTIES% %WLP_JAVA_PROPERTIES%  set JAVA_OPTIONS=%JAVA_OPTIONS% %JAVA_PROPERTIES% -  DUseSunHttpHandler=true -Dwlw.iterativeDev=%iterativeDevFlag% -  Dwlw.testConsole=%testConsoleFlag% -Dwlw.logErrorsToConsole=%  logErrorsToConsoleFlag%  This setting tells WebLogic to use the Sun's https Handler   implementation rather than the WebLogic one.  So after this,it will use the  class HttpsURLConnection from the  javax package.   See Also   SSL Handshake error   java.lang.RuntimePermission modifyThread
Read more