You are viewing limited content. For full access, please sign in.

Question

Question

Laserfiche Forms encountered an internal error [LFF500-InternalError] after upgrade from 9.2 to 10.2.1.205

asked on December 18, 2017

We have a customer that is able to submit a form fine however when the approver goes to view the document they receive an error. This error shows up if you: 

  1. Click on the document in the "My Tasks" pane
  2. Open the instance via "My Tasks", "Instances", "Monitor" or any other method

 

Additionally, event viewer logs the below error each time the error occurs:

[502]: An unexpected error has occurred. [LFF502-UnexpectedError]

Details:

URL: /Forms/webapi/v1/Data?instanceId=375301&mode=variable&onlySummaryVariables=true

Error: UnexpectedError

Date: 12/18/2017 4:19:58 PM (Central Standard Time)

HTTP Status Code: 500

Business Process ID: 0

User: ADS\hallc

IP: 10.135.211.145

Browser: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:27.0) Gecko/20100101 Firefox/27.0

Business Process Name:

Stack Trace:

Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException

Message: An unexpected error has occurred. [LFF502-UnexpectedError]

Inner exception: System.NullReferenceException

Message: Object reference not set to an instance of an object.

   at Laserfiche.Forms.Routing.VariableXMLGenerator.<>c__DisplayClass55_1.<ValidateEntity>b__1(cf_bp_dataset a)

   at System.Linq.Enumerable.Any[TSource](IEnumerable`1 source, Func`2 predicate)

   at Laserfiche.Forms.Routing.VariableXMLGenerator.ValidateEntity(XElement entityElement, entity entityToValidate, String memberPath, List`1 attributePool)

   at Laserfiche.Forms.Routing.VariableXMLGenerator.GenerateXml(Int32 bpInstanceId, Nullable`1 formId, cf_user_snapshot initiator, Nullable`1 submissionId, Nullable`1 initiatedTime, Nullable`1 taskTime, Boolean includeSeparators, HashSet`1 includeAttrIds)

   at E_Forms.WebApi.Version1.QueryServices.DataServices.Get(IWebApiContext webApiContext, String dashboardType)

   at lambda_method(Closure , Object , Object[] )

   at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ActionExecutor.<>c__DisplayClass10.<GetExecutor>b__9(Object instance, Object[] methodParameters)

   at System.Web.Http.Controllers.ReflectedHttpActionDescriptor.ExecuteAsync(HttpControllerContext controllerContext, IDictionary`2 arguments, CancellationToken cancellationToken)

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

   at System.Web.Http.Controllers.ApiControllerActionInvoker.<InvokeActionAsyncCore>d__0.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

   at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

   at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()

   at System.Web.Http.Filters.ActionFilterAttribute.<CallOnActionExecutedAsync>d__5.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at System.Web.Http.Filters.ActionFilterAttribute.<ExecuteActionFilterAsyncCore>d__0.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

   at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext()

--- End of stack trace from previous location where exception was thrown ---

   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()

   at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__0.MoveNext()

0 0

Replies

replied on December 18, 2017

Hi Jonathan,

It seems that there is certain invalid variable (with unexpected name or property) according the the error message. Can you ask the customer to double check the variables?

If the cause could not be found, can you open a support case and provide us the process?

0 0
replied on December 19, 2017

I have already checked all the variables. I will open a case, thanks.

0 0
replied on April 13, 2018

Did you get this resolved?

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.