asked on

Share Point WSS error on check out and deleting documents from Document Library

After much digging into the WSS logs message that I believe is the reason why documents cannot be checked out or deleted:

“Error when trying to get trusted forests and domains. Exception message: The specified domain either does not exist or could not be contacted. Name: "ad.mpc.com" , callstack: at System.DirectoryServices.ActiveDirectory.Locator.GetDomainControllerInfo(String computerName, String domainName, String siteName, Int64 flags) at System.DirectoryServices.ActiveDirectory.Utils.GetPolicyServerName(DirectoryContext context, Boolean isForest, Boolean needPdc, String source) at System.DirectoryServices.ActiveDirectory.Forest.GetTrustsHelper(String targetForestName) at System.DirectoryServices.ActiveDirectory.Forest.GetAllTrustRelationships() at Microsoft.SharePoint.Utilities.SPUserUtility.GetTrustedDomains(List`1 trustedForestNames, List`1 trustedDomainNames)

Please let me know if you have seen this kind of errors and how can it be fixed.

rlog

Has this server been moved from one domain to another? ad.mpc.com - windows can't connect to any domain controllers in this domain for user verification. You could check if any trusts are removed between any domains.

nsdlsandy

ASKER

Did that and added new IP address to the Host , pinged and verified that it is correct.
Now getting Error

RPC method = url to web url
RPC method = open service
RPC method = getDocsMetaInfo
in getDocsMetaInfo after getlinks
RPC method = server version
Unexpected query execution failure, error code 8144. Additional error information from SQL Server is included below. "Procedure or function proc_FetchDocForRead has too many arguments specified." Query text (if available): "{?=call proc_FetchDocForRead(?,?,?,?,?,?,?,?,?,?,?,?,?,?,?,?)}"
RPC method = get document

ASKER CERTIFIED SOLUTION

nsdlsandy

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

nsdlsandy

ASKER

Used Microsoft support to resolve issue.