SharePoint 2010 Using blob caching throws many errors in the ULS and Event Logs -The system cannot find the file specified

 

Various ULS Logs errors:

· "An error occurred in the blob cache. The exception message was: 'The system cannot find the file specified. (Exception from HRESULT: 0x80070002)'."

· GetFileFromUrl: FileNotFoundException when attempting get file Url /favicon.ico The system cannot find the file specified. (Exception from HRESULT: 0x80070002)    at Microsoft.SharePoint.Library.SPRequestInternalClass.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid& pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)     at Microsoft.SharePoint.Library.SPRequest.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid& pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)     at Microsoft.SharePoint.SPWeb.GetListItem(String strUrl, Boolean bFields, String[] fields)     at Microsoft.SharePoint.Publishing.CommonUtilities.GetCurrentFileVersionFromUrl(String url, SPWeb web)

· Error in blob cache. System.IO.FileNotFoundException: The system cannot find the file specified. (Exception from HRESULT: 0x80070002)     at Microsoft.SharePoint.Library.SPRequestInternalClass.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid& pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)     at Microsoft.SharePoint.Library.SPRequest.GetMetadataForUrl(String bstrUrl, Int32 METADATAFLAGS, Guid& pgListId, Int32& plItemId, Int32& plType, Object& pvarFileOrFolder)     at Microsoft.SharePoint.SPWeb.GetListItem(String strUrl, Boolean bFields, String[] fields)     at Microsoft.SharePoint.Publishing.CommonUtilities.GetCurrentFileVersionFromUrl(String url, SPWeb web)     at Microsoft.SharePoint.Publishing.CommonUtilities.GetPublishedFile(SPWeb web, ULSCat ulsCategory, String fileUrl, SPFile& file, SPListItem& item)     at Microsoft.SharePoint.Publishing.BlobCache.<>c__DisplayClass34.<>c__DisplayClass37.<FetchItemFromWss>b__31()     at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)

· Unable to cache URL /FAVICON.ICO.  File was not found

Event Log error:

Log Name:      Application

Source:        Microsoft-SharePoint Products-Web Content Management

Date:          7/30/2013 1:57:45 PM

Event ID:      5538

Task Category: Publishing Cache

Level:         Error

Keywords:     

User:          CONTOSO\SPSvc

Computer:      SP.contoso.com

Description:

An error occured in the blob cache.  The exception message was 'The system cannot find the file specified. (Exception from HRESULT: 0x80070002)'.

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

  <System>

    <Provider Name="Microsoft-SharePoint Products-Web Content Management" Guid="{0219F589-72D7-4EC3-ADF5-1F082061E832}" />

    <EventID>5538</EventID>

    <Version>14</Version>

    <Level>2</Level>

    <Task>1</Task>

    <Opcode>0</Opcode>

    <Keywords>0x4000000000000000</Keywords>

    <TimeCreated SystemTime="2013-07-20T18:57:45.255293200Z" />

    <EventRecordID>308352</EventRecordID>

    <Correlation />

    <Execution ProcessID="3052" ThreadID="2236" />

    <Channel>Application</Channel>

    <Computer>www.contoso.com</Computer>

    <Security UserID="S-1-5-21-1385174992-979951090-295046656-1108" />

  </System>

  <EventData>

    <Data Name="string0">The system cannot find the file specified. (Exception from HRESULT: 0x80070002)</Data>

  </EventData>

</Event>

Status:

We are aware of this issue and are currently investigating. 

 

This issue has been fixed as part of December CU for SharePoint 2010

KB 2849971 - SharePoint Server 2010 (SharePoint server-package)

This specific issue is described in the article KB 2849989 (which is included in the above SharePoint Server hotfix package)

The fix is as follows,

a.  The Exception log entry in the ULS is no more present with default level of logging.

b.  The Event viewer log entry is no more present with default level of logging.

c.  The mini-dump generation has stopped.

d.  We will continue to log a ‘Monitorable’ level entry.

Though few customers have confirmed the issue as resolved, we have heard back from some that the issue still persists. Investigation is on.

 

Blog By : Vijay Gangolli [MSFT]