Unable To Start Appian Services 18.1

RE: Unable To Start Appian Services 18.1

Benhail — Sun, 03 Jun 2018 06:22:20 GMT

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

RE: Unable To Start Appian Services 18.1

Venkatesh Suram — Thu, 31 May 2018 19:13:35 GMT

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.

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" .

RE: Unable To Start Appian Services 18.1

Alok Mohare — Thu, 31 May 2018 14:41:43 GMT

Can you attach the server.log?

RE: Unable To Start Appian Services 18.1

Venkatesh Suram — Thu, 31 May 2018 07:38:04 GMT

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.

RE: Unable To Start Appian Services 18.1

Venkatesh Suram — Thu, 31 May 2018 07:12:25 GMT

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!!

RE: Unable To Start Appian Services 18.1

vimalkumars — Thu, 31 May 2018 06:16:34 GMT

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

RE: Unable To Start Appian Services 18.1

Venkatesh Suram — Thu, 31 May 2018 06:11:11 GMT

Still it is showing same issue..

RE: Unable To Start Appian Services 18.1

vimalkumars — Thu, 31 May 2018 05:45:04 GMT

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&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

RE: Unable To Start Appian Services 18.1

Venkatesh Suram — Thu, 31 May 2018 05:37:13 GMT

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

RE: Unable To Start Appian Services 18.1

vimalkumars — Wed, 30 May 2018 23:48:43 GMT

Hi Venkatesh,

Change the url in appian-ds.xml as below

<xa-datasource-property name="URL">jdbc:mysql://localhost:3306/appianprimary?useOldAliasMetadataBehavior=true&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

RE: Unable To Start Appian Services 18.1

srikanthm0004 — Wed, 30 May 2018 14:23:26 GMT

Can you please take a look on the Part 8 of the Installation Guide which would help you fix the module issue.

docs.appian.com/.../Quick_Start_Installation_Guide_for_Windows_and_JBoss.html

RE: Unable To Start Appian Services 18.1

Venkatesh Suram — Wed, 30 May 2018 09:35:08 GMT

community.appian.com/.../1512.server.log

vimalkumars (vimals) : Can you please find the Latest Log File.

Please find attachedscreenshot of Jboss CMD Prompt.

appian-ds.xml file:

community.appian.com/.../5734.appian_2D00_ds.xml

Note:

1. suite.ear fle deployed but appian-ds.xml file failed.

RE: Unable To Start Appian Services 18.1

Venkatesh Suram — Wed, 30 May 2018 08:27:16 GMT

vimalkumars : I will do above steps and will update.

RE: Unable To Start Appian Services 18.1

vimalkumars — Wed, 30 May 2018 08:11:19 GMT

Have you did 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

Also, please check and share your appian-ds.xml file. Based on the below log looks like there are some issues

07:52:25,503 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-1) MSC000001: Failed to start service jboss.deployment.unit."appian-ds.xml".PARSE: org.jboss.msc.service.StartException in service jboss.deployment.unit."appian-ds.xml".PARSE: JBAS018733: Failed to process phase PARSE of deployment "appian-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

RE: Unable To Start Appian Services 18.1

Venkatesh Suram — Wed, 30 May 2018 07:57:32 GMT

community.appian.com/.../1882.server.log

vimalkumars (vimals) : Thanks for the response.

I have removed the " jdbc/AppianBusiness" from custom properties file.

Now in In Jboss logs it is showing Undeployed "suite.ear".

appian-ds.xml file also failed.

PFA Latest Log file and Please help me out on ths.

Thanks InAdvance.

RE: Unable To Start Appian Services 18.1

vimalkumars — Wed, 30 May 2018 07:45:15 GMT

Hi,

From your logs looks like JBOSS is not able to resolve the jdbc/AppianBusiness datasource.

