locked
Error occurred in deployment step 'Add Solution': Operation is not valid due to the current state of the object RRS feed

 > 

Answers

All replies

  • Question
    Sign in to vote
    3
    Sign in to vote

    This issue cause because of feature activation failure while WSP deployment.

    when you create a WSP using visual studio, it creates WSP package with default deployment configuration settings.

    Please restrict feature activation configuration, this will help you to troubleshoot this issue.

    - Click on Project in WSP and press F4, it will open "Project Properties"

    - set "Active deployment Configuration" - as "No Activation"

    - you can activate this features in required sequence after deployment using Activate-SPFeature

    Deployment Configuration

    If my contribution helps you, please click Mark As Answer on that post and Vote as Helpful

    Thanks, ShankarSingh(MCP)


    Saturday, August 9, 2014 6:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    the above suggestion didnt work for me. i am  getting the same errors.

    i tried  adding the solution using  stsadm -addsolution cmd  also.

    stsadm -o addsolution -filename "yourProyectName.wsp"

    that also  failed to  execute.

    Can any other reason for this?



    Monday, August 11, 2014 6:03 AM
  • Question
    Sign in to vote
    3
    Sign in to vote

    HI Benjamin,please check the below thread that relates to the issue.

    http://expertsharepoint.blogspot.de/2014/02/error-while-deploying-solutions-in.html

    http://expertsharepoint.blogspot.de/2014/07/deployment-of-solutions.html

    Anil Avula[MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/

    • Marked as answer by Lindali Friday, August 15, 2014 2:47 AM
    Monday, August 11, 2014 6:24 AM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Please check if solution already exists in Solution gallery, if it exists please retract/remove from Solution gallery.

    - Restart "SharePoint Timer Service" on all the servers and try adding solution with -Force

    - If you have more then one APP/WFE, please make sure that "SharePoint Timer Service" should running on all the server

    If my contribution helps you, please click Mark As Answer on that post and Vote as Helpful

    Thanks, ShankarSingh(MCP)

    • Marked as answer by Lindali Friday, August 15, 2014 2:47 AM
    Monday, August 11, 2014 7:38 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks it works

    Monday, January 18, 2016 11:17 AM