Monday, October 26, 2015

DocAve 6: An error occurred while loading the node

Problem

You are using DocAve SharePoint Administrator.  You have a SharePoint Server 2013 Enterprise farm.  You are trying to configure a DocAve Security Search on a farm site.  You were able to successfully execute security searches just fine a few days ago.  You have not made any configuration changes to DocAve SharePoint Administrator since you last used it.  The only thing you have done since then is install the SharePoint cumulative update package for this month.  Now, you can't execute security searches and you experience unusual problems.  For example, when you try to expand the farm in the Scope pane, you see the following error message:
You also find that when you enter a user's name in the User and Group box, when configuring a Security Search on a user account known to be in the content database, you see this error message:
You then log into a farm server and review the server event logs.  You see the following event log occurring repeatedly at the same time as the above DocAve errors:
Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          [date/time]
Event ID:      5586
Task Category: Database
Level:         Error
Keywords:      
User:          DOMAIN\SPDOCAVE
Computer:      [a farm server]
Description:
Unknown SQL Exception 262 occurred. Additional error information 
from SQL Server is included below.
CREATE TABLE permission denied in database 'Farm_Config'.
Event Xml:
...
This error message seems to point to an access issue. Checking the AgentService.exe log on the farm application server, you find this error message recurring each time you attempt to configure the security search:
ERROR 10-17 17:01:12,435 8 AgentPreHostingService 0- An error occurred 
while registering the agent. Exception: 
System.ServiceModel.EndpointNotFoundException: There was no 
endpoint listening at 
https://[DocAveSvr]:14000/ControlCore/ControlCoreService.svc that could 
accept the message. This is often caused by an incorrect address or 
SOAP action. See InnerException, if present, for more details. ---> 
System.Net.WebException: The remote name could not be resolved: 'DocAveSvr'

You then launch SQL Server Management Studio and check the mapping of the DocAve service account: you find that it is not longer mapped as DBO to the farm configuration database and other databases.

Solution

  • Verify that the DocAve agent service account has been mapped as DBO for all farm databases, particularly the farm configuration database.

References

  • None

Notes

  • The AgentService.exe.log is located in C:\Program Files\AvePoint\DocAve6\Agent\Logs.

No comments: