We have just had our first install of Appian created last week. All is ok with

We have just had our first install of Appian created last week. All is ok with the portal, but we have issues with Tempo.
Initially all images were missing within Tempo including the Appian logo. Talking to Sathya we had to change the file custom.properties. changing the property from conf.suite.SERVER_AND_PORT=localhost:8080 to conf.suite.SERVER_AND_PORT=hawkenbury:8080.

Services had to be stopped as the file was saying access denied.

The following was carried out in order to stop and start the services
To Start
1. E:\\appian\\server\\scripts\\start-suite.bat – to start Appian engines
2. E:\\appian\\server\\scripts\\diagnostics\\check-engine.bat to check if all the engines are running.
3. E:\\appian\\bin\\jboss-6.1\\bin\\standalone.bat to start JBOSS Application server
a. This will take a few moments.
To stop
1. You can do Ctrl-C on the command console that runs JBOSS. This will stop JBOSS
2. ...

OriginalPostID-85733

OriginalPostID-85733

  Discussion posts and replies are publicly visible

Parents
  • 1. What about Venkat's suggestion? What was the outcome of that test?
    2. If you are getting an error even when posting you should be able to determine the root cause by looking at the application-server.log.

    ---> 2.1 Reproduce the issue
    ---> 2.2 Open the application-server.log from <APPIAN_HOME>\\logs
    ---> 2.3 Find the relevant error at the end of the log and read the error from top to bottom; pay attention to the "Caused by" clauses
    ---> 2.4 The most informative will be the last one from top to bottom in the main error stack trace.
Reply
  • 1. What about Venkat's suggestion? What was the outcome of that test?
    2. If you are getting an error even when posting you should be able to determine the root cause by looking at the application-server.log.

    ---> 2.1 Reproduce the issue
    ---> 2.2 Open the application-server.log from <APPIAN_HOME>\\logs
    ---> 2.3 Find the relevant error at the end of the log and read the error from top to bottom; pay attention to the "Caused by" clauses
    ---> 2.4 The most informative will be the last one from top to bottom in the main error stack trace.
Children
No Data