​Issue:

Within SharePoint Central Admin, a server is listed as Not Configured under the Services Running column but is listed as a Microsoft SharePoint Server under the SharePoint Products Installed column.

This server, although not configured in SharePoint and with no DocAve Agent installed, is counted against the DocAve license as an actual server.

Cause:

In DocAve 6.2 and above the information in the Services Running Column is not accounted for when considering servers for the DocAve license. If the server is shown as a Microsoft SharePoint Server under the SharePoint Products Installed column within SharePoint Central Admin, the server will be counted against the license.

Solution:

If you encounter this issue, please contact AvePoint Technical Support, and refer to this KB Article ID.

When running a Content Manager job, if you want to keep a Content Type ID in the destination, complete the following steps:

1. Navigate to the destination server.
2. Open the file at the following path: …AvePoint\DocAve 6\Agent\Data\SP2010\SP2010Content Manager Configuration.xml.
3. Locate <ForceCreate index="3" /> in the configuration file.
4. Replace <ForceCreate index="3" /> with <ForceCreate index="1" />.
5. Replace <UseParent index="1" /> with <UseParent index="3" />.

    *Note: The number in quotes next to each of the attributes represents the running sequence. Using the screenshot above as an example, UseParent Index=“1” indicates that DocAve will not keep the Content Type ID in the destination. If the first step fails, DocAve will move to the next step UseId index=”2” to keep the Content Type ID in the destination. If step 2 fails, DocAve runs ForceCreate index=”3”.
 
If you encounter this issue, please contact AvePoint Technical Support at support@avepoint.com. Please be sure to reference this KB Article ID.

​The cache data in the following directory is used to store index files: …\AvePoint\DocAve6\Manager\Media\cache\data_platform\Farm. The cache can help improve the efficiency of loading farm structure and restore related information. If the cache is deleted, it will only affect the speed of loading trees and restoring data. If the slowdown is acceptable to the user, it can be deleted. Moreover, when deleting some occupied caches, do not force their deletion since there may be jobs currently running.

It is recommended to delete the cache when no job is running. After the deletion, if you’re running a new job, a new cache will be generated again.

If you encounter this issue, please contact AvePoint Technical Support at support@avepoint.com. Please be sure to reference this KB Article ID.

In DocAve 6 SP2 CU1, if a user tries to connect to the SharePoint Online site collection, the following error message appears: No Agent can connect to this site collection.

To solve this issue, complete the following checks:

1. Ensure that the Agent Account has sufficient permissions.
2. Ensure that the DocAve agents in the SharePoint on-premise farm are able to connect to the Office 365 site collection.
3. Ensure that .Net framework 4.5 is installed on all agent servers.

If you encounter this issue, please contact AvePoint Technical Support at support@avepoint.com. Please be sure to reference this KB Article ID.

​When upgrading from DocAve 6 to 6 SP3, you may receive an error indicating that PatchDependInfoConfig cannot be found. If the user customized the download location in DocAve GUI > Control Panel > Update Manager > Update Settings > Download Location, the account should have Full Control permission to the path. Otherwise, the upgrade package cannot be accessed.

To solve this error, you must confirm the permission of the account or deselect the Use the Net Share path as the update storage location and download the update to the default location.

If you encounter this issue, please contact AvePoint Technical Support at support@avepoint.com. Please be sure to reference this KB Article ID.

If you want to check for the remaining EBS stubs in a specific content database, you can use one of the following SQL query commands:

SELECT DeleteTransactionId,* from AllDocs where (Docflags&65536)<>0
SELECT DeleteTransactionId,* from AllDocVersions where (Docflags&65536)<>0
 
You need to execute the two commands above at the same time.

If you encounter this issue, please contact AvePoint Technical Support at support@avepoint.com. Please be sure to reference this KB Article ID.

​If a Platform Restore job completes with exceptions and the following error message appears in the job report, there are insufficient permissions in place for the SQL Agent.

The given key was not present in the dictionary.

To solve this issue, give the DBO permission for Master DB to the SQL Agent.

If you encounter this issue, please contact AvePoint Technical Support at support@avepoint.com. Please be sure to reference this KB Article ID.

If a Granular Backup job fails with the following error message, check the length of the media cache location: The specified path and / or filename is too long. The fully qualified file name must be shorter than 260 characters and the path name shorter than 248 characters.

To solve this issue, complete the following steps:

1. Set the media cache location to a short path.
2. Open the Manager Monitor in the DocAve Manager GUI Control Panel.
3. Select the Media Service. 
4. Click Configure.
5. Click Add Cache Location. 
6. Add a new cache location with a short path. 
7. Delete the default cache location. 

