Posts tagged "error"

LiveCycle ES: CONTENT INTEGRITY ERROR using Content Services

Issue

If you are working with Content Services ES you may notice the following exception in the log files:

ERROR [org.alfresco.repo.admin.ConfigurationChecker] CONTENT INTEGRITY ERROR: System content not found in content store.
ERROR [org.alfresco.repo.admin.ConfigurationChecker] Ensure that the 'dir.root' property is pointing to the correct data location.
ERROR [org.springframework.web.context.ContextLoader] Context initialization failed
org.alfresco.error.AlfrescoRuntimeException: Ensure that the 'dir.root' property is pointing to the correct data location.
 at org.alfresco.repo.admin.ConfigurationChecker.check(ConfigurationChecker.java:312)
 at org.alfresco.repo.admin.ConfigurationChecker.access$000(ConfigurationChecker.java:72)
    at org.alfresco.repo.admin.ConfigurationChecker$1.execute(ConfigurationChecker.java:178)
    at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:278)
    at org.alfresco.repo.transaction.RetryingTransactionHelper.doInTransaction(RetryingTransactionHelper.java:227)
    at org.alfresco.repo.admin.ConfigurationChecker.onBootstrap(ConfigurationChecker.java:182)
    at org.alfresco.util.AbstractLifecycleBean.onApplicationEvent(AbstractLifecycleBean.java:62)

Reason

This exception will occur when the data in the database is no longer synchronized with the data in the file system data store.  Both must remain synchronized at all times, otherwise data loss will occur.  It is part of the maintenance tasks to ensure that the following items are backed up regularly at the same time:

  • GDS document store (file system/network location)
  • Content Services data store (file system/network location)
  • Database schema

This information is described in detail with instructions in the LiveCycle Administration guide:

http://help.adobe.com/en_US/livecycle/8.2/admin_guide.pdf#page=129

If the data in the Content Services data store is no longer synchronized with the data in the database, then this exception is thrown, as data integrity has been compromised.  This can happen if another server/user has access to the file data store and makes changes, or if the data in the database is modified by another user/application.

It can also occur while performing configuration changes to your LiveCycle installation if the deployment of these changes quits unexpectedly leaving the database and local data stores out-of-synch.

Solution

To resolve this situation you will need to restore the components above from the last valid configuration.

If this is a fresh installation of LC content services, then you can drop the Content Services tables in the database, delete any content in the data store, and re-try the deployment. The following technote describes which tables you need to drop (i.e. it gives you the SQL commands to run):

http://kb2.adobe.com/cps/405/kb405444.html

The Content Services tables in the database get created while the adobe-contentservices.ear file is being deployed (not during database initialization).  Once you have cleaned the DB and the data store, simply re-start the application server with the content services EAR file, and the tables will be re-created.

reference: (182870106)

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

LiveCycle Designer: XFAImageService error importing a Photoshop JPG into an XFA form

Issue

 If you are trying to import JPEG images produced with Adobe Photoshop into an XFA-based form in LiveCycle Designer, then you may notice the following error in the warning palette:

Error reading JPeg file : JFIF supports only 1 and 3 component streams. 

XFAImageService: Image cannot be resolved for node: StaticImage1

Solutions

 1. Use Photoshop version 6 or less to produce the JPEG images

2. Re-save the JPEG images from Photoshop using the “Save for Web…” option in the File menu

3. Re-save the JPEG images using Paint in windows, or any other image editing tool which does not add the preview information described below

Additional information

 This error occurs when Photoshop 7 or greater was used to create the JPEG images.  This is due to a change in the JPEG format produced with Photoshop 7 and greater, which now includes a thumbnail preview of the JPEG image included in the JPEG profile.  Such profile information does conform to the JPEG/JFIF specification, however some applications like web browsers, or in this case, LiveCycle Designer cannot handle the preview data correctly.

Further information can be found below:

http://photo.net/ps7-problems.html

reference: (182368249)

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

Configuring Adobe Reader help files for offline use

Description

