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

Question

Question

SQL database schema does not match error 9110

asked on March 10, 2014

I have a client that was using LF Avante 9.0.2 with SQL 2008 R2 express. Well they just upgraded their version of LF for full SQL and also are putting the LF SQL db on a 2008 Standard machine. I had to find some information on how to "downgrade" the database, and I was able to do that. I am able to see the tables and all and everything looks right to me, but not for sure. The thing I am having issues with is that when registering the repository I receive an error 9110-  SQL database schema does not match... I already activated the new license for their LF Avante. Any clues what the real issue is?

 

Thanks,

Chad

0 0

Replies

replied on March 10, 2014

9110 usually indicates you're using a SQL database that has a LF7 schema in it. What sort of "downgrade" are you referring to?

0 0
replied on February 27, 2015

I'm getting an error for this exact thing, too. I'm upgrading from 8.3 and migrating over to a new server, I have successfully attached the SQL Database to SQL Management Studio Express 2012. But when registering the repository, it is giving me this 9110 error. Any ideas?

0 0
replied on September 3, 2015

I got a client with 2 repositories one is working fine but the second I don't know why its not registered and when they try they get: The Laserfiche server encountered an error when trying to create or attach the repository: 9110. The database schema is the wrong type or is not supported version.

 

What could be wrong? 

This wasnt an upgrade.

 

They got LF 9.1.

In the first repository all works fine 

0 0
replied on September 3, 2015

This just started happening without the software being modified?

Run the following query on your SQL database to see what the schema version is listed as:

SELECT [optionname]
      ,[optionvalue]
  FROM [dboptions]
  WHERE [optionname] = 'version'

Post the results back here or open a support case.

0 0
replied on September 3, 2015

Looks like the database is 9.2 and the Admin console its 9.1 so look like thats the issue.

They got 3 environments: Developing, QA (Testing) and Production.

Apparently they make improvements on the first one, and when they restore the backup in QA  turns that the first one its in 9.2.1 and the second one is 9.1 so maybe that's the origin of the issue.

 

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

Sign in to reply to this post.