2

I have restored the sharepoint WFE server to roll back some changes, and now I get Service Unavailable

HTTP Error 503. The service is unavailable.

My farm consists of 1 WFE and 1 SQL server.

What could the reason for the error be?

Improve this question
7
  • can you check IIS pools and sites if are Started? Commented Feb 16, 2019 at 18:06
  • The server says "the specified network password is not correct" when I try to log on so I c an't check IIS either... Commented Feb 16, 2019 at 20:32
  • probably problem with the time on servers, try to update it (try to log as local computer admin) or try to update time with an PS with remote control Commented Feb 16, 2019 at 21:19
  • after you log to your server, probably IIS pools will be stopped, cause there were maybe problems with identities, so refresh paswords and start pools and sites. Commented Feb 16, 2019 at 21:20
  • if it will be done, i will create answer and you can mark it :) hope it helps Commented Feb 16, 2019 at 21:20

2 Answers 2

Reset to default
2

This issue usually occurs in case of

The App pool of your web application is stopped.

If you got this issue after the restart that means

You have recently changed the password of your APP pool Identity from Active Directory that not reflected directly to the IIS and needs to be reflected manually.

In your case, you can't connect to the IIS and you got

The specified network password is not correct.

That means there is an issue in your network occurred after the restart, and you should check it with

Once this issue solved, try to

  • Open ISS.
  • Go to Application Pools.
  • Check the App Pool of your web application.
  • Make sure it's started properly, and try to restart it again.

  • If it's stopped, try to update the App Pool Identity as the following:

    • Right Click > Advanced Settings.
    • Check Identity, and provide it again in a correct manner.

    enter image description here

    • Restart The App Pool.
    • Browse your web app that should be browsed properly.
Improve this answer
1

It was actually just a trust relationship issue with AD. Once that was solved server and SharePoint were up.

Improve this answer
1
  • Please mark as answer. Commented Oct 30, 2019 at 11:59

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.