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
6 replies
Subscribers
7 subscribers
Views
1919 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Hi, I have a node to update a PDF and it have worked until 26 Feb 2016.
jurim409
A Score Level 1
over 8 years ago
Hi,
I have a node to update a PDF and it have worked until 26 Feb 2016.
Today, everytime I launch this node, the process generate this Alert: "Cannot merge template".
The same thing happens if I prove to create a new PDF.
Can you help me?
Thanks in advance.
OriginalPostID-197624
OriginalPostID-197624
Discussion posts and replies are publicly visible
0
sikhivahans
over 8 years ago
@jurim Have you had a chance to dig through the logs? If not, I would like to suggest to do so and attach them here if you aren't able to interpret them. I wouldn't say that this resolves your issue but it might give you leads.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jurim409
A Score Level 1
over 8 years ago
Hi,
I attach an example. Thank you for your help.
CannotMergeTemplateError.txt
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mpontius
over 8 years ago
Looks like a filesystem access issue. Could potentially be the way that Appian was started.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jurim409
A Score Level 1
over 8 years ago
Hi,we have a problem of space in the environment. Thanks for your help
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
siddharths
over 8 years ago
was space the issue for this problem? or was it any other issue? I am getting the same alert and wanted to know what was the root cause for this.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
jurim409
A Score Level 1
over 7 years ago
Hi,
I'll confirm that it was about the space and so we prove to make a restart of JBoss.
After, when I restart the node, i didn't have this problem anymore
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel