Category Archives: Security

parse error processing item failed sharepoint

parse error processing this item failed because of an unknown error when trying to parse its contents

There is parse error found in the Crawl log of a SharePoint 2013 environment. Processing this item failed because of an unknown error when trying to parsing its contents. (Error parsing document,Sandbox worker pool is closed,SearchID)

  1. In order to fix this you can try to perform the following action plan:
  2. Open "Local Policies
  3. Click on “User rights assignment
    adjust memory quotes-1276x416

    adjust memory quotes

  4. Make sure that the search service account has the following rights:"Replace a process level token”.
    replace process level token-1060x766

    replace process level token

  5. "Adjust memory quotas for a process"
    adjust memory quota-1054x762

    adjust memory quota

  6. "Impersonate a client after authentication"
    impersonate client-1052x758

    impersonate client

  7. Please make sure that the policies don't get changed afterwards.
  8. Run a clear configuration cache
  9. Start a full crawl and the errors should be gone.
Advertisements

Site slow taking long time querying sharepoint

What you can do if SharePoint is sometimes very slow.

E.g.: on the first start of a Site

Sometimes during the day a search query will take about a minute until you get results…..

  1. Just look on that article: http://support.microsoft.com/kb/2625048

it will improve your “feeled” performance (site response times) massive, if you’re going to implement both solutions.

  1. Disabling CRL Check is just necessary if the SP Server does not have internet connectivity! -> that means proxy settings must be configured for the server itself

http://technet.microsoft.com/de-de/library/bb430772(v=exchg.141).aspx, and your proxy must allow traffic from the server of course.

filename invalid or too long 1920x1080

filename invalid or too long SharePoint

Advertisements
Advertisements

The filename invalid or too long. Specify a different filename

"The filename invalid or too long Specify a different filename" error while opening document library in windows explorer mode.

File name invalid or too long

File name invalid or too long

For testing  I tried to upload a single file using browser but its generated error as below:

Sorry, something went wrong.The URL ‘Shared documents/Project budget.xlsx’ is invalid.

File name invalid or too long

File name invalid or too long

Actually filename is not very long at all, including the full path. I looked into the ULS logs (for the time i tried to upload file) and found log as as below:

Exception thrown storing stream in new SqlRemoteBlob: System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> Microsoft.Data.SqlRemoteBlobs.BlobStoreException: There was a generic database error. For more information, see the included exception. —> System.Data.SqlClient.SqlException: RBS Error. Original Error: Number 297, Severity 16, State 1, Procedure rbs_fs_sp_check_pool_size, Line 31, Message: The user does not have permission to perform this action.  Transaction count after EXECUTE indicates a mismatching number of BEGIN and COMMIT statements. Previous count = 1, current count = 0.     at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)

I have RBS (Remote Blob Storage) enabled for this content database so it appears that, this has got messed up somehow.  After reading various other blog posts and TechNet articles I began some trial and error with the database permissions.

Solution :

So as to resolve this issue we need to grant the service account used by the application pool "db_owner" rights on the content database, in addition to the "db_rbs_* " permissions.

File name invalid or too long

File name invalid or too long

The original error about the filename being too long or invalid is very misleading, there is no hint of a permissions.

Advertisements
Advertisements