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

Question

Question

LFS received an unrecognized or unexpected error from LFDS

Laserfiche Version 10
Updated December 18, 2017
asked on June 5, 2017

Hi All, 

 

Was wondering what this is related to? the client is on a RIO system that has LFDS and all Laserfiche applications installed on one server? (Terminal Server). 

 

I just had a quick look into Event Viewer and under Laserfiche > Service > Admin I see the below:

LFS received an unrecognized or unexpected error from LFDS. Service Call=GetUnsignedTokenEx(token=<a:Token xmlns:a="http://laserfiche.com/namespace/lm">

 

I have not added the whole string incase it was not required, but can create a case if needed. But, just wanted to know why this is showing up within Event Viewer? 

 

Thank you

Ziad

0 0

Replies

replied on October 7, 2017

Hi Guys, 

 

One thing i would suggest checking is the user account that is connecting to the DB. Check to see if there are any ports blocking you from accessing the DB server, or if the user has complete access to the required Database as well. 

Keep me posted,

 

Ziad

1 0
replied on July 14, 2017

We are experiencing the same issue, have you found a cause for this? 

0 0
replied on July 16, 2017

Not yet, but I have been advised to re-licence LFDS which iam yet to do at the moment, 

 

Thanks

Ziad

0 0
replied on October 4, 2017

@████████

Any joy on this issue? I have a client with the same error message now too. LF RIO 10.2.1 with all the latest updates.

I tried renewing the LFDS master license too.

I also have an issue where the LF Forms aren't saving to the Repository. Not sure if it is related or not

0 0
replied on October 4, 2017

Hi Jonathan, 

 

The forms issue would not be related, check to see if the user account has access rights to the folder? Also, check under Event Viewer > Laserfiche > Forms to see if there are any errors why it would not save into LF? 

 

Also, with regards to the LFDS issue, I was awaiting the new version of LF to do the whole renewing of LFDS master license. But, this means to drop the original DB and create a whole new DB from scratch. 

 

Let me know how you go?

Ziad

0 0
replied on October 7, 2017

Receiving the same error when trying to add LFDS user accounts in Web Admin.

0 0
replied on October 19, 2017

Good Afternoon,

 

I am seeing daily errors of the same type on the Laserfiche application server. I have not been able to pin down the cause of this. I also have not had any reports on the user side of any processes not functioning. I am curious to know if Laserfiche has seen this come across their cases before and if so how did they resolve it?

0 0
replied on December 13, 2017

Has anyone that was experiencing this issue found a resolution? Did anyone open a support ticket with Laserfiche?

0 0
replied on December 14, 2017

We have a customer getting the same errors as well.  Very interested to hear the resolution.

0 0
replied on December 15, 2017

I ended up opening a support ticket.  In our situation, the LFDS was originally 10.0.0.222.  They had us run a hotfix to 10.0.0.270.  After restarting and reissuing the repository server license, the error didn't return.

0 0
replied on December 18, 2017

Hi Frankie, 

 

I have updated LF to the latest version released and wanted to make sure I do this correctly. I was advised as I mention to relicense and renew the LFDS master license. But, this means to drop the original DB and create a whole new DB from scratch.

Is this what you did? Or did you just generate a whole new license for the LF server only? And when you did, did you also have to generate new licenses for each other module? 

 

Thanks

Ziad 

0 0
replied on December 18, 2017 • Show version history

Hi Ziad,

I ran the hotfix located here:  https://support.laserfiche.com/kb/1013805/list-of-changes-for-directory-server-10-0-update-2

This hotfix runs in place.  I didn't do anything with the master license. (Well besides making a back up of the master license database.)  Then delete and reissue the repository server license.  If the error is happening on more than 1 repository server, delete and reassign for each repository server. 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...