Al habilitar el blob cache en un sitio de publicación, después de cierto tiempo (pueden ser días, o incluso semanas) empieza a registrarse un par de errores en el Application Log:
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Publishing Cache
Event ID: 5538
Date: 5/6/2008
Time: 4:34:51 PM
User: N/A
Computer: PRONOSTIC04
Description:
An error occured in the blob cache. The exception message was 'Access to the path 'C:\blobCache\1998969947\21eb88ef-e87f-4f3c-80d6-67b818822736.bin' is denied.'.
Event Type: Error
Event Source: Office SharePoint Server
Event Category: Office Server General
Event ID: 7888
Date: 5/6/2008
Time: 4:34:51 PM
User: N/A
Computer: PRONOSTIC04
Description:
A runtime exception was detected. Details follow.
Message: Access to the path 'C:\blobCache\1998969947\21eb88ef-e87f-4f3c-80d6-67b818822736.bin' is denied.
Techinal Details:
System.UnauthorizedAccessException: Access to the path 'C:\blobCache\1998969947\21eb88ef-e87f-4f3c-80d6-67b818822736.bin' is denied.
at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
at Microsoft.SharePoint.Publishing.BlobCache.WriteIndex(Boolean tokensOnly)
at Microsoft.SharePoint.Publishing.BlobCache.<>c__DisplayClasse.<CheckSiteChanges>b__a()
at Microsoft.Office.Server.Diagnostics.FirstChanceHandler.ExceptionFilter(Boolean fRethrowException, TryBlock tryBlock, FilterBlock filter, CatchBlock catchBlock, FinallyBlock finallyBlock)
Jussi Paolo tiene un post donde resuelve el problema http://howtocode.blogspot.com/2007/11/moss-blogcache-not-working.html, el dar permisos a la cuenta IIS_WPG hizo desaparecer el error!! Bueno, además desactive el blobcache, borre las carpetas, y lo volvi a activar.
Si en algunos dias o la proxima semana vuelve a aparecer el error, veran otro post al respecto... esperemos que no :D