Unable To Start Appian Services 18.1

License Issue, Kindly request a new Temporary License and try again. As per your log file, it speaks about errors regards to license.

Thanks for the Response BenhaIl. Is there any issue while creating temp license from Appian?

Hi Venkatesh,

Change the url in appian-ds.xml as below

<xa-datasource-property name="URL">jdbc:mysql://localhost:3306/appianprimary?useOldAliasMetadataBehavior=true&amp;useSSL=false</xa-datasource-property>

 

Also, make sure to verify the below before starting JBOSS

1. Make sure that the suite.ear.dodeploy file exists and does not have the extensions .undeployed, .isdeploying or .failed:

<APPIAN_HOME>\_admin\_scripts\configure\templates\ear\suite.ear.dodeploy

2. Delete the appian-mysql-ds.xml.deployed file if it has the extensions .undeployed, .isdeploying or .failed:

<JBOSS_HOME>\standalone\deployments\appian-mysql-ds.xml.deployed

 

It is showing same error.

Please find below log error.

We have tried with ; at end but still appian-mysql-ds failed.

We have checked above mentioned steps and still appian-mysql-ds file failed..

 

ERROR [org.jboss.msc.service.fail] (MSC service thread 1-5) MSC000001: Failed to start service jboss.deployment.unit."appian-mysql-ds.xml".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."appian-mysql-ds.xml".PARSE: JBAS018733: Failed to process phase PARSE of deployment "appian-mysql-ds.xml"
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:166) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1980) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1913) [jboss-msc-1.1.5.Final-redhat-1.jar:1.1.5.Final-redhat-1]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) [rt.jar:1.8.0_92]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) [rt.jar:1.8.0_92]
at java.lang.Thread.run(Thread.java:745) [rt.jar:1.8.0_92]
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'useSSL'
at [row,col {unknown-source}]: [11,118]
at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:99)
at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:159) [jboss-as-server-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
... 5 more
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'useSSL'
at [row,col {unknown-source}]: [11,118]
at com.ctc.wstx.sr.StreamScanner.throwUnexpectedChar(StreamScanner.java:639)
at com.ctc.wstx.sr.StreamScanner.parseEntityName(StreamScanner.java:2059)
at com.ctc.wstx.sr.StreamScanner.fullyResolveEntity(StreamScanner.java:1517)
at com.ctc.wstx.sr.BasicStreamReader.readTextSecondary(BasicStreamReader.java:4701)
at com.ctc.wstx.sr.BasicStreamReader.readCoalescedText(BasicStreamReader.java:4147)
at com.ctc.wstx.sr.BasicStreamReader.getElementText(BasicStreamReader.java:679)
at org.jboss.jca.common.metadata.AbstractParser.rawElementText(AbstractParser.java:168)
at org.jboss.jca.common.metadata.AbstractParser.elementAsString(AbstractParser.java:154)
at org.jboss.jca.common.metadata.AbstractParser.parseConfigProperty(AbstractParser.java:826)
at org.jboss.jca.common.metadata.ds.v11.DsParser.parseXADataSource(DsParser.java:150)
at org.jboss.jca.common.metadata.ds.v10.DsParser.parseDataSources(DsParser.java:185)
at org.jboss.jca.common.metadata.ds.v10.DsParser.parse(DsParser.java:124)
at org.jboss.jca.common.metadata.ds.v10.DsParser.parse(DsParser.java:87)
at org.jboss.as.connector.deployers.ds.processors.DsXmlDeploymentParsingProcessor.deploy(DsXmlDeploymentParsingProcessor.java:89)
... 6 more

05:30:13,083 ERROR [org.jboss.as.controller.management-operation] (DeploymentScanner-threads - 2) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "appian-mysql-ds.xml")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"appian-mysql-ds.xml\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"appian-mysql-ds.xml\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"appian-mysql-ds.xml\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'useSSL'
at [row,col {unknown-source}]: [11,118]
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'useSSL'
at [row,col {unknown-source}]: [11,118]"}}
05:30:13,094 ERROR [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS015870: Deploy of deployment "appian-mysql-ds.xml" was rolled back with the following failure message:
{"JBAS014671: Failed services" => {"jboss.deployment.unit.\"appian-mysql-ds.xml\".PARSE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"appian-mysql-ds.xml\".PARSE: JBAS018733: Failed to process phase PARSE of deployment \"appian-mysql-ds.xml\"
Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'useSSL'
at [row,col {unknown-source}]: [11,118]
Caused by: com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '=' (code 61); expected a semi-colon after the reference for entity 'useSSL'
at [row,col {unknown-source}]: [11,118]"}}
05:30:13,095 INFO [org.jboss.as] (Controller Boot Thread) JBAS015961: Http management interface listening on 127.0.0.1:9990/management
05:30:13,145 INFO [org.jboss.as] (Controller Boot Thread) JBAS015951: Admin console listening on http://127.0.0.1:9990
05:30:13,147 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss EAP 6.4.0.GA (AS 7.5.0.Final-redhat-21) started (with errors) in 152198ms - Started 1706 of 1742 services (1 services failed or missing dependencies, 83 services are lazy, passive or on-demand)
05:30:13,154 INFO [org.jboss.as.controller] (DeploymentScanner-threads - 2) JBAS014774: Service status report
JBAS014777: Services which failed to start: service jboss.deployment.unit."appian-mysql-ds.xml".PARSE

Venkatesh,
Sorry looks like something wrong with earlier URL Connection String.

Give a try with the below one:
<xa-datasource-property name="URL">jdbc:mysql://localhost:3306/appianprimary?useOldAliasMetadataBehavior=true&amp;useSSL=false</xa-datasource-property>

If this doesn't works try giving the URL without SSL as below
<xa-datasource-property name="URL">jdbc:mysql://localhost:3306/appianprimary?useOldAliasMetadataBehavior=true</xa-datasource-property>

Note:
Make sure to verify the below before starting JBOSS

1. Make sure that the suite.ear.dodeploy file exists and does not have the extensions .undeployed, .isdeploying or .failed:

<APPIAN_HOME>\_admin\_scripts\configure\templates\ear\suite.ear.dodeploy

2. Delete the appian-mysql-ds.xml.deployed file if it has the extensions .undeployed, .isdeploying or .failed:

<JBOSS_HOME>\standalone\deployments\appian-mysql-ds.xml.deployed

Still it is showing same issue..

Have you tried without SSL?
<xa-datasource-property name="URL">jdbc:mysql://localhost:3306/appianprimary?useOldAliasMetadataBehavior=true</xa-datasource-property

Yes!!.. Vimal we have tried with above URL.

We have performed below steps:

1. Stopped the Jboss  Server.

2. Stopped Search Server and Data Server.

3. Stopped all the Appian Services.

4. We have performed the configure script , and we have used above URL without useSSL Connection in mysql-ds.xml file.

5. After restarting the Appian Services and Jboss , Please find below Log error.

ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "appian-mysql-ds.xml")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"appian-mysql-ds.xml\".FIRST_MODULE_USE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"appian-mysql-ds.xml\".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of deployment \"appian-mysql-ds.xml\"
    Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS010464: Exception deploying datasource java:/jdbc/AppianPrimary
    Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.java:/jdbc/AppianPrimary is already registered"}}
07:00:56,074 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "appian-mysql-ds.xml" (runtime-name : "appian-mysql-ds.xml")
07:00:56,080 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "suite.ear" (runtime-name : "suite.ear")
07:00:56,103 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report
JBAS014777:   Services which failed to start:      service jboss.deployment.unit."appian-mysql-ds.xml".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."appian-mysql-ds.xml".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of deployment "appian-mysql-ds.xml" .

 

Thanks InAdvance!!

 

We are using the below software:
Details:
=====
1. MySQL 5.7.22
2.My SQL Connector 5.1.46
2.JBOSS 6.4.0
3. Appian 18.1

4. OS: Windows 10 , 64 Bit.

May be issue with Jboss version.
In System Requirements mentioned JBoss version minimum requirement 6.4.xx and Found on KB also related to same issue.

https://community.appian.com/support/w/kb/439/kb-1224-jbas018733-failed-to-process-phase-first_5f00_module_5f00_use-of-deployment-suite-ear-error-returned-during-jboss-startup

 

Thanks InAdvance.

Can you attach the server.log?

Thanks for the response.

I have found one KB Thread related same issue but That issue is for Jboss 6.4.9.

Currently we are using Jboss EAP 6.4.0 Version But in System Requirement Mentioned Minimum JBoss Enterprise Application Platform 6.4 (6.4.14 or later).

Is there any issue with Jboss version? and Please find below KB.

community.appian.com/.../kb-1224-jbas018733-failed-to-process-phase-first_5f00_module_5f00_use-of-deployment-suite-ear-error-returned-during-jboss-startup

In my log i have found below error issue.

ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014612: Operation ("deploy") failed - address: ([("deployment" => "appian-mysql-ds.xml")]) - failure description: {"JBAS014671: Failed services" => {"jboss.deployment.unit.\"appian-mysql-ds.xml\".FIRST_MODULE_USE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.\"appian-mysql-ds.xml\".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of deployment \"appian-mysql-ds.xml\"

   Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: JBAS010464: Exception deploying datasource java:/jdbc/AppianPrimary

   Caused by: org.jboss.msc.service.DuplicateServiceException: Service jboss.data-source.java:/jdbc/AppianPrimary is already registered"}}

07:00:56,074 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "appian-mysql-ds.xml" (runtime-name : "appian-mysql-ds.xml")

07:00:56,080 INFO  [org.jboss.as.server] (ServerService Thread Pool -- 30) JBAS015859: Deployed "suite.ear" (runtime-name : "suite.ear")

07:00:56,103 INFO  [org.jboss.as.controller] (Controller Boot Thread) JBAS014774: Service status report

JBAS014777:   Services which failed to start:      service jboss.deployment.unit."appian-mysql-ds.xml".FIRST_MODULE_USE: org.jboss.msc.service.StartException in service jboss.deployment.unit."appian-mysql-ds.xml".FIRST_MODULE_USE: JBAS018733: Failed to process phase FIRST_MODULE_USE of deployment "appian-mysql-ds.xml" .

Can I have access (RDP or Teamviewer) and solve your issue?

Sorry was kinda busy and wasn't been able to login to the community

Can I have access (RDP or Teamviewer) and solve your issue?

Sorry was kinda busy and wasn't been able to login to the community