World is now on Opti ID! Learn more


May 6, 2009
  5151
(0 votes)

Solving The Issue :Failed to load some types from "EPiServer.Blog_Accessor”

 

This post is to solve an issue in the integration of EPiServer CMS5 R2 SP1 And Visual Studio .When you create a new EPiServer  project in Visual Studio 2008 and you don’t have VS Team Test  installed on your machine ,you might get an error message like this as and when you run the application :-

Message:-

Failed to load some types from "EPiServer.Blog_Accessor": Could not load file or assembly 'Microsoft.VisualStudio.QualityTools.UnitTestFramework, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: EPiServer.PlugIn.PlugInException: Failed to load some types from "EPiServer.Blog_Accessor": Could not load file or assembly 'Microsoft.VisualStudio.QualityTools.UnitTestFramework, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

This one had me baffled for a while.Thanks to Mr.Allan Thræn for getting this problem solved. It is actually a problem in the EPiServer CMS5 R2 SP1 And Visual Studio Integration, where an internal test dll (EPiServer.Blog_Accessor.dll) by accident has been included. That dll requires VS Team Test and if you don't have that installed you'll see the error above.

Solution:- The solution is easy, just delete the EPiServer.Blog_Accessor from your bin folder / remove it from your project.

May 06, 2009

Comments

Please login to comment.
Latest blogs
Make Global Assets Site- and Language-Aware at Indexing Time

I had a support case the other day with a question around search on global assets on a multisite. This is the result of that investigation. This co...

dada | Jun 26, 2025

The remote server returned an error: (400) Bad Request – when configuring Azure Storage for an older Optimizely CMS site

How to fix a strange issue that occurred when I moved editor-uploaded files for some old Optimizely CMS 11 solutions to Azure Storage.

Tomas Hensrud Gulla | Jun 26, 2025 |

Enable Opal AI for your Optimizely products

Learn how to enable Opal AI, and meet your infinite workforce.

Tomas Hensrud Gulla | Jun 25, 2025 |

Deploying to Optimizely Frontend Hosting: A Practical Guide

Optimizely Frontend Hosting is a cloud-based solution for deploying headless frontend applications - currently supporting only Next.js projects. It...

Szymon Uryga | Jun 25, 2025

World on Opti ID

We're excited to announce that world.optimizely.com is now integrated with Opti ID! What does this mean for you? New Users:  You can now log in wit...

Patrick Lam | Jun 22, 2025

Avoid Scandinavian Letters in File Names in Optimizely CMS

Discover how Scandinavian letters in file names can break media in Optimizely CMS—and learn a simple code fix to automatically sanitize uploads for...

Henning Sjørbotten | Jun 19, 2025 |