Crawl Log Errors/Warnings

20 May

We were receiving this error message in our crawl log for our top level site:

https://top level url

The item could not be accessed on the remote server because its address has an invalid syntax.

I had never seen this before in our logs so I actually tracked down the file that was specified in the top level url and navigated to it. When I found the specified document and clicked on it, it came up with the message below:

Crawl Log Error

I wanted a backup copy so I clicked on the drop down arrow to the right of the document and highlighted Send To and downloaded a copy (see image below) just in case. Then I deleted the document(s).

Download a Copy

Once I removed the document(s), I ran a full crawl and the error did not reappear. What I found out was that we had actually exceeded the 256 character path limitation. This file was about 8 folders deep in a subsite so it was 1 character too long. Here is my suggestion on working around this and also a list of MOSS limitations. I hope this helps!

 This is a limitation of .NET (C#, VB, etc), the language that SharePoint was built on.  

When programming in .Net there are ways around this using Win API calls, but I am inclined to believe that MS did not use any WIN API calls, but rather used the native .Net file handlers

I’ve found a way around this by creating another network place on the server that points to the folder that is buried a lot further down.

For example:
\\server\path1\longpath2\longpath3\longpath4\reallylongname.txt   (assume this is 300 characters)


Short of that, there is not much you can do.

Another suggestion as far as some of the limitations…inform the client not to use spaces in file or folder names. If they need a space, they should use a dash or an underscore since html for a space is %20. This takes up three characters in the URL versus one for a – or an _. Those extra spaces add up fast.

SharePoint 2007 Maximum Limitations

Following is a list of names and other parameters with the maximum allowable size on each.

Entity                        Max Permissible Size
Site Name                    128 characters
Site URL                 255 characters
Display name                 128 characters
Connection string                 384 characters
Email address                    128 characters
Version numbers                064 characters
Virtual Server Friendly Name            064 characters
SQL Database Name                123 characters
SQL Database Column                128 characters
SQL Database Table Name            128 characters
SQL Role Name                    128 characters
Server Name                    128 characters
Windows User Name                300 characters
Windows Password                300 characters
Dependencies per object            032 objects
Zone enumeration value            004 zones
Default SQL command timeout             300 seconds
Number of simultaneous
workflows that can be run*             015

If during your course of using the product, you inadvertently cross these limits, then you would end up with errors. These are hard limits.

Leave a comment

Posted by on May 20, 2009 in SharePoint Common Issues


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: