Hello, We have successfully done an upgrade from Appian 7.7 to 16.1 and hav

Adel Ammari over 9 years ago

Hello,
We have successfully done an upgrade from Appian 7.7 to 16.1 and have applied the latest Hotfix Package B. But we are facing these error messages which we are not able to resolve or get around. Below are further stuff we noticed:

- All engines are OKAY.
- Database started.
- Search Server Started.
- When starting jboss, no errors except for "10:42:08,591 ERROR [stderr] (Spring executor 3) ScriptEngineManager providers.next(): javax.script.ScriptEngineFactory: Provider com.sun.script.javascript.RhinoScriptEngineFactory not found", which can be ignored i guess.
- We are able to login normally to Appian as well, except that some connections to some records is broken (when using the "feed" view) but works normal (when using the new "list" view).
- But soon after we click on tasks or records, we get a huge block of errors which we are not able to solve.

Furthermore, we noticed that whenever we save any query rule or datastore, inst...

LogsAndScreenshot.zip

Discussion posts and replies are publicly visible

0 Adel Ammari over 9 years ago

...ead of it saving/publishing and closing, it stays stuck on the screen which is saving, keeping the buttons disabled. Attached is a screenshot to illustrate this. This screenshot is after pressing "Save New Version" on a query rule.

Thank you.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Khalil Ben Naceur
Appian Employee
over 9 years ago

Concerning your last point, which browser are you using to save the query rule? Is the behavior seen when using IE11 as well?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tom Ryan
Appian Employee
over 9 years ago

Additionally, can you check that all the contents of the directories under <Appian Home>/_admin are present in the upgraded environment>, especially the contents of the accdocs* directories. It could be that there is an invalid content ID because some files are missing.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Adel Ammari over 9 years ago

Hello Khalil, this behavior is present in all browsers, including IE11.
Hello Tom, yes we moved all of the files and these zip files were used to extract/move them from the previous installation to this upgrade.

Any other thoughts gents? Those are a lot of errors in that log.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Adel Ammari over 9 years ago

The zip files contain the files we took from the original installation.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Adel Ammari over 9 years ago

Its wrth to share that eventually it DOES save! So the screenshot where it shows the buttons disabled and nothing is happening is simply missing the "Waiting" at the top. But its taking a lot of time to save anything, very weird behavior!
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Adel Ammari over 9 years ago

After deleting the search_local in the search server, the part around stuck/slow saving has vanished. Remains the main problem of the errors we see in the attached logs above,
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Tom Ryan
Appian Employee
over 9 years ago

Further investigation of the stack trace shows that this is related to the Physical URL of Documents plugin:

10:43:03,444 ERROR [stderr] (http-/0.0.0.0:80-1) at com.appian.ps.documentservices.GetDocumentPhysicalURL.getDocumentURL(GetDocumentPhysicalURL.java:30)

My suggestion would be to review your use of this plugin and ensure you are not passing any invalid arguments.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Adel Ammari over 9 years ago

Thanks Tom, we have removed the plugin as we are not using it and the errors went away. One new issue we have noticed is that we are getting a error related to CLOB.
[Appian Timer - 1] ERROR org.hibernate.util.JDBCExceptionReporter - ORA-00932: inconsistent datatypes: expected - got CLOB

Any thoughts?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Khalil Ben Naceur
Appian Employee
over 9 years ago

Do you see this error during JBoss startup or when running a database query from appian? If it appears while running a query it means you have a CLOB (Character Large Object) in a WHERE clause, which is not supported:

stackoverflow.com/.../ora-00932-inconsistent-datatypes-expected-got-clob
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel