Error Occurred in Deployment step 'Recycle IIS Application Pool'

Question

We have more than 3 developers working on a single solution file. Because of this, we cannot add them all in the site collection administrator menu.

When I deploy with administrator credentials in Visual Studio, I am able to successfully deploy to the particular SharePoint Application. When I login with any of these users, I am not able to. It gives me the below error:

Error occurred in deployment step 'Recycle IIS Application Pool': 
<nativehr>0x80070005</nativehr><nativestack></nativestack>Access denied

We have given administrative rights for these users' login to the Active Directory.

What can we do to resolve this issue?

Check all causes at [Error occurred in deployment step 'Recycle IIS Application Pool': The local SharePoint server is not available. Check that the server is running and connected to the SharePoint farm](https://blog.devoworx.net/2012/10/07/error-occurred-in-deployment-step-recycle-iis-application-pool-the-local-sharepoint-server-is-not-available-check-that-the-server-is-running-and-connected-to-the-sharepoint-farm/) — Mohamed, Apr 15 '18 at 18:47

score 25 · Accepted Answer · edited Feb 12 '15 at 21:08

25

I tried all the possible solutions with Active Directory, IIS Authentication and finally was able to fix the issue just by doing the below. Hope this will help you in similar kind of issue.

Do a IIS reset
Check if IIS is resetting.
If it is not, then disable UAC from control panel and IIS reset will work.
Go to Central Administration site
Navigate to the Manage Web Applications page
Click on the web application that hosts the site you are trying to deploy to
Click the User Policy ribbon item.
Add your windows account to the list of users with the Full Control permission.

It worked for me!

edited Feb 12 '15 at 21:08

Ryan Gates

4,501
6
50
90

answered Jan 23 '14 at 08:53

Alex Varghese

499
2
6
13

1

Second step worked for me. What is strange is that I had been deploying to the same server for weeks without any issues. Suddenly it stopped working, and started again to work after setting User Policy for the user. – Jussi Palo Jan 28 '15 at 12:32

score 8 · Answer 2 · answered Jul 22 '14 at 18:52

8

Make sure you're a site collection admin

answered Jul 22 '14 at 18:52

Peter Walke

2,497
6
33
50

Well for me it does provide an answer. I had the issue and this corrected it for me. – GBU Jun 08 '16 at 17:44

score 5 · Answer 3 · answered Dec 16 '14 at 16:43

5

The following worked for me:

Open the Sharepoint SQL Server database in Management Studio. The default name of it is SHAREPOINTWEB.
Under the Security folder, right click Logins and add the user who needs to deploy solutions. Grant them db_owner schema.

answered Dec 16 '14 at 16:43

mm201

526
4
15

I had the specific error of "the local sharepoint server is not available". This solution helped resolve that error. – Jim Yarbro Jan 06 '16 at 11:03

score 5 · Answer 4 · edited Feb 08 '17 at 15:02

5

OFFTOPIC:

Even though the problem is solved for the original poster, I came here because I had the same issue, and these solutions (and more found in the internet) didn't help me. This being said...

On-topic:

I'll add the solution that worked for me (in order to avoid duplicates), because it may help someone else:

Deploy the solution to fully created site collection

In Visual Studio 2010-2012:

Right click the Solution you want to deploy (in the Solution explorer)
Go to Properties
Go to the "Site URL" attribute. If the Site's URL you want to deploy it is incomplete (i.e: the port you are working on is missing), change it.

Example

This happened to me, since it was targeting http://webservice/ instead of http://webservice:123/

Source

edited Feb 08 '17 at 15:02

Community

1
1

answered May 12 '15 at 20:50

Mayer M

243
1
6
17

1

I was having the same problem, and this is the only one that fixed it. Dumb me had the wrong port. – tlbignerd Sep 13 '16 at 19:52
1

I even had the incorrect site, instead of machineName/sites/mySite I only had machineName there – rdmptn Sep 07 '17 at 13:02

score 2 · Answer 5 · answered Jun 19 '17 at 11:48

2

adding user as a db_owner of the content database solved my problem

answered Jun 19 '17 at 11:48

Mahmoud Farahat

5,364
4
43
59

score 1 · Answer 6 · answered Aug 15 '14 at 22:30

1

In my case, I closed and opened visual studio and it works for me

answered Aug 15 '14 at 22:30

Jamil Haddadin

51
3

score 0 · Answer 7 · edited Dec 15 '14 at 07:48

0

Run the Visual Studio as administrator and problem will be solved if any with Visual Studio permission.

edited Dec 15 '14 at 07:48

Andrew T.

4,701
8
43
62

answered Dec 15 '14 at 07:05

sharath m

1

score 0 · Answer 8 · answered May 20 '15 at 19:25

I came across this when I opened my SharePoint project in Visual Studio and then started my local SharePoint and SQL services (don't leave them running all the time to conserve resources).

The error went away once I closed and restarted Visual Studio once I verified SharePoint was running correctly in the background.

score 0 · Answer 9 · answered Oct 02 '15 at 06:44

I came across similar situation a year ago and fixed it but then I forgot how i did that. Last night once again it came up. I was trying to deploy a sharepoint solution and this error came up.

if you can then try to restart the server. Sometimes it takes care of most of the problems.

if not then make sure to add your machine's administrator account to sharepoint administration as full control. Why? because when you are deploying via Visual Studio you have to run Visual Studio as Administrator. So you need to ensure that sharepoint is also allowing this login to make changes.

score 0 · Answer 10 · answered Dec 29 '15 at 12:48

Even I was facing the issue now and then, but it once worked by changing the namespace and then I proceeded, but actually the issue was with the application pool account being locked due to password expiry and while resetting the IIS the app pool got disabled.

So the issue was the App pool account getting locked.

Regards Arvind

score 0 · Answer 11 · answered May 26 '17 at 08:26

I'm posting this answer because even as of SharePoint 2016 (Singer-Server Farm - aka Development Farm) and deploying with Visual Studio 2017, I was still getting this problem. Trying each of these answers was not giving me success.

In my case, re-running the SharePoint 2016 Products Configuration Wizard with your default settings, always solved this problem for me.

score 0 · Answer 12 · edited Sep 16 '20 at 06:43

0

One more potential fix for this, as the steps in this thread didn't work for me:

I had to assign myself as the site collection administrator

Central Administration
Application management
Change site collection administrators
Primary Site Collection Administrator => Your account

edited Sep 16 '20 at 06:43

Dharman

30,962
25
85
135

answered Sep 16 '20 at 06:38

GoranSu

479
4
9

score -1 · Answer 13 · edited Apr 29 '15 at 20:31

-1

On the IIS console, checked settings under Authentication. Enable windows and anonymous authentication.

edited Apr 29 '15 at 20:31

Ryan Gates

4,501
6
50
90

answered Jan 22 '14 at 09:03

user3202232

1
1

No Luck Garish... In the sharepoint application, we have used forms authentication aswell. – Alex Varghese Jan 22 '14 at 10:05

Error Occurred in Deployment step 'Recycle IIS Application Pool'

13 Answers13