We have this error comes up randomly in our TEST environment. Sometimes it comes up immediately when a user logs in. Other times the user will be kicked out and the error appears. How I do begin to isolate this?
********************************
The error is a System Error and reads: "A system error has occured. Please contact your adminstrator and provide the folowing information:
The error message is a System Error and reads:
A System Error has occurred.
Please contact your system administrator and provide the following information:
Windowmenu: f_get_nextid
Object: f_get_nextid
Objectevent: f_get_nextid
Line: 10
Error Code: 20
Error Text: Database command not successfully prepared at line 10 in function f_get_nextid of object f_get_nextid
Dropping and recreating logins using the Tessitura Security module is a required step in the process of moving/copying a database from one server to another as outlined in the "Moving a Database" documentation and is touched upon in this related Tessitura help topic: https://www.tessituranetwork.com/Help_System/Content/Security/Dropping%20and%20Creating%20Logins.htm
The process of dropping logins cycles through the active user logins in the Tessitura/Impresario database and removes the "Database Login" as seen in Tessitura Security from SQL server (and this process can be used to drop a single login). The process of creating the logins cycles through the active user logins in the Tessitura/Impresario database to create logins in SQL server that matches each user's Database Login's Login Name and Login Password (and this process can be used to create a single login). So essentially this process synchronizes the user logins in the Tessitura database with the user logins in SQL Server. If a user login exists in your source database which is then copied to a destination server where the SQL login does not exist, the login for Tessitura will fail. If a user login does already exist on the destination SQL server but the Database Login or Database Password in the copied Impresario database does not match these values in SQL Server of if the user login's database mapping or database role membership is incorrect on the destination server, the SQL login will not succeed.
Bob
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Martin Keen Sent: Monday, August 4, 2014 8:45 PM To: Robert Bell Subject: RE: [Tessitura Technical Forum] f_get_nextid
Hi Bob,
This is a very common occurrence in our non-LIVE environments - we have an environment called MODEL which is refreshed on a nightly basis from that nights backup of LIVE and is an environment we use a lot for some of our (very resource) hungry reports.
Whilst the solution you post works, are you able to tell me what causes this issue? Curiously, it appears to affect particular users on a (reasonably) regular basis.
Martin
From: Bob Bell <bounce-bobbell2200@tessituranetwork.com> Sent: 6/8/2010 5:35:10 PM
This error is usually solved by dropping and recreating the affected user's login in the test Security module. If all user logins were not dropped on the test system before a live to test copy or restore and recreated after the copy/restore is complete, this may result for one or more users.
From: Tessitura Technical Forum [mailto:forums-technical@tessituranetwork.com] On Behalf Of Randall Mitchell Sent: Tuesday, June 08, 2010 6:26 PM To: Robert Bell Subject: [Tessitura Technical Forum] f_get_nextid
This message was sent automatically to you by www.tessituranetwork.com because you subscribed to the Tessitura Technical Forum. You may reply to this message to post to the Technical forum or visit the site to search, read and post to the forums. In the interest of keeping the forum posts from becoming cluttered, we encourage you to delete previous message text from your reply before sending. Thank you!
Bob,
Thanks for this reply. The curious thing is that it only affects one or two users and on a very regular basis. We tried getting their user dropped and recreated in the LIVE environment but the next day, they were again unable to log into MODEL.
As it only affects very few (maybe 1 or 2) users, I'm assuming (yes, I know!) that the dropping and recreating process is being followed.