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

Question

Question

Does LFDS support using a Managed Service Account to run the service?

asked on April 12, 2017

I am trying to reconfigure a client's RIO installation to use a Managed Service Account to run all the LF services. Has anyone else had success configuring LFDS with an MSA? Troubleshooting has revealed that all services except LFDS function properly with the MSA. As soon as I configure LFDS to run under the MSA the repository never comes online.

 

Microsoft states that MSA's cannot span multiple computers and are typically not supported for cluster nodes or authenticated load-balancing type scenarios.  I feel that LFDS could be classified as a cluster management type of service. So I'm leaning towards the belief that LFDS may not support the use of an MSA.

 

Any thoughts or suggestions?

0 0

Answer

SELECTED ANSWER
replied on April 13, 2017

Ok, so it's unlikely this is caused by the service account. It rather looks like a configuration issue. Did you run the XMLEndpointUtility.exe after changing the service user?

It's probably best that you open a case with Tech Support so they can double-check your configuration. There is nothing special about Managed Service Accounts when it comes to running services. But configuration utility needs to be run after changing the service account for the LFDS service.

2 0

Replies

replied on April 12, 2017

What error do you get?

0 0
replied on April 12, 2017

Error Code: 9528

Error Message: Cannot connect to the Laserfiche Directory Server. [9528]

 

------------ Technical Details: ------------

 

LFSO:

    Call Stack: (Exception)

        ProcessResponseHeaders

        InternalDoLogin

        LFSession::Login

        CLFConnection::Create

    Additional Details:

        HRESULT: 0xc0042538 (ProcessResponseHeaders, LFSession.cpp:4898)

         (LFSO/10.1.1.274)

LF.exe (10.1.1.320):

    Call Stack: (Exception)

        CLoginDialog::AttemptLogin

        CLoginDialog::LoginToServer

        CLoginView::LoginHandler

    Call Stack: (Current)

        CLoginDialog::LoginToServer

        CLoginView::LoginHandler

    Additional Details:

        Exception: 0x80042538 [9528] (Cannot connect to the Laserfiche Directory Server.) (CLoginDialog::AttemptLogin at LoginDialog.cpp:796)

    Call History:

           CLFClientAutomation::ExecuteAutomationCommand (GetWindowInfo)

           CLFClientAutomation::ExecuteAutomationCommand (GetInstanceInfo)

           CLFClientAutomation::ExecuteAutomationCommand (GetWindows)

           CLFClientAutomation::ExecuteAutomationCommand (GetWindowInfo)

           CLFClientAutomation::ExecuteAutomationCommand (GetInstanceInfo)

           CLFClientAutomation::ExecuteAutomationCommand (GetWindows)

           CLFClientAutomation::ExecuteAutomationCommand (GetWindowInfo)

           CLFClientAutomation::ExecuteAutomationCommand (GetInstanceInfo)

0 0
replied on April 12, 2017

That's a Laserfiche Server error. Is the Directory Server's web administration site accessible?

0 0
replied on April 12, 2017

Yes and I am able to add a new AD user with no issue. I just can't login to the repository. It's as if the LFS service cannot communicate with LFDS.

0 0
replied on April 12, 2017

I should also say that when LFDS is running as the MSA, we can login to the repository with Local Laserfiche accounts. We cannot login with AD accounts. So again LFS seems to function in a silo as if it cannot communicate with LFDS.

0 0
replied on April 12, 2017

And vice versa. LFDS functions independently using the MSA account since I can access the web console and add/remove AD users.

0 0
SELECTED ANSWER
replied on April 13, 2017

Ok, so it's unlikely this is caused by the service account. It rather looks like a configuration issue. Did you run the XMLEndpointUtility.exe after changing the service user?

It's probably best that you open a case with Tech Support so they can double-check your configuration. There is nothing special about Managed Service Accounts when it comes to running services. But configuration utility needs to be run after changing the service account for the LFDS service.

2 0
replied on April 13, 2017

That was it exactly. I did open a case yesterday. That was the step that I was missing. I had never used that utility before. I did try to reissue the license, but had no idea I had to run the XmlEndpointUtility first. So BINGO! That is the solution. Thanks so much for your help. Issue resolved.

0 0
replied on April 13, 2017

Thanks for confirming the resolution Elexis. I will relay this back to the support engineer who worked with you on your support case that the information he provided to you in the case resolved your matter.

0 0
replied on April 13, 2017

Thanks Alex. I did do that. He is aware.

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

Sign in to reply to this post.