File Share Graph Connector - Feedback & Problems

%3CLINGO-SUB%20id%3D%22lingo-sub-2037269%22%20slang%3D%22de-DE%22%3EFile%20Share%20Graph%20Connector%20-%20Feedback%20%26amp%3B%20Problems%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2037269%22%20slang%3D%22de-DE%22%3E%3CP%3EI've%20installed%20and%20tested%20the%20Graph%20Connector%20Agent%20with%20File%20Share%20Connector.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EFeedback%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20within%20the%20documentation%20a%20lot%20of%20information%20missing.%20The%20agent%20needs%20TCP%20port%205671%20to%20Azure%20to%20start%20the%20connectors%20-%20costs%20me%20an%20hour%20to%20find%20out.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Indexing%20failes%20for%20over%20hundred%20thousand%20files%20reporting%20there%20is%20a%20permission%20error%20-%20by%20checking%20NTFS%20%26amp%3B%20Share%20ACL%20Everything%20is%20fine.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20The%20hidden%20logfile%20in%20C%3A'Windows'ServiceProfile...%20has%20a%20lot%20of%20nonsense%20written%20to%20it%20and%20missing%20important%20information%20for%20troubleshooting%20%2F%20debugging.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-%20Its%20a%20pain%20to%20find%20out%20about%20graph%20costs%20for%20additional%20index%20space%20and%20queries%20-%20almost%20no%20information%20available%20for%20planning%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EQuestion%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENo%20search%20results%20for%20my%20file%20share%20vertically%20at%20the%20moment%20-%20how%20to%20troubleshoot%3F%20Any%20way%20to%20receive%20the%20complete%20index%20to%20ensure%20there%20is%20no%20problem%20with%20SID%20to%20AAID%20mapping%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

I´ve installed and tested the Graph Connector Agent with File Share Connector.

 

Feedback:

 

- within the documentation a lot of informations missing. The agent needs TCP port 5671 to Azure to start the connectors - costs me an hour to find out.

 

- Indexing failes for over hundred thousand files reporting there is a permission error - by checking NTFS & Share ACL Everything is fine.

 

- The hidden logfile in C:\Windows\ServiceProfile ... has a lot of nonsense written to it and missing important informations for troubleshooting / debugging.

 

- Its a pain to find out about graph costs for additional index space and queries - almost no information available for planning

 

Question:

 

No search results for my file share vertikal at the moment - how to troubleshoot? Any way to receive the complete index to ensure there is no problem with SID to AAID mapping?

 

 

 

6 Replies

Thank you for the feedback, @Phillll. We really appreciate you taking the time to enumerate places we can improve. 
 

Some common issues to check:

  • A result type hasn't been created for items for that connection
  • Make sure that you use the cache-clear=true flag in the URL to make the vertical appear

For instructions on how to do all the above, you can look at the documentation here: Customize the Microsoft Search page | Microsoft Docs

Hi, @JudyN, same problem here.

 

We have configured succesfully the connector and is indexing but after configure both, the result type and the vertical no results are shown. Any idea?

Hi @areyecat, have you also created a custom vertical and result type for the connection?
Hi, yes, both, with the default configuration. On the result type I configured this layout, but nothing is shown.
{
"type": "AdaptiveCard",
"version": "1.3",
"body": [
{
"type": "ColumnSet",
"columns": [
{
"type": "Column",
"width": 8,
"items": [
{
"type": "TextBlock",
"text": "[${title}](${titleUrl})",
"color": "Accent",
"size": "Medium",
"weight": "Bolder",
"$when": ""
},
{
"type": "TextBlock",
"text": "**${createdBy}** modified {{DATE(${modifiedDateTime})}}",
"spacing": "Small"
},
{
"type": "TextBlock",
"text": "${name}",
"wrap": true,
"maxLines": 3,
"spacing": "Medium",
"$when": ""
}
],
"horizontalAlignment": "Center",
"spacing": "Medium"
}
]
}
],
"$schema": "http://adaptivecards.io/schemas/adaptive-card.json"
}

@areyecat Sorry to hear you are facing issues with the connector. Can you please drop a mail to MicrosoftGraphConnectorsFeedback@service.microsoft.com with your tenant ID? We will troubleshoot the issue and reply with a resolution. Thanks.

Hi, thanks to https://twitter.com/mikaelsvenson/status/1444017436869726243?s=20 the issue has been resolved. There was a missunderstood for my side about how the search service retrieves the permissions to show the indexed content. To summarize, the groups have to be synced between local domain and Azure AD