If you are using Adobe Reader 9 or greater, you may have noticed that the help files are now only available online with an active internet connection to adobe.com.  In Adobe Reader 8 the help files were available within the product itself on your local machine and you did not need an internet connection.

If you do not have an active internet connection on the computers where Adobe Reader 9 and greater is installed, then you will not be able to access the help documentation, and will receive a 404 error in the browser.  This can occur for large enterprises where some machines are not allowed to have an open internet connection for security and data protection reasons.

Suggestions

There are 2 different solutions or workarounds to this issue:

1. Create a local PDF file containing the Help content.

You can reference this PDF file locally, or put the PDF file in a central location where all of your users can access it, i.e. on a network location, or on your internal web server. Here are the example PDF files for Adobe Reader 9 in English and German:

Adobe_Reader_9.0_Help.pdf (English)

Adobe_Reader_9.0_Hilfe.pdf (German)

Note: To create PDF files of the Adobe Reader 9 Help for other languages, go to the Help page for your language on Adobe.com (use a computer where you have Adobe Acrobat installed). Use the Acrobat Web capture plug-in to export the page as a PDF. Then, use Acrobat to fix the links in the PDF file and correct any structural issues.

For Reader X the help documentation is now available online in PDF format, so you can just download the PDF file from: http://help.adobe.com/en_US/reader/using/reader_X_help.pdf.

2. Re-construct the online Help documentation for Adobe Reader within your organization’s intranet environment.

You can deploy the Adobe Reader help pages on your internal web server where everyone in your organization can access them using a browser.

Download the .zip file below and extract it, maintaining the folder structure. Deploy the files to an internal web server. These Help files are available in English and German.

Adobe_Reader_9.0_HTML_Help.zip

Addendum: Use Customization Wizard to tune the Adobe Reader installation.

In an enterprise environment you may want to configure Adobe Reader for all users to point to the custom Help documentation automatically. You can use the script in this solution to disable the standard Help menu item in Adobe Reader, and replace it with a custom Help menu item pointing to the help documentation from solution 1 or 2 above.

For solution 1 (local PDF file): create a custom folder in your Adobe Reader installation using Customization Wizard (e.g. C:\Program Files\Adobe\Reader <version>\Help), and put the local PDF file in there. Place the WinReader_Local_Help.js file into the Javascripts folder in Customization Wizard (C:\Program Files\Adobe\Reader <version>\Reader\Javascripts).

For solution 2 (HTML help files): after putting the Reader HTML files on your local intranet server, place the WinReader_Intranet_Help.js file into the Javascripts folder in Customization Wizard (C:\Program Files\Adobe\Reader <version>\Reader\Javascripts).

Now when Adobe Reader is launched on the user’s computer the help menu link will be replaced with your custom link. There may be a short delay before the link is updated after starting Adobe Reader.

reference: (181774134)

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

LiveCycle ES: warning in server log when passivating document

Issue

A Form Guide stitches a PDF from multiple XDP fragments and then returns the PDF to the process in LiveCycle ES 8.2.1 or 9. When you submit this Form Guide, a warning appears in the server log:

[12/18/09 15:34:08:003 EST] 0000015a SystemOut
 O XDP form1.xdp,form2.xdp,form3.xdp,form4.xdp,form5.xdp,form6.xdp
