Within one of our Appian instances we are getting the 'Illegal attempt to ch

dons over 9 years ago

Within one of our Appian instances we are getting the 'Illegal attempt to change an input to an output' errors during deployment of the plugins. This is happening for plugins we have developed and other plugins that we didn't develop. None of the CDT or the parameters to the plugins have changed in quite some time. In order to figure out / resolve the issue, I have two questions regarding this problem.

First, can anyone tell me entries I can add to appian_log4j.properties file that will help me determine exactly what differences Appian thinks there are between the currently deployed plugin and the plugin attempting to deploy? The message tells me the parameter/CDT name, but what I need to know more specific details about what is different.

Second, is there some utility or option that can be used to completely remove a plugin from Appian so the latest plugin can be deployed successfully without having to change the plugin's key?

Thanks

Discussion posts and replies are publicly visible

Parents

0 dons over 9 years ago

Thanks for the reply and the reminder. This makes sense. Unfortunately, we don't know how we originally got into the situation. I don't believe anyone manually or purposely deleted the CDTs, nowever it is an avenue to research further. At this point however, the CDTs have been deleted once since originally encountering the problem,since all other efforts failed to resolve the issue.

So a couple follow-up questions...

1. Since it isn't possible to delete all references to a plug-in in Appian (even if it isn't used) so that we can redeploy it successfully without changes to the plugin, is it possible through Appian or an API to get a list of the plugins deployed in Appian, along with their CDT parameter version numbers, so we can attempt to annotate the plugin with the proper versions so we can perhaps deploy them without changing the key?

2. Assuming this situation has happened in a new envrionment which has a complex intial setup and configuration, is there a way to restart Appian with fresh data (as if it was a new installation) so the plugins will deploy, without having to go through the entire installation and setup process again?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Reply

0 dons over 9 years ago

Thanks for the reply and the reminder. This makes sense. Unfortunately, we don't know how we originally got into the situation. I don't believe anyone manually or purposely deleted the CDTs, nowever it is an avenue to research further. At this point however, the CDTs have been deleted once since originally encountering the problem,since all other efforts failed to resolve the issue.

So a couple follow-up questions...

1. Since it isn't possible to delete all references to a plug-in in Appian (even if it isn't used) so that we can redeploy it successfully without changes to the plugin, is it possible through Appian or an API to get a list of the plugins deployed in Appian, along with their CDT parameter version numbers, so we can attempt to annotate the plugin with the proper versions so we can perhaps deploy them without changing the key?

2. Assuming this situation has happened in a new envrionment which has a complex intial setup and configuration, is there a way to restart Appian with fresh data (as if it was a new installation) so the plugins will deploy, without having to go through the entire installation and setup process again?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Children

No Data