KB-1144 Appian attempts to overwrite files in accdocs folders after an upgrade

Parmida Borhani — Fri, 23 Aug 2019 05:56:40 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 8/23/2019 5:56:40 AM

Symptoms

After an upgrade the application server either fails to start, or, it starts successfully but uploading/creating new files sometimes fails. The following message is seen in the application server log:

java.lang.IllegalArgumentException: Attempt to write over a file that already exists: <PATH_TO_FILE_IN_ACCDOCS>

Cause

This usually happens during upgrades with improper migrations or when the contents of the _admin folder have been moved around.

The cause for this is that the Collaboration engine has a mismatch with the _admin/accdocs folders. Specifically, the Collaboration engine has an internal counter that determines the next internal filename when creating a file. If the internal file already exists, then this will cause a conflict in the filename, causing Appian startup or document creation to fail.

Action

If upgrading from a previous version, make sure to copy the highest numbered engine database file *.kdb from the old directory to the new installation’s directory. If moving the *.kdb for any reason, it is also necessary to move the contents of the _admin folder.
In case of an unsuccessful upgrade, roll back to a backup from before the upgrade and attempt the migration again. Do not use the existing data to roll back, as there might be additional system files generated during the unsuccessful/partial upgrade attempt.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2019

Tags: administration, engines, upgrade

KB-1144 Appian attempts to overwrite files in accdocs folders after an upgrade

Parmida Borhani — Thu, 07 Mar 2019 19:08:56 GMT

Revision 4 posted to Appian Knowledge Base by Parmida Borhani on 3/7/2019 7:08:56 PM

Symptoms

After an upgrade to a new version, you see errors in the application server log that state the system is attempting to overwrite files in the _admin\accdocs* folders. The server eventually fails to start. The log messages are similar to the one below:

INFO  [stdout] (ServerService Thread Pool -- 73) com.appiancorp.ix.ConsumerException: type=content, srcId=SYSTEM_CONTENT_ICON_INDICATOR_MOVE_DOWN, dstId=8668, cause=com.appiancorp.suiteapi.common.exceptions.AppianException: java.lang.IllegalArgumentException: Attempt to write over a file that already exists: ##PATH TO FILE IN ACCDOCS##, level=ERROR, object=ContentHaul[content=[Content:id=8668,name=iconIndicatorMoveDown,description=,type=1,uuid=SYSTEM_CONTENT_ICON_INDICATOR_MOVE_DOWN,parent=92,visibility=20,security=143,attributes={},partition=2147483647],resourceName=move_down.png,roleMap=com.appiancorp.suiteapi.content.ContentRoleMap@1565d0ce[

INFO  [stdout] (ServerService Thread Pool -- 73) Caused by: java.lang.IllegalArgumentException: Attempt to write over a file that already exists: ##PATH TO FILE IN ACCDOCS

Cause

This usually happens during upgrades with improper migrations or when the contents of the _admin folder have been moved around.

Action

If you are upgrading from a previous version, make sure that you copied the highest numbered engine database file *.kdb from the old directory to the new installation’s directory. If you move the *.kdb for any reason, you also have to move the contents of the _admin folder.
In case of an unsuccessful upgrade, roll back to a backup from before the upgrade and attempt the migration again. Do not use the existing data to roll back, as there might be additional system files generated during the unsuccessful/partial upgrade attempt.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2019

Tags: administration, engines, upgrade

KB-1144 Appian attempts to overwrite files in accdocs folders after an upgrade

Parmida Borhani — Thu, 07 Mar 2019 19:08:08 GMT

Revision 3 posted to Appian Knowledge Base by Parmida Borhani on 3/7/2019 7:08:08 PM

Symptoms

INFO  [stdout] (ServerService Thread Pool -- 73) com.appiancorp.ix.ConsumerException: type=content, srcId=SYSTEM_CONTENT_ICON_INDICATOR_MOVE_DOWN, dstId=8668, cause=com.appiancorp.suiteapi.common.exceptions.AppianException: java.lang.IllegalArgumentException: Attempt to write over a file that already exists: ##PATH TO FILE IN ACCDOCS##, level=ERROR, object=ContentHaul[content=[Content:id=8668,name=iconIndicatorMoveDown,description=,type=1,uuid=SYSTEM_CONTENT_ICON_INDICATOR_MOVE_DOWN,parent=92,visibility=20,security=143,attributes={},partition=2147483647],resourceName=move_down.png,roleMap=com.appiancorp.suiteapi.content.ContentRoleMap@1565d0ce[

