Author Archive: dmcmahon

LiveCycle Designer ES2: Designer hangs after renaming the binding file

Issue

While editing an XDP in certain versions of LiveCycle Designer ES2, if the data binding file on disk is renamed, designer registers this change and offers to reload the current form.  If you then click Save, it again offers to reload the current form.  After clicking “Yes” to reload the form, you may notice that Designer hangs.

Method:
1. Download test_files.zip
2. Extract the 2 files to the same local folder
3. Open XDP in Designer
4. Rename the binding XML file in your local folder
5. You will see a dialog in Designer asking to reload the form, click Yes
6. Click Save
7. Again the dialog in Designer asking to reload the form, click Yes

Result:
Designer hangs

Solution

This is an issue in certain versions of LiveCycle Designer ES2 and has been addressed in later versions, including Designer ES3.  If you require a quickfix for this issue in LiveCycle Designer ES2 you should contact the enterprise support team.

reference: (183667516/3337854)

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

LiveCycle Designer ES2: Multiple pages imported to a single Master Page causing overlap

Issue

If you are importing a multi-page PDF into LiveCycle Designer ES2 to create a form using the “…Flowable Layout > Place Content In > Master Pages” method you may notice that the content of the pages are placed in a single Master page causing overlap.

Solution

This is an issue in LiveCycle Designer ES2 and has been addressed in later versions, including Designer ES3.  If you require a quickfix for this issue in LiveCycle Designer 9 you should contact the enterprise support team.

reference: (183629724/3337453)

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

LiveCycle Designer ES2: Corners appear unexpectedly when clicking on hidden rectangle object

Issue

If you are editing older XDP forms from LiveCycle Designer 7.1, or 8,  in Designer ES2, and you have hidden rectangle objects in the form design, you may notice that when selecting these hidden objects in the hierarchy, visible corners suddenly appear on these objects.  These hidden rectangle objects are created automatically when importing Word documents into Designer to create a form.

Reason

The problem is caused by the import from doc/PDF where the edge property for the rectangle is created and set to hidden, but no corners property is created.  When you create a new form in Designer (without importing), the edge and corner properties for a rectangle are always created together and the presence for both usually kept in synch.
It seems that when Designer finds a rectangle without a corner property it creates it automatically with visible corners.

Rectangle in XML after import from word:
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
               </rectangle>

Rectangle in XML after selecting it on canvas:
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
                  <corner radius=”5.08mm”/>
               </rectangle>

Rectangle in XML after manually fixing it in Designer (XML Source or Object Palette):
               <rectangle>
                  <edge thickness=”0pt” presence=”hidden”/>
                  <corner radius=”5.08mm” presence=”hidden”/>
               </rectangle>

Workaround

You can change the line style to “solid” and back to “none”, and then the corners property in XML is synchronized (presence=hidden) with the line edge property as expected.

Solution

This is an issue in LiveCycle Designer ES2 and will be fixed in Designer 10 and later versions.  If you require a quickfix for Designer 9 you should contact the enterprise support team.

The logic has now been changed, so that when Designer creates the corner property, it checks if the relevant edge is hidden, and sets the presence for the corners to match.

reference: (183589079/3322036)

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

LiveCycle ES: AccessDeniedException: Access Denied. The system is currently in read-only mode.

Issue

If you are using LiveCycle Content Services you may notice the following error message in the server logs when starting the server:

00:05:55,646 ERROR [org.alfresco.service.descriptor.DescriptorService] Error installing embedded license
org.alfresco.service.license.LicenseException: Failed to save license
                at org.alfresco.repo.descriptor.RepositoryDescriptorDAOImpl.updateLicenseKey(RepositoryDescriptorDAOImpl.java:294)
                at org.alfresco.enterprise.license.AlfrescoLicenseManager.setLicenseKey(AlfrescoLicenseManager.java:220)

Caused by: org.alfresco.service.cmr.repository.ContentIOException: Failed to create directory for file storage: \\share\Adobe\lccs_data\contentstore\2012\10\26\0\5
                at org.alfresco.repo.content.filestore.FileContentStore.makeDirectory(FileContentStore.java:288)
                at org.alfresco.repo.content.filestore.FileContentStore.createNewFile(FileContentStore.java:234)
                at org.alfresco.repo.content.filestore.FileContentStore.createNewFile(FileContentStore.java:202)
                at org.alfresco.repo.content.filestore.FileContentStore.getWriterInternal(FileContentStore.java:478)
                at org.alfresco.repo.content.AbstractContentStore.getWriter(AbstractContentStore.java:242)
                at org.alfresco.repo.content.RoutingContentService.getWriter(RoutingContentService.java:402)
                at org.alfresco.repo.descriptor.RepositoryDescriptorDAOImpl.updateLicenseKey(RepositoryDescriptorDAOImpl.java:285)
                … 15 more
03:00:00,020 ERROR [org.quartz.core.JobRunShell] Job DEFAULT.indexBackupJobDetail threw an unhandled Exception:
org.alfresco.repo.security.permissions.AccessDeniedException: Access Denied.  The system is currently in read-only mode.

Reason

This error can occur when the user account that started the application server (JBoss/WebSphere/Weblogic) no longer has “write” permissions on the lccs_data shared directory used by content services (alfresco).

During startup sequence, Alfresco tries to create files in lccs_data shared directory, and if it cannot, it starts content services in read only mode.

Solution

Verify the user rights on the shared lccs_data directory, and try to create a folder/file manually.  Restarting the LiveCycle server will usually resolve the problem, but you should investigate the root cause why the user permissions are being lost in your environment.

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

LiveCycle Designer ES2: Unable to delete default value in rich-text fields

Issue

After updating to LiveCycle Designer ES2 QF4 (9.0.0.2.20110401.1.827986), you may notice that you are no longer able to delete the default value in rich-text fields.  It is possible to edit the value, but when you delete it, the value will re-appear in the field after refreshing.  This only happens for rich-text fields and not standard text fields.

Solution

This is an issue in LiveCycle Designer 9.5 QF4 and has been addressed in later versions, including Designer 10.  If you require a quickfix for this issue in LiveCycle Designer 9 you should contact the enterprise support team.

Workaround

You can delete the default value by opening the XML Source tab and removing the value manually.

reference: (183571067/3318438)

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

CQ5.5: SlingException running workflowreport.html

Issue

If you are using the workflow report under /etc/reports/workflowreport.html it may return with an error 500 in the browser and the following exception:

org.apache.sling.api.SlingException:
    at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.handleJspExceptionInternal(JspServletWrapper.java:686)
    at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:603)
    at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:528)
    at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:447)

Caused by: org.apache.sling.api.SlingException: An exception occurred processing JSP page /libs/cq/workflow/components/report/report.jsp at line 132
… 74 more
Caused by: java.lang.NullPointerException
    at org.apache.jsp.libs.cq.workflow.components.report.report_jsp._jspService(report_jsp.java:309)
    at org.apache.sling.scripting.jsp.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
    at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
    at org.apache.sling.scripting.jsp.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:497)
… 97 more

Reason

This problem can occur when a workflow model is deleted, but that workflow model had been used to start multiple processes, and therefore workflow statistics for that model exist.  This is a product issue and has been addressed in CQ5.6.

Workaround

As a workaround you can use the attached overlay for
/apps/cq/workflow/components/report/report.jsp
instead of the problematic
/libs/cq/workflow/components/report/report.jsp

workflow_report_overlay_40332-1.0.zip

The workaround will resolve the NullPointerException and the workflow report will display as expected, but there are still some unresolved exceptions in the server log. These will be resolved with the full product fix.

reference: (40332/CQ5-23798)

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

CQ5.5 SP2.1: IllegalArgumentException: Servlet must not be null

Issue

If you are updating your CQ5.5 installation to SP2.1 on an application server you may notice the following exception in the logs:

12.11.2012 03:20:21.683 *ERROR* [CQSE HTTP Service] org.apache.felix.http.whiteboard Failed to register servlet
java.lang.IllegalArgumentException: Servlet must not be null
    at org.apache.felix.http.base.internal.service.HttpServiceImpl.registerServlet(HttpServiceImpl.java:88)
    at org.apache.felix.http.whiteboard.internal.manager.ServletMapping.register(ServletMapping.java:54)
    at org.apache.felix.http.whiteboard.internal.manager.ExtenderManager.registerAll(ExtenderManager.java:235)
    at org.apache.felix.http.whiteboard.internal.manager.ExtenderManager.setHttpService(ExtenderManager.java:195)
    at org.apache.felix.http.whiteboard.internal.tracker.HttpServiceTracker.added(HttpServiceTracker.java:37)

After restarting the server you may notice the following errors in the log:

