Every minute I receive the same error in the application-eventlog:

Application Server Administration job failed for service instance
Microsoft.Office.Server.Search.Administration.Sear chAdminSharedWebServiceInstance (32b9b3e1-7c3c-44eb-a163-6ab832e6cc40).

Reason: The specified account name is invalid.
Parameter name: account

Techinal Support Details:
System.ArgumentException: The specified account name is invalid.
Parameter name: account --->
System.Security.Principal.IdentityNotMappedExcepti on: Some or all identity
references could not be translated.
at
System.Security.Principal.NTAccount.Translate(Iden tityReferenceCollection
sourceAccounts, Type targetType, Boolean forceSuccess)
at System.Security.Principal.NTAccount.Translate(Type targetType)
at
Microsoft.Office.Server.Utilities.WindowsSecurity. ValidateAccount(NTAccount
account, Boolean throwIfInvalid)
--- End of inner exception stack trace ---
at
Microsoft.Office.Server.Utilities.WindowsSecurity. ValidateAccount(NTAccount
account, Boolean throwIfInvalid)
at Microsoft.Office.Server.Administration.SharedAcces sRule.Validate()
at
Microsoft.Office.Server.Administration.SharedCompo nentSecurity.SetAccessRule(SharedAccessRule accessRule)
at
Microsoft.Office.Server.Administration.SharedCompo nentSecurityFormatter.DeserializeFromXml(XmlReader xmlReader, SharedComponentSecurity& security)
at
Microsoft.Office.Server.Administration.SharedCompo nentSecurityFormatter.FromXmlString(String xml)
at
Microsoft.Office.Server.Administration.SharedResou rceProvider.InternalGetAccessControl()
at
Microsoft.Office.Server.Administration.SharedResou rceProvider.GetApplicationSecurity()
at
Microsoft.Office.Server.Administration.SharedWebSe rviceInstance.ProvisionSharedResourceProviderWebCo nfigSettings(SharedResourceProvider srp)
at
Microsoft.Office.Server.Administration.SharedWebSe rviceInstance.Synchronize()
at
Microsoft.Office.Server.Administration.Application ServerJob.ProvisionLocalSharedServiceInstances(Boo lean isAdministrationServiceJob)


I think this was started after leaving our primary Moss-administrator and
deleting his account in the AD.

What can I do to solve this?

With regards,

Hugo van Dort

When these jobs are created, they often require a worker process account to
run through. It is not a good practice to use your personal login for these
jobs, but it is a common mistake. You can either edit the job and change the
credentials it uses to run or delete and recreate. I would suggest creating a
service account and giving it only the permissions needed to run the job,
then use that account as the process account the job uses to startup.

Hope this helps,

-- Jerry