Monthly Archive for September, 2008

The feature name XXX already exists in SharePoint. You need to rename the feature before solution deployment can succeed.

From time to time when I try to deploy a SharePoint project from Visual Studio 2005 I’m getting this error:

The feature name XXX* already exists in SharePoint. You need to rename the feature before solution deployment can succeed.

Solution
Whenever I get this (annoying) error I go to C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\FEATURES\ and remove the directory named XXX*. Sometimes then I need to restart Visual Studio or even log off and on again (on my Windows account).

17/102008
Sometimes restarting Visual Studio does the job.

* is the name of the module that should be deployed

Reblog this post [with Zemanta]
Share and Enjoy:
  • del.icio.us
  • Digg
  • Technorati
  • Reddit
  • StumbleUpon
  • description
  • Wykop
  • Gwar
  • E-mail this story to a friend!

Visual Studio: The language-neutral solution package was not found.

I’m getting this (and a few more, which maks me frustrated) error from time to time when I try to deploy a SharePoint project from Visual Studio 2005 (under Windows Server 2003 RC2)…

Solution:
Restart Visual Studio…

Share and Enjoy:
  • del.icio.us
  • Digg
  • Technorati
  • Reddit
  • StumbleUpon
  • description
  • Wykop
  • Gwar
  • E-mail this story to a friend!

ASPX running on Sharepoint - display stack trace

Should you need to see the stack trace when an error on an APSX page hosted by Sharepoint occurs do the following:

  • SharePoint\SafeMode: AllowPageLevelTrace="true" and CallStack="true"
  • system.web\customErrors:mode="Off" or mode="RemoteOnly"

Yet the standard error page usually does not tell aything that can suggest the reason for the error…

Share and Enjoy:
  • del.icio.us
  • Digg
  • Technorati
  • Reddit
  • StumbleUpon
  • description
  • Wykop
  • Gwar
  • E-mail this story to a friend!