Hi, I have the message below starting the engines. Collabo

yes

description -

  1      N/A            Unable to communicate with the server

                         Gateway Details (Process-Design):

 _GW_  _Host_            _Port_ _Resp_  _Trans_ _Conn_  _Online_        _Size_
  1   localhost           5016   Unable to contact server:parse

 Legend:
  Resp    - The response time of the gateway (seconds).
  Trans   - The number of transactions in the log.
  Conn    - The total number of read/write connections.
  Online  - The amount of time which the server has been online.
  Size    - The current size of the database.

        ---     ---     ---     ---     ---     ---     ---     ---

 ## Process-Analytics0000 ##   (2017-06-06 05:12:38 GMT)   ## Process-Analytics0
000 ##

                         Application Issues (Process-Analytics0000)
  No issues detected.

                         Gateway Issues (Process-Analytics0000)

 _GW_   _Severity_      _Details_

  1      N/A            No issues detected.

                         Gateway Details (Process-Analytics0000):

 Gateway Chain(s):

   GW 1 (STANDALONE)

 _GW_  _Host_            _Port_ _Resp_  _Trans_ _Conn_  _Online_        _Size_
  1   localhost           5018   0.007   0       1      18 mins         2 MB

 Legend:
  Resp    - The response time of the gateway (seconds).
  Trans   - The number of transactions in the log.
  Conn    - The total number of read/write connections.
  Online  - The amount of time which the server has been online.
  Size    - The current size of the database.

        ---     ---     ---     ---     ---     ---     ---     ---

 ## Process-Analytics0001 ##   (2017-06-06 05:12:38 GMT)   ## Process-Analytics0
001 ##

                         Application Issues (Process-Analytics0001)
  No issues detected.

                         Gateway Issues (Process-Analytics0001)

 _GW_   _Severity_      _Details_

  1      N/A            No issues detected.

                         Gateway Details (Process-Analytics0001):

 Gateway Chain(s):

   GW 1 (STANDALONE)

 _GW_  _Host_            _Port_ _Resp_  _Trans_ _Conn_  _Online_        _Size_
  1   localhost           5020   0.003   0       1      18 mins         2 MB

 Legend:
  Resp    - The response time of the gateway (seconds).
  Trans   - The number of transactions in the log.
  Conn    - The total number of read/write connections.
  Online  - The amount of time which the server has been online.
  Size    - The current size of the database.

        ---     ---     ---     ---     ---     ---     ---     ---

 ## Process-Analytics0002 ##   (2017-06-06 05:12:38 GMT)   ## Process-Analytics0
002 ##

                         Application Issues (Process-Analytics0002)
  No issues detected.

                         Gateway Issues (Process-Analytics0002)

 _GW_   _Severity_      _Details_

  1      N/A            No issues detected.

                         Gateway Details (Process-Analytics0002):

 Gateway Chain(s):

   GW 1 (STANDALONE)

 _GW_  _Host_            _Port_ _Resp_  _Trans_ _Conn_  _Online_        _Size_
  1   localhost           5022   0.003   0       1      18 mins         2 MB

 Legend:
  Resp    - The response time of the gateway (seconds).
  Trans   - The number of transactions in the log.
  Conn    - The total number of read/write connections.
  Online  - The amount of time which the server has been online.
  Size    - The current size of the database.

        ---     ---     ---     ---     ---     ---     ---     ---

 ## Process-Exec00 ##   (2017-06-06 05:12:38 GMT)   ## Process-Exec00 ##

                         Application Issues (Process-Exec00)

  _Severity_    _Details_

   FATAL!        No gateway is active.

                         Gateway Issues (Process-Exec00)

 _GW_   _Severity_      _Details_

  1      N/A            Unable to communicate with the server

                         Gateway Details (Process-Exec00):

 _GW_  _Host_            _Port_ _Resp_  _Trans_ _Conn_  _Online_        _Size_
  1   localhost           5024   Unable to contact server:parse

 Legend:
  Resp    - The response time of the gateway (seconds).
  Trans   - The number of transactions in the log.
  Conn    - The total number of read/write connections.
  Online  - The amount of time which the server has been online.
  Size    - The current size of the database.

        ---     ---     ---     ---     ---     ---     ---     ---

 ## Process-Exec01 ##   (2017-06-06 05:12:38 GMT)   ## Process-Exec01 ##

                         Application Issues (Process-Exec01)

  _Severity_    _Details_

   FATAL!        No gateway is active.

                         Gateway Issues (Process-Exec01)

 _GW_   _Severity_      _Details_

  1      N/A            Unable to communicate with the server

                         Gateway Details (Process-Exec01):

 _GW_  _Host_            _Port_ _Resp_  _Trans_ _Conn_  _Online_        _Size_
  1   localhost           5026   Unable to contact server:parse

 Legend:
  Resp    - The response time of the gateway (seconds).
  Trans   - The number of transactions in the log.
  Conn    - The total number of read/write connections.
  Online  - The amount of time which the server has been online.
  Size    - The current size of the database.

        ---     ---     ---     ---     ---     ---     ---     ---

 ## Process-Exec02 ##   (2017-06-06 05:12:38 GMT)   ## Process-Exec02 ##

                         Application Issues (Process-Exec02)

  _Severity_    _Details_

   FATAL!        No gateway is active.

                         Gateway Issues (Process-Exec02)

 _GW_   _Severity_      _Details_

  1      N/A            Unable to communicate with the server

                         Gateway Details (Process-Exec02):

 _GW_  _Host_            _Port_ _Resp_  _Trans_ _Conn_  _Online_        _Size_
  1   localhost           5028   Unable to contact server:parse

 Legend:
  Resp    - The response time of the gateway (seconds).
  Trans   - The number of transactions in the log.
  Conn    - The total number of read/write connections.
  Online  - The amount of time which the server has been online.
  Size    - The current size of the database.

        ---     ---     ---     ---     ---     ---     ---     ---

   S U M M A R Y    (2017-06-06 05:12:38.958 GMT)    S U M M A R Y

 _APP_                          _ACTIVE_GW_    _STATUS_  _ISSUES_
 Discussion Forums               0/1          * FATAL!  No gateway is active.

 Notifications Service           0/1          * FATAL!  No gateway is active.

 Notifications Email Processor   0/1          * FATAL!  No gateway is active.

 Channels                        0/1          * FATAL!  No gateway is active.

 Collaboration                   0/1          * FATAL!  No gateway is active.

 Collaboration Statistics        0/1          * FATAL!  No gateway is active.

 Personalization                 0/1          * FATAL!  No gateway is active.

 Portal                          0/1          * FATAL!  No gateway is active.

 Process-Design                  0/1          * FATAL!  No gateway is active.

 Process-Analytics0000           1/1            Okay

 Process-Analytics0001           1/1            Okay

 Process-Analytics0002           1/1            Okay

 Process-Exec00                  0/1          * FATAL!  No gateway is active.

 Process-Exec01                  0/1          * FATAL!  No gateway is active.

 Process-Exec02                  0/1          * FATAL!  No gateway is active.

    * : Not all instances defined in the gateway XML are currently active.

                  *  *  * ALERT *  *  *

  The following 12 applications require *IMMEDIATE* attention:

        Discussion Forums
        Notifications Service
        Notifications Email Processor
        Channels
        Collaboration
        Collaboration Statistics
        Personalization
        Portal
        Process-Design
        Process-Exec00
        Process-Exec01
        Process-Exec02

                  *  *  * ALERT *  *  *

