suite.ear not deploying after Windows update

I'm seeing this error in the log:

15:36:43,888 INFO [stdout] (ServerService Thread Pool -- 226) 2016-09-16 15:36:43,886 [ServerService Thread Pool -- 226] ERROR com.appiancorp.common.config.ConfigObject - An error occurred while trying to initialize the config object com.appiancorp.process.admin.LoadSmartNodeACSchemas using the following resources: /WEB-INF/conf/process/appian-internal2-activities.xml, /WEB-INF/conf/process/appian-internal3-activities.xml, /WEB-INF/conf/process/appian-integration-activities.xml, /WEB-INF/conf/process/appian-internal-activities.xml, /WEB-INF/conf/process/appian-custom-activities.xml, /WEB-INF/conf/process/appian-connector-activities.xml

It has the following caused by:

15:36:43,893 INFO [stdout] (ServerService Thread Pool -- 226) Caused by: PrivilegeException[null=>null]: Insufficient permission


Can you confirm that the user has sufficient privileges to start JBoss / Appian?

Could you attempt to start JBoss as an administrator?

JBoss is started using a windows services that uses the local system Administrator account. Again, none of this should have changed by just installing the windows update...

Have you checked the permissions, just to be safe?

It is running using the Administrator account. Any other permissions I should check?

I started JBoss command line as well and get the same errors.

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.

Eduardo - Followed these steps. Here is the server.log file. The apian-MySQL-ds.xml is undeployed.

server.log.09.18.log

suite.ear.failed

Just to confirm, when opening the command line from the Windows Start Menu, you right-clicked and selected run as administrator?

Yes, I did exactly that Steven. Funny thing, I used the windows uninstaller and got rid of the windows patches that were installed that created this problem in the first place. Even after I did that, the same errors are occurring!

Here is the first error that shows up in the log:

ERROR com.appiancorp.common.config.ConfigObject - An error occurred while trying to initialize the config object com.appiancorp.process.admin.LoadSmartNodeACSchemas using the following resources: /WEB-INF/conf/process/appian-internal2-activities.xml, /WEB-INF/conf/process/appian-internal3-activities.xml, /WEB-INF/conf/process/appian-integration-activities.xml, /WEB-INF/conf/process/appian-internal-activities.xml, /WEB-INF/conf/process/appian-custom-activities.xml, /WEB-INF/conf/process/appian-connector-activities.xml.

com.appiancorp.kougar.mapper.exceptions.UndeclaredException: PrivilegeException[null=>null]: Insufficient permission

What could be causing this? The instance is connecting to AppianPrimaryDS.