none
Solution cannot be deployed. RRS feed

  • Question

  • I have tried to build a solution while workign in my development envrionment on the server and get the following error. Does I don's see these items in the GAC, and am not sure how to purge the old one so that i can deploy the new. Can anyone telll me how to do this ?

    Error 1 The solution can not be deployed.  The feature 'ac20bb8e-2969-4b88-afbb-b09c81758bbb' uses the directory "AjaxifiedWebPart_ac20bb8e-2969-4b88-afbb-b09c81758bbb" in the solution. However, it is currently installed in the farm to the directory "Actu20250u3Au20Ajaxifiedu20Webu20Partu20-u20Abstract_ac20bb8e-2969-4b88-afbb-b09c81758bbb". Uninstall the existing feature before you install a new version of the solution.  0 0 
    Monday, June 22, 2009 5:00 PM

Answers

  • I would try removing the old feature you don't want with stsadm.  i.e.: stsadm -o uninstallfeature -name Actu20250u3Au20Ajaxifiedu20Webu20Partu20-u20Abstract_ac20bb8e-2969-4b88-afbb-b09c81758bbb -force.  Once you get it to remove it, completely retract your solution and then readd and deploy it.
    Corey Roth blog: www.dotnetmafia.com twitter: twitter.com/coreyroth
    • Marked as answer by Aaron Han - MSFT Friday, July 3, 2009 7:14 AM
    • Edited by CoreyRoth [MVP]MVP Thursday, September 2, 2010 2:51 PM changed deletefeature to uninstallfeature
    Monday, June 22, 2009 7:01 PM

All replies

  • Hello,

    the issue is simple. Actually, you're trying to install a feature on which you have changed the name of the directory.

    You developp the feature X, with a name. After, you edited this feature and renamed the directory and then you try to deploy it, so there is a conflict. You have to unistall your feature before trying to deploy the new version.

    You can open the central administration and go to Operation > Solution Management. You localize your feature, you click on it and click on Retract Solution. You wait for the job to execute, you click again on your feature and if Remove Solution appeard, you click on it. Otherwise, if retract solution appears again, you click on it, in the drop down, you select the webApp in which you central administration is running, and you retract the solution and remove it after.

    After that, you will be able to deploy the new version of your feature ;-)
    http://www.areaprog.com
    Monday, June 22, 2009 6:22 PM
  • I would try removing the old feature you don't want with stsadm.  i.e.: stsadm -o uninstallfeature -name Actu20250u3Au20Ajaxifiedu20Webu20Partu20-u20Abstract_ac20bb8e-2969-4b88-afbb-b09c81758bbb -force.  Once you get it to remove it, completely retract your solution and then readd and deploy it.
    Corey Roth blog: www.dotnetmafia.com twitter: twitter.com/coreyroth
    • Marked as answer by Aaron Han - MSFT Friday, July 3, 2009 7:14 AM
    • Edited by CoreyRoth [MVP]MVP Thursday, September 2, 2010 2:51 PM changed deletefeature to uninstallfeature
    Monday, June 22, 2009 7:01 PM
  • You need to deactivate the feature and then uninstall it.
    Use stsadm -help deactivatefeature and stsadm -help uninstallfeature for syntax.
    if that doesn't work you could try to use -force
    (e.g. stsadm -o uninstallfeature -filename "......" -force) or something like that. But I would try to avoid it because this method leaves a lot of mess behind.

    Monday, June 22, 2009 7:28 PM
  • Is there any down time on the sharepoint server associated with implementing this sollution?  Also does this sollution change any of the sharpoint databases or are all the changes local to the front end sharepoint server?
    Wednesday, October 28, 2009 9:37 PM
  • The feature that you are retracting and anything that depends on your feature will not be available to Sharepoint after you retract it, but the rest of sharepoint that does not depend on your feature will continue to run with no downtime.

    And yes, the databases are affected by this feature.  The databases keep track of what web application your solution is deployed to, where your feature has been activated, and possibly many other things such as web part properties, etc., depending on what is included in your feature.  But removing a feature shouldn't change the content of any lists or document libraries.

        Tim

    Wednesday, October 28, 2009 10:42 PM
  • I don't get it. STSADM -o deletefeature doesn't even exist... Do you mean STSADM -o uninstallfeature?
    Thursday, September 2, 2010 2:48 PM
  • Sorry.  -o uninstallfeature is correct.  I updated my post to reflect that.
    Corey Roth blog: www.dotnetmafia.com twitter: @coreyroth
    Thursday, September 2, 2010 2:51 PM
  • I would try removing the old feature you don't want with stsadm.  i.e.: stsadm -o uninstallfeature -name Actu20250u3Au20Ajaxifiedu20Webu20Partu20-u20Abstract_ac20bb8e-2969-4b88-afbb-b09c81758bbb -force.  Once you get it to remove it, completely retract your solution and then readd and deploy it.
    Corey Roth blog: www.dotnetmafia.com twitter: twitter.com/coreyroth


    Thank you.. It is worked for me.. my error is

    The solution can not be deployed.  Directory "SiteElementse60eadd4-5ca5-4e19-9d04-23c72bbffbb7" associated with feature '0ce7c175-a265-4fe2-92a6-b1f2871db1a0' in the solution is used by feature 'ea79ebe9-c9b1-46a4-aa7c-1087efc90539' installed in the farm. All features must have unique directories to avoid overwriting files.

    Monday, October 11, 2010 9:58 AM