If you encounter this issue, please contact AvePoint Technical Support at support@avepoint.com. Please be sure to reference this KB Article ID.

With e-mail notifications configured in DocAve, an issue may occur where multiple e-mails are sent stating that the Agent Service is down. This issue may occur even if the Agent is actually up and running without any issues.

When the Control Service checks for the Agent status, an exception occurs obtaining the status of the Agent. The status is incorrectly reported as down, subsequently sending a notification e-mail.

If you encounter this issue, please contact AvePoint Technical Support at support@avepoint.com. Please reference this KB Article ID​.

Within the Report Center module, when attempting to load a node within Farm Explorer within Infrastructure Reports, the node beings to load, but then the DocAve GUI subsequently freezes.
After a few minutes, an error message appears with the following message: Index: 0, Size: 0. If you select OK on the error message, the DocAve GUI unfreezes, but the node you wanted to expand will not open.
 
This issue occurs if there is a large amount of data in the selected node. When attempting to query the data, the GUI freezes and a timeout occurs.
If you encounter this issue, please contact AvePoint Technical Support at support@avepoint.com. Please be sure to reference this KB Article ID.

With AvePoint Governance Automation, you can manage site collection lifecycles by enabling a site collection inactivity threshold in the site collection policy. If activity in the site collection has ceased for the configured time threshold, Governance Automation will start an approval process. The purpose of the approval task is to alert the assignee to the inactivity, and to optionally provide them with tools to manage the site collection lifecycle. This leads to a fundamental question: how do we calculate site collection inactivity?

For Governance Automation Server, an on-premises solution, site collection inactivity is calculated based on two conditions: 1. the configured inactivity threshold in the site collection policy, and 2. the value of the LastContentModifiedDate property in the SharePoint Server API. This property is updated when a change is made to the database for that site collection, including the addition of view audit records. This can be interpreted as a Last Accessed Time for that site collection, and thus inactivity is based on site collection access of any kind.

However, the LastContentModifiedDate property used for on-premises calculation is not available in the SharePoint Online API. So for Governance Automation Online, a hosted solution in the AvePoint Online Services platform, and for SharePoint Online site collections managed by Governance Automation Server, site collection inactivity is calculated based on: 1. the configured inactivity threshold in the site collection policy, and 2. the value of the LastItemModifiedDate property in the SharePoint Online API. This property is updated when content is modified in the site collection, not including the addition of audit records to the database. This calculation can be interpreted as a Last Modified Time for the site collection, and thus the distinction between on-premises and Online site collection inactivity is that for Online, inactivity is based on actions taken on content in the site collection rather than access to the site collection. ​

Issue: After updating the SharePoint farm where DocAve 6 is installed to SharePoint Server/Foundation 2013 Service Pack 1, you may experience the following symptoms:

Cause: While updating to SharePoint Server/Foundation 2013 Service Pack 1, the role members of the db_owner database roles are automatically removed in the SharePoint databases related to the updated farm, such as SharePoint Configuration database and SharePoint content databases. The Agent accounts for this farm no longer have the db_owner roles in the corresponding SharePoint databases. The db_owner role is required for DocAve Agents to interact with the SharePoint object model.

Solution: After updating the SharePoint farm where DocAve 6 is installed to SharePoint 2013 Server/Foundation Service Pack 1, grant the Agent accounts the db_owner roles in all of the databases related to the updated SharePoint farm in SQL Server. For details on the SQL permissions required for using each DocAve module, refer to the "Appendix A: Permission Requirements for DocAve Modules" section in the DocAve 6 Installation Guide.

​After applying a license to the DocAve for Salesforce GUI, the user is prompted with an error stating that the module is not licensed for use. 

To resolve this, go into the server that DocAve for Salesforce is installed on and navigate to Start > Administrative Tools > Services.  Restart the DocAve.Salesforce.SP2010.Service and then reopen GUI.  This should resolve the error.

The table below lists the TSM client API DLL version used in each DocAve version and the TSM server versions supported by each DocAve version.