INFO  [stdout] (ServerService Thread Pool -- 73) Caused by: java.lang.IllegalArgumentException: Attempt to write over a file that already exists: ##PATH TO FILE IN ACCDOCS

Cause

This usually happens during upgrades with improper migrations or when the contents of the _admin folder have been moved around.

Action

If you are upgrading from a previous version, make sure that you copied the highest numbered engine database file *.kdb from the old directory to the new installation’s directory. If you move the *.kdb for any reason, you also have to move the contents of the _admin folder.
In case of an unsuccessful upgrade, roll back to a backup from before the upgrade and attempt the migration again. Do not use the existing data to roll back, as there might be additional system files generated during the unsuccessful/partial upgrade attempt.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: administration, engines, upgrade

KB-1144 Appian attempts to overwrite files in accdocs folders after an upgrade

Parmida Borhani — Tue, 11 Sep 2018 00:31:08 GMT

Revision 2 posted to Appian Knowledge Base by Parmida Borhani on 9/11/2018 12:31:08 AM

Symptoms

INFO  [stdout] (ServerService Thread Pool -- 73) com.appiancorp.ix.ConsumerException: type=content, srcId=SYSTEM_CONTENT_ICON_INDICATOR_MOVE_DOWN, dstId=8668, cause=com.appiancorp.suiteapi.common.exceptions.AppianException: java.lang.IllegalArgumentException: Attempt to write over a file that already exists: ##PATH TO FILE IN ACCDOCS##, level=ERROR, object=ContentHaul[content=[Content:id=8668,name=iconIndicatorMoveDown,description=,type=1,uuid=SYSTEM_CONTENT_ICON_INDICATOR_MOVE_DOWN,parent=92,visibility=20,security=143,attributes={},partition=2147483647],resourceName=move_down.png,roleMap=com.appiancorp.suiteapi.content.ContentRoleMap@1565d0ce[

INFO  [stdout] (ServerService Thread Pool -- 73) Caused by: java.lang.IllegalArgumentException: Attempt to write over a file that already exists: ##PATH TO FILE IN ACCDOCS

Cause

This usually happens during upgrades with improper migrations or when the contents of the _admin folder have been moved around.

Action

If you are upgrading from a previous version, make sure that you copied the highest numbered engine database file *.kdb from the old directory to the new installation’s directory. If you move the *.kdb for any reason, you also have to move the contents of the _admin folder.
In case of an unsuccessful upgrade, roll back to a backup from before the upgrade and attempt the migration again. Do not use the existing data to roll back, as there might be additional system files generated during the unsuccessful upgrade attempt.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2018

Tags: administration, engines, upgrade

KB-1144 Appian attempts to overwrite files in accdocs folders after an upgrade

Nick Vigilante — Fri, 24 Feb 2017 16:22:53 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 2/24/2017 4:22:53 PM

Symptoms

INFO  [stdout] (ServerService Thread Pool -- 73) com.appiancorp.ix.ConsumerException: type=content, srcId=SYSTEM_CONTENT_ICON_INDICATOR_MOVE_DOWN, dstId=8668, cause=com.appiancorp.suiteapi.common.exceptions.AppianException: java.lang.IllegalArgumentException: Attempt to write over a file that already exists: ##PATH TO FILE IN ACCDOCS##, level=ERROR, object=ContentHaul[content=[Content:id=8668,name=iconIndicatorMoveDown,description=,type=1,uuid=SYSTEM_CONTENT_ICON_INDICATOR_MOVE_DOWN,parent=92,visibility=20,security=143,attributes={},partition=2147483647],resourceName=move_down.png,roleMap=com.appiancorp.suiteapi.content.ContentRoleMap@1565d0ce[

INFO  [stdout] (ServerService Thread Pool -- 73) Caused by: java.lang.IllegalArgumentException: Attempt to write over a file that already exists: ##PATH TO FILE IN ACCDOCS

Cause

This usually happens during upgrades with improper migrations or when the contents of the _admin folder have been moved around.

Action

If you are upgrading from a previous version, make sure that you copied the highest numbered engine database file *.kdb from the old directory to the new installation’s directory. If you move the *.kdb for any reason, you also have to move the contents of the _admin folder.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: February 2017

Tags: administration, engines, upgrade