We are upgrading Appian from 7.2 to Appian 7.6 and we have received below error

The error you're seeing

14:39:53,094 INFO [stdout] (ServerService Thread Pool -- 50) Caused by: com.appiancorp.suiteapi.type.exceptions.InvalidTypeException: com.appiancorp.suiteapi.common.exceptions.AppianException: Invalid Type: Type Error: Invalid Type Number (1961) (APNX-1-4047-000)

can indicate two things:

1. There was a race condition when propagating data types during the start-up of the migration after rebuilding analytics that is preventing this data type from being present on the required engines

2. Or this environment wasn't fully migrated and you forgot to copy one or more engines from 7.5 to 7.6, most likely process design

SOLUTION:

1. For scenario #1 simply stop JBoss and delete <JBOSS_HOME>\\standalone\\log\\*.log. Restart JBoss again to confirm enough time has passed by to finish propagating data types.

2. For scenario #2 open all logs of type db_*.log and make sure the all show the 100% migrated message. I am thinking that db_PD is missing and you're running with the out of the box pd*.kdb instead of migrating it by mistake.

Even though I think the issue may be with Process Design make sure to review each db_*.log and search for the 100% migrated message; the log will also show what ID of the *.kdb file it's using that should also give you a clue in whether you missed copying one or more engines to 7.6

If you find out you forgot to copy one or more engines you will have to repeat the migration; copying the missing one now that the migration code ran is going to cause more trouble.

The error you're seeing

14:39:53,094 INFO [stdout] (ServerService Thread Pool -- 50) Caused by: com.appiancorp.suiteapi.type.exceptions.InvalidTypeException: com.appiancorp.suiteapi.common.exceptions.AppianException: Invalid Type: Type Error: Invalid Type Number (1961) (APNX-1-4047-000)

can indicate two things:

1. There was a race condition when propagating data types during the start-up of the migration after rebuilding analytics that is preventing this data type from being present on the required engines

2. Or this environment wasn't fully migrated and you forgot to copy one or more engines from 7.5 to 7.6, most likely process design

SOLUTION:

1. For scenario #1 simply stop JBoss and delete <JBOSS_HOME>\\standalone\\log\\*.log. Restart JBoss again to confirm enough time has passed by to finish propagating data types.

2. For scenario #2 open all logs of type db_*.log and make sure the all show the 100% migrated message. I am thinking that db_PD is missing and you're running with the out of the box pd*.kdb instead of migrating it by mistake.

Even though I think the issue may be with Process Design make sure to review each db_*.log and search for the 100% migrated message; the log will also show what ID of the *.kdb file it's using that should also give you a clue in whether you missed copying one or more engines to 7.6

If you find out you forgot to copy one or more engines you will have to repeat the migration; copying the missing one now that the migration code ran is going to cause more trouble.