The above message is in the event viewer for every repository we have (running RIO) so have over 15 Repsoitories. I'm not certain what it means...the users can get into the system with the exception of one Repository which we're getting a Database 9008 error which we're researching as well.
Question
Question
Database statement execution error encountered. Session ID: ; Dialog ID: ; Repository: 'WorkforceDevelopment'; CLI routine: SysLogin; Message: Failed to retrieve error information!; SQL Statement: ''; SQL variable: ''; SQL State: .
Replies
Hey Daryl,
Do you know what version of Laserfiche the customer is using? This sounds like an old bug that was fixed several years ago. I'd recommend you check out this KB article and see if it helps at all.
In addition to Brett's advice, has the SQL Server been restarted recently? I've seen Support cases reference similar errors when the SQL Server was restarted and the LF Server service was not. In those cases a restart of the LF Server service cleared up the issues.
Version 9.1.1
No, SQL wasn't restarted, however, we did end up rebooting both the SQL Server and the Laserfiche Server and that seemed to clear up our issue. Going to pay close attention to see if the above errors show back up in the Event Viewer.
I just had this issue today while running a large group of files on OCR:
Database statement execution error encountered. Session ID: 29; Dialog ID: 3254699; Repository: 'MartinezUnified'; CLI routine: SysTrusteeGetInfo; Message: [Microsoft][SQL Native Client]TCP Provider: An existing connection was forcibly closed by the remote host.
; SQL Statement: 'select trustee_name, isuser, trustee_flags, privs, uif, auditmask, descrip, readonly, password, salt, last_pwchange, last_login, last_logout, bad_logins, temp_pass from trustee left outer join account_security on trustee.sid = account_security.sid left outer join user_login on trustee.sid = user_login.sid where trustee_id = :trustee_id<int>'; SQL variable: ''; SQL State: 08S01.
Always fails after about 300 or so documents OCRed, then I have to go in and select where I left off. The client also has 9.1.1
I'm going to update their server to 10.1 today.
I had the same issue while doing generate pages and OCR after it. It was a small document 27 pages
Database statement execution error encountered. Session ID: ; Dialog ID: ; Repository: 'database'; CLI routine: SysLoginTrusted; Message: Failed to retrieve error information!; SQL Statement: ''; SQL variable: ''; SQL State: .
I wanted to update this post since updating the clients server to 10.1 and running large OCR groups I was still encountering it failing after a random amount of OCRs. They are at the end of what was needed to OCR but this did cause the process to take weeks more than it should have due to it not running while we thought it was.