We are getting the following error upon uploading an xls sheet with 300 records

RE: We are getting the following error upon uploading an xls sheet with 300 records<

mohamedb — Wed, 10 Sep 2014 20:24:22 GMT

Thanks Cesar. It was a CDT/XLS variables match issue ...

RE: We are getting the following error upon uploading an xls sheet with 300 records<

Cesar Machuca — Wed, 10 Sep 2014 00:02:32 GMT

I see you are using the following function, =linktodocument(todocument(pv!AppianId_Cdt.pricingDoc_int),"Click here to view document"), it seems that todocument(pv!AppianId_Cdt.pricingDoc_int) is returning a null value, check if the cdt pv!AppianId_Cdt has a value in pricingDoc_int.

RE: We are getting the following error upon uploading an xls sheet with 300 records<

mohamedb — Tue, 09 Sep 2014 23:56:14 GMT

Here you go Cesar ...

jboss1-stdOut.log.2014-09-08

RE: We are getting the following error upon uploading an xls sheet with 300 records<

Cesar Machuca — Tue, 09 Sep 2014 23:48:22 GMT

Please attach the complete log for review.

RE: We are getting the following error upon uploading an xls sheet with 300 records<

mohamedb — Tue, 09 Sep 2014 23:28:43 GMT

Here is the log ... the caused by was received a few minutes after the other errors were thrown ...

RE: We are getting the following error upon uploading an xls sheet with 300 records<

mohamedb — Tue, 09 Sep 2014 23:27:38 GMT

08:32:36,433 INFO [stdout] (ajp-/0.0.0.0:8009-14) Caused by: java.lang.NullPointerException: A null parameter has been passed as parameter 1.
08:32:36,433 INFO [stdout] (ajp-/0.0.0.0:8009-14)           at com.appiancorp.core.expr.fn.Signature.nullCheck(Signature.java:328)
08:32:36,433 INFO [stdout] (ajp-/0.0.0.0:8009-14)           at com.appiancorp.core.expr.fn.Function.nullCheck(Function.java:158)
08:32:36,433 INFO [stdout] (ajp-/0.0.0.0:8009-14)           at com.appiancorp.core.expr.fn.Function.nullCheck(Function.java:154)
08:32:36,433 INFO [stdout] (ajp-/0.0.0.0:8009-14)           at com.appiancorp.core.expr.fn.Signature.eval(Signature.java:136)
08:32:36,433 INFO [stdout] (ajp-/0.0.0.0:8009-14)           at com.appiancorp.core.expr.fn.Function.eval0(Function.java:44)
08:32:36,433 INFO [stdout] (ajp-/0.0.0.0:8009-14)           at com.appiancorp.core.expr.Evaluable.eval(Evaluable.java:154)
08:32:36,433 INFO [stdout] (ajp-/0.0.0.0:8009-14)           at com.appiancorp.core.expr.tree.FunctionCall.evalEvaluable(FunctionCall.java:283)
08:32:36,433 INFO [stdout] (ajp-/0.0.0.0:8009-14)           ... 151 more

RE: We are getting the following error upon uploading an xls sheet with 300 records<

Cesar Machuca — Tue, 09 Sep 2014 22:51:48 GMT

My apologies, I forgot to tell you that in cloud instances the file is called jboss1-stdOut.log.YYYY-MM-DD. Review jboss1-stdOut.log.YYYY-MM-DD.log and pay especial attention to the "Caused by" clauses in the stack trace to determine the root cause.

RE: We are getting the following error upon uploading an xls sheet with 300 records<

mohamedb — Tue, 09 Sep 2014 22:46:07 GMT

I can not find this file under "Directory Listing For /logs/". Any other suggestions?

RE: We are getting the following error upon uploading an xls sheet with 300 records<

Cesar Machuca — Tue, 09 Sep 2014 22:25:23 GMT

Please check the Log Files section from the following documentation:
forum.appian.com/.../Appian_Cloud_Web_Administration.html

RE: We are getting the following error upon uploading an xls sheet with 300 records<

mohamedb — Tue, 09 Sep 2014 22:19:21 GMT

We are using a cloud instance. Where I can find this file?

RE: We are getting the following error upon uploading an xls sheet with 300 records<

Cesar Machuca — Tue, 09 Sep 2014 00:33:49 GMT

What exception is shown in the application-server.log? Please upload it to this post.

RE: We are getting the following error upon uploading an xls sheet with 300 records<

mohamedb — Tue, 09 Sep 2014 00:31:04 GMT

Yup, it has timed out a lot longer after receiving this error ...

RE: We are getting the following error upon uploading an xls sheet with 300 records<

Cesar Machuca — Mon, 08 Sep 2014 23:19:51 GMT

There's a 60 mns non-configurable limit for unattended nodes to complete. If this limit is hit you will get the following alert:

"The amount of time allocated for the completion of an unattended activity was insufficient to allow the activity to complete."

if you are seeing an error within the first 10 minutes then your assumption is not accurate enough, and the node is not timing out there should be something else.

This smart service generates a very generic alert that asks you to check the application-server.log for more details, my suggestion is the same, review the application-server.log and pay especial attention to the "Caused by" clauses in the stack trace to determine the root cause.