We followed these two links to restore the server.

docs.appian.com/.../Quick_Start_Installation_Guide_for_Windows_and_JBoss.html
docs.appian.com/.../Upgrade_Guide.html

if the old instance of Appian is working fine, last one is good...Please verify below steps once..

1. Stop all engines for the currently running Appian suite.
2. Navigate to old instance(which you were using before update)
3. Start the engines and verify all engines are in OKAY status.

If any problem here, there is an issue with your old kdbs . we need fix it by following the steps I mentioned in my previous comments.

sonamg

What do you are planning to do now? Fresh installation or Updation.

If fresh installation, Do it by following installation guide.

If Updation, follow below steps.

1. Switch back to old instance.
   • Stop Application server, search server and engines (Verify all processes are stopped by executing ps -ef , kill if any not stopped)
   • rename it to different name or delete the 'Appian' folder.
   • Rename your old instance to 'Appian'
2. Start Appian engines (now you are running old instance)
   • Make sure all engines are started with 'Okay' status(If any FATAL error follow steps I have mentioned earlier)
   • Run check point script and followed by clean up script
3. Start Search server
4. Start Application server, make sure suite.ear is successfully deployed and you are able to login
5. Stop the suite(Stop Application server, Search server and engines and Verify all processes are stopped)
6. Now either do the fresh installation of your required version
7. If you are updating follow the update guide.

sonamg

What do you are planning to do now? Fresh installation or Updation.

If fresh installation, Do it by following installation guide.

If Updation, follow below steps.

1. Switch back to old instance.
   • Stop Application server, search server and engines (Verify all processes are stopped by executing ps -ef , kill if any not stopped)
   • rename it to different name or delete the 'Appian' folder.
   • Rename your old instance to 'Appian'
2. Start Appian engines (now you are running old instance)
   • Make sure all engines are started with 'Okay' status(If any FATAL error follow steps I have mentioned earlier)
   • Run check point script and followed by clean up script
3. Start Search server
4. Start Application server, make sure suite.ear is successfully deployed and you are able to login
5. Stop the suite(Stop Application server, Search server and engines and Verify all processes are stopped)
6. Now either do the fresh installation of your required version
7. If you are updating follow the update guide.

We have to do either repair or rename only.

The problem is with your old instance. First you need fix that issue, then only you can do the update.So before going for fresh installation first fix the issue with old kdb files either by following my instruction in earlier comment or by raising support ticket.

I would suggest you contact Appian support, so you could get better help. Below are the contact details.

Email: support@appian.com

Call:

United States: +1 703 442 1066          

United Kingdom: +44 20 3695 0246

France: +33 184 886 650    

Australia: +61 285 203 042

ramanjaneyulut,

I'd raised the ticket and mailed the support team.

We have checked in the task manager for engines which are inactive. It is showing the below error(screenshot attached):