Posts tagged error

Troubleshooting Adobe ES4 Mobile Workspace Build failure issue with xCode 5

With the upgrade of OS X to version 10.8 and above and xCode version to 5.0 onward, some build issues might come up with Adobe Mobile Workspace

MWS build error

To resolve this problem, we need to remove the weak library link flags from the Linking options.


For details about the issue and steps to fix it, see Adobe LiveCycle blog.

LiveCycle ES3 – FileNet Connector for FileNet 5.0 – Documentation Clarification

Issue:

For LC ES3 – the “Preparing to Install Adobe LiveCycle ES3″ Guide – section 2.2.9 (Additional requirements for Connector for IBM FileNet) – for FileNet Connector configuration is unclear.

The section reads as below -

=======

IBM FileNet 5.0

If LiveCycle is connecting to IBM FileNet 5.0 Content Engine, you must install the Content Engine Java Client. Use the IBM FileNet 5.0 content engine client installer located by default in C:Program FilesFileNetCEClient. During installation, select at least one of the components from Application Engine or Process Engine on the component selection screen.

For IBM FileNet 5.0 Process Engine, you must install the IBM FileNet 5.0 Process Engine Client located by default in C:Program FilesFileNetBPMClient. During installation, select the Other option on the component selection screen.

=======

Questions:

The above text in red does not clearly answer the below questions:

- Does this mean that during the Java Client installation, the user needs to point to an existing Application Engine installation (which maybe be on a different server than LiveCycle)?

- Or does this mean that the Java Client has to be installed where the Application Engine resides (which it already is) and so this step can effectively be skipped?

- Or does this mean that another instance of Application Engine needs to be installed on the same server as LiveCycle?

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle XMLForms Native Process and WebSphere Global Security

- Santosh Tatke, Sr. Support Architect @ Adobe

Debugging form rendering issues related to XMLforms native process could be challenging. In one of the earlier blogs I’ve put together a few points those could help narrow down problem areas. Blog post is available here.

We recently encountered a situation with another customer which was another manifestation of form rendering related problem and root cause was very different.

They were using LiveCycle ES2 SP2 + AIX 6.1 + WAS 7.0.0.17 + Oracle 11g.

---

Read the complete post at Adobe LiveCycle Blog.

Working around a “Turnkey service JBoss for Adobe LiveCycle does not exist” error

- Waldo Smeets

Disease:
After installing a new Jboss turnkey instance of Adobe LiveCycle, some people run into an issue when the LiveCycle Configuration Manager is doing it’s work. At about 40%, the configuration manager might display the following error:

 

Failed on ‘Verifying JBoss for Adobe LiveCycle ES service is installed’
Windows turnkey service JBoss for Adobe LiveCycle ES does not exist

When checking in the Windows Service Panel, indeed there is no such service defined, even though the installer should have created it. I have not been able to replicate this issue, but it happened to me at a customer site and by searching Google it seems that others have run into it as well.

Prescription:
The Google search results tells us that some people forget to set the Java_Home system variable and that you should be using the right version of the JDK. However, this did not seem to be the problem in this case.

Through the install documentation you can find the steps needed to re-create the JBoss for Adobe LiveCycle ES service (page 62). You can use those to try and create the service ‘manually’. For our install, the problem seemed to be in the [LC_INSTALL_ROOT]jbossInstallJBossService.bat script file. Somehow the username / password did not seem to work, whatever we tried it failed. Well, sort off: strangely enought the command prompt output first mentions that there was an error, though still reports that the script was executed succesfully. Still no service created though.

The solution was too simple to come up with: just remove the username / password parameters from the script and execute it. This time the script did not fail and as expected created the service for us. Next thing to do is go into the service panel, select the ‘JBoss for Adobe LiveCycle’ service, right click to go to it’s Properties and in the Log On tab specify Log In As This Account. Then specify the username password (in my case “.administrator” and the password), click OK and you are done.

Now run the LiveCycle Configuration Manager again and most likely it won’t fail anymore cause of the missing service. This seemed to have overcome our issue.

Tip to stay healthy:
When installing the turnkey solution, it is highly recommended to keep the right documentation at hand: Installing and Deploying LiveCycle® ES Using Turnkey.

Did you run into this issue as well? Please let us know if this worked for you or if you have additional tips for our readers.

—-
Original article at http://www.drflex.eu/2009/03/turnkey-service-jboss-for-adobe-livecycle-does-not-exist/?utm_source=rss&utm_medium=rss&utm_campaign=turnkey-service-jboss-for-adobe-livecycle-does-not-exist.

Working around a “Turnkey service JBoss for Adobe LiveCycle does not exist” error

Waldo Smeets

Disease:
After installing a new Jboss turnkey instance of Adobe LiveCycle, some people run into an issue when the LiveCycle Configuration Manager is doing it’s work. At about 40%, the configuration manager might display the following error:

 

Failed on ‘Verifying JBoss for Adobe LiveCycle ES service is installed’
Windows turnkey service JBoss for Adobe LiveCycle ES does not exist

When checking in the Windows Service Panel, indeed there is no such service defined, even though the installer should have created it. I have not been able to replicate this issue, but it happened to me at a customer site and by searching Google it seems that others have run into it as well.

Prescription:
The Google search results tells us that some people forget to set the Java_Home system variable and that you should be using the right version of the JDK. However, this did not seem to be the problem in this case.

Through the install documentation you can find the steps needed to re-create the JBoss for Adobe LiveCycle ES service (page 62). You can use those to try and create the service ‘manually’. For our install, the problem seemed to be in the [LC_INSTALL_ROOT]jbossInstallJBossService.bat script file. Somehow the username / password did not seem to work, whatever we tried it failed. Well, sort off: strangely enought the command prompt output first mentions that there was an error, though still reports that the script was executed succesfully. Still no service created though.

The solution was too simple to come up with: just remove the username / password parameters from the script and execute it. This time the script did not fail and as expected created the service for us. Next thing to do is go into the service panel, select the ‘JBoss for Adobe LiveCycle’ service, right click to go to it’s Properties and in the Log On tab specify Log In As This Account. Then specify the username password (in my case “.administrator” and the password), click OK and you are done.

Now run the LiveCycle Configuration Manager again and most likely it won’t fail anymore cause of the missing service. This seemed to have overcome our issue.

Tip to stay healthy:
When installing the turnkey solution, it is highly recommended to keep the right documentation at hand: Installing and Deploying LiveCycle® ES Using Turnkey.

Did you run into this issue as well? Please let us know if this worked for you or if you have additional tips for our readers.

—-
Original article at http://www.drflex.eu/2009/03/turnkey-service-jboss-for-adobe-livecycle-does-not-exist/.

Go to Top