none
Visual Studio Deployment Error : Error occurred in deployment step 'Recycle IIS Application Pool'

    Question

  • My Sharepoint Server and Development machine are different computers. Sharepoint Server is installed and running on a computer and my development machine is another computer (Sharepoint Server is installed on my development machine too).

    I create an Empty Sharepoint Project on my development machine. When I try to DEPLOY, there is an error:

    Error occurred in deployment step 'Recycle IIS Application Pool': Cannot connect to the SharePoint site: http://servername Make sure that this is a valid URL and the SharePoint site is running on the local computer. If you moved this project to a new computer or if the URL of the SharePoint site has changed since you created the project, update the Site URL property of the project.

    How can I solve this problem?

    Thanks

    Monday, November 14, 2011 3:56 PM

Answers

  • I see. Well it sounds like the SharePoint server is on a remote farm, in which case you can't click 'deploy' from VS and deploy straight to that server. I even struggled when it was on the same domain, but that's just me...

    see this post with the same problem: http://social.technet.microsoft.com/Forums/ar/sharepoint2010programming/thread/7f15edf6-33dc-4739-9fd5-4ee6c5d6fd56

    If you have SharePoint Server on your development machine, can't you debug on that machine (Change URL location to http://developmentmachine)? When you're ready to deploy on the server, copy the .wsp that is built as the package and deploy this solution on the server farm. We have the same setup as you (several developer machines) but we never deploy to remote farms, all the development machines are SharePoint servers that we use to debug locally then package up to deploy to live server later.

    Any good?

    • Marked as answer by pty33 Tuesday, November 15, 2011 9:01 AM
    Tuesday, November 15, 2011 8:55 AM

All replies

  • So, just trying to understand, you built a project on your development machine with a Site Url of http://developmentmachine, and you tried deploying it on your server of url http://servername? Or are you just deploying it on your development machine, in which case I'm not sure where your server fits into it all...

    Or are the two machines in some way connected on the same domain (I'm guessing not seeing as how you say you have SharePoint installed on both machines)? I'm not being funny, but have you tried to "update the Site URL property of the project" to the correct URL like it says, and then package and deploy it on the correct machine? Can you give the actual steps you've been through on each computer?

    Many thanks, Mike.

    Monday, November 14, 2011 5:00 PM
  • I have a site collection on SERVER and I want to build a Sharepoint project on DEVELOPMENT MACHINE. I create project (Site URL : http://servername) and I want to build it on DEVELOPER MACHINE. When I deploy this project from development machine (visual studio), it deploys to site collection on server. 

    I want to do this because 8 people will work on a site collection at same time and they have to work on their DEVELOPMENT MACHINEs.

    I painted this image :) 

    Note : I installed Sharepoint Server on DEVELOPMENT MACHINE because Sharepoint Projects want Sharepoint to be installed on developer machines. I asked about it on MSDN Forum and a MVP (Sharepoint) said this way.

    Monday, November 14, 2011 6:43 PM
  • I see. Well it sounds like the SharePoint server is on a remote farm, in which case you can't click 'deploy' from VS and deploy straight to that server. I even struggled when it was on the same domain, but that's just me...

    see this post with the same problem: http://social.technet.microsoft.com/Forums/ar/sharepoint2010programming/thread/7f15edf6-33dc-4739-9fd5-4ee6c5d6fd56

    If you have SharePoint Server on your development machine, can't you debug on that machine (Change URL location to http://developmentmachine)? When you're ready to deploy on the server, copy the .wsp that is built as the package and deploy this solution on the server farm. We have the same setup as you (several developer machines) but we never deploy to remote farms, all the development machines are SharePoint servers that we use to debug locally then package up to deploy to live server later.

    Any good?

    • Marked as answer by pty33 Tuesday, November 15, 2011 9:01 AM
    Tuesday, November 15, 2011 8:55 AM