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

Question

Question

LFDS 11 post upgrade issues

Version 11 Directory Server
Updated June 22, 2021
asked on April 26, 2021 • Show version history

Hi All;

We recently upgraded to LaserFiche 11 but over the weekend we experienced issues with LFDS and ended up upgrading everything else but leaving LFDS on 10.4.3. 

The issues we had were that it was just responsive and then unresponsive. If you were trying to login from web client and simultaniously accessing the web admin on LFDS it would hang for a while.

Now I understand that some architectural changes have been made to LFDS since 10.4.2. There are definitely schema changes too. The one I know of which was documented in the release notes is that app's need to be able to access the sso etc via http.

I am trying to work out what I am missing in order to get LFDS 11 running again. 

0 0

Replies

replied on June 17, 2021

Shane,

Have you received any response from Laserfiche about your question? Have you gotten it to work with LFDS 11 and STS on previous versions?

We are planning to do an upgrade to our system and would like to do it in a multiple phase process (LFDS first, followed by Test System, Followed by 2 Production environments). 

Thanks in advance,

Steven

0 0
View 3 previous replies
replied on June 17, 2021

We went big bang on 11 just post release. I had to back off to 10.3 on LFDS because 11 was not playing nicely. There was an architecture change where one of the services - I think STS - moved to http (from - correct me if I am wrong tcp).

Our biggest issue was it being unresponsive on every request - whether on the admin portal or trying to login to sites that require single signon.

Presuming it is doing http on port 80 / 443 instead of a custom tcp port, I can't see why it was unresponsive. But regressing to 10.4? was our only option so as to not go back to 10.2 (multiple servers, etc).

10.3 / .4 LFDS works 100% apart from a little glitch on your first login - I have traced this to LFDS not having a cookie for the user - because it has expired. Work around is just to hit F5 and from there on in you have no problems across mulitple apps like forms, web client etc.

It is really difficult to isolate issues with the standard dot net error messages - apart from the obvious sql timeouts - and in some applications even error messages appear in the event viewer as information which does not help.

So for now we are foregoing v11 for LFDS until the first patches start coming through.

Personally I probably jumped the gun on this one going in a little early. But everything else in 11 has been peachy. Audit trail - not sure if this was the case before - now uses the same catalog for searching and reporting as LFFTS - so make sure you have space on your web server for this because as soon as you start the background services it will start creating the catalog and can be quite big. For now - I have left it disabled. We are moving to Azure in August so can then spec my servers a little better for this and probably move installs around a bit - the catalog gets created in ProgramData (which is usually on the OS disk) and this can be a problem. I tried moving it elsewhere but did not get this working.

0 0
replied on June 17, 2021

I appreciate the follow-up information. 

We will likely go though the same option as we need to upgrade LFDS to take advantage of some of the options available for Auditing and Syncing with AD. We have two live systems and are unable to upgrade everything at one single time. 

 

0 0
replied on June 21, 2021 • Show version history

Hi Shane and Steven,

We haven't had any other reports, either internal or through support cases, of the behavior you described.

Without support cases, we can't pinpoint what might be causing this behavior and releasing a hotfix. As such, I recommend contacting your reseller and opening a support case so we can help determine the root cause. We cannot release a hotfix for something we cannot reproduce or gather data on.

The only marginally related behavior is that some very large (80-100k users) systems experience login slowness when LFDS is undergoing a large operation (AD sync, admins performing changes on many users), but that is not new to 11. 

 

Regarding the architecture change: the change was for communication between LFDS and the STS (the login page) in 10.4.3, changing from WCF (a Windows framework than runs over HTTP) to pure HTTP. The only user-facing application to also update to pure HTTP was Federated Search.

If you have a separated STS, you now always should be configuring a certificate on the LFDS side and enabling HTTPs on the STS instance. The endpoint config utility has options to help you configure this binding.

The ports used have not changed.

0 0
replied on June 22, 2021

Brianna, 

I appreciate the update and agree with you completely about opening up a support case to help troubleshoot and resolve. 

We are looking to minimize any downtime and issues during an upgrade to LFDS as we need some newer functionality provided by LFDS 10.4 (Database Maintenance and Audit configuration). 

We are also looking to upgrade our system in phases (over a months time frame) since we have multiple production environments. We contacted our support channel and they recommended that if we upgrade LFDS to version 11, we would need to upgrade all Laserfiche products to version 11. They couldn't direct us that an LFDS 11 upgrade would cause issues with older versions of STS.

The above situation by Shane is something we are looking to avoid in order for our system to be running with minimal issues.  

Thanks again,

Steven

1 0
replied on June 22, 2021 • Show version history

Hi Steven,

LFDS 11 is compatible with many older Laserfiche products. You do not need to upgrade everything to 11 all at once. For example, LFDS 11 requires Laserfiche Server version 10.2.1 and later or Laserfiche Server 10.1 Update 3.

There is a chance that older STS instances will work in some cases with LFDS 11 but it is not recommended nor a supported configuration to have LFDS and STS versions mismatched.

1 0
replied on June 22, 2021

Awesome Chase! Thanks for the additional information.

Quick question. If we upgrade LFDS to version 10.4.3 so that are current production environments continue to run (2 environments one is 10.2.1 and one is 10.4.1). The plan would be to upgrade the 10.2.1 environment to version 11 (LF, WF, Forms w/ STS, Web Client w/ STS, WL, and Quickfields w/Agent) followed by the 10.4.1 environment (LF, WF, Forms w/ STS, and Web Client w/ STS).

Will the new versions of STS be compatible with LFDS 10.4.3? 

It sounds like if we plan upgrade Laserfiche products that use STS we need to upgrade LFDS at the same time. 

I'm only going on an assumptions for the following scenario so correct me if I'm wrong. 

If I want to upgrade one environment to version 11 ((LF, WF, Forms w/ STS, Web Client w/ STS, and Quickfields w/Agent). I will then need to upgrade LFDS to version 11. Which leads to the possibility that the other environment version 10.4.1 would have issues with the STS page and LFDS mismatch). It sounds like I will need to upgrade the both environment at the same time. **NOTE** We understand that some products have software requirements with lower versions but we have an integrated environment (Forms\Workflow Integrations, Web Client\DocuSign Integrations, Weblink,etc..) that I would expect we would want the entire environment to match. 

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

Sign in to reply to this post.

Details
Related Posts
Loading ...