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
17 replies
Subscribers
7 subscribers
Views
4432 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
Hi there ! I'm trying to import an application on my production s
michelb
over 9 years ago
Hi there !
I'm trying to import an application on my production server and having the following error:
The model could not be published. Errors: [Connection endNodeGuiIds must match guiid of a node in this process model.,
Connection endNodeGuiIds must match guiid of a node in this process model., Connection endNodeGuiIds must match guiid of a node in this process model.,
Connection endNodeGuiIds must match guiid of a node in this process model., Logic node rules specify output nodes that do not exist., Invalid node gui ID in connection]
The problem is that both process models that are not being imported because of this error, are being published in my development environment.
I'm a little lost and could use some help.
Thanks !...
OriginalPostID-124448
OriginalPostID-124448
Discussion posts and replies are publicly visible
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Have a look down into the import log, it could be that gateway node is connected to a custom smart service (i.e. plug-in) and that plug-in is not present in the environment where you are importing.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
michelb
over 9 years ago
Hi Eduardo,
I double checked and in both cases we are not using any custom smart service in the process model.
Could it be happening because I'm importing in 7.6 a 7.4 application ?
The import log doesn't give me much more information than the lines I posted before.
Thanks
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Can you attach the import log?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
michelb
over 9 years ago
No, I'm sorry...but there are confidential information in there. But I can paste here what it says in the "caused by" part of the log:
Caused by: com.appiancorp.suiteapi.common.exceptions.AppianException: The model could not be published. Errors:
[Connection endNodeGuiIds must match guiid of a node in this process model., Connection endNodeGuiIds must match guiid of a node in this process model.,
Connection endNodeGuiIds must match guiid of a node in this process model., Connection endNodeGuiIds must match guiid of a node in this process model.,
Logic node rules specify output nodes that do not exist., Invalid node gui ID in connection]
Caused by: com.appiancorp.suiteapi.common.exceptions.AppianException: The model could not be published. Errors:
[Connection endNodeGuiIds must match guiid of a node in this process model., Logic node rules specify output nodes that do not exist.,
Logic node rules specify output nodes that do not exist., Invalid node gui ID in connection]
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
The model states that it was imported but couldn't be published, simply open the model in this environment and try to publish manually it will make more sense if you do it from the designer
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
michelb
over 9 years ago
I tried to do this earlier, but when I open any of the process models with the error, nothing appears, it comes blank.
It's like just the name of the process model was imported but the content is not there.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
When you open it there should be a new error in the log, do you see something?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
michelb
over 9 years ago
It looks like this error is appearing when I try to open it:
2014-10-02 04:04:24,558 [Thread-152] ERROR com.appiancorp.core.timer.timers.TransientTopicHeartbeat - No acknowledgement from TransientTopic in 60 seconds, forcing rules cache to be cleared now.
I just opened the process start form (that does no exists, this was just to test it) and when I came back I could see that the variables of the process model were there.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
No that error is not related.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
michelb
over 9 years ago
This is the only error that appears when I try to load it.
Should I look somewhere else ? Is there any other away to debug this error ?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
>