Posts tagged "500"

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

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.

Reason

This issue can occur when you are attempting to access the services with a user account that does not exist in the LiveCycle database, especially when you are migrating applications from one LiveCycle environment to another (e.g. ES2 to ES3).  User accounts that were used by applications in the 1st environment will also need to be available in the 2nd environment.

Solution

Try whichever of the following solutions is applicable to your environment:  (contact your LiveCycle administrator if you do not have sufficient privileges)

1. Synchronize your LDAP server with LiveCycle (AdminUI > Settings > User Management > Domain Management > (Select LDAP Domain) > Sync Now)

2. Create the user manually in a local LiveCycle domain (AdminUI > Settings > User Management > Users and Groups > New User)

reference: (183300170)

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

LiveCycle ES2: UserM:GENERIC_WARNING: errorCode:12817 errorCodeHEX:0x3211 The user [user] is marked as Obsolete

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.common.errors.exception.IDPLoggedException] (Thread-21) 
UserM:GENERIC_WARNING: [Thread Hashcode: 1859008299] 
com.adobe.idp.common.errors.exception.IDPLoggedException| [AuthenticationManagerBean] 
errorCode:12817 errorCodeHEX:0x3211 message:The user <user> is marked as Obsolete

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

=========== Authentication failure detail report ==================
Scheme Type : Username/Password 
UserId : user 
Current Thread : ajp-0.0.0.0-11148-2
Following users were identified as per received authentication data. Details are (UserId, domain, oid)
     - user, DefaultDom, 7C5E5622-96A9-102F-AE67-00000XXXXXXX 
Following are the response details from various authProviders.
1 - com.adobe.idp.um.provider.authentication.LDAPAuthProviderImpl
- Authentication Failed : Exception stacktraces are avialable at TRACE level 
Messages collected for this AuthProvider are provided below
    - LDAP authentication failed for user [user] in Domain [corp.domain]
        - Unprocessed Continuation Reference(s)
2 - com.adobe.idp.um.provider.authentication.LocalAuthProviderImpl
- Authentication Failed : Exception stacktraces are avialable at TRACE level 
Messages collected for this AuthProvider are provided below
    - The user user is marked as Obsolete
    - No local user found with UserId [user] in Domain [DefaultDOM]

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.

Reason

This issue can occur when you are attempting to access the services with a user account that has been marked obsolete in the LiveCycle database.  This can occur if you have deleted this specific user from LDAP or from the local domain in LiveCycle.

If you have written applications depending on this user account then you will encounter the problem outlined above when running/calling those applications.

Solution

You could either re-create the user in your LDAP or local domain, or you can create a new user and then change your application to reference this new user rather than the obsolete user account.

reference: (183305926)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 5.5/10 (2 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)

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)