Troubleshooting tips
Problem description | Solution |
---|---|
The component does not send documents or list items when the Host Header of the SharePoint server is used in the Server and Site collection text box on the General tab. | For correct work with Host Headers, the SharePoint administrator should correctly set the Host Header in IIS on the SharePoint server machine. For details, see Configure a Host Header for a Web Site (http://technet.microsoft.com/en-us/library/cc753195(WS.10).aspx). |
The component does not connect to the server or site collection when the Server and Site collection text box contains IP address. | For correct connection to servers using IP addresses, the SharePoint administrator should correctly set up the Alternate Access Mappings. For more details, see Configure alternate access mappings for SharePoint Server (https://docs.microsoft.com/en-us/sharepoint/administration/configure-alternate-access-mappings). |
Web service does not write information into the log file. | For correct logging, ensure that the WSS_ADMIN_WPG Windows group on the web service computer has Full Control and the WSS_WPG Windows group has Read & Execute, List Folder Contents, and Read permissions or higher on the folder containing the trace log. To perform this procedure, you must be a member of the Administrators group on the server host machine. For more details, see Event ID 5400 (http://technet.microsoft.com/en-us/library/cc561020.aspx). |
Documents processing fails and the Status Monitor shows one of the following messages:
|
Such issues appear when you select the predefined "Network Service" account for your Web application pool as a security
account and store the data in an external data column. To resolve this problem, you should grant access to a local SQL Server
database to this account. To solve this problem, grant access to the "Network Service" account to the local SQL database.
For more information, see Use the Network Service Account to Access Resources in ASP.NET (http://msdn.microsoft.com/en-us/library/ff647402.aspx). |
When configuring the component, you receive the following error message:
Could not load file or assembly 'Microsoft.IdentityModel, Version=3.5.0.0, Culture=neutral, PublicKeyToken= ...' or one of its dependencies. The system cannot find the file specified. |
This error appears when there is no Windows Identity Foundation (WIF) installed on the machine, where the workflow server is running, and the .NET Framework version is 3.5.
To resolve this problem, make sure that the Windows Identity Foundation is installed on the machine, where the workflow server is running. To download the application, see Download Windows Identity Foundation. Windows Identity Foundation is now a part of .NET Framework 4.5; therefore, the upgrade to this Framework version can also fix the problem.
|
One of the following problems appears when the user works with the component:
|
The possible reason for this problem is that the component reaches the maximum
limit, set in the configuration of the web application. This limit is set for the
maximum number of items that can be retrieved from the web application at the same
time; by default, the limit is 5000. If there are less items than the maximum number,
then the component will retrieve all found folders, but if the number of items exceeds
the maximum limit, then the component will retrieve only the folders found within the
first max_number items, where max_number is the
current list view threshold. To solve this problem, increase the List View Threshold by the following path: Central Administration >> Application Management >> Manage Web Application >> web_application >> General Settings >> Resource Throttling >> List View Threshold, where web_application is the name of a web application on the SharePoint site, for which you need to increase the threshold. |