[12/18/09 15:34:08:004 EST] 0000015a SystemOut O OPS form1.xdp
[12/18/09 15:34:08:234 EST] 0000015a AdobeCacheImp W com.adobe.repository.cache.AdobeCacheImpl put Document error while passivating document [<document state=”passive” senderVersion=”3″ persistent=”false” senderPersistent=”false” passivated=”true” senderPassivated=”true” deserialized=”true” senderHostId=”127.0.0.1/10.101.158.145″ callbackId=”0″ senderCallbackId=”4228″ callbackRef=”com.adobe.idp._IDocumentCallbackStub:

Solution

This warning is an informational message from the repository cache and can be ignored. In the ADEP platform (ES3) Adobe will downgrade this warning to an INFO or FINE level message, so it doesn’t appear in the logs.

reference: (181308950/2523516)

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

LiveCycle ES: Error 500 in the AdminUI when searching for tasks

Issue

When you search for tasks in the AdminUI (Adminui > Services > LiveCycle Process Management ES > Task Search), the following HTTP error occurs:

Error 500--Internal Server Error 

From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:

10.5.1 500 Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

Reason

This error occurs when there is information missing from the database entry for a certain task in the returned list of results. For example, if the PROCESS_NAME value is empty or null for a task in the TB_TASK table. This issue can happen if you use custom code to access the database directly and modify it. It can also occur if you are running a purge utility not supplied by Adobe on the database.

Adobe plans to fix this issue in ES2 SP2 and in ES3.

Solution

This error is a product issue in LiveCycle ES and there are patches available for 8.2.1.2 and 8.2.1.3.  You should contact enterprise support if you require one of these patches.  The issue has been fixed in ES2 SP2 and later versions.

 reference: (181590010/2633888)

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

LiveCycle ES: ALC-PDG-001-001 Invocation error.

Issue

 If you are using the API for PDFG ES to convert documents to PDF on a localized operating system as outlined in the documentation, you may encounter the following error message:

"Error OCCURRED: ALC-PDG-001-001 Invocation error."

It may also say that the Job settings cannot be found, or are invalid.  Conversion through the PDFG web interface works successfully.

You may be using code similar to:

HtmlToPdfResult result = new HtmlToPdfResult();
result = new GeneratePdfServiceClient(factory).htmlToPDF(
    inputFileName,
    "Standard",
    "No Security",
    null,
    null);

Reason

The names of the settings files for file type (“Standard”), and security settings (“No Security”) as mentioned in the documentation, may have been localized, which explains why the server cannot find the files at run time.

Solution

 Use the localized names for these settings files in your code.  You can check the names for these settings files in the AdminUI > Services > LiveCycle PDFG ES > File Type Settings.

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

Workspace ES: Error 500: Null input provided: Accepted-Language null

Issue

 If you are trying to access Workspace in the internet browser you may receive the following error:

An error occurred determining the locale.

Error 500: Null input provided: Accepted-Language null

This may be accompanied by the following exception in the server.log:

[2/5/08 16:35:59:984 EST] 0000003f WebApp E [Servlet Error]-[determine-locale]: 
java.lang.IllegalArgumentException: Null input provided: Accept-Language null
at com.ibm.ws.genericbnf.impl.BNFHeadersImpl.appendHeader(BNFHeadersImpl.java:470)
at com.ibm.ws.webcontainer.channel.WCCResponseImpl.addHeader(WCCResponseImpl.java:149)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.addField(SRTServletResponse.java:288)
at com.ibm.ws.webcontainer.srt.SRTServletResponse.addHeader(SRTServletResponse.java:1534)
at javax.servlet.http.HttpServletResponseWrapper.addHeader(HttpServletResponseWrapper.java:202)
at com.ibm.ws.cache.servlet.CacheProxyResponse.addHeader(CacheProxyResponse.java:421)
at com.adobe.workspace.users.DetermineLocale.doGet(DetermineLocale.java:37)

Reason

 The workspace client code uses the browser language settings to control the locale.  Unfortunately, on the client there is no way to ask the browser for that setting.  So as a workaround, the HTML wrapper requests the determine-locale servlet from the server.  The determine-locale servlet simply returns the Accept-Language header that the browser sent.  So the string returned by determine-locale completely depends on the settings and capabilities of the client you hit that servlet from.  In this case, the browser should be sending the ‘Accept-Language’ headers so either the browser did not send this information, or it was stripped along the way.

Solution

 This has been fixed in Lc ES 8.2.1, to correctly handle the situtation where no ‘Accept-Language’ information is received from the browser/server.

reference: (1708975)

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

LiveCycle ReaderExtensions: Error 400 trying to apply usage rights to a PDF

Issue

 If you are trying to apply rights to a PDF document with ReaderExtensions 7.0, you may receive the following error in the web browser:

Error 400: Applying User Rights to the document ‘SAE_V0.9Static.pdf’ failed:
‘com.adobe.document.pdf.PDFOperationFailure: com/adobe/document/pdf/PDFOperationFailure:1.0′.

and the following exception in the log file:

[26.08.05 09:21:03:361 CEST] 500fe7b1 Logger
E com.adobe.document.PDFManipulation document does not have certifying signature
[26.08.05 09:21:19:622 CEST] 50e8a7b1 Logger
E com.adobe.document.PDFManipulation an unknown exception caused the call

This error can occur on all application servers.

Reasons

1. This is due to an incompatibility when using Designer 6 to design documents to be processed with ARES 7.  This issue has also been seen using some language versions of Designer.

2. This issue could also occur if you are trying to apply rights to a password-protected PDF document, and you dont supply the password when applying the rights.

Solutions

1. If you use Designer 7 or greater then the documents can be correctly extended with LCRE 7.

2. If you supply the password for the PDF when applying the rights, the error will not occur.

reference: (1-15848413)

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

LiveCycle ReaderExtensions: “Error 473: Credential permissions are invalid”

Issue

 If you are trying to ReaderExtend a PDF in LCRE 7 either in the web interface, or using the API, you may receive the following error:

Error 473: Credential permissions are invalid...

Reason

 This error is related to the credential permissions provided with LCRE.  There is a .pfx credential file which must be configured with LCRE to allow you to ReaderExtend documents.  This credential is essentially used to certify the PDF when applying the rights, to prevent unauthorized changes to the PDF once distributed.  You need to provide an alias/password for this credential file when installing LCRE.

Often the wrong alias/password combination is used for this credential when installing LCRE.

Solution

 Make sure you use the alias/password provided with the credential file.

Other possible causes:

1) using the wrong JDK or using JDK 1.4.2_10 which is not supported

