Cause: "The specific user or domain group was not found"
Solution: In MOSS 2007, you will have access to change the service accounts and there is no concept like register managed account. Once you changed the service account which deleted from AD and still available in MOSS 2007.
When looking a solution for SharePoint 2010 as well as SharePoint 2013, First we need to find what the ID which is blocking the service application to do its work.
To find that account execute the following powershell command in SharePoint PowerShell.
Solution: In MOSS 2007, you will have access to change the service accounts and there is no concept like register managed account. Once you changed the service account which deleted from AD and still available in MOSS 2007.
When looking a solution for SharePoint 2010 as well as SharePoint 2013, First we need to find what the ID which is blocking the service application to do its work.
To find that account execute the following powershell command in SharePoint PowerShell.
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEhcwcqODy5izUUd2uw3JviadOIY8YfFbJ4ubDdI-hr99x2Qz2Gg61TyIFRpAFZT9Oo53vfWvdPpEW2MxuHrnoVtBMtPVgSNRdb3BKXheqV1c7HSgLRrG8RXftFGIg1ebIOIluve_HFIlg/s400/1.jpg)
Now i know the Service Application which making me the problem, then need to execute the following query in MSSQL server at SharePoint Config Database.
SELECT [Name], [Version], CAST([Properties] as xml) from [SharePoint_Config].[dbo].[Objects] with (nolock) Where [Name] LIKE '%PPS1%'
The result of the above query will give lot of XML files open the latest one and traverse it from last line. You will get the details which are the account have mapped with the service application using that you will come to know the User account which making the problem.
If you are working in Enterprise environment ask the AD team to recreate the account in domain with deny logon to the machine.
Restart the SharePoint server once, Now you will able to pick the user id from domain and you will have access service application page as well as configure service account page.
Change the account every where using UI itself, and then verify it through powershell. Like the below.
Get-SPServiceApplicationPool | FL Id,Name,*account*
now you output will updated with the account with configured for the service application. And remove the account from SharePoint farm.
1. Change the service account.
2. Remove the permission if it have any delegate permission to any service application.
3. Remove from Managed Account.
4. Delete the account from AD as well.
Now your won't get the issue.
Note: Without recreating the account in AD there is no other way to solve the issue. If it is development environment and it doesn't have any data or any customization, Take web application content database break the farm and recreate a farm freshly.
Thanks in Advance!!!