12.11.2012 03:22:14.621 *ERROR* [Thread-1] org.apache.sling.servlets.resolver.internal.SlingServletResolver bindServlet: Unexpected problem initializing component com.day.cq.opensocial.gadgets.servlet.ConcatProxyServlet com.google.inject.ProvisionException: Guice provision errors:
1) Error injecting method, java.lang.IllegalStateException: Servlet already initialized
    at org.apache.shindig.gadgets.servlet.ConcatProxyServlet.setConcatUriManager(ConcatProxyServlet.java:90)
    while locating com.day.cq.opensocial.gadgets.servlet.ConcatProxyServlet
Caused by: java.lang.IllegalStateException: Servlet already initialized
    at com.google.common.base.Preconditions.checkState(Preconditions.java:145)
    at org.apache.shindig.common.servlet.InjectedServlet.checkInitialized(InjectedServlet.java:59)
    at org.apache.shindig.gadgets.servlet.ConcatProxyServlet.setConcatUriManager(ConcatProxyServlet.java:90)

12.11.2012 03:23:10.151 *ERROR* [FelixStartLevel] com.day.cq.wcm.cq-wcm-mobile-core [com.day.cq.wcm.mobile.core.impl.redirect.RedirectFilter] The bindStats method has thrown an exception (java.lang.NullPointerException) java.lang.NullPointerException
    at com.day.cq.wcm.mobile.core.impl.redirect.RedirectFilter.bindStats(RedirectFilter.java:173)
    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:597)
    at org.apache.felix.scr.impl.helper.BaseMethod.invokeMethod(BaseMethod.java:227)
    at org.apache.felix.scr.impl.helper.BaseMethod.access$500(BaseMethod.java:38)
    at org.apache.felix.scr.impl.helper.BaseMethod$Resolved.invoke(BaseMethod.java:591)

Reason

These errors occur due to the files for the CQ Servlet Engine which are still deployed.  These files should not be included when deploying CQ to an application server, and there is a step in the SP2.1 release notes describing this.

Solution

  1. Go to /crx/explorer and open the Content Explorer
  2. Go to /libs/system/install, delete the cqse-httpservice-4.1.32.jar node and save your changes
  3. Restart the instance

These steps are listed in the release notes for SP2.1 when deploying to an application server:

http://dev.day.com/docs/en/cq/current/release_notes_service_pack_2.html

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

CQ5: “LDAPException: error result (4); Sizelimit exceeded” when synchronizing users

Issue

If you are using an LDAP connection with your CQ server you may notice that the LDAP users are not imported correctly to CQ with a warning similar to the following in the error.log:

09.11.2012 10:22:57.624 *WARN* POST /system/console/jmx/com.adobe.granite.ldap…DTools/op/syncAllUsers/ HTTP/1.1 com.day.crx.security.ldap.principals.LDAPPrincipalProvider Error finding user * com.day.crx.security.ldap.LDAPRepositoryException: LDAP error: com.day.ldap.LDAPException: error result (4); Sizelimit exceeded
        at com.day.crx.security.ldap.principals.LDAPPrincipalProvider.findUser(LDAPPrincipalProvider.java:396)
        at com.day.crx.security.ldap.principals.LDAPPrincipalProvider.findPrincipals(LDAPPrincipalProvider.java:553)
        at com.day.crx.security.ldap.LDAPUserSync.syncAllUsers(LDAPUserSync.java:182)
        at com.day.crx.security.ldap.LDAPSynchronization$Directory.syncAllUsers(LDAPSynchronization.java:283)
        at com.day.crx.security.ldap.jmx.LDAPUserMBean.syncAllUsers(LDAPUserMBean.java:117)
        at com.day.crx.security.ldap.jmx.LDAPUserMBean.invoke(LDAPUserMBean.java:187)


09.11.2012 10:22:57.625 *INFO* POST /system/console/jmx/com.adobe.granite.ldap…Tools/op/syncAllUsers/ HTTP/1.1] com.day.crx.security.ldap.LDAPUserSync LDAP synchronization: 0 of 0 users synchronized in 0 seconds

Reason

This error is caused by your LDAP settings. In ActiveDirectory (AD), for example, there is a maxpagesize limit set to 1000 by default. This is the maximum number of results returned for any given LDAP query, including CQ user synchronization.  For more information see: http://support.microsoft.com/kb/315071?wa=wsignin1.0

Solution

You have a few options to avoid this problem:

  1. ask your LDAP administrator to increase the maxpagesize on your LDAP server
  2. use filters in your LDAP queries to reduce the number of LDAP entries returned so that you do not hit this limit

