Posts tagged error message

Process ID value comes up as “-1″

- Ameeth Palla, Technical Account Manager @ Adobe

Issue: Recently I worked on an issue for a customer who reported a problem with Process ID value becoming “-1″.

Scenario: Customer had a process where they were naming the output file using a combination of “Process ID + time-stamp”. They reported that the value of the output filename was coming up as “-1+time-stamp” for some files.

Trouble-shooting: Upon reviewing their process, the design was – A long-lived process takes an input from a watched-folder end-point and checks to see if the incoming file is a TIFF, MS Word document or XML data file. If the input was any other format other than XML, then these files would be converted to PDF’s and the output file would be named as “Process-ID+timestamp” and stored in a directory. If the input file was an XML data file then it would be sent to a sub-process and merged with a form-template and flattened and then named as “Process-ID+timestamp” and stored in the same output directory. By running some tests, we could see that the file name would come out as “-1+timestamp” only when the input file was an XML data file.

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle ES3: Authentication failed for user (Scheme – Username/Password) Reason: Username or password is incorrect

- David McMahon, Sr. Technical Account Manager @ Adobe

Issue

If you are accessing any LiveCycle services and have problems getting a response, you may notice the following warning in the server logs:

WARN  [com.adobe.idp.um.businesslogic.authentication.AuthenticationManagerBean] (Thread-21) 
Authentication failed for user [user] (Scheme - Username/Password) Reason: Username or password is incorrect. 
Refer to debug level logs for category com.adobe.idp.um.businesslogic.authentication for further details
 

If you enable DEBUG level logging you will see the following DEBUG information in the log:

DEBUG [com.adobe.idp.common.errors.exception.IDPLoggedException] (Thread-21)
UserM:: [Thread Hashcode: 1796127844] com.adobe.idp.common.errors.exception.IDPLoggedException|
[com.adobe.idp.um.businesslogic.authentication.AuthenticationManagerBean] errorCode:12803 errorCodeHEX:0x3203 message:
Authentication failed for user [user] (Scheme - Username/Password) Reason: Username or password is incorrect
 =========== Authentication failure detail report ================== 
 Scheme Type : Username/Password 
 UserId : user 
 Current Thread : ajp-0.0.0.0-11148-8 
 Following are the response details from various authProviders.  
 1 - com.adobe.idp.um.provider.authentication.LocalAuthProviderImpl - 
 Authentication Failed : Exception stacktraces are avialable at TRACE level 
 Messages collected for this AuthProvider are provided below
      - No local user found with UserId [user] in Domain [DefaultDom]
      - No local user found with UserId [user] in Domain [EDC_SPECIAL]
These warnings in the log may also be accompanied by an Error 500 if you are attempting to call the LC services through a browser/web application.

---

Read the complete post at Adobe LiveCycle Blog.

Access Denied while activating ‘Adobe LiveCycle Connector’ feature on SharePoint 2010

- Pankaj Gakhar,  Software Engineer @ Adobe

After installing Adobe LiveCycle Connector Web Part on SharePoint 2010, you may encounter an error Access Denied while activating Adobe LiveCycle Connector feature on a SharePoint Site Collection. This issue occurs due to a new security feature implemented in SharePoint 2010. You can refer Microsoft KB 2564009 for details.

You can check SharePoint logs for details of the exception. The logs would look similar to:

w3wp.exe (0x0F48) 0x190C    SharePoint Foundation Feature Infrastructure  88jm    High     Feature receiver assembly ‘AdobeLiveCycleConnector, Version=1.0.0.0, Culture=neutral, PublicKeyToken=6720cbcc342f4ca4′, class ‘LiveCycleInterop.LiveCycleFeatureReceiver’, method ‘FeatureActivated’ for feature ’33a7c6b5-4e62-44aa-bf99-62d283de683a’ threw an exception: System.Security.SecurityException: Access denied.     at Microsoft.SharePoint.Administration.SPWebService.set_RemoteAdministratorAccessDenied(Boolean value)     at LiveCycleInterop.LiveCycleFeatureReceiver.addToWebConfig(SPFeatureReceiverProperties properties)     at LiveCycleInterop.LiveCycleFeatureReceiver.FeatureActivated(SPFeatureReceiverProperties properties)     at Microsoft.SharePoint.SPFeature.DoActivationCallout(Boolean fActivate, Boolean fForce)  The Zone of the assembly that failed was:  MyComputer    fda8f095-7baa-47e4-b400-740259ad8ff5

---

Read the complete post at Adobe LiveCycle Blog.

Dealing with – Tried to assign more tasks [xxx] than the maximum tasks per transaction threshold [110]. – error message

Ameeth Palla, Technical Account Manager @ Adobe

I had recently worked on an issue where the process had an ‘Assign Mutiple Tasks’ step in it. It was assigning the same task to many users (>110). During runtime, when this step was executed, it would fail with the below error message and stack trace:

Tried to assign more tasks [xxx] than the maximum tasks per transaction threshold [110].

---

Read the complete post at Adobe LiveCycle Blog.

LiveCycle ES2 Connector for Microsoft SharePoint – Upload Large File sizes

- Abhijit Ghosh, LiveCycle TRT Engineer @ Adobe

We were recently working on a customer scenario who was facing issues with uploading documents greater than 50 MB on the Microsoft Sharepoint Server 2010. There are a couple of things that one needs to keep in mind when dealing with large file sizes.

---

Read the complete post at Adobe LiveCycle Blog.

Go to Top