Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

How to remove an errant WebPart from a SharePoint site

Posted on 2012-04-05
6
Medium Priority
?
721 Views
Last Modified: 2012-04-05
I am working on a SharePoint site that was restored to a development machine from a test server. Whenever I try to compile and build a new Web Part that I am working on from Visual Studio, I get the following error (in the browser Window):

Line 1:  <%@ Register TagPrefix="WpNs3" Namespace="<ProjectName>.WeatherMap" Assembly="<ProjectName>, Version=4.0.0.0, Culture=neutral, PublicKeyToken=0521399ff9cdd4c1"%>

The ENTIRE error page looks like this:

Server Error in '/' Application.
--------------------------------------------------------------------------------

Parser Error
Description: An error occurred during the parsing of a resource required to service this request. Please review the following specific parse error details and modify your source file appropriately.

Parser Error Message: Could not load file or assembly '<ProjectName>, Version=4.0.0.0, Culture=neutral, PublicKeyToken=0521399ff9cdd4c1' or one of its dependencies. The system cannot find the file specified.

Source Error:


Line 1:  <%@ Register TagPrefix="WpNs3" Namespace="<ProjectName>.WeatherMap" Assembly="<ProjectName>, Version=4.0.0.0, Culture=neutral, PublicKeyToken=0521399ff9cdd4c1"%>
Line 2:  <%@ Register TagPrefix="WpNs2" Namespace="<ProjectName>.GenericStatus" Assembly="<ProjectName>, Version=4.0.0.0, Culture=neutral, PublicKeyToken=0521399ff9cdd4c1"%>
Line 3:  <%@ Register TagPrefix="WpNs1" Namespace="<ProjectName>.Forecast" Assembly="<ProjectName>, Version=4.0.0.0, Culture=neutral, PublicKeyToken=0521399ff9cdd4c1"%>
 

Source File: /cnic/default.aspx    Line: 1

Assembly Load Trace: The following information can be helpful to determine why the assembly '<ProjectName>, Version=4.0.0.0, Culture=neutral, PublicKeyToken=0521399ff9cdd4c1' could not be loaded.


WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

 


--------------------------------------------------------------------------------
Version Information: Microsoft .NET Framework Version:2.0.50727.5448; ASP.NET Version:2.0.50727.5456
0
Comment
Question by:Rahsaan-Pringle
  • 4
  • 2
6 Comments
 
LVL 32

Expert Comment

by:Jamie McAllister MVP
ID: 37812478
Append the querystring argument "?contents=1" to the page url. Use the options that are displayed to delete the webpart from the page.
0
 

Author Comment

by:Rahsaan-Pringle
ID: 37812527
That was certainly useful, thanks. It didn't solve the problem (this is the SharePoint install from hell). I did try it, and I rebooted IIS after deleting some of the web parts that were showing as having errors.
0
 
LVL 32

Accepted Solution

by:
Jamie McAllister MVP earned 2000 total points
ID: 37812561
So what's the remaining errors?

From looking at the message, your page references features and components that have not been installed on this other server. Just the content database has been moved over?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:Rahsaan-Pringle
ID: 37812640
Attached, you will find a PDF with screenshots of what I am seeing. You say I might not have features activated? That's odd, because the site runs fine BEFORE I run the code in debug mode in Visual Studio. Even the web part in question (known as the WeatherMap) looks fine until I try to debug.
Visio-Drawing3.pdf
0
 

Author Comment

by:Rahsaan-Pringle
ID: 37812774
I DID have some features that were not activated, but none of them had to do with the "WeatherMap" Web Part. Following your lead, I activated them all, and the error went away. Now, I'm reloading the site to make sure it works.
0
 

Author Closing Comment

by:Rahsaan-Pringle
ID: 37812827
Moral of the story: Even if you don't think your Web Part is connected to a feature, it might be.
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

There is one common problem that all we SharePoint developers share: custom solution deployment. This topic can't be covered fully in this short article, so all I want to do in this one is to review it from a development-to-operations perspectiv…
Microsoft SharePoint Foundation 2010 and Microsoft SharePoint Server 2010 do not offer the option to configure the location of the SharePoint diagnostic trace log files during installation.  This can, however, be configured through Central Administr…
This course is ideal for IT System Administrators working with VMware vSphere and its associated products in their company infrastructure. This course teaches you how to install and maintain this virtualization technology to store data, prevent vuln…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…
Suggested Courses

972 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question