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

Question

Question

Object reference not set after 10.2 upgrade

Forms
Updated February 7, 2017
asked on January 31, 2017

After upgrading to 10.2 Forms, we have one forms processes where 3 out of 4 forms simply show:

Laserfiche Forms has encountered a problem.

An unexpected error has occurred. [LFF502-UnexpectedError]

This error comes up when getting to them via the process or by simply hitting preview in the designer.  I can look at the form and fields though in the designer, just not preview/use it.

Checking the Forms event viewer I see:

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.
 

This is a generic error that I can never seem to decipher no matter the occurrence.  

 

Any ideas as to where to start?

 

Thanks,

Chris

0 0

Replies

replied on January 31, 2017

Is there any custom CSS or JS running on the forms?

Please create a support case and provide the exported business process xml along with the LFForms event log (.evtx).

0 0
replied on January 31, 2017

Ok it seems that I figured it out.  Due to another similar bug in 10.2 with character limit on read-only fields I went through the form and checked if there were any.  There we no character limits on any fields.  However after clicking on each field, then clicking Done, the form worked. 

Moved on to the next form and confirmed that it errored on preview.  Clicked all the fields and hit Done, then the Form worked.

Same for the third....  Not sure what that does or causes but the errors in the log certainly were the same time I hit preview.  

0 0
replied on February 7, 2017

Do you have date fields on those forms? We fixed an issue in hotfix 1013831 of form will be loaded with "object reference not set to an instance of an object" error(SCR 153935) when the format is null in the database.  You can apply the hotfix to avoid similar issues for other processes.

0 0
replied on February 15, 2017

@████████ - I'm getting a "object reference not set to an instance of an object" error on a form that was created after the 10.2 upgrade.  Installing the hotfix 1013831 did not resolve the issue.  It's a form that is being reused on three user tasks.  When routing from task 1 to task 2, it works, but then when routing from task 2 to task 3, I get the error.  Any other suggestions?

You are not allowed to follow up in this post.

Sign in to reply to this post.

Details
Related Posts
Loading ...