FAQs
Specific
AspireBDCService trust level
AspireBDCService in version 2 of Aspire requires full trust in IIS. This will eventually change in future versions.
Field Mappings from Aspire to Crawled Properties
AspireBDCService is invoked from SharePoint Business Data Connectivity Services (BCS). It reads the batches in the Intermediate Repository, mapping some of the fields found there. Those have been mapped from Aspire fields using an XSL transformation. Starting with Aspire, the field names take this route:
Aspire-Name >XSLT> XML-Name >AspireService> BCS-Name >BCS> Crawled Property Name
Important: The /batch/doc@id attribute in the XML batch file is only used in AspireService internally for caching.
| XML <field name="name"> | BCS | Crawled Property | Remarks |
|---|---|---|---|
| author | Author | Author | Single-valued. Additional instances of the <field name="author"> tag will overwrite the current value. |
| claim_issuer | SecurityType | UsesPluggableAuth | Possible values
|
| description | Description | Description | Single-value. Additional instances of the <field name="description"> tag will overwrite the current value. |
| displayUrl | Url | Url | SharePoint URLs are not case sensitive. Make sure to use unique values; IBM Connections for example allows URLs which differ in character case only. |
| last_modified | LastModifiedTime | LastModifiedTime | |
| text | Content | Content | Single-value. Additional instances of the <field name="content"> tag will overwrite the current value. |
| title | Title | Title | Single-value. Additional instances of the <field name="title"> tag will overwrite the current value. |
| other fields | CrawledProperties Dictionary object | GetAspireDocument.<field name> | These fields are multi-value. Additional instances of the <field name="name"> tag will be addded to the current list of values. |
Maximum number of batches per crawl execution
In order to maintain an acceptable performance and resource usage in the server a limit of the number of batches processed per execution of the Aspire BDC service was implemented.
This setting is found in the web.config file of the AspireBDCService site folder and is set to 50 by default.
\inetpub\wwwroot\AspireBDCService\web.config
Under the 'MaxBatchesToProcess' value.
It is important to keep in mind that the Aspire BDC Service will process these batches in parallel, meaning that the bigger the batch files are, the bigger the impact on memory that the execution will have. Thus, care must be taken to ensure that the setting value takes into consideration the average batch size.
For this change to take effect, be sure to recycle the Application Pool of the BDCService in IIS.
Batch size estimation
Batch file size is influenced by the following:
- The number of files per batch setting in the Aspire Publisher component (default is 50)
- The volume of text content in the source files. If the source files are txt, the batched content ratio is 1:1
Thus maximum batch size can be as big as (file size) * (maximum files per batch).
Can the Aspire BDC Service be load balanced?
In the current version of the Aspire SharePoint 2013 Publisher (2.2) it is not possible to have more than one SharePoint server in a farm crawling a specific content source at a time.
However, it is possible to have the SharePoint Search Service Application pass through a load balancer to a collection of IIS servers with AspireBDCService instances. This will ensure availability of the service and scalability when there is more than one content source to be crawled in the SharePoint farm.
Troubleshooting
Error while creating the BDC Model
When the publisher tries to create a BDC model for a new Content source it may throw the following error:
Microsoft.SharePoint.BusinessData.Parser.PackageFormatException Retrieving the COM class factory for component with CLSID {BDEADF26-C265-11D0-BCED-00A0C90AB50F}
failed due to the following error: 800703fa Illegal operation attempted on a registry key that has been marked for deletion. (Exception from HRESULT: 0x800703FA).
Solution
To fix the issue you could try doing the steps on the following link and re-test:
Cannot find any matching endpoint configuration
While trying to crawl a content source it is possible that you get the following error on the content source crawl logs.
Error while crawling LOB contents. ( Error caused by exception: Microsoft.BusinessData.Infrastructure.BdcException The shim execution failed unexpectedly - Cannot find any matching endpoint configuration..; SearchID = 18B6E7B4-E65C-4E68-90F1-FDB810905B2A )
This means that the AspireBDCService isn't reachable.
Solution
A possible solution for this is to check if the AspireBDCService requires to be accessed using the server fully qualified domain name. Try to browse to it first and if it works, set it on the publisher configuration. Then recreate the model and content source so it picks up the new url.
Overview
Content Tools