ElegantJ BI fail to deploy. Unable to connect

Modified on Mon, 19 Sep 2016 at 06:50 PM

Cannot login to ElegantJ BI

On entering localhost:8080/elegantjbi, unable to connect

Check if WildFly Server is running

ElegantJ BI failed to Deploy elegantjbi.war.dodeploy file shows elegantjbi.war.failed

Issue : Deployment Fail
Error : File Failed to Deploy/ elegantjbi.war.dodeploy file shows elegantjbi.war.failed
Root cause :
  1. dodeploy file not available or extension misspelled
  2. elegantjbi.war.failed file present in deployment folder- change the extension to dodeploy
  3. Wildfly server started twice (Kill Java Services using task manager)
  4. RAM set in XMS or XMX is more than actual RAM
  5. Check system.properties file is available in elegantjbi.war/conf folder then check the data directory path in it, correct it or delete the file
  6. If the cube folder is extracted in data folder (in case of transferring the cube in zipped format) check if folder under folder of the same name is created
  7. In ElegantJ BI Version 4.2, check whether  "-noverify" is added next to memory (Xms and Xmx) settings in standalone.conf and standalone.conf.bat files

If none of the solution works, check error description in Server Log (Standalone folder) or send the log to support@elegantjbi.com

Note: This article is based on ElegantJ BI Version 4.0. This may or may not be relevant to the ElegantJ BI version you may be using.
deployment fail java services elegantjbi.war.dodeploy elegantjbi.war.failed standalone.xml Xms Xmx ElegantJ BI Support ElegantJ BI Knowledgebase ElegantJ BI Articles ElegantJ BI Training Business Intelligence Support Business Intelligence Articles Business Intelligence Training

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select atleast one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article