2) ares-roles.properties, ares-users.properties not correctly mapping users in

C:\Program Files\Adobe\LiveCycle\ReaderExtensions\jboss-3.2.5\server\all\conf

 reference: (1-16246910)

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

LiveCycle PolicyServer7: MySQL error 1005 restoring mysqldump of EDC database

Issue

 If you are attempting to restore a backup copy (mysqldump) of the EDC database into MySQL, you may encounter a MySQL error 1005.

Reason

 This is linked to INNODB and the foreign keys.

Solution

 You should follow the steps below to backup and restore the EDC database successfully on JBoss/MySQL:

A/ Backup

To fully backup the current state of a policy server, you need to do the following:

  1. While the APS service is running, export the configuration settings from the UI by going to Configuration -> Manual Configuration -> Export
  2. While the APS service is either running or shut down, backup the login-config.xml from the jboss\server\all\conf directory (and any other JBoss configuration files that you might have manually modified)
  3. While the APS service is shut down, backup the database using mysqldump (from the bin directory in mysql) by issuing the following command on a command prompt: mysqldump –user=root –password edc > backup.sql

B/ Restoration

Assuming that you are restoring on a clean machine, here are the steps you would follow:

  1. Install Policy Server and logon as Admin
  2. Import the APS configuration settings which you saved in step a) above
  3. Shut down the service and edit/restore the jboss\server\all\conf\login-config.xml so that the <application-policyname="UsernamePwd_Auth_Search"> section matches the one you were using previously
  4. Logon to mysql (mysql -u root -p) and issue the following commands:  drop database edc;        create database edc;        grant ALL on edc.* to root@localhost;

Note: The last step shouldn’t really be necessary, as the root user should already have all rights on all databases.  These commands clear the whole database content.

       5. edit the backup.sql which you saved in 3) above, and add the following line at the beginning:

  SET foreign_key_checks=0;

Note: If you don’t do this, you will get error 1005 / errno 150 from mySQL when restoring the table – this is a known issue with foreign_keys and mysqldump, and can be easily addressed with the above line.

       6. run the following command to restore all the SQL data:

     mysql -u root -p edc < backup.sql

This should not give you any error.

