KB-1846 Processes fail to archive with no relevant error in application server logs

Parmida Borhani — Fri, 18 Jan 2019 00:45:10 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 1/18/2019 12:45:10 AM

Symptoms

All process instances fail to archive and the following error is found in the db_PX.log file:

WARN .workq "An exception has occurred. This action will be retried until it succeeds or the maximum retry period is reached. Work item 358, Archive [Process id=-1609403044]"

No relevant information is printed in the application server logs. Appian's out of the box archiveprocess.bat|sh script fails to archive with a success message on the console.

Cause

This issue can occur if the user who is running the application server does not have write permission in the <APPIAN_HOME>\server\archived-process directory.

Action

Ensure that the same user is starting the application service and engines. Also, ensure that the application server has permission to write in <APPIAN_HOME>\server\archived-process directory.

Note: Once the issue is fixed, the processes which failed to archive previously will not be archived automatically. Run the archive script to archive them.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2019

Tags: engines, application server, processes, infrastructure

DRAFT KB-XXXX Processes fail to archive with no relevant error in application server logs

Anirudh Rathi — Thu, 17 Jan 2019 12:05:38 GMT

Revision 4 posted to Appian Knowledge Base by Anirudh Rathi on 1/17/2019 12:05:38 PM

Symptoms

All process instances fail to archive and the following error is found in the db_PX.log file:

WARN .workq "An exception has occurred. This action will be retried until it succeeds or the maximum retry period is reached. Work item 358, Archive [Process id=-1609403044]"

No relevant information is printed in the application server logs. Appian's out of the box archiveprocess.bat|sh script fails to archive with a success message on the console.

Cause

This issue can occur if the user who is running the application server does not have write permission in <APPIAN_HOME>\server\archived-process directory.

Action

Ensure that the same user is starting the application service and engines. Also, ensure that the application server has permission to write in <APPIAN_HOME>\server\archived-process directory.

Note: Once the issue is fixed, the processes which failed to archive previously will not be archived automatically. Run the archival script to archive them.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2019

Tags: engines, application server, infrastructure

DRAFT KB-XXXX Processes fail to archive with no relevant error in application server logs

Anirudh Rathi — Tue, 15 Jan 2019 21:52:31 GMT

Revision 1 posted to Appian Knowledge Base by Anirudh Rathi on 1/15/2019 9:52:31 PM

Symptoms

All the process instances fail to archive and following error is found in db_PX_DATE_TIME.log file:

2018-12-15 19:45:08 [PX101] {pe615.kdb ,23484904} (Default) WARN .workq "An exception has occurred. This action will be retried until it succeeds or the maximum retry period is reached. Work item 358, Archive [Process id=-1609403044]"

No relevant information is printed in application server logs. Appian OOTB archiveprocess.bat|sh scripts fails to archive with a success message on the console.

Cause

This issue occurs if the user who is running application server does not have write permission in <APPIAN_HOME>\server\archived-process directory.

Action

Ensure that the same user is starting the application service and engines or ensure that the application server has permission to write in <APPIAN_HOME>\server\archived-process directory.

Affected Versions

This article applies to all versions of Appian

Last Reviewed: January 2019

Tags: engines, application server, infrastructure

DRAFT KB-XXXX Processes fail to archive with no relevant error in application server logs

Anirudh Rathi — Tue, 15 Jan 2019 16:58:33 GMT

Revision 3 posted to Appian Knowledge Base by Anirudh Rathi on 1/15/2019 4:58:33 PM

Symptoms

All the process instances fail to archive and following error is found in db_PX_DATE_TIME.log file:

2018-12-15 19:45:08 [PX101] {pe615.kdb ,23484904} (Default) WARN .workq "An exception has occurred. This action will be retried until it succeeds or the maximum retry period is reached. Work item 358, Archive [Process id=-1609403044]"

No relevant information is printed in application server logs. Appian OOTB archiveprocess.bat|sh scripts fails to archive with a success message on the console.

Cause

This issue occurs if the user who is running application server does not have write permission in <APPIAN_HOME>\server\archived-process directory.

Action

Ensure that the same user is starting the application service and engines or ensure that the application server has permission to write in <APPIAN_HOME>\server\archived-process directory.

Note: Once the issue is fixed, the processes which failed to archive previously will not be archived automatically. Run the archival script to archiving them.

Affected Versions

This article applies to all versions of Appian

Last Reviewed: January 2019

Tags: engines, application server, infrastructure

DRAFT KB-XXXX Processes fail to archive with no relevant error in application server logs

Anirudh Rathi — Tue, 15 Jan 2019 16:52:58 GMT

Revision 2 posted to Appian Knowledge Base by Anirudh Rathi on 1/15/2019 4:52:58 PM

Symptoms

All the process instances fail to archive and following error is found in db_PX_DATE_TIME.log file:

2018-12-15 19:45:08 [PX101] {pe615.kdb ,23484904} (Default) WARN .workq "An exception has occurred. This action will be retried until it succeeds or the maximum retry period is reached. Work item 358, Archive [Process id=-1609403044]"

No relevant information is printed in application server logs. Appian OOTB archiveprocess.bat|sh scripts fails to archive with a success message on the console.

Cause

This issue occurs if the user who is running application server does not have write permission in <APPIAN_HOME>\server\archived-process directory.

Action

Ensure that the same user is starting the application service and engines or ensure that the application server has permission to write in <APPIAN_HOME>\server\archived-process directory.

Affected Versions

This article applies to all versions of Appian

Last Reviewed: January 2019

Tags: engines, application server, infrastructure