suite.ear not deploying after Windows update

Raj

Certified Senior Developer

over 7 years ago

I updated windows server last night with the latest windows update. Since then, suite.ear is not getting deployed. I am on Appian 16.2. I stopped Jboss, search server, and appian engines, applied the windows update and then brought back the services starting with appian engines, search server and JBoss. All of them come up. However, suite.ear is not getting deployed. Latest server log is attached.

Server Log - 09-16.log

Discussion posts and replies are publicly visible

Parents

0 Eduardo Fuentes
Appian Employee
over 7 years ago

I am concerned about the fact that the following method is throwing an Insufficient Privileges exception:

com.appiancorp.process.design.service.ExtendedProcessDesignServiceJavaImpl.getRegisteredService(ExtendedProcessDesignServiceJavaImpl.java:281)

I am wondering if somehow someone changed the "Administrator" user to be basic.

Can you try this:

1. Open ear/suite.ear/resources/appian_log4j.properties
2. Add this line at the bottom

log4j.logger.com.appiancorp.process.admin=DEBUG

3. Rename /ear/suite.ear.failed and/or /ear/suite.ear.undeployed to .dodeploy (only one .dodeploy should exist)

4. Do the same with any .undeployed or .failed files under JBOSS_HOME\\standalone\\deployments

5. Delete JBOSS_HOME\\standalone\\log\\server.log

6. Start JBoss

7. Attach the output.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 Eduardo Fuentes
Appian Employee
over 7 years ago

I am concerned about the fact that the following method is throwing an Insufficient Privileges exception:

com.appiancorp.process.design.service.ExtendedProcessDesignServiceJavaImpl.getRegisteredService(ExtendedProcessDesignServiceJavaImpl.java:281)

I am wondering if somehow someone changed the "Administrator" user to be basic.

Can you try this:

1. Open ear/suite.ear/resources/appian_log4j.properties
2. Add this line at the bottom

log4j.logger.com.appiancorp.process.admin=DEBUG

3. Rename /ear/suite.ear.failed and/or /ear/suite.ear.undeployed to .dodeploy (only one .dodeploy should exist)

4. Do the same with any .undeployed or .failed files under JBOSS_HOME\\standalone\\deployments

5. Delete JBOSS_HOME\\standalone\\log\\server.log

6. Start JBoss

7. Attach the output.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data