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

Question

Question

Federated Search Setup Error

asked on February 23, 2018

Good Afternoon All,

I am setting up a new Federated Search server as part of a new client's LF install and am getting a strange error.  The install itself goes fine and activates against LFDS without issue. 

When I launch the Federated search admin page, I get the following error "The search service has not been started, or the endpoint does not match. Please contact your administrator. "

I have verified that the search services are running.  There may be a piece I am missing, but where would I check the endpoint name that needs to match?

Thanks,
Jasno

0 0

Answer

SELECTED ANSWER
replied on May 15, 2018

Sorry for the late reply, this is an issue for Federated Search 10.3.

First of all, you would need a valid SSL certificate and bind it on port 443. You can check "Requirements for Using SSL/TLS with Laserfiche" section in https://www.laserfiche.com/support/webhelp/Laserfiche/10/en-US/administration/#../Subsystems/LFAdmin/Content/Using_SSL_TLS.htm?Highlight=SSL%20certificate

After that, you can do the following workaround:

  • Stop FederatedSearch service
  • Restart FederatedSearchAdminAppPool and FederatedSearchAppPool in IIS
  • Replace https://localhost/FederatedSearchApi with https://%FQDN%/FederatedSearchApi in the following files. (Please use your fully qualified domain name instead of %FQDN%)
    • %programfiles%\Laserfiche\Federatedsearch\SearchSite\Web.config
    • %programfiles%\Laserfiche\Federatedsearch\AdminSite\Web.config
    • %programfiles%\Laserfiche\Federatedsearch\SearchService\Laserfiche.FederatedSearch.Host.exe.config
    • %programdata%\Laserfiche\Federatedsearch\FederatedSearch.json
    • %programdata%\Laserfiche\Federatedsearch\ServiceContainer.json
  • Start FederatedSearch service

 

If the error still exists or you have other issues, you might want to open a support case so we can further troubleshoot the problem.

2 0
replied on November 5, 2018

Commenting on this old resolution, but I wanted to update in case anyone else runs into this.  In our case, this was because we used a wildcard SSL, so the setup automatically configured the address as "https://*.client.com/FederatedSearch/..." in each of the config files.  Once we did a find/replace on each of the files following the instructions above, we were able to add a repository without issue.  This is a potential gotcha to watch out for if you are using a wildcard ssl.

0 0

Replies

replied on February 23, 2018

Hi Jason,

After installing Federated Search, make sure that you go into C:\Program Files\Laserfiche\FederatedSearch\SearchService and run the EndpointUtility.exe program.

0 0
replied on February 28, 2018

Hi Alex,

Thanks for the response.  Even after running the utility, I get the same error.  The utility seems to error out as well.  Here is the output from it...

 

2/27/2018 4:55:35 PM: Start configuraton migration.
2/27/2018 4:55:35 PM: Start back up GeneralData.json
2/27/2018 4:55:35 PM: GeneralData.json path is C:\ProgramData\Laserfiche\FederatedSearch\GeneralData.json
2/27/2018 4:55:35 PM: C:\ProgramData\Laserfiche\FederatedSearch\GeneralData.json does not exist.
2/27/2018 4:55:35 PM: Finish back up GeneralData.json
2/27/2018 4:55:35 PM: Start migrating search site web.config
2/27/2018 4:55:35 PM: Back up C:\Program Files\Laserfiche\FederatedSearch\SearchSite\Web.config to C:\Program Files\Laserfiche\FederatedSearch\SearchSite\102Backup.
2/27/2018 4:55:35 PM: Migrate C:\Program Files\Laserfiche\FederatedSearch\SearchSite\Web.Default.config to C:\Program Files\Laserfiche\FederatedSearch\SearchSite\Web.config
2/27/2018 4:55:35 PM: Finish migrating search site web.config
2/27/2018 4:55:35 PM: Start migrating admin site web.config
2/27/2018 4:55:35 PM: Migrate C:\Program Files\Laserfiche\FederatedSearch\AdminSite\Web.Default.config to C:\Program Files\Laserfiche\FederatedSearch\AdminSite\Web.config
2/27/2018 4:55:35 PM: Finish migrating admin site web.config
2/27/2018 4:55:35 PM: Start migrating 10.2 GeneralData.json to 10.3 configuration files.
2/27/2018 4:55:35 PM: C:\ProgramData\Laserfiche\FederatedSearch\GeneralData.json does not exist.
2/27/2018 4:55:35 PM: Finish configuraton migration.

