Relative vs Absolute paths for Form fragments

Here’s another gotcha when using LiveCycle Output ES2 that’s had me stumped for a few hours.  I designed a form which used a number of fragments which tested fine within designer.  Once deployed to the server I was always getting blank forms.  A quick check of the logs revealed the following warning:

ALC-OUT-002-058: Cannot retrieve the resource from Repository Path.

A bit of digging around and I hit the a knowledge base article on Adobe’s site.  Basically there’s a “limitation” with the way the form is compiled which means relative paths within fragments and XDPs can cause problems.  The solution is to turn the relative path references (which are inserted by default in Designer) into absolute paths.  Doing this sorted the problem for me but this is something that needs fixing!


Blank screen when opening process in Workbench

Back to working with LiveCycle ES2 on a new project and had problems opening any process after installed Workbench ES2 on my laptop.  When opening a process in Workbench ES2 I was being shown a grey tab with no content.  The workaround seems to be to run Workbench as an Administrator (right click on icon > Run as Administrator).  Solved the problem but don’t know why it needs it!

Connecting to LiveCycle ES2 Repository outside of Workbench

When trying to test some forms I was struggling to remember the location of the LiveCycle repository.  Turns out that you can access it via WebDav from Windows or directly from a browser using the following:


Login with your usual username and password and you’ll be able to browse the repository hierarchy.