*Note: Based on IBM technote (http://www-01.ibm.com/support/docview.wss?uid=swg21053218), AvePoint assumes that DocAve 5.7.2 and all versions of DocAve 6 should work with TSM server v7.1.

​

DocAve can maintain the state of a running workflow after migrating or replicating it between the source and destination. However, DocAve must write directly to the Content Database in order to do so. Please be aware that Microsoft does not support database writing methods, and using such methods may void your Microsoft Terms of Service. If you choose to use either of the methods below, you do so at your own risk, and AvePoint is not liable for any violation of your Microsoft Terms of Service.

Maintaining the State of Running Workflows with DocAve SharePoint Migrator

If you have a running SharePoint 2010 workflow instance in your SharePoint Server 2010 environment, you can maintain the state of that workflow in the destination SharePoint Server 2013 environment after migrating it using DocAve SharePoint Migrator.  To do this, follow the steps below prior to performing your migration. Please be aware that Microsoft does not support database writing methods, and using such methods may void your Microsoft Terms of Service.

*Note: When a SharePoint 2010 workflow is migrated to a SharePoint Server 2013 environment, it will remain a SharePoint 2010 workflow in the destination.

1. Log into DocAve.
2. Launch the DocAve SharePoint Migrator module.
3. Click Profile Settings on the ribbon.
4. In the Profile Settings tab, click Download Profile on the ribbon to download the Default Profile to your desktop or another easily accessible location.
5. Open the Default Profile.xml file with Notepad.
6. Navigate to the keepRunningWorkflowInstance = " " node, set the value to True, and save your changes. 
7. Rename the Default Profile.xml to RunningWorkflowProfile.xml or another easily identifiable profile name.
8. In DocAve, navigate to SharePoint Migrator > Profile Settings and click Upload Profile in the Upload/Download group on the ribbon.
9. Select the renamed Default Profile.xml that you edited in the previous step. The file will be uploaded, and your Online Profile will automatically be changed to the profile you created.
10. In the Source Component Options section under Workflow, select Include Workflow instance, Include running workflows, and Cancel and restart the running workflows after migration jobs.
11. Run the migration job. For more information about running migration jobs, see the SharePoint Migrator User Guide.

Maintaining the State of Running Workflows with DocAve Replicator

If you have a running SharePoint 2010 workflow instance in your SharePoint Server 2010 or SharePoint Server 2013 environment, you can maintain the state of that workflow in the destination after a replication. To do this, follow the steps below prior to performing your replication using DocAve Replicator. Please be aware that Microsoft does not support database writing methods, and using such methods may void your Microsoft Terms of Service.

*Note: DocAve does not support replicating the workflow instance of a checked-out file.

1. Log into DocAve.
2. Launch the DocAve Replicator module.
3. Navigate to Profile Settings > Content > Include running workflow instances, and select Restart workflows from 0% after the replication.
4. On all Replicator Agents that will run jobs or plans that you want to maintain the state of SharePoint 2010 running workflows, navigate to …AvePointDocAve6AgentdataSP2010Replicator.
5. Find the SP2010Replicator.xml file, right-click it, and select Edit.
6. Find the attribute ReplicateRunningWorkflowInstance and modify the value to True.
7. Save and close the file, and then run your replication. For more information about running replication jobs, see the Replicator User Guide.

The DocAve 6 Agent account must have the database role of SharePoint_Shell_Access for SharePoint 2013 Content Databases.

*Note: The SharePoint_Shell_Access role can only be assigned via SharePoint 2013 Management Shell. For instructions on how to assign this role to a user, refer to the following Microsoft technical article: https://technet.microsoft.com/en-us/library/ff607596.aspx.

When the DocAve Agent account has this role for Content Databases, some DocAve 6 modules have several limitations. The following table details those limitations. 

AvePoint recommends that you assign the db_owner role of Content Databases to the DocAve Agent account. When using the db_owner role, DocAve 6 does not experience these limitations.​

The post Limitations for DocAve 6 Products If DocAve Agent Account has the SharePoint_Shell_Access Role appeared first on Knowledge Base | AvePoint.

The post AvePoint Product Compatibility Matrix appeared first on Knowledge Base | AvePoint.

​Issue:

Within SharePoint Central Admin, a server is listed as Not Configured under the Services Running column but is listed as a Microsoft SharePoint Server under the SharePoint Products Installed column.

This server, although not configured in SharePoint and with no DocAve Agent installed, is counted against the DocAve license as an actual server.

Cause:

In DocAve 6.2 and above the information in the Services Running Column is not accounted for when considering servers for the DocAve license. If the server is shown as a Microsoft SharePoint Server under the SharePoint Products Installed column within SharePoint Central Admin, the server will be counted against the license.

Solution:

If you encounter this issue, please contact AvePoint Technical Support, and refer to this KB Article ID.

The post Server listed as Not Configured in Central Admin is still counted against the DocAve License appeared first on Knowledge Base.