0 0
replied on February 27, 2018

Thanks Alex.

When I run the EndpointUtility application as an administrator with UAC off, I get this as output..

 

2/27/2018 4:55:35 PM: Start configuraton migration.
2/27/2018 4:55:35 PM: Start back up GeneralData.json
2/27/2018 4:55:35 PM: GeneralData.json path is C:\ProgramData\Laserfiche\FederatedSearch\GeneralData.json
2/27/2018 4:55:35 PM: C:\ProgramData\Laserfiche\FederatedSearch\GeneralData.json does not exist.
2/27/2018 4:55:35 PM: Finish back up GeneralData.json
2/27/2018 4:55:35 PM: Start migrating search site web.config
2/27/2018 4:55:35 PM: Back up C:\Program Files\Laserfiche\FederatedSearch\SearchSite\Web.config to C:\Program Files\Laserfiche\FederatedSearch\SearchSite\102Backup.
2/27/2018 4:55:35 PM: Migrate C:\Program Files\Laserfiche\FederatedSearch\SearchSite\Web.Default.config to C:\Program Files\Laserfiche\FederatedSearch\SearchSite\Web.config
2/27/2018 4:55:35 PM: Finish migrating search site web.config
2/27/2018 4:55:35 PM: Start migrating admin site web.config
2/27/2018 4:55:35 PM: Migrate C:\Program Files\Laserfiche\FederatedSearch\AdminSite\Web.Default.config to C:\Program Files\Laserfiche\FederatedSearch\AdminSite\Web.config
2/27/2018 4:55:35 PM: Finish migrating admin site web.config
2/27/2018 4:55:35 PM: Start migrating 10.2 GeneralData.json to 10.3 configuration files.
2/27/2018 4:55:35 PM: C:\ProgramData\Laserfiche\FederatedSearch\GeneralData.json does not exist.
2/27/2018 4:55:35 PM: Finish configuraton migration.

After that, I restarted the service and ran the admin console again with the same result

Thanks,

Jason

replied on March 22, 2019

Did anyone find a resolution to this? I'm completely stuck with the following error:-

 

 

The EndpointUtility.exe program completes sucessfully, however this error persists.

 

(FYI - Right click and running the EndpointUtility.exe as administrator resolved the above error for me)

0 0
replied on March 25, 2019 Show version history

Same for me at first, I tried running the EndpointUtility.exe (as administrator also) but still got that error until I ran through the manual steps of find/replace on the FQDN. I'm still getting errors on the File Provider and Web Provider tabs but will try to get around that - may need to update some config files.

 

0 0
replied on March 26, 2019

Hi Nigel,

For file and web provider, can you please stop "Laserfiche Federated Search Crawler Service" first, and then Replace https://localhost/ with https://%FQDN%/ in the following files. (Please use your fully qualified domain name instead of %FQDN%)

  • %programfiles%\Laserfiche\Federatedsearch\CrawlerAdminSite\Web.config
  • %programfiles%\Laserfiche\Federatedsearch\CrawlerService\Laserfiche.FederatedSearch.CrawlerService.Host.exe.config

 

Restart "Laserfiche Federated Search Crawler Service" after all are done.

Also, can i know if you have a wildcard ssl on your server?

1 0
replied on March 27, 2019

Hi,
 

I tried those steps but still having no joy I'm afraid. We don't a wildcard SSL cert - it's just a self signed one created via IIS.


Both the federated search services are running 

0 0
replied on April 1, 2019

Hi,

Do you mind show us these two files:

  • %programfiles%\Laserfiche\Federatedsearch\CrawlerAdminSite\Web.config
  • %programfiles%\Laserfiche\Federatedsearch\CrawlerService\Laserfiche.FederatedSearch.CrawlerService.Host.exe.config
  • %programdata%\Laserfiche\Federatedsearch\FederatedSearch.json
  • %programdata%\Laserfiche\Federatedsearch\ServiceContainer.json

That can be helpful for us to identify the problems.

1 0
replied on April 2, 2019

Hi - i checked through the  %programfiles%\Laserfiche\Federatedsearch\CrawlerAdminSite\Web.config file there was still a reference to localhost (I thought I'd done a fine/replace on all, most references had been updated but this one hadn't).

It now loads those pages correctly so looks like I'm good to go. Thanks for pointing me in the right direction!

0 0
replied on April 2, 2019

Continuing from this, I've managed to configure a file provider and successfully searched for content from there, but despite adding two local Laserfiche repositories, neither return and results and do not show as a source (assuming they should?)