reference: (40240/CRX-3043)

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

CQ5.5: When to restart CQ after installing a service pack

Issue

If you are installing a service pack (SP) on top of CQ5.5 you will see a dialog recommending to restart the instance after you have run the SP installation:

Do not restart the instance at this point, as the contents of the service pack are still being extracted and installed in the background.  Restarting at this point could result in unknown problems, and you may have to repeat the SP installation.

Solutions

You can monitor the log output in error.log and wait until the log no longer has new “BundleEvent STARTED” entries, before restarting the instance.  This usually takes 2 – 5 minutes depending on server specifications.

Monitoring log output may not be a good solution for large enterprise organisations which may have many CQ instances to update, and may need to use some kind of automated install script or process documentation.  In this case, you can either add a pause to the installation documentation (e.g. 15 or 30 minutes), or use a script to check for installation completion as described under 2 below.

1. Monitor the log output to figure out when to restart

The release notes for SP2.1 do contain instructions relating to this process (http://dev.day.com/docs/en/cq/current/release_notes_service_pack_2.html):

Quickstart Install Process

  1. Login to Package Share and download SP2 package: cq-service-pack-5.5.2.zip
  2. Back in Package Manager – Install package
  3. After the package install is done – the PackageManager tells you to restart. DO NOT RESTART. The actual install of the package only starts now in background, given that the packages have been placed in /install folders. The best way to follow the process of the install is to tail the error.log
    The background install starts with “com.day.jcr.vault.packaging.impl.ZipVaultPackage Extracting day/cq550/update:cq-update-pkg:5.5.8″ and stops with bundles been restarted – best seen by “BundleEvent STARTED” log entries.
  4. After the error.log goes quiet with “BundleEvent STARTED” messages
  5. Restart the instance
  6. The Welcome Screen should now show the updated Version String: Adobe CQ, Version 5.5.0.20120220 Service Pack 2

2.  Use a script to automatically check for installation completion

You can use the script below which polls the server to check when the SP contents have been extracted, and then waits another few minutes for the relevant bundles to be started.  You can use the script on its’ own, or you could integrate it into existing scripts which you use to automatically install the CQ servicepack.

1. use a script similar to the following (designer for CQ5.5 SP2.1, you may need to adjust the cq-update-pkg version for other service packs)

count=0
res=1
until [ $res -eq 0 ]
do
    curl -u admin:admin -D- http://<cq_server_hostname>/etc/packages/day/cq550/update/cq-update-pkg-5.5.10.zip/jcr:content/vlt:definition/lastUnpacked.json 2>/dev/null | head -1 | grep -q “HTTP/1.1 200″
    res=$?
    if [ $((count++ % 10)) -eq 0 ]
     then
     echo “Waiting for service pack installation to finish…”
    fi
    sleep 1
done
sleep 300
echo “Service pack installation complete. You can restart the instance now.”

2. start the script in a terminal
3. install SP2.1
4. check the script output and await the completion message

5. restart the instance

reference: (39810/CQ5-22648)

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

LiveCycle ES3 SP1: Gemfire errors in server log after installing patches on top of 10.0.2

Issue

If you are using TCP locators in a LiveCycle cluster with ES3 (10.0.2) and have installed a service pack or patches on top of this version, you may notice some errors in the server log similar to the following:

com.adobe.livecycle.cache.CacheRuntimeException: Error loading cache configuration
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.getCacheContainer(GemfireCacheAdapter.java:164)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.createRootRegion(GemfireCacheAdapter.java:853)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.init(GemfireCacheAdapter.java:218)
at com.adobe.livecycle.cache.adapter.GemfireCacheAdapter.<init>(GemfireCacheAdapter.java:207)
at com.adobe.livecycle.cache.adapter.CacheAdapterFactory.getCache(CacheAdapterFactory.java:103)

Caused by: com.gemstone.gemfire.SystemConnectException: Attempt to connect to distributed system timed out

If you have a UDP-based cluster caching mechanism, you are not affected by this issue.

Reason

This issue occurs when the Gemfire version on the server is different from the Gemfire version used by the TCP locators.  Gemfire.jar and GemFireVersion.properties are delivered in two different places in the LC installation – 1. Core EAR 2. /lib/caching directory.

Gemfire version 6.5.1.17 was used for LC ES3 (10.0.2).  To address some known issues a new Gemfire version (6.5.1.35) was used in later versions and patches.  This newer Gemfire version was used for the Core EAR, but unfortunately not included for updating the caching directory.

To verify the issue, compare the Gemfire version in the GFLocator.log file for your TCP Locator with the Gemfire version in the Gemfire logs for your application server at the following location:

  • JBoss: <adobe_temp_dir>/adobejb_<server_name>/caching/Gemfire.log
  • Weblogic: <adobe_temp_dir>/adobewl_<hostname>/caching/Gemfire.log
  • WebSphere: <adobe_temp_dir>/adobews_*/caching/Gemfire.log

You will find that Gemfire on the LiveCycle server has a higher version.

Solution

This issue has been addressed in SP2 and later patch versions.

Note: the patch installer will only update the default caching directory (<lc_install_dir>/lib/caching) on the machine where LC is installed.  If you are running LC on various machines, and/or use custom caching directories, you will need to update the 2 Gemfire files for your TCP locators manually.  All TCP locators need to be restarted before starting LC servers.

Workaround

For existing patches you can use the following workaround to fix the issue on your LiveCycle installation.

  1. Stop the LiveCycle server(s).
  2. Stop the TCP Locator(s).
  3. Go to <LC_INSTALL_DIR>/deploy folder.
  4. Open adobe-core-<appserver_name>.ear.
  5. Go to TCP locator installation directory. Typically the default location is <LC_INSTALL_DIR>/lib/caching.
  6. gemfire.jar and GemFireVersion.properties can be found here.
  7. Replace the two files above in the TCP locator with the same files from the core ear.
  8. Repeat the replacement procedure (steps 5 – 7) for each TCP locator.
  9. Start TCP Locator(s).
  10. Start LiveCycle server(s) in the Cluster.

Verify the Gemfire versions in GFLocator.log and Gemfire.log files. You should see the same Gemfire version in both files.

reference: (183615151/3327651)

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

Acrobat 10.1.4: Acrobat/Reader hangs while scanning

Issue

If you are scanning documents with Acrobat/Reader 10.1.4 using any mode (Grayscale/Color/BW),  Acrobat/Reader may hang when scanning is about to complete.

Reason

This is an issue in the 10.1.4 update and will be addressed in future versions.  It is also being discussed in our forums: http://forums.adobe.com/thread/1050323?start=0&tstart=0

Solution

Install the patch for Acrobat and Reader 10.1.4 (Windows only).

  • Log in to your Windows computer as an Administrator.
  • Click the following link to download the patch file: AdobeAcrobatReaderPatch10.1.4_3314564.zip
  • When prompted “Do you want to open or save this file?,” click Open.
  • Extract the file using a ZIP tool to a location on your local computer.
  • Double-click the AdobeAcrobatReaderPatch10.1.4_3314564.exe file to begin the update.
  • When a prompt notifies you that the update is complete, restart your computer.

_______________________________________________________________________________________________

 Install the patch for Acrobat and Reader 10.1.4 in silent mode (Windows only).
  • Log in to your Windows computer as an Administrator.
  • Click the following link to download the patch file: AdobeAcrobatReaderPatch10.1.4_3314564.zip
  • When prompted “Do you want to open or save this file?,” click Open.
  • Extract the file.
  • Open the command prompt “As Administrator.”
  • Type the path to the patch file executable, and add the -silent flag on the command line. For example:
    AdobeAcrobatReaderPatch10.1.4_3314564.exe -silent
    Silent mode suppresses all dialog boxes so you do not get a message indicating that the update is complete. The executable creates a log file “AcroPatchApplication1014.log” in the temp directory (%temp%).
  • When the update is complete, restart the computer.

reference: (3314564)

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

Acrobat XI: new tab-stop feature available for rich-text fields

Information

With the latest release of Adobe Acrobat/Reader XI there is a new feature available for structuring text in rich-text fields in XFA-based forms.  You can now add/modify tab-stops in rich-text fields using new UI components.  Adding tab-stops in rich-text fields allows for better formatting and table-like structuring of the text, which is a much requested feature from customers and users.

Instructions

You download the sample file tabstops_richtext_field_dyn.pdf to see how this feature works.

1. Open the sample file in Acrobat/Reader XI.

2. Place the cursor in the large rich-text field.

3. Press CTRL+E on the keyboard to bring up the Form Field Text Properties toolbar.

4. Click the button “More…”

5. You will see the new Tabs dialog where you can create/modify the tabs in the field.

6. From here you can create/modify/delete the defined tab-stops, and change the alignment (Left, Right, Center, Decimal), or the position.

Notes

You can now also use the key combination CTRL+TAB on the keyboard to tab between tab-stops in the rich-text field.

The measurement units for the tab stops are inherited from the units defined in the Preferences (Edit > Preferences > Units & Guides > Page & Ruler Units):

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

CQ5: new page/site buttons disabled in WCM siteadmin

Issue

If you are using WCM siteadmin and wish to create a new page/site using the available buttons, they may appear disabled so that you are unable to click on them.  Firstly, you should check your permissions for these actions and/or check with an administrator or admin account.  If these problems persist it may be related to an issue in your repository structure.

Reason

These buttons can also be disabled if there is an invalid Page node in the /content tree.  A cq:Page node must have a child named jcr:content of type cq:PageContent, otherwise it is invalid and can lead to this issue.  The root /content node is not of type cq:Page and therefore does not require a jcr:content child of type cq:PageContent, but every other Page node below /content should have this structure.

It seems that if the invalid node is a top-level page/site in the content tree (e.g. /content/geometrixx) then it will affect the site actions for all other top-level nodes, and other nodes in that specific tree.
If the invalid node is a sub node (e.g. /content/geometrixx/en/services), then it seems to only affect the site actions for that level in that tree.

Such invalid nodes can appear in the tree if they were created outside of WCM (i.e. using CRXDE, or Content Explorer), or by importing a package containing such invalid nodes.

Solution

Check your content tree for such invalid page nodes, and repair the nodes as required, by creating a jcr:content child node of type cq:PageContent.

reference: (37890)

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

LiveCycle Designer ES2: Word (version XP or onwards) could not be found on the machine

Issue

If you are using LiveCycle Designer ES2 to import Microsoft Word documents from MS Word 2010 or later, you may receive the following error

Word (version XP or onwards) could not be found on the machine

Reason

This error occurs because LC Designer ES2 does not recognise the installation folder for Microsoft Word 2010 or later versions.  LiveCycle Designer ES2 was released before these versions existed and therefore the installation folders were not known/recognised.

Solution

This issue has been fixed in LiveCycle Designer ES3 and last cumulative QuickFixes (QF) for Designer ES2.  Ensure you are using the latest QF for Designer ES2, or request the latest from your support representative.

If you require an urgent fix for this issue you can make the following change in the registry:

Note: we cannot provide support for any problems that may arise as a result of modifying the registry.  Only an experienced user or an administrator should attempt this, and a full registry backup should be performed before making changes.

1. For 32-bit Windows:

  • Create the following path in the registry:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\12.0\Word\InstallRoot
  • Create a new string value named Path with value C:\Program Files\Microsoft Office\Office14\

2. For 64-bit Windows

  • Create the following path in the registry:
    • HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Office\12.0\Word\InstallRoot
  • Create a new string value named Path with value C:\Program Files (x86)\Microsoft Office\Office14\

You should check the installation folder used in the Path value exists and contains WINWORD.EXE.  You will need to restart LiveCycle Designer for the changes to take effect.

Additional information

This issue is also being discussed in the forums:

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

reference: (183608560/2751566)

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

LiveCycle Designer ES2: Unable to save old XDPs with external data binding option

Issue

If you are attempting to save an XDP file in LiveCycle Designer ES2, created with an earlier version of Designer (i.e. 7, 7.1 or ES), then it can occur that the Save process never completes, and you must kill the Designer process manually in Task Manager.  If you analyse the files on your local disk, you will notice some tmp files with large file sizes.

Reason

This issue is related to the Data Binding option Allow binding to data not defined by the default data connection.  For some forms that contain data connections, Designer ES2 can get stuck in an endless loop while saving the XDP to an intermediary tmp file.  You will see the tmp file will contain a huge number of repeated entries related to the DataDescription similar to the following:

<DATACONNECTION xmlns:dd=”http://ns.adobe.com/data-description/” dd:additions=”$template(DATACONNECTION)”/>

Solution

This issue has been fixed in LiveCycle Designer ES3 and later cumulative QuickFixes for Designer ES2.  You should ensure you are using the latest QF for Designer ES2, or contact your support representative.

Workaround

Removing the data connection will allow the file to be saved, and also disabling the option in the form properties Allow binding to data not defined by the default data connection.  Also putting the sample XML data/schema file used to create the data connection into the same folder as the XDP, opening the XDP, refreshing the Data connection, will then allow to save properly.

reference: (183464630/3296440)

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