CFS issue when referencing images via handler to UNC virtual for /filestorage

CFS issue when referencing images via handler to UNC virtual for /filestorage

This question is answered

We host our community on a web farm of 3 servers.  Our images are on a centralized content server so we've mapped /filestorage to a UNC share.  This works fine most of the time, but about once a week our images in blog posts, etc won't show up.  When I try to hit a full path URL (that references a file using the cfs-filesystemfile.ashx image handler) I get a 404.  However when I try to access the file without the handler by referencing the complete file path - http://mydomain.com/filestorage/CommunityServer.Blogs.Components.WeblogFiles/00/00/00/00/12/... the file returns just fine.  We know this is therefore not an issue with the UNC share disconnecting but an issue somehow in the community.

Does anyone have any suggestions as to what might be the issue?  Thanks!

Verified Answer
All Replies
  • The recommended approach for sharing files in a Web Farm is to update the baseUrl path of the CFS filestore node in communityserver.config

    telligent.com/.../web-farm-configuration.aspx

    If that is what you've done, then you should *not* be able to access media via mydomain.com/filestorage.

  • ~/filestorage/ is the basePath for all our fileStore nodes.  We can't set the basePath to a UNC because we need to use an identity other than Network Service.

  • In that case you should either set your Application Pool Identity to use a user account which can access a UNC share, or configure Impersonation - see msdn.microsoft.com/.../ms998351.aspx for more details.

  • With the application pool identity are you suggesting to still use the communityserver.config filestorage basePath overrides?

  • This seemed to solve the issue at least temporarily.  Only time will tell if it works for the long haul.