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
12 replies
Subscribers
7 subscribers
Views
3404 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
General
I have installed Appian on my PC and till the command start-suite.bat everything
milid
over 7 years ago
I have installed Appian on my PC and till the command start-suite.bat everything seemed fine but after I run the command chekengine.bat I get status as 'FATAL' for certain instances with issues saying 'No gateway is active' .I am attaching a screenshot for the same.
Any guidance pertaining to my issue are welcome.
OriginalPostID-216662
OriginalPostID-216662
Discussion posts and replies are publicly visible
0
mathanap
over 7 years ago
Link to the post where a practitioner got into a similar case
forum.appian.com/.../e-215548
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
prosenjitd
A Score Level 2
over 7 years ago
I would like to suggest few steps to see if it resolves your issue.
1. Stop the Engines.
2. Run the CheckEngine to confirm the status of all the engines reporting as FATAL
3. At this point, make sure you do not have any running processes(in the Windows Task manager) that are Appian related. If there are, please kill the processes manually
4. Start the Engines again.
If some of the engines continue to report FATAL status -
1. Stop the Engines
2. Please go back to the last good KDB files for the problematic engines and rename to make them highest numbered(eg. pd8.kdb to pd12.kdb).
3. Start the Engines
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
milid
over 7 years ago
I am attaching the server log file. The FATAL issue status got resolved and status for every instance said 'okay'. Now when I start JBOSS and open my url-
hostname.domain:8080/suite
, it says 'Web page cannot be displayed'. Please help
serverlogfile.txt
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mathanap
over 7 years ago
Is the attached server log taken after jboss has been started? Because, the server log shows that there is an error while starting the jboss and that error seems to be related to missing of .dodeloy file in <Appian>/ear folder.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
prosenjitd
A Score Level 2
over 7 years ago
@milid, Your app logs indicate that deployment of Appian EAR did not go through successfully because your Jboss standalone.xml is missing several required configurations. Please make sure to complete all the steps mentioned in the Quick Installation https://forum.appian.com/suite/help/16.2/Quick_Start_Installation_Guide_for_Windows_and_JBoss.html, if this is what you are following for the installation.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
prosenjitd
A Score Level 2
over 7 years ago
@milid, Can you also please also share the root cause of the engine issue and how did it get resolved? It's always good to share the findings and solutions to the benefit of the Forum user community.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
milid
over 7 years ago
@mathanap Yes, the attached server log file has been taken after jboss had been started.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
milid
over 7 years ago
@prosenjitd, I started appian again and just after start-suite.bat , I ran the command checkengine.bat. The status for all instances showed 'OKAY'.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
milid
over 7 years ago
@prosenjitd I have followed the https://forum.appian.com/suite/help/16.2/Quick_Start_Installation_Guide_for_Windows_and_JBoss.html but still when I start JBOSS and open my url- http://hostname.domain:8080/suite, it says 'Web page cannot be displayed'. I am attaching the new server log file after starting appian again.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
mathanap
over 7 years ago
Once the jboss is started successfully then we would get message in log like 'Started in <yyy>ms. Started <yyy> of <yyy> services'. Based on the type of installation you did, follow the corresponding documentation once again and make sure that all required configurations are done correctly. As pointed by prosenjitd there might be some configurations missing in standalone.xml.
Follow 'ERROR' and its corresponding 'Caused By' in the log to track and debug the jboss error.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
>