Troubleshooting Tips

Problem description Solution
The list of SharePoint sites is not visible for selection in the Site field of the General tab.
  1. Probably the component cannot connect to SharePoint 2007 Server. Make sure that you have entered correct connection parameters. If they are correct, check if the user has sufficient access rights to the SharePoint 2007 server. Contact your server administrator.
  2. Make sure that the correct version of web service is installed on the SharePoint 2007 Server machine.
The Status Monitor shows the following message:

"Cannot connect to #Server#. Check site name and login settings.",

where #Server# is the specified Server address specified on the General tab.
Probably the component cannot connect to SharePoint 2007 Server. Make sure that you have entered correct connection parameters. If they are correct, check if the user has sufficient access rights to the SharePoint 2007 server. Contact your server administrator.
A document is not sent to the server. The Status Monitor shows the following message:

"Document library #Libraryname# could not be found",

where #Libraryname# is the specified name of the Document library.
Probably you have specified a non-existent library in the Document library field on the Documents tab. Specify the correct library name.
A list item is not sent to the server. The Status Monitor shows the following message:

"List #Listname# could not be found",

where #Listname# is the specified name of the List.
Probably you have specified a non-existent list in the List field. Specify the correct list name.
A document is not sent to the server. The Status Monitor shows the following message:

"Field #Fieldname# could not be found",

where #Fieldname# is a name of an added field. 
Each document library has its own specific set of fields, and you may specify only the fields from this set. Probably #Fieldname# field does not belong to the set of specified fields. Remove this field from the component configuration.
A list item is not added to a list on the server. The Status Monitor shows the following message:

"List item is not created. Value does not fall within the expected range."

.
Each list has its own specific set of fields, and you may specify only the fields from this set. Probably some field does not belong to the set of specified fields. Remove this field from the component configuration.
A document or a list item is not sent to the server and the Status Monitor shows one of the following error messages:
  1. "The request failed with HTTP status 503: Service Unavailable."
  2. "The underlying connection was closed: An unexpected error occurred on a receive."
  3. "The server committed a protocol violation. Section=ResponseHeaderDetail=Header name is invalid at System.Net.HttpWebRequest.GetResponse()".
These messages are concerned with SharePoint 2007 server failure. Try again later or contact your server administrator.
When you enter "https://" followed by server name, for example, https://sp2007 in Server address field, a document is not routed and the Status Monitor shows the following error message:

"Request Entity Too Large. at System.Net.HttpWebRequest.GetResponse() at WSS3Gateway.CWSS3Gateway.SendRequest(String sUser, String sPassword, String sDomain, String uri, Byte[] postBody, Int64 postLength)"

.
The reason of this problem is concerned with SSL settings on the server. Do one of the following:
  1. Enter "https://" followed by IP address, for example, https://192.168.0.178 in Server address field.
  2. Make a request to your server administrator to check on the "Ignore user certificates" option.
Status Monitor shows the correct component work, but the routed document or list item is not visible on the SharePoint site. Probably the user has not sufficient access rights to the SharePoint 2007 server. Contact your server administrator.
When you are sending documents or list items to the server having a Host Header, and use the Host Header in the Server address text box, the error message appears at run time:

"Cannot check folder path. Web application #HostHeaderAddress# could not be found.",

where #HostHeaderAddress# is the address of the site via Host Header, for example, http://host123.
For correct work with a server having a Host Header, add "Alternate Access Mappings" for the Host Header on the SharePoint 2007 server. This operation can be performed by a SharePoint 2007 administrator via web access: SharePoint 3.0 Central Administration/Operations/Alternate Access Mappings. For more details see http://blogs.msdn.com/b/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx.
If you send a document to a document library where the Require check out option in the Document Library Versioning settings is set to "No" and the last version of the file on server is checked in, the component creates more than one new document versions. Such behavior is related to the Share Point 2007 server that creates a new version when performing each operation: saving file, assigning fields, assigning permissions, and so on.
The Status Monitor shows one of the following error messages:
  1. "The request failed with the error message: <h2>Object moved to <a href="http://hostname/_layouts/1033/error.aspx?ErrorText=Request timed out.">here</a>.</h2>", where hostname is replaced with the address of the SharePoint 2007 server.
  2. "Unable to connect to database. Check database connection information and make sure the database server is running. STACK TRACE: at Nsi.SharePoint2007.Utilities.FileUploadRequest.ProcessResponse(WebResponse oResponse)"
These error messages may appear when the SharePoint 2007 server is overloaded. Contact your server administrator.
If you are using the impersonation option, the Status Monitor displays the following error message at run time:

"Internal error description: The parameter loginName cannot be empty or bigger than 251 characters"

.
This problem may take place if the anonymous access is enabled for the file /_vti_bin/NSI_SP2007WS.asmx in the IIS settings on the SharePoint 2007 server machine. To avoid this problem, disable anonymous access for this file as the user with anonymous access cannot be an impersonator.