• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 879
  • Last Modified:

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.
  • 3
1 Solution
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.
nsdlsandyAuthor Commented:

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
nsdlsandyAuthor Commented:
This issue got resolved. Issue was caused because of incomplete installation of WSS Patch. Had to consult Microsoft support because only they can look in the tables and folders to see till what point installation was done and how to complete it.

nsdlsandyAuthor Commented:
Used Microsoft support to resolve issue.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now