06:59:14,219 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/suite]] (ServerService Thread Pool -- 106) JBWEB000287: Exception sending context initialized event to listener instance of class com.appiancorp.rdbms.datasource.BusinessDataSourceValidator: com.appiancorp.common.config.FatalConfigurationException: com.appiancorp.suiteapi.common.exceptions.AppianException: com.appiancorp.rdbms.datasource.DataSourceException: javax.naming.NameNotFoundException: jdbc/AppianBusiness -- service jboss.naming.context.java.jdbc.AppianBusiness
	at com.appiancorp.common.web.StartupHaltingServletContextListener.contextInitialized(StartupHaltingServletContextListener.java:86) [appian-ae-18.1.81.0.jar:]
	at org.apache.catalina.core.StandardContext.contextListenerStart(StandardContext.java:3339) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
	at org.apache.catalina.core.StandardContext.start(StandardContext.java:3780) [jbossweb-7.5.7.Final-redhat-1.jar:7.5.7.Final-redhat-1]
	at org.jboss.as.web.deployment.WebDeploymentService.doStart(WebDeploymentService.java:163) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
	at org.jboss.as.web.deployment.WebDeploymentService.access$000(WebDeploymentService.java:61) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
	at org.jboss.as.web.deployment.WebDeploymentService$1.run(WebDeploymentService.java:96) [jboss-as-web-7.5.0.Final-redhat-21.jar:7.5.0.Final-redhat-21]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) [rt.jar:1.8.0_92]
	at java.util.concurrent.FutureTask.run(FutureTask.java:266) [rt.jar:1.8.0_92]
	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]
	at org.jboss.threads.JBossThread.run(JBossThread.java:122)
Caused by: com.appiancorp.rdbms.datasource.DataSourceException: javax.naming.NameNotFoundException: jdbc/AppianBusiness -- service jboss.naming.context.java.jdbc.AppianBusiness
	at com.appiancorp.rdbms.datasource.DataSourceRegistry.get(DataSourceRegistry.java:21) [appian-ae-18.1.81.0.jar:]
	at com.appiancorp.rdbms.datasource.JndiDataSourceProvider.get(JndiDataSourceProvider.java:22) [appian-ae-18.1.81.0.jar:]
	at com.appiancorp.rdbms.datasource.CompositeDataSourceProvider.get(CompositeDataSourceProvider.java:25) [appian-ae-18.1.81.0.jar:]
	at com.appiancorp.rdbms.datasource.BusinessDataSourceValidator.validateDataSources(BusinessDataSourceValidator.java:63) [appian-ae-18.1.81.0.jar:]
	at com.appiancorp.rdbms.datasource.BusinessDataSourceValidator.contextInitialized0(BusinessDataSourceValidator.java:49) [appian-ae-18.1.81.0.jar:]
	at com.appiancorp.common.AppianServletContextListener.doContextInitialized(AppianServletContextListener.java:36) [appian-ae-18.1.81.0.jar:]
	at com.appiancorp.common.web.StartupHaltingServletContextListener$1.run(StartupHaltingServletContextListener.java:74) [appian-ae-18.1.81.0.jar:]
	at com.appiancorp.security.changelog.AuditLogLocationService.runWithLocation(AuditLogLocationService.java:38) [appian-ae-18.1.81.0.jar:]
	at com.appiancorp.common.web.StartupHaltingServletContextListener.contextInitialized(StartupHaltingServletContextListener.java:71) [appian-ae-18.1.81.0.jar:]
	... 11 more
Caused by: javax.naming.NameNotFoundException: jdbc/AppianBusiness -- service jboss.naming.context.java.jdbc.AppianBusiness
	at org.jboss.as.naming.ServiceBasedNamingStore.lookup(ServiceBasedNamingStore.java:104)
	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:197)
	at org.jboss.as.naming.InitialContext$DefaultInitialContext.lookup(InitialContext.java:243)
	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:183)
	at org.jboss.as.naming.NamingContext.lookup(NamingContext.java:179)
	at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0_92]
	at javax.naming.InitialContext.lookup(InitialContext.java:417) [rt.jar:1.8.0_92]
	at com.appiancorp.rdbms.datasource.DataSourceRegistry.get(DataSourceRegistry.java:19) [appian-ae-18.1.81.0.jar:]
	... 19 more

Please check the below:

1. DataSource Name given in custom.properties and appian-ds.xml

2. Check Connection is defined for jdbc/AppianBusiness in appian-ds.xml

Also, recommend you to remove the configurations for jdbc/AppianBusiness from property files and configure it in admin console of Appian.

Refer the link - docs.appian.com/.../Configuring_Relational_Databases.html

