Updating this post to let you guys know of the WebLogic fix.  The problem is documented in Oracle Support's ID 1543065.1 (CORBA.MARSHAL Stream Corruption Error [ID 1543065.1]).  WebLogic released patch 14691998 for WLS 10.3.5.  You will probably have to ask WebLogic to backport the patch to a differ...

An update for users on what is the fix in my stream corruption situation.  Turn off native IO on the managed WebLogic servers.  Turn off the option by going to the WebLogic admin console GUI, managed server, Configuration tab, Tuning tab and uncheck Enable Native IO.  Restart the managed server(s). ...

I've encountered this error before on LC ES Update 1.  I tried the same action of deleting the working folder inside <LC Root>/configurationManager, but that suggestion didn't work.  I had to uninstall the Adobe LiveCycle application to get past the problem.  Here are the details of my environment a...

I'm getting the same type of error.  Were you able to figure out this error?  My scenario in a Production environment is the same.  I get this error randomly.  I save off the XML and XDP template and run it through the FormsIVS and OutputIVS tests.  The IVS tests pass, so it's not the XML or XDP.  I...

I couldn't get a LC ES Forms server solution to this problem.  Adobe LC support stated that I had to modify the XDPs that show the bolding problem.  According to Product Engineering and Escalations group, LC ES 8.2.1 contained changes with respect to font attributes that we need to modify the XDP.  ...

Old Environment:  LC 7.2 Forms, Windows 2003, Weblogic 8.1 SP5, Oracle 10.2.0.4Old Fonts Directory:  c:\windows\fonts.  The customer fonts were also added to this directory and the fonts were embedded into the adobe-FontManager.ear.New Environment:  LC ES Update 1 (8.2) SP3, Solaris 10, WebLogic 10....