000014851 - AxM - MSSQL 2005 error: SQLException : Code:208;TextInvalid object name 'NEXT_KEY' when trying to start eserver

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 21, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000014851
Applies ToRSA Access Manager 6.x
Microsoft Windows 2003
Microsoft SQL Server 2005 Datastore
IssueAxM - MSSQL 2005 error: SQLException : Code:208;TextInvalid object name 'NEXT_KEY' when trying to start eserver

When the eserver is in debug mode the eservers standard output log shows the following error:

2009/10/06 14:43:44:826 [*] [main (sirrus.da.sql.util.SQLExceptionHelper.getErrorMessage)] - Database Exception Message : SQLException : Code:208;TextInvalid object name 'NEXT_KEY'.

Cause

NEXT_KEY is an mssql table used to track and allocate IDs when new mssql users are added via AxM apis (such as admingui).  AxM will read this table (which contains a single entry which is the last available ID number used), and on eserver startup will increment the current table value by 1000.   On shutdown of the eserver, the last used ID number will be written to the table.  If the NEXT_KEY table ownership is changed, permissions are removed or the table is recreated and lost its dependency information, the eserver can become unable to communicate to the NEXT_KEY table and will throw this error.

To obtain more detailed information from mssql itself on exactly what is wrong with the table, set up mssql detail logging.  To do so, see this Microsoft technical article:
http://support.microsoft.com/kb/199037

ResolutionInsure that the AxM account as specified in the sql,conf has sys admin rights to the NEXT_KEY table.  The error "SQLException : Code 208" indicates the table owner does not have rights to connect to and modify the table.  This will prevent the eserver from starting.
Legacy Article IDa47853

Attachments

    Outcomes