OnBase 18 upgrade error

[Dale_Meyer]

Error I'm receiving in Diagnostics Console on the AppServer:

Failed to generate key for 'WkstEntryNum'.
The UPDATE permission was denied on the object 'maxnumkeys', database 'Database', schema 'hsi'.

I've verified that the permission is correct on the table in the database.

[AdamShaneHyland · Accepted solution]

Hi Dale,

These type of issues has been noticed since we switch to using ADO.NET in order to connect to the database whereas previous versions of the software prior to OnBase 18 used ODBC connections.  With ADO.NET, you can either specify the user connecting to the database in the connection string or user integrated security which would use the account running the Application Server.  

My assumption is that the user which is configured within the connection string doesn't have the necessary permissions to make the mentioned database change.  You can review your connection string for your Application Server by using the Web Application Management Console.

Best wishes.

[AdamShaneHyland]

As the discussion mentions, the OnBase Thick Client doesn't use an ADO.NET connection and is based on an ODBC.  The OnBase Thick Client uses a hard coded users (hsi) in order to connect to the database. 

With the Core using the connection string (and therefore any client which connects to the Application Server - e.g. the Unity Client, OnBase Studio, Web Server, etc), my assumption is that if you were to hard code the hsi user, you wouldn't have any issues.  Since you are using integrated security, you are using the account which is configured at the Application Pool Identity (or Impersonation level) account for access to the database.  What you are seeing is that the Application Server is unable to make those specific requests because the account used for integrated security doesn't have the necessary permissions to the database.  Likely you would see the same error in the Database Server log files.

[Christian_Jones · Accepted solution]

Hi Dale,

What OnBase clients are you trying to login to use? 

i.e., OnBase Thick/Config? Unity? Briefcase? Studio? Outlook Integration? Web? and of those, are you trying to access via a machine that has IIS installed on it?

[Dale_Meyer]

Unity throws the error primarily. Unity won't log on at all, neither does Studio. Thick client not affected.

[Christian_Jones]

Studio - you should be able to login via the AppServer URL, if you're trying via local? Otherwise, recommend re-install of OnBase Studio to rename the ADO.NET connection display name as OnBase[environment]Studio and then when logging into Studio, select "OnBase[environment]Studio" for datasource - on the local machine. If this makes sense.

We found that while we may name the ADO.NET connection string anything we want as Hyland stated, it was best to name it after the module that is being installed/used. Distribution Service, Unity Scheduler, Studio, etc.

Unity Client does not need ADO.NET connect string where it is installed... it goes through the AppServer... so thinking then that there is an issue with ADO.NET connection string on your AppServer, which is where Adam Shane appeared to be going in his reply.

First line of support is probably your best option with the connection issues.