RE: Unable To Start Appian Services 18.1

Venkatesh Suram — Wed, 30 May 2018 07:00:59 GMT

community.appian.com/.../8054.server.logThanks For the response, I got new Temp license today and We have placed in appropriate folders.

But after restarting the server we are getting below errors while starting the Jboss.

RE: Unable To Start Appian Services 18.1

davel001150 — Fri, 25 May 2018 14:04:26 GMT

From what I've found that's just a warning and there's nothing in that to keep jboss from loading. I read about a support ticket to make newer versions of Appian suppress that warning.

Your actual error is farther down.

RE: Unable To Start Appian Services 18.1

Venkatesh Suram — Thu, 24 May 2018 15:39:01 GMT

Alok Mohare (alok.mohare) Thanks for the Resonse , We have fixed the issue and currently we are facing SSL Verification Issue.

PF Below Logs File.

21:05:27,143 ERROR [stderr] (Periodic Recovery) Wed May 23 21:05:27 GMT 2018 WARN: Establishing SSL connection without server's identity verification is not recommended. According to MySQL 5.5.45+, 5.6.26+ and 5.7.6+ requirements SSL connection must be established by default if explicit option isn't set. For compliance with existing applications not using SSL the verifyServerCertificate property is set to 'false'. You need either to explicitly disable SSL by setting useSSL=false, or set useSSL=true and provide truststore for server certificate verification.

Thanks InAdvance

RE: Unable To Start Appian Services 18.1

Alok Mohare — Thu, 24 May 2018 15:02:37 GMT

It seems like the module.xml is invalid.

Caused by: org.jboss.modules.ModuleLoadException: Error loading module from C:\APPIAN_HOME18.1\bin\jboss\jboss-eap-6.4\modules\com\mysql\jdbc\main\module.xml
...
Caused by: org.jboss.modules.xml.XmlPullParserException: Invalid/mismatched module name (expected com.mysql.jdbc:main) (position: START_TAG seen <module xmlns="urn:jboss:module:1.0" name="com.mysql.jdbc.main">... @1:64)
...

Can you validate the moduel.xml using an XML validator?
https://www.xmlvalidation.com/

RE: Unable To Start Appian Services 18.1

Venkatesh Suram — Wed, 23 May 2018 12:28:07 GMT

Alok Mohare (alok.mohare) Thanks for the response , We have already resolved that Issue .

Currently we are facing DataSoure issue and appian_mysql-ds failed

Can you please find latest Log File .

Can you please help on this.

community.appian.com/.../15838.server.log

Thanks InAdvance

RE: Unable To Start Appian Services 18.1

Alok Mohare — Wed, 23 May 2018 12:08:02 GMT

Based on the error, it seems like Jboss is unable to find the MySQL driver:

Caused by: org.jboss.modules.xml.XmlPullParserException: Failed to add resource root 'mysql-connector-java-5.1.46-bin' at path 'mysql-connector-java-5.1.46-bin' (position: END_TAG seen ...rces>\r\n <resource-root path="mysql-connector-java-5.1.46-bin"/>... @3:60) caused by: java.io.FileNotFoundException: C:\APPIAN_HOME18.1\bin\jboss\jboss-eap-6.4\modules\com\mysql\jdbc\main\mysql-connector-java-5.1.46-bin (The system cannot find the file specified)

RE: Unable To Start Appian Services 18.1

Venkatesh Suram — Wed, 23 May 2018 11:47:24 GMT

community.appian.com/.../1538.server.logNow we are able to run the Appian Services .

But we are facing Jboss Server issue.

Can anyone help me out on this.

PFA Jboss Logs.

Thanks In Advance.

RE: Unable To Start Appian Services 18.1

Venkatesh Suram — Wed, 23 May 2018 05:12:06 GMT

After placing an New Temp Licence we are unable to run the all services .

In Log file it is showing as Unable to connect Forum Id.

Forum and Notification engines are not running.community.appian.com/.../5127.service_5F00_manager.log

PFA Logs.

RE: Unable To Start Appian Services 18.1

Benhail — Tue, 22 May 2018 05:33:27 GMT

Nothing like that, Its gonna expire soon, so why don't we try with a new license.
And come up with a solution for your problem.