A colleague is seeing something different on his system in that no repositories appear under the config page but do appear as sources, and yield search hits along with his other configured sources (web and file).

0 0
replied on April 2, 2019

Hi Nigel,

1. For your issue, does your account which you use to login Federated Search have access/ search rights to added repositories? You can try using the same account to search within the added repositories in Web Access to check if you can perform search operation successfully. It would be better if you can give us some screenshots for this.

 

2. For your colleague's problem, is it a seperate Federated Search server compared to yours?  Did your colleague ever add some repositories before?  Was the url the same one as the federated search instance he/she wanted to access?

 

For both of your issues, it would be helpful if you can offer us some more information:

  • %programdata%\Laserfiche\Federatedsearch\RepositoryProvider.json
  • Screenshots for FederatedSearch Admin site repositories configuration
  • Screenshots for FederatedSearch Search site landing page and search result page with errors you met
1 0
replied on April 3, 2019

Hi,

 

Quick update on this. The account the service was running as was able to login to the repository via the Windows and Web Client but this was by virtue of a repository user being linked to that AD account. 

Once I'd unlinked the repository user and explicitly added the same AD account as a Windows account, the repository then appeared as a source and I was able to complete searches OK. With hindsight that makes sense.
 

Thanks,


Nigel.

1 0
replied on April 3, 2019

Hi,

The behaviour of the config page allows me to enter the details for the repository but clicking apply the button disables as though its doing something but then does nothing.  No indication its adding the repository and you can navigate to another part of the config.

Returning to the Repository Tab and nothing again is showing but as Nigel said, the repository is being searched within the Federated Search Client.

 

1 0
replied on April 3, 2019

Hi Richard,
Thanks for reaching us. In order to identify problems you encounter, can you give us some more information:
    1. %programdata%\Laserfiche\Federatedsearch\RepositoryProvider.json if it is convenient for you
    2. What browser are you using? Does this happen in other browsers?
    3. In the first screenshot the repo name is MBS2, while the name in the second screenshot is mbsuk, are they the same repository? Did you add mbsuk before?
    4. To make sure I understand your words, when accessing admin site, you see no repositories, and the first screenshot happened after you clicked the "Apply" button?

0 0
replied on April 3, 2019

{
  "Version": "1040",
  "4b2012a7-58df-4dd3-a2ad-11f2570d52bc": {
    "Repositories": {
      "d7dca1ff-f07a-4be3-8c07-83fca75a174d": {
        "Id": "d7dca1ff-f07a-4be3-8c07-83fca75a174d",
        "RepoName": "mbsuk",
        "CustomerID": null,
        "EffectivePort": 80,
        "Port": null,
        "EffectiveSecurePort": 443,
        "SecurePort": null,
        "ServerName": "192.168.1.2",
        "UseTls": false,
        "SupportStreamingSearch": true,
        "DocumentUrlTemplate": "https://192.168.1.2/laserfiche/Browse.aspx?db=mbsuk#?id={0}",
        "SearchOptionLink": "https://192.168.1.2/laserfiche/options.aspx?repo=mbsuk#/searchpane",
        "UseGlobalWindowsLogIn": false,
        "State": 0,
        "Weight": 1,
        "WebAccessUrl": "https://192.168.1.2/laserfiche"
      }
    },
    "Info": {
      "Id": "4b2012a7-58df-4dd3-a2ad-11f2570d52bc",
      "Name": "Repository Provider",
      "ProviderType": "repo",
      "Properties": null
    }
  }
}
0 0
replied on April 3, 2019

Hi

Correct,  No repositories show and the line MBS2 is my attempt to add a new repository and when clicking the Apply button, it disables and does nothing else.

The MBS2 is a second repository I want to add to the RepositoryProvider that I created yesterday as a test.

Im using and have tried Chrome and IE both installed on the server.

I have added the JSON text to reply which shows the registration of the MBSUK repository.

Richard

0 0
replied on April 3, 2019 Show version history

Hi Richard,

Please open a case with support so we can troubleshoot the issue. And it would be helpful if you can attach a screencast on the Support Case for how to reproduce this issue on your Federated Search Admin site.

Thanks,
Shengyao Que

0 0
replied on April 10, 2019

Hi Richard,

We didnot find any support case about this issue. If you already opened a support case,  can you give us the case id?

 

Thanks,

Shengyao Que

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

Sign in to reply to this post.