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

Question

Question

siteguid mismatch between the primary licence and database laserfiche

Directory Server Version 11 Licensing
Updated April 7, 2022
asked on April 4, 2022

Hello every body,

After installing a new LFDS 11, deactivating the old LFDS and activating the new one, each time restarting Laserfiche service , there is a message telling us there is a siteguid mismatch between the primary licence and database laserfiche. 

 

Is there anyone who had this problem and resolved it?

 

Best regards.

1 0

Answer

SELECTED ANSWER
replied on April 6, 2022

That approach may work, but instead give this a try on your existing database:

 

  1. Back up the LFDS database (IMPORTANT, the following steps include manually altering the database).
  2. Open the database in Microsoft SQL Server Management Studio.
  3. Right click on the database and select Tasks > Generate scripts.
  4. Click Next, select "Select specific database objects", then expand "Tables" and select "dbo.db_settings". Click Next.
  5. Click the Advanced button,
    1. Set the "Script DROP and CREATE" value to "Script DROP and CREATE".
    2. Set the "Types of data to script" value to "Schema and data".
    3. Click OK.
  6. Select "Save to new query window", click Next.
  7. Click Next again and click Finish.
  8. In the newly opened query window, find the line that reads "[name] [nvarchar](100) NOT NULL,"
  9. Change this line to "[name] [nvarchar](100) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,"
  10. Execute the query.
  11. Try to reproduce the problem again by restarting LFDS and see if the issue is fixed.

1 0

Replies

replied on April 5, 2022

By Laserfiche service are you referring to the Laserfiche Server Service?  If so, that means the license file is looking for the old Directory Server.  You can either update the license, or put a dns rule in place to route the old LFDS to the new LFDS.

1 0
replied on April 5, 2022

Hi Mr Craig,

Please, do you mean that we have to attach the old sqlserver database files to the new sqlserver database on the new LFDS?  

0 0
replied on April 5, 2022

Hi Ged,

To clarify, you switched machines and created a new LFDS database on a new machine instead of attaching the previously used database?

1 0
View 4 previous replies
replied on April 5, 2022

Hi Mr Chase,

Of course yes. A new Virtual machine with a new sqlserver Database, and also a new LFDS installation.

We have recently upgrated to LFDS 10.4 from the licence manager, and since then we have this problem each time the server restarts LFDS stop working and displays "the database is invalid or the master license is already in use"

When we select ‘renew the license’  and give the master license, everything seems to work fine, until the next time the server restarts.

we did somme investigating on the issue and we found out :

This error happens when the directory server service restarts .

We checked the Directory Server log on the event logs and found this error : SiteGuid mismatch between the primary license and the database.

We tried upgrading to LFDS11 to resolve the issue, but without success we had the same behavior. Next we repeated the operation on a new machine with a new LFDS site, but it also did not resolve the issue.

We also tried deactivating and an reactivating the master license it didn’t change anything.

 Thanks !

 

0 0
replied on April 5, 2022

Can you please navigate to your new LFDS SQL database via SQL Server Management Studio, right click on the database, select properties, and send a screenshot of the General properties? We've seen issues in the past when customers have databases with a case-sensitive collation.

1 0
replied on April 5, 2022

Hi Mr Chase, 

Thank you for answering.

Will do it tomorrow morning once in the office.

Good night!

0 0
replied on April 6, 2022 • Show version history

Hi Mr Chase,

The default server-level collation in SQL Server is "French_CS_AI", I believe it's a case-sensitive collation. Can this lead to complications? Is it recommended in our case to choose a case insensitive collation like "French_CI_AI" before creating the database to solve the invalid LFDS license issue?

Regards!

0 0
SELECTED ANSWER
replied on April 6, 2022

That approach may work, but instead give this a try on your existing database:

 

  1. Back up the LFDS database (IMPORTANT, the following steps include manually altering the database).
  2. Open the database in Microsoft SQL Server Management Studio.
  3. Right click on the database and select Tasks > Generate scripts.
  4. Click Next, select "Select specific database objects", then expand "Tables" and select "dbo.db_settings". Click Next.
  5. Click the Advanced button,
    1. Set the "Script DROP and CREATE" value to "Script DROP and CREATE".
    2. Set the "Types of data to script" value to "Schema and data".
    3. Click OK.
  6. Select "Save to new query window", click Next.
  7. Click Next again and click Finish.
  8. In the newly opened query window, find the line that reads "[name] [nvarchar](100) NOT NULL,"
  9. Change this line to "[name] [nvarchar](100) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,"
  10. Execute the query.
  11. Try to reproduce the problem again by restarting LFDS and see if the issue is fixed.

1 0
replied on April 6, 2022

Thank you,

Will try it and give you answer.

Regards.

0 0
replied on April 7, 2022

Hi Mr Chase,

Thank you very much for your help, it really solved the problem yes.

I will mark the post as resolved.

 

Best regards.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...