Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
4 replies
Subscribers
7 subscribers
Views
1624 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
User Interface
Just upgraded to Appian 7.6, and we're seeing issues trying to use the OOB r
peterk
over 9 years ago
Just upgraded to Appian 7.6, and we're seeing issues trying to use the OOB reassign functionality.
"There was a problem retrieving the task" is the error message that pops up. I created a new PM with a default form, and just tested the reassigning functionality, and the error dialog appears without reassigning the task.
Anybody run into this?
Thanks,
OriginalPostID-163990
OriginalPostID-163990
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Excellent, then I know what the problem is. Someone deployed a hotfix to this environment incorrectly.
The hotfix needs to be re-applied to both ENGINE_SERVER and APP_SERVER if they are two separate boxes.
Remember the hotfix has an "ear" directory while your environment might have a "runtime_ear" one. The CONTENT of the hotfix ZIP "ear" goes into "runtime_ear".
You also need to re-copy the static content to the web server after deploying the patch.
I know this is the root cause because a "valence" error indicates an internal API method is being called with the wrong number of parameters meaning you have mixed code from two different versions/hotfixes of Appian running in that environment causing the request to that API to have more/less arguments that needed.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Excellent, then I know what the problem is. Someone deployed a hotfix to this environment incorrectly.
The hotfix needs to be re-applied to both ENGINE_SERVER and APP_SERVER if they are two separate boxes.
Remember the hotfix has an "ear" directory while your environment might have a "runtime_ear" one. The CONTENT of the hotfix ZIP "ear" goes into "runtime_ear".
You also need to re-copy the static content to the web server after deploying the patch.
I know this is the root cause because a "valence" error indicates an internal API method is being called with the wrong number of parameters meaning you have mixed code from two different versions/hotfixes of Appian running in that environment causing the request to that API to have more/less arguments that needed.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data