Hi TestScreen,Could you explain the use-case? Did you do a fresh ADEP
installation or did you upgrade/apply a service pack?It seems the
database has not been initialised.Thanks and Regards,Hina Rastogi
What environment did you select for you target LiveCycle ES4
environment? Also, is your application server starting up fine if no
EARs are deployed to it?Please check that both the JBoss servers are not
running while you are running the upgrade to ES4.Thanks,Hina Rastogi
Hi,Depending upon the supported application server, database and JDK
versions in LiveCycle ES4 you can decide how you want to upgrade.The
link @
http://helpx.adobe.com/livecycle/help/livecycle-es4-supported-platforms.html
lists all the supported versions of application server, database and
JDK.Once you have decided on your target environment, you might choose
to stay on the same machine or move to a different machine. In both
these cases your upgrade will be out-of-place since JBoss 4.2.0 is not...
First and foremost you cannot use the XMLs which are part of turnkey
JBoss directly.You should discard adobe-ds.xml and mysql-ds.xml from
/jboss/server//deploy and get hold of
SQL Server specific adobe-ds.xml and mssql-ds.xml and then make
necessary modifications w.r.t your SQL Server.In addition to this you
would have to modify login-config.xml as well to add an entry of
application policy for MSSQL DB.If you have performed all these steps
and still issues are coming then the error could be bec...
I believe you are using a 64 Bit Windows OS.The error above suggests
that your JAVA_HOME is incorrectly set in environment variables.Please
make sure that you are using 64 Bit Java and your environment variables
are correctly set.Sample JAVA_HOME would be : C:\Program
Files\Java\jdk1.6.0_34HTH,Hina Rastogi
Hi Ravi-Kant,LiveCycle makes a call to the database while trying to
authenticate a user.Please make sure that your database is up and
running and accessible by the LiveCycle server machine.Also, ensure that
your database is not corrupted in any way.Thanks and Regards,Hina
Rastogi
Thanks for your response.As of today LiveCycle ES3 v10.0.2 doesn't
support WebLogic 12.1.1.0We are planning to support it in future
LiveCycle releases.You can refer the official LiveCycle platform matrix
available @
http://help.adobe.com/en_US/livecycle/10.0/supported_platforms.htmlIf
you must use WebLogic 12.1.1.0 for your deployment, you can get in touch
with LiveCycle Support and log a CCR.Thanks and Regards,Hina Rastogi
Could you please provide the information about your setup? It would help
assess in a better way.Following are the details required:LiveCycle
VersionTurnkey (Y/N)OS & VersionDB & VersionJDK VersionApp Server &
VersionLiveCycle Modules in Use
Hi Ravi,WebLogic 12c is not a supported Application Server for LiveCycle
ES3.You can visit
http://help.adobe.com/en_US/livecycle/10.0/supported_platforms.html for
a list of supported Application Servers for LiveCycle ES3.Thanks and
Regards,Hina Rastogi
Hi Buddiga,Yes you are correct, it is BOOTSTRAP_ADDRESS.So, is your
BOOTSTRAP_ADDRESS default i.e. 2809 or is it other than that?Thanks and
Regards,Hina Rastogi
Hi Buddiga,Please verify that you are using the correct JNDI port.By
default the value is 2809. However, this can be any other value too and
can be confirmed from WebSphere admin console.Look for value of
SOAP_CONNECTOR_ADDRESS under Ports section of your WebSphere Application
Server instance.Thanks and Regards,Hina Rastogi
Hi Buddiga,There could be two reasons for this issue:1) You have
launched LiveCycle Configuration Manager (LCM) from a JDK other than
IBM’s. This is least likely since it is an AIX box.2) You are using
version 7.0.0.9 or 7.0.0.11 of WebSphere.If at all it is the first case,
kindly make sure that you are launching you LCM from IBM JDK.In case it
is second, please apply the IBM patch as mentioned in
http://help.adobe.com/en_US/LiveCycle/9.5/supported_platforms.html (the
text to look for is ‘Versio...
Hi g5spark,Yes, in case you choose to upgrade, you'll have a downtime.
The downtime is required to take a consistent backup of the data
associated with your current LiveCycle system.This data will be used
during the upgrade process, hence, you must have a copy of it and it is
also required in the event you encounter an unexpected failure during
upgrade.However, this is the ONLY downtime required.In a LiveCycle
cluster, the global document storage (GDS) directory contents and the
database is shar...
Hi g5spark,There are specific advantages/disadvantages to each of the
options you have. I'm listing them below and I hope that would help you
make a decision.In case you choose to upgrade, you'll be reusing a lot
of stuff from your existing installation, global document storage (GDS)
directory contents and database being some of these.The benefit of
upgrade is:1) You'll NOT have to re-create your processes in LiveCycle
ES2.52) If you have configured an LDAP directory server, it will come
pre-con...
Hi Dave,The relevant information for configuring a JBoss server with MS
SQL 2005 can be found under
http://help.adobe.com/en_US/livecycle/8.2/prepareinstallsingle.pdfPlease
have a look at section 'Configuring SQL Server for Adobe-preconfigured
JBoss' on Page 64.Thanks,Hina
Hi Tanmay,There's no direct path to upgrade a LiveCycle 7.2.2
installation to LiveCycle ES2.You must either upgrade to LiveCycle ES or
LiveCycle ES Update 1 before upgrading to LiveCycle ES2.Let me know if
you need more information.Thanks,Hina
You can follow 'Upgrading' section of LiveCycle 9.0 documentation set @
http://help.adobe.com/en_US/livecycle/9.0/documentation.htmlto find out
how you can upgrade your existing LiveCycle server to LiveCycle 9.0
Hi,Are you still facing this issue?Did you run LCM with the same user
who installed it?Also, could you confirm that an anti-virus isn't
running on your system with on-access scan enabled that might be
preventing the LCM to delete this file?Thanks,Hina Rastogi
Hi Marcos,Could you please confirm if your MySQL service is running or
not? It is not running by default.Also, LiveCycle Configuration Manager
shows port#3306 by default, you should specify the port you have entered
while installing turnkey.Thanks and RegardsHina Rastogi
Hi,Can you try the following steps and re-attempt the upgrade?1) Go to
pre-upgrade state for your LiveCycle system (restore database, global
directory storage etc.)2) From your ES2 SP2 installation delete the
following folders. a) /configurationManager/export
b) /configurationManager/log c) /configurationManager/working3) Re-attempt upgradeLet me know if it
works for you.Thanks,Hina Rastogi
Hi Albert,You can try exploring the partial turnkey option for JBoss. It
provides you a Windows service for your JBoss application server and
also helps you configure databases other than MySQL through LiveCycle
Configuration Manager. It is very similar to a pure JBoss Turnkey
installation.Thanks,Hina Rastogi
Hi Sunil,The 'working' directory is located inside /configurationManager folderPlease exit LiveCycle Configuration
Manager, clean this directory manually and try to re-launch
configuration manager.Also, make sure that no other application (for
example, anti virus etc) is accessing this directory while LiveCycle
Configuration Manager is running.Thanks,Hina
Hi Sunil,I believe you have already created and configured a domain on
the WebLogic server machine as per preparing to install guide for
cluster.Please follow the steps below and let me know if they work for
you:1) Exit LiveCycle Configuration Manager.2) Copy and paste the
ojdbc6.jar from your LiveCycle machine to
C:\bea\user_projects\domains\\lib folder on your WebLogic
server machine.3) Stop WebLogic Managed Server, Admin Server and Node
Manager (in that order).4) Start WeLogic Node Manager, A...
Hi Sunil,Could you confirm if the JDBC driver jar location that you are
specifying for both the fields is correct?In the screenshot attached, I
can see that for the field 'JDBC driver in application server lib' also
you have specified the location of driver jar in LiveCycle
installation.I assume this is a remote installation and the location
specified is not available on the server machine.Please specify the
correct location and re-attempt 'Test Connection'.Thanks,HinaN.B
Pressing F1 on the scre...
Hi,As I understand from the problem description the following two
LiveCycle components are not yet deployed/running on your system.a)
adobe-launchpad-assets.lcab) adobe-auditworkflow-dsc.jarFor the first
one, do the following steps:1) Login to LiveCycle administrative
console.2) Go to Services > Applications and Services > Application
Management3) Select adobe-launchpad-assets.lca (Name: Launchpad Assets
(system)) from the list and remove it.For the second one, do the
following steps:1) Launch L...
