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

Question

Question

LFDS registering legacy products

Directory Server Version 9
Updated February 15, 2016
asked on February 12, 2016

Having an issue with the LFDS providing the correct signature within the license file for Quick Fields 8.0. 

When we review the license file, the hardware fingerprint is showing the 8.3 - 9.0 version, even though we selected the hardware fingerprint for the legacy version 8.0. 

When we update the hardware fingerprint manually within the file, it throws an error stating invalid signature.

0 0

Answer

SELECTED ANSWER
replied on February 12, 2016 • Show version history

I did encounter an issue similar to what you describe on 9.2.1.208, but the workaround I described worked for me.

You must make sure that version 8.0 is selected AND copy + paste the legacy fingerprint; just doing one won't work.

If you have access to the SQL database, the query to fix it is simple (but backing up your DB is always a good idea):

USE [yourLFDSDatabase]
GO

UPDATE [dbo].[hosts]
   SET [fingerprint1] = 'yourlegacyfingerprint'
 WHERE [name]='yourmachinename'
GO

To see if it's set correctly:

SELECT [id]
,[name]
,[fingerprint1]
,[fingerprint2]
FROM [yourLFDSDatabase].[dbo].[hosts]

You could also try going to the "Machines" tab and completely removing the machine, then re-registering your application(s).

I think this issue may also be present in version 10, so we'll look into it and aim to include a fix in the next service pack.

1 0

Replies

replied on February 12, 2016

If you are having issues with fingerprints, you should resolve them within LFDS, not by editing the license. It is not possible to edit the license manually and still have a valid license.

To force LFDS to use the correct fingerprint, you can try entering the legacy fingerprint in the UI. Click "Edit" on that specific instance, copy + paste the correct fingerprint, and save. Then, download the new license and try that.

There maybe be an issue within LFDS; we will look into the behavior you described and see if we can reproduce. What exact version of LFDS are you on?

 

 

0 0
View 1 previous reply
replied on February 12, 2016

LFDS - 9.2.1.208

I already performed the recommendation you provided. This is why I attempted to change the HWFP manually within the file. 

By either entering the 8.0 version or by entering the legacy fingerprint within the UI, the file would still show the wrong HWFP. 

0 0
SELECTED ANSWER
replied on February 12, 2016 • Show version history

I did encounter an issue similar to what you describe on 9.2.1.208, but the workaround I described worked for me.

You must make sure that version 8.0 is selected AND copy + paste the legacy fingerprint; just doing one won't work.

If you have access to the SQL database, the query to fix it is simple (but backing up your DB is always a good idea):

USE [yourLFDSDatabase]
GO

UPDATE [dbo].[hosts]
   SET [fingerprint1] = 'yourlegacyfingerprint'
 WHERE [name]='yourmachinename'
GO

To see if it's set correctly:

SELECT [id]
,[name]
,[fingerprint1]
,[fingerprint2]
FROM [yourLFDSDatabase].[dbo].[hosts]

You could also try going to the "Machines" tab and completely removing the machine, then re-registering your application(s).

I think this issue may also be present in version 10, so we'll look into it and aim to include a fix in the next service pack.

1 0
replied on February 15, 2016

I will perform the work around within SQL to see if it fixes the issue. 

I will let you know. 

I did remove the machine already and re-registered it to see if it would fix it. It did not resolve it.

0 0
replied on February 15, 2016

This resolved the issue. I appreciate your help.

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

Sign in to reply to this post.

Details
Related Posts
Loading ...