Asked by:
SharePoint central admin throws error 503

Question
-
After relocating and changing the ip address of active directory DC, SharePoint central admin throws error 503 .Also Starting the SharePoint CA application pool manually through the IIS dose not work and it keeps stopping itself after about 2 minutes.
Does anyone knows how can i solve this?
All replies
-
Hi,
Can you check if your DNS server have the correct IP address of your domain controller?
- Run the command line.
- Type nslookup.
- Type server DNS_ip_address // #change the "DNS_ip_address" with yours.
- Enter the hostname of your domain controller.
On the Sharepoint server, run the following command line (as admin): ipconfing /flushdns to clear the DNS cache client.
Regards,
SAAD Youssef
______
Please remember to mark the replies as answer if they help, thank you!
- Edited by SAAD Youssef Tuesday, July 16, 2019 4:41 PM
- Proposed as answer by Sara FanMicrosoft contingent staff, Moderator Wednesday, July 17, 2019 2:38 AM
-
Hi SAAD Youssef,
To troubleshoot the issue, check things below:
1. Restart the central administration site in IIS. Go to IIS->expand the sites->select the central administration site->Click Restart in the right panel.
2. Recycle central administration application pool in IIS. Go to IIS->Application Pools->select “SharePoint Central Administration v4” Application Pool->Click “Recycle” in the right panel.
More reference:
Changing the IP Address of a Domain Controller.
https://www.petri.com/change-ip-address-domain-controller
Best regards,
Sara Fan
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
SharePoint Server 2019 has been released, you can click here to download it.
Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019. -
-
-
Hi SAAD Youssef,
To troubleshoot the issue, you could change or re-type the identity of the “SharePoint Central Administration v4” Application Pool.
Go to IIS->Application Pools->right click “SharePoint Central Administration v4” Application Pool->advanced settings->Process Model->Identity->change to another user or re-type the user and password.
Best regards,
Sara Fan
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
SharePoint Server 2019 has been released, you can click here to download it.
Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019. -
-
Hi SAAD Youssef,
Troubleshoot the issue, check things below:
1. Reset IIS.
2. Run SharePoint 2013 products configuration wizard.
Best regards,
Sara Fan
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
SharePoint Server 2019 has been released, you can click here to download it.
Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.- Proposed as answer by Wendy DZMicrosoft contingent staff, Moderator Friday, July 19, 2019 8:49 AM
-
Hi SAAD Youssef,
How is everything going?
Is there anything update about this issue?
If the reply is helpful to you, you could mark the reply as answer. Thanks for your understanding.
Best regards,
Sara FanPlease remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
SharePoint Server 2019 has been released, you can click here to download it.
Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019. -
Hi Moderator
when I run configuration wizard, I encounter a "Failure to register SharePoint Services" error on Step: 5
An exception of type Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException was thrown. Additional exception information: An update conflict has occurred, and you must re-try this action. The object SPWebService was updated by DOMAIN\user, in the OWSTIMER(88304) process, on machine MACHINENAME. View the tracing log for more information about the conflict.
- Edited by LB-softcom Saturday, July 20, 2019 5:56 AM
-
-
Try Clearing the Config Cache from the below article and try running the below command.
https://github.com/DwayneSelsig/spcachecleaner/blob/master/SPCacheCleaner.ps1
PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -cmd services -install
Thanks & Regards,sharath aluri
- Proposed as answer by Wendy DZMicrosoft contingent staff, Moderator Thursday, July 25, 2019 4:43 AM
-
Hi SAAD Youssef,
After clear configuration cache, you could run SharePoint 2013 products configuration wizard.
For more detailed information, refer to the article below.
There is a similar post:
Best regards,
Sara Fan
Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
SharePoint Server 2019 has been released, you can click here to download it.
Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.- Proposed as answer by Wendy DZMicrosoft contingent staff, Moderator Thursday, July 25, 2019 4:43 AM
-
Hi SAAD Youssef,
How is everything going?
Is there anything update about this issue?
If the reply is helpful to you, you could mark the reply as answer. Thanks for your understanding.
Best regards,
Sara FanPlease remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.
SharePoint Server 2019 has been released, you can click here to download it.
Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.