HTTP Status 500 error suddenly occurs

Avatar

Avatar

JosephDoggie

Avatar

JosephDoggie

JosephDoggie

09-10-2013

I have two different forms that were rendering correctly on my local for a long time, including just yesterday.

Suddently, I get the following error:

{Note:  Somebody should enable copy-paste on these forum pages!):

HTTP Status 500 - DSCError:  ComponentID= DSC ErrorCode =2 MinorCode = 0 Message= Parameter: inFormDoc is required.  ErrorMessage:  Parmeter:  inFormDoc is required.

This occured suddently.

I didn't make any changes to either form or to my LiveCycle setup, files, or folders.

It looks like my computer was not updated last night and it looks like no new software was installed.

It is highly unlikely that a programming "bug" would affect both forms at the same time to the extent that they'd both stop rendering.

The "inFormDoc" variable is all over my various LiveCycle files, but since they were working yesterday, I think this may be a red herring.

Of course, I tried rebooting at least twice as well as stopping/starting services with the "iisreset" command in command prompt.

I googled this error but didn't find much that would be helful to this situation, just enough to see other people have had it in various contexts.

Has anyone seen this or does any one know of a solution?

I'm pretty sure our policy is to not allow me to post/email code and files and such (sorry).

Thanks in advance!

Accepted Solutions (1)

Accepted Solutions (1)

Avatar

Avatar

JosephDoggie

Avatar

JosephDoggie

JosephDoggie

09-10-2013

A colleague came up with an answer that I share here if anyone has problems with this.

There is a location (tmp) that fills up with GB of memory -- why doesn't LiveCycle auto-clean this, b.t.w. ?

On my testap, this is located at:

E:\Adobe\Adobe LiveCyle ES3\jboss\server\lc_turnkey\tmp  

{Thanks for not enabling copy & paste on this forum, b.t.w.}

After emptying this folder, it still didn't work as a restart of the server is needed.

Now both forms do render.

I knew that it couldn't be a programming issue as such.

Please be on the look-out for this in the future, and please reply if this post helped you.

Thanks!

Answers (0)