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 · 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.

[Dale_Meyer]

I've redone the ADO .NETConnection string and  still produces the same error, even after a AppServer restart. An additional error is showing now: The UPDATE permission was denied on the object 'maxnumkeys', database 'OnBase18Prod', schema 'hsi'.  Both seem to be related.

[Dale_Meyer]

I should add I'm using integrated security.

[Ryan_Wakefield]

We have found an issue with the ADO.NET connections as well. Granted we are using the Thick Client, but I would try switching it to a hard coded instead of integrated. We currently have an SCR for our issue, but this might at least give you a workaround to go with.