7. restart the APS service. Once APS is started, you should be back to the state from the backup, and all the policies should work exactly as before.

After running these exact steps, you should be able to open a PDF with an existing policy even after you have removed the server and its database completely.

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

Acrobat/Reader 7: install with MSI failed with SQL errors

Issue

 If you are trying to install Acrobat/Reader 7.0.7 using the MSI you may receive the following error:

Action start 12:35:52: INSTALL.
DEBUG: Error 2235: Database: . Column ‘Action’ not present or ambiguous in SQL query:

SELECT `Action`,NULL,`Condition` FROM `InstallExecuteSequence` WHERE `Sequence` > 0
ORDER BY `Sequence`

Internal Error 2235. , Action, SELECT `Action`,NULL,`Condition` FROM `InstallExecuteSequence`
WHERE `Sequence` > 0 ORDER BY `Sequence`Action ended 12:36:50: INSTALL. Return value 3.

Reason

 This is a problem with the InstallShield configuration.  Such issues should be raised directly with InstallShield support, or in their forums.

Solution

 This problem is described here:

http://kb.acresso.com/selfservice/microsites/search.do?cmd=displayKC&docType=kc&externalId=Q107132&sliceId=

reference: (1-28110668)

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

LiveCycle PDFG7: Error 1009 trying to start application server

Issue

 If you have installed PDF Generator 7, you may receive the following error when trying to start the application server service:

Error 1009

Reason

 You must use the same user to install MS Word and PDFG, and this user must be the same user account used to start the application server service.

Solution

 Re-install MS Word and PDFG using the same user account (this should be an Administrative user), and then change the LogOn properties for the application server service in the Control Panel to use this account to start the service.

reference: (1-32085976)

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

LiveCycle PDFG7: LCMerror 9007 trying to start the application server after installing PDFG

Issue

 If you have installed PDFG7 you may encounter the following error when the application server is trying to start:

LCMerror 9007 Failed to start turnkey service JBOSS

Trying to start the application server service manually results in this error:

Error 1029 The service did not start due to a logon failure.

Reason

  During the installation, you would have been asked to enter the username and password for PDFG so that you can install the product.  This should be the same user which installed the application server and should be an administrator with sufficient privileges to install new software and run processes.

Solution

First check that you are logged in as an administrator.  Then you should check in Control Panel -> Services, and open the Properties for the application server service.

In here you will find the properties for LogOn for the service, and here you must enter the Administrator logon details.

Additional Information

 After resolving this issue you may receive error 1053, which says that the service did not respond in the allocated time.  You can ignore this error as the application server just takes a long time to reply, but it does start successfully after some delay.

reference: (1-23596767)

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

LiveCycle PDFG7: Error Code 1015: This file type is not supported

Issue

 If you are using PDFG7 to convert HTML files to PDF using the Convert PDF function you may receive the error message:

Error Code: 1015

Error Message: This file type is not supported.

Reason

This is the expected behaviour.  When you enter a physical HTML file in the browser Create PDF servlet, then it will be sent to Distiller, but Distiller does not understand HTML files.

PDF Generator 7 can convert the following content to PDF:

  • PostScript and Encapsulated PostScript (EPS)
  • Image formats (JPG, JPG 2000, GIF, BMP, TIFF, PSD)
  • Microsoft Word, Microsoft Excel, and Microsoft PowerPoint (DOC, XLS, PPT)
  • Microsoft Project (MPP)
  • Corel WordPerfect
  • Plain text and rich text (TXT, RTF)
  • Web (HTML)
  • AutoCad (DWG)
  • Microsoft Visio (VSD)

Solution

When you want to convert an HTML file, then you must enter the URL with “http://…” or “https://…” and convert it using the web page converter function. Then it will be sent to Acrobat to be conveted with Web Capture.  HTML files reside on a webserver and so it is expected that they are referenced through the URL, not as a local .HTML file.

If you really need to work with local .HTML files, then you could open the .HTML file using Microsoft Word, and save it as a .doc for example.  PDFG can then convert this .doc file without problems.

reference: (1-25037774)

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