Intermittent user authentication failed errors for SQL clients.

SQL clients are unable to be authenticated.

  • Sep 1, 2018
  • Knowledge

Title
Intermittent user authentication failed errors for SQL clients.
URL Name
Intermittent-user-authentication-failed-errors-for-SQL-clients
Article Number
000153278
Environment
Product: OpenEdge Version: 10.x, 11.x OS: All supported platforms Other: SQL
Question/Problem Description
SQL connections via CyberQuery intermittently encounter authorization errors.
Issue occurs intermittently.
Has been occurring for a very long period of time.
Typically clients do not receive an error message that they are aware of.
On one occasion the client received the following error: Error opening domain file eueepd.pub.VD_MSTR@gdcusqad10:50203: Progress error (DATABASE): Access denied(Authorization failure).
Multiple SQL clients are logging within seconds of each other.
Steps to Reproduce
Clarifying Information
Users that experience this issue are identified as SQL Only users in the _User Table.
These are the only two user accounts that make SQL connections to the database.
Issue appears to resolve itself.
Validated that permissions on $DLC/bin/_* are set appropriately.
Clients that intermittently receive the error are batch processes that read data from the database.
Error Message
(-----) Authentication service: user authentication failed for cyberq - The user account does not exist Also received this error once: (-----) Authentication service: user authentication failed for cyberq - General error detected in the PAM library
Defect Number
Enhancement Number
Cause
CyberQuery is locking records.
Resolution
Set the isolation level on the SQL client to be read uncommitted.
Workaround
Try changing the client/server ratio to be 1:1.  One SQL client per SQL Server process.

Try changing the -SQLLockWaitTimeout from 5 to 10 or more and see if that changes the behavior.

See if this issue can be duplicated in a test environment. That way if we need to provide a debug module or enable enhanced logging, we could do it in a non-production environment.
Notes
Keyword Phrase
Last Modified Date
9/1/2018 11:20 PM
OpenEdge DeploymentOpenEdge ArchitectureOpenEdge DevelopmentOpenEdge General DiscussionsOpenEdge Pro2OpenEdge RDBMS

Files(0)

Drop Files

    Was this article helpful?

    Related Articles

    Disclaimer

    The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

    Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.