Posts in Category "Installation"

LiveCycle ES: support for LC ES in virtualized environments

Posted on January 14, 2011 by dmcmahon | Comments (0)

Information

 Virtualization technologies tested and supported by Adobe for LiveCycle ES include VMware ESX, IBM LPAR, and Solaris Zones. Microsoft Hyper-V is not supported.

VMware created the virtualization market in the x86 world. Their product offerings can be grouped under two buckets: hosted and bare-metal. Bare-metal virtualization offers better performance than hosted virtualization.

Hosted virtualization requires a “host” operating system which hosts other “guest” operating systems hat are contained in virtual machines.  A bare-metal virtualization platform is a bases operating system-like kernel called the hypervisor, usually with a management console that runs on top of the kernel. There is no host OS.

http://forums.adobe.com/message/2270201

You can find detailed information about installing/deploying LiveCycle ES and ES2 in virtualized environments under the following links, or by searching on adobe.com:

http://www.adobe.com/content/dam/Adobe/en/devnet/livecycle/pdfs/lces2_virtualized_environments.pdf

http://www.vmware.com/files/pdf/techpaper/Adobe_LiveCycle_ES_Deployment_on_VMware.pdf

http://blogs.adobe.com/livecycle/2009/02/solaris_10_zones_support.html

http://blogs.adobe.com/livecycle/2007/12/livecycle_quick_and_dirty_serv.html

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: ALC-UPG-040-000 UpgradeException: Invalid Join: process_instance

Posted on March 29, 2010 by dmcmahon | Comments (0)

Issue

When you upgrade your LiveCycle 7 environment to LiveCycle ES 8.2.1, the following exception may occur during the Migrate Essential Data step while running the LCM:

[2010-03-11 10:33:11,699], SEVERE, Thread-54, com.adobe.livecycle.upgrade.control.PhaseRunner, Aborting. Invocation of method 
[migrateCriticalData] failed for com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin. Caught 
com.adobe.livecycle.upgrade.UpgradeException, message: ALC-UPG-040-000: Internal error: ALC-UPG-040-000: 
Internal error: Invalid Join: process_instance
com.adobe.livecycle.upgrade.UpgradeException: ALC-UPG-040-000: Internal error: ALC-UPG-040-000: 
Internal error: Invalid Join: process_instance
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.execute(WorkflowUpgradePlugin.java:320)
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.migrateCriticalData(WorkflowUpgradePlugin.java:226)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
 at java.lang.reflect.Method.invoke(Method.java:585)
 at com.adobe.livecycle.upgrade.control.PhaseRunner.run(PhaseRunner.java:217)
 at java.lang.Thread.run(Thread.java:595)
Caused by: com.adobe.livecycle.upgrade.UpgradeException: ALC-UPG-040-000: Internal error: Invalid Join: process_instance
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.migrateWorkflow7Templates(WorkflowUpgradePlugin.java:392)
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.execute(WorkflowUpgradePlugin.java:314)
 ... 7 more
Caused by: java.lang.RuntimeException: Invalid Join: process_instance
 at com.adobe.pof.omapi.AbstractQueryCompoundExpression.addObjectFilter(AbstractQueryCompoundExpression.java:571)
 at com.adobe.pof.omapi.AbstractQueryCompoundExpression.addFilter(AbstractQueryCompoundExpression.java:325)
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.updateProcessInstanceWithServiceInfo(WorkflowUpgradePlugin.java:1368)
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.upgradeLC7ProcessTypeToService(WorkflowUpgradePlugin.java:487)
 at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.migrateWorkflow7Templates(WorkflowUpgradePlugin.java:386)
 ... 8 more
[2010-03-11 10:33:11,803], INFO, AWT-EventQueue-0, com.adobe.livecycle.upgrade.gui.UpgradePhaseDialog, ALC-UPG-040-000: 
Internal error: ALC-UPG-040-000: Internal error: ALC-UPG-040-000: Internal error: Invalid Join: process_instance

Additional information

Corruption in the LiveCycle ES database can cause this error.  The database can get corrupted if there were any manual modifications, or SQL statements run on the DB, or if you are using an external (not from Adobe) purge utility on the DB.

