The circle of life – ** .Net – Training – MOSS **

  • Past Post

  • Vistor Locations

  • Advertisements

VSeWSS Deployment Issues

Posted by Clayton James on November 4, 2008

I have come across a few deployment issues using VSeWSS. These issues can be time consuming so I am going to start posting Errors and Solutions.
Note: There obviously may be more than one solution to an error so don’t take this as Gospel.

  1. Error
    – Feature ’75a0fea7-c54f-46b9-86b1-2e103a8fedba’ is not installed in this farm, and can not be added to this scope
  2. Solution
    – I had an error in my web.config file. As soon as I fixed this I redeployed from VSeWSS
  1. Error
    – This solution contains two assemblies with the same name, or the SharePoint server already has an assembly with the specified name
  2. Solution
    – Uninstall the assembly from bin or GAC and then redeploy from VSeWSS
  1. Error
    – The Feature name …. already exists in SharePoint. You need to rename the Feature before solution deployment can succeed
  2. Solution
    Deactivate the feature (if it is activated)
    Delete the Feature …. from the 12/Template/Feature directory and redeploy from VSeWSS
  1. Error
    Cannot find this file specified in the manifest file: FileName …
  2. Solution
    Open the Manifest file (Use WSP View) and remove the offending line and redeploy from VSeWSS
  1. Error
    Feature …. is already activated at scope [url]
  2. Solution
    – Deactivate feature through UI or stsadm if hidden

5 Responses to “VSeWSS Deployment Issues”

  1. Badarinath said


    Thank you very much for this simple and yet effective solution. I was struggling for last 2 days.

    I could accomplish this in just half an hour.

    Thanks buddy…..

  2. Karl Parsons said

    I had some of the errors above and the mentioned solutions seemed to do the trick, great post!

    I am getting a new error now though when trying to Deploy my custom action from Visual Studio 2008:
    “Attempted to perform an unauthorized operation.”

    Not a very helpful message 😦 Do you have any idea what this means or how to solve it?? (Is it a permissions thing?)

  3. Karl Parsons, i had the same error and i added the user that RDP’s to the server into Site Collection Administrators and the error disapeared. Hope it helps

  4. Mustafa said

    how to add the user to RDP’s to the server into site collection Administrators

  5. manish Nath Choudhary said

    Hi friends ,

    Please do these code 101% you will resolve this issue .


    stsadm -o addsolution -filename “C:\Inetpub\wwwroot\wss\VirtualDirectories\WSP\ApplicationTemplateCore.wsp”

    stsadm -o deploysolution -name “ApplicationTemplateCore.wsp” -allowgacdeployment -immediate -force

    stsadm -o copyappbincontent


    stsadm -o addsolution -filename “C:\Inetpub\wwwroot\wss\VirtualDirectories\WSP\ProjectTrackingWorkspace.wsp”

    stsadm -o deploysolution -name “ProjectTrackingWorkspace.wsp” -allowgacdeployment -immediate -force

    stsadm -o copyappbincontent

    actually firstly you need to download ApplicationTemplateCore.wsp from mirosoft site then another one . Enjoy thing i waste my 4-5 hr then hit and trial resolve this .


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: