You are viewing limited content. For full access, please sign in.

Question

Question

Unable to Upgrade Repository

asked on October 23, 2021

Summary: Attempting to migrate & upgrade from Laserfiche United version 8.3 to Laserfiche RIO 10.4

  • Everything is moving to new server(s), as well as being upgraded.  
  • I've had a test environment in place for awhile and had no issues with the original upgrade/migration process into a "test" RIO repository.  
  • Current "production" environment is all LF 8.3 components running on a single server (Windows Server 2008 R2) with the database residing on a separate SQL Server 2012 instance.
  • Target environment includes LFDS and has other LF components distributed on multiple Windows Server 2019 servers with the target database(s) on a SQL Server 2019 instance with all DBs currently running under Compatibility Level 110 (SQL 2012).
  • The RIO Laserfiche Service is running under a domain account which has db_owner permissions on the database to be upgraded.

 

Based on the success of the initial test migration/upgrade etc. I had expected this to be a simple process this time around.  Unfortunately that is not the case and I had to cancel our migration this weekend.

After registering the repository in the Admin Console I get a set of 5 messages (1 info, 4 error) in the Admin event log. I've attached the messages (named in order of appearance).

In addition to attempting the upgrade the database after restoring it to the target SQL 2019 db server, I've tried to upgrade it in place on the existing SQL 2012 server.  Both were unsuccessful.

Our upgrade/migration to get back to a supported version is on hold until this can be resolved.

TIA!

 

Event1.Info.jpg
Event2.Error.jpg
Event3.Error.jpg
Event4.Error.jpg
Event5.Error.jpg
Event1.Info.jpg (147.64 KB)
Event2.Error.jpg (153.47 KB)
Event3.Error.jpg (171.15 KB)
Event4.Error.jpg (148.98 KB)
Event5.Error.jpg (183.95 KB)
0 0

Replies

replied on October 25, 2021

Hi John,

I'd advise opening a support case through your Solution Provider that references this post. From the information you've provided (which is great and detailed), this is likely to be difficult to troubleshoot over Answers.

Best,
Sam

1 0
You are not allowed to follow up in this post.

Sign in to reply to this post.