Solution

  1. Restore the database to a valid state before running the LCM.
  2. Make sure that there are no SQL queries running on the LiveCycle ES Database, before the LCM has run.

reference: (181485096/2526063)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: “ALC-UPG-040-005: Exception Migrating Workflow Tasks” Error while migrating the DB in LCM

Posted on December 17, 2009 by dmcmahon | Comments (1)

Issue

When migrating from a LC7 to a LC ES server, you may receive the following exception during the “Migrating Essential Data” step in LiveCycle Configuration Manager:

ALC-UPG-040-005: Exception Migrating Workflow Tasks: [97,571]
com.adobe.livecycle.upgrade.UpgradeException: ALC-UPG-040-000: Internal error: ALC-UPG-040-000: Internal error:
ALC-UPG-040-005: Exception Migrating Workflow Tasks: [97,571]
at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.execute(WorkflowUpgradePlugin.java:320)
at com.adobe.livecycle.upgrade.workflow.WorkflowUpgradePlugin.migrateCriticalData(WorkflowUpgradePlugin.java:226)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.adobe.livecycle.upgrade.control.PhaseRunner.run(PhaseRunner.java:217)
at java.lang.Thread.run(Thread.java:595)
Caused by: com.adobe.livecycle.upgrade.UpgradeException: ALC-UPG-040-000: Internal error:
ALC-UPG-040-005: Exception Migrating Workflow Tasks: [97,571]

Reason

This will occur when a task has been started by opening a form in Form Manager, but a process was never initiated, probably because the user just closed the form again without submitting. The task has no corresponding entry in the TB_ASSIGNMENT table in the DB.

Solution

The solution in this case is to delete the task entry manually from the database, as it does not affect any running processes. This is a very rare case and should not show up at all in most installations. Here is an SQL statement you can use to search for such tasks in the DB before running LCM.

_____________________________________________

select * from tb_task tsk where
not exists (select 1 from tb_assignment assign where assign.id=tsk.current_assignment_id) or ((tsk.process_instance_id > 0) and
not exists (select 1 from tb_process_instance proc where proc.id=tsk.process_instance_id)) or ((tsk.action_instance_id > 0) and
not exists (select 1 from tb_action_instance act where act.id=tsk.action_instance_id)) or
not exists (select 1 from edcprincipalentity ent where ent.id=tsk.create_user_id) or
not exists (select 1 from tb_form_data form where tsk.form_data_id=form.id)

_____________________________________________

reference: (180999333/2360548)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (1 vote cast)

LiveCycle ES: how to reset the administrator password for the LC server

Posted on October 2, 2009 by dmcmahon | Comments (0)

Issue

 If you wish to change the administrator’s password for the LiveCycle server you must do it manually in the database.

Reason

 The administrator’s password is the only password stored in the database table EDCPrincipalLocalAccountEntity.

Solution

 To select the correct record run this query:

SELECT uidstring, password, salt
FROM adobe.edcprincipallocalaccountentity A, adobe.edcprincipaluserentity B
WHERE A.refuserprincipalid = b.id AND b.uidstring = ‘administrator’;

The values in the salt and password field together constitute the password for the administrator account. On a sample installation where the password for the administrator account was “password” the password field was set to:

TXScDjEEQCzWccUMUdf8wijx/hE=

and the salt field was set to:

JNIBnmos3d0WE9W8oquFIQ==

To reset your password to “password” run this update command to update the two fields in the EDCPrincipalLocalAccountEntity table with the above values and you should be able to login.

UPDATE adobe.edcprincipallocalaccountentity, adobe.edcprincipaluserentity
SET password = ‘TXScDjEEQCzWccUMUdf8wijx/hE=’, salt = ‘JNIBnmos3d0WE9W8oquFIQ==’
WHERE adobe.edcprincipallocalaccountentity.refuserprincipalid = adobe.edcprincipaluserentity.id
AND adobe.edcprincipaluserentity.uidstring = ‘administrator’;

You may have to restart the application server for these changes to take affect.

Additional Information

This solution has been verified on a MySQL database with LiveCycle ES 8.0.  The database schema for later versions of LiveCycle ES (8.2.1, 9, 10 etc…), and for other Database types (Oracle, SQL Server) may differ, and may require modifications to the above SQL statements.

In some databases the “edcprincipallocalaccountentity” table does not exist, but is represented by the “edcprincipallocalaccount” table. The information in this technote is provided as-is and should be tested before applying it to a production database.  Performing a full backup of the database before applying any changes is recommended.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle7: “A system temporary table space with sufficient page size does not exist” error on DB2

Posted on September 5, 2009 by dmcmahon | Comments (0)

Issue

 If you are installing Workflow 7.2.2 onto a DB2 database you may encounter the following error during the bootstrapping process:

“A system temporary table space with sufficient page size does not exist”

Reason

 This is due to the “CREATE TEMPORARY TABLESPACE” command having failed when you created the LiveCycle Database.

Solution

 This can occur when the DB creation script is invalid, due to missing line breaks, or spaces.  Please consult the appropriate LC installation documentation for your version.  The script for LC7 is as follows:

CREATE TEMPORARY TABLESPACE ADOBE_TEMP_8K IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 8192 MANAGED BY SYSTEM USING (‘C:\DB2\ADOBE_TEMP’) EXTENTSIZE 32 PREFETCHSIZE 16 BUFFERPOOL BP8K;

CREATE REGULAR TABLESPACE ADOBE_DATA_8K IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 8192 MANAGED BY DATABASE USING (FILE’C:\DB2\ADOBE_DATA’1000) EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL BP8K;

 

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: ALC-LCM-999-022 error running LCM on a localized OS

Posted on September 5, 2009 by dmcmahon | Comments (0)

Issue

 If you are attempting to install LC ES on an Italian operating system, you may receive the following error trying to run LiveCycle Configuration Manager:

Error [ALC-LCM-999-022]

Failed on 'Stopping JBoss Service JBoss for Adobe LiveCycle ES v8.0'

Service shutdown failed for: JBoss for Adobe LiveCycle ES v8.0

Reason

 Installation on a localized OS is supported as long as it is one of the supported OS versions, however, localized operating systems have not been tested and you may encounter issues.

Solution

 Install on an English operating system if possible.  If you only have a localized OS, then proceed with the installation and report any issues to Adobe support.  We can provide patches as necessary to get LiveCycle running on the localized OS you are using.

reference: (1-48812420/1625939)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: ClassNotFoundException: org.jboss.web.jsf.integration.config.JBossJSFConfigureListener

Posted on September 5, 2009 by dmcmahon | Comments (0)

Issue

 If you have manually configured the JBoss4.2.x  application server and installed LiveCycle ES, you may receive the following exception when starting JBoss:

13:36:29,277 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
13:36:29,793 ERROR [[/]] Error configuring application listener of class 
org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
java.lang.ClassNotFoundException: org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
 at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1358)
 at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1204)
 at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3797)
 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4359)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

Reason

During the manual configuration of JBoss 4.2.x the documentation from prepareinstallsingle.pdf advises you to disable the JSF libraries contained in [appserver root]/server/all/deploy/jboss-web.deployer.  You must disable the JSF libraries, and also remove the related entries from the web.xml, otherwise the above excpetion will occur when starting JBoss.

Solution

Comment out or remove the following entries from [appserver root]/server/<config-name>/deploy/jboss-web.deployer/conf/web.xml:

<!-- Comment/Remove this -->
<!-- Configures JSF for a web application if thejavax.faces.webapp.FacesServlet is declared -->
<!-- in web.xml.-->
<!--
    <listener>
        <listener-class>org.jboss.web.jsf.integration.config.JBossJSFConfigureListener</listener-class>
    </listener>
-->

<!-- Comment/Remove this -->
<!-- Listens to all web app lifecycle events so that @PreDestroy can becalled on -->
<!-- JSF managed beans that go out of scope. You can comment this out if you-->
<!-- don't use JSF or you don't use annotations on your managed beans.-->
<!--
    <listener>
        <listener-class>com.sun.faces.application.WebappLifecycleListener</listenerclass>
    </listener>
-->

<!--
    <init-param>
        <description>JSF standard tlds</description>
        <param-name>tagLibJar0</param-name>
        <param-value>jsf-libs/jsf-impl.jar</param-value>
    </init-param>
-->
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle 7: “Directory Exception javax.servlet.jsp.JspException” accessing webservice portal

Posted on August 24, 2009 by dmcmahon | Comments (0)

Issue

When you try to access the web service portal in JBoss (http://localhost:8080/services/) using LiveCycle 7, you may receive the following error:

Web Service Directory Services
Directory Exception javax.servlet.jsp.JspException: 
An error occurred while evaluating custom action attribute "items" with value "${directoryBean.deployedServices}": 
An error occurred while getting property "deployedServices" from an instance of 
class com.adobe.workflow.service.WorkflowServiceDirectoryBean (java.lang.NullPointerException)

Solution

 Add the following lines to the service XML file: [appserver root]/server/all/conf/jboss-service.xml:

_____________________________________

<-- Isolate all ears in their own classloader space -->
<attribute name="Isolated">true</attribute>
<-- Enforce call by value to all remote interfaces -->
<attribute name="CallByValue">true</attribute>

_____________________________________

reference: (180009712)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: Command Line Interface (CLI) for installer and LCM language settings

Posted on July 14, 2009 by dmcmahon | Comments (0)

Issue

 The CLI tool for the LiveCycle installer and Configuration Manager is only supported in English.  You may notice errors in the output if you use the tool in any other language.  Some of the variables for host names may not be resolved in the localized output, or accented characters may not be displayed correctly as in the following screenshots:

French:

German:

It is possible to change the language for the LCM graphical user interface by changing the locale in Regional Settings, or by changing the LCM.lang property in the userValues.properties file found under:

[LiveCycleES root]/configurationManager/config/userValues.properties

Changing the language for the command-line interface however is not supported as it only works in English.

Solution

Ensure that you run the CLI tool on a machine with English regional settings, and change the LCM_lang property value to “en” in the LCM properties files found under: [LiveCycleES root]/configurationManager/config

Additional Information

Note: If you use the GUI version of LiveCycle Configuration Manager, and then chose to use the CLI version, you can use the property file created by the GUI version as the template for the CLI version property file.  When you run the [LiveCycleES root]/configurationManager/bin/ConfigurationManager.bat file, the userValuesForCLI.properties file is created in the [LiveCycleES root]/configurationManager/config directory. You can use this file as input for the LiveCycle Configuration Manager CLI.

You can find further information and a parameter appendix for the CLI tools in the installation guides for each platform:

http://www.adobe.com/support/documentation/en/livecycle/

reference: (181022950)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycleES: “The application has failed to start because omniDynamic403_rt.dll was not found”

Posted on May 10, 2009 by dmcmahon | Comments (1)

Issue

When you are attempting to perform a render operation in LiveCycle ES, you may receive the following error in Windows itself:

The application has failed to start because omniDynamic403_rt.dll was not found.
Re-installing the application may fix the problem.

You should then check the server log for any exceptions. You may see the following exception:

Service XMLFormService: Starting native process with command line
"D:\bea\user_projects\domains\lc_domain\null\adobe\lc_server\XMLFormService\bin\XMLForm.exe"
-MyPath D:\bea\user_projects\domains\lc_domain\null\adobe\lc_server\XMLFormService................
BMC024: Service XMLFormService: Process ProcessResource(name=XMLForm.exe,pid=0) terminated abnormally with error code {3}

This could also be accompanied with an ALC-WKS-007-040 error in workspace if you are attempting to render into the browser. You may also see another error code in the server log ALC-FRM-001-004, which indicates a problem with the XMLFormService, of FontManager service. You can check that both of these services are running in the admin console for LiveCycle.

Reason

The underlying cause of this is that the XMLFormService could not be found. This is due to the “null” entry in the path to the XMLFormService as seen in the exception above. This actually creates a “null” directory on your server’s file system, and will populate it with the native files. However at runtime it cannot interpret this “null” in the path, and so reports that it cannot find the XMLFormService.

Solution

You will have to modify your weblogic startup script to set the adobeidp.RootDirectory property.
1. stop your weblogic server and any admin server that might be running
2. find the setDomainEnv.cmd or setDomainEnv.sh script and search for JAVA_OPTIONS (this is usually at the end of the file)
3. you will need to add the following argument to the JAVA_OPTIONS:
-Dadobeidp.RootDirectory=<path to LiveCycle Domain>  (e.g. D:\bea\user_projects\domains\lc_domain)
4. save the file
5. restart your weblogic server

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: “DocumentBuilder returned is not DOM3 compliant, using Xerces’s DOM parser” warning

Posted on March 9, 2009 by dmcmahon | Comments (0)

Issue

After installing LiveCycle ES Update 1 SP2 with WebSphere 6.1 as the application server, you may observe the following warnings in the SystemOut.log:

[06.03.09 11:21:40:015 CET] 0000002d SAMLToken W com.adobe.idp.common.errors.Logger$LogConsumer run UserM:GENERIC_WARNING:
[Thread Hashcode: 1753770120] DocumentBuilder returned is not DOM3 compliant, using Xerces's DOM parser

[06.03.09 11:21:45:140 CET] 000000be Reference I org.apache.xml.security.signature.Reference verify
Verification successful for URI "#d143154d8548fe37c847df7490b054cc"

Reason

This warning message is logged if the XML parser available to LiveCycle ES is not DOM 3 compliant. This warning has been reported on some Websphere installations, but seems to have been resolved in the latest fixpacks from IBM.

Solution

Upgrade to the latest WebSphere fixpack.  You can suppress the warning in the log by setting the log level for com.adobe.idp.um.businesslogic.authentication.SAMLToken to “ERROR”.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle 7: disable “An active transaction should be present…” message from the WebSphere log output

Posted on February 2, 2009 by dmcmahon | Comments (0)

Issue

 If you are running LC7 products in the WebSphere application server you may notice the following message appearing repeatedly in the log file:

[21/09/07 15:40:24:562 IST] 72d82e0c ConnectionMan W J2CA0075W: 
An active transaction should be present while processing method allocateMCWrapper.
[21/09/07 15:40:24:578 IST] 72d82e0c ConnectionMan W J2CA0075W: 
An active transaction should be present while processing method initializeForUOW.

You may want to disable this message, to prevent it appearing in the log.

Reason

This message can be ignored as it is merely an informational message.  This message can appear so much, that it starts to fill up the log and makes it very difficult to see any actual problems in the log.

Solution

To simply suppress the messages from being logged to the SystemOut.log, do the following:

Open the <WEBSPHERE_HOME>\properties\j2c.properties file in a text editor.  Find the following block:

<!-- The cm-properties are in a comment block. Uncomment to use -->
 <!--
 <cm-properties>
     <manageCachedHandles>false</manageCachedHandles>
     <logMissingTranContext>true</logMissingTranContext>
 </cm-properties>
 -->

Remove the comments and change the true to false.  It should look like the following once complete:

<!-- The cm-properties are in a comment block. Uncomment to use -->
 <cm-properties>
 <manageCachedHandles>false</manageCachedHandles>
     <logMissingTranContext>false</logMissingTranContext>
 </cm-properties>

___________________________________
reference: (1-25647507)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle 7: MissingResourceException in FontManagerService during LiveCycle startup

Posted on January 28, 2009 by dmcmahon | Comments (0)

Issue

You may encounter problems starting the application server with LC7 installed where it can take up to an hour to start, or you may get the following exceptions:

FontManagerService: Exception while attempting to read initialization properties from com/adobe/config/FontManagerService-init

java.util.MissingResourceException: Can’t find bundle for base name com/adobe/config/FontManagerService-init, locale de_DE

Reason

These problems occur when using JDK version 1.4.2_10.  This JDK version has backwards compatibility issues and is therefore not supported for LC7.

Solution

 Use a different supported JDK version and this will resolve the issues.

reference: (1-21393042)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle 7: LCMerror101 trying to run ConfigurationManager

Posted on January 26, 2009 by dmcmahon | Comments (0)

Issue

If you have successfully installed Workflow, FormServer or FormManager and then run LiveCycle Configuration Manager (LCM), you may receive the following error:

Configuration Manager Errors

Error Code:LCMerror101

Message: Livecycle modules could not be copied to working directory.

Reason

 This is due to the version of the JDK being used: JDK 1.4.2_10.  This JDK version has broken backwards compatibility, and so is not supported for LC7.

Solution

 Use a different JDK version and this will resolve the problem.

reference: (1-21322849)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)