Question
How to troubleshoot a MacroView DMS Provisioning error message?
Example: Error Message
Answer
Please send us the MacroView DMS Provisioning extension log and diagnostic files.
In MacroView DMS go to Options > Support and click the "Trace Files" button (see image below).
This will open a File Explorer window to the following location.
Please zip the MVSP folder and email it through.
Question
How do I enable the Export Configuration option?
Answer
[1] Create Support Folder
To enable the Export Configuration functionality (which is disabled by default) in MVSP you have to create a folder called Support in the following location on your local file system.
Note: the Extensions folder and MVSP folder may also have to be created.
The resulting folder path needs to be:
C:\Users\[username]\AppData\Roaming\MacroView DMF\Store\Extensions\MVSP\Support
[2] Copy the Functions.xml file
Make a copy of the Functions.xml file located at:
%ProgramFiles%\MacroView\MVSP\XML\
C:\Program Files\MacroView\MVSP\XML
and paste the Functions.xml file to the Support folder (created in step [1]).
[3] Edit the Functions.xml file
Edit the Functions.xml file in the support folder so it looks as follows.
<?xml version="1.0" encoding="utf-8" ?>
<Functions Title="MVSP Extension - enable / disable settings" MacroViewVersion="1.20">
<Function Name="ExportConfiguration" Enabled="1"/>
</Functions>
[4] Restart
Restart DMS (excluding the local service) to load the Functions.xml file.
You will then be able to export your configuration by right-click in the DMS tree and selecting Provision > Export Configuration.
Please right-click and Export the Configuration for both the site collection and sub-site.
Please ensure that both the site collection and sub-site are exported. If you do not have sub-sites then just a site collection level export will suffice.
Only export a sub-site if there is a library in this site that is of interest.
*If there are no sub sites then just the site collection export will suffice.
[5] Clean-up
Post export it is recommended to update the Functions.xml in the support folder in order to disable the export option, by setting Enabled="0".
Question
What configuration files can be edited?
Answer
The following custom XML files allow customers to make changes:
- Functions.xml
- SearchConfiguration.xml
- SiteListContents.xml
- SiteLists_CalculatedColumns.xml
- SiteLists_ContentTypes_HideColumns.xml
- TermSets.xml
Note: to ensure backward compatibility with the previous versions of MVSP the SiteLists_CalculatedColumns.xml and TermSets.xml files are still signed.
Question
Now that there are multiple MacroView Provisioning products, which installer do I use?
Answer (MacroView DMS Provisioning Extension)
If you are after the DMS provisioning extension the installer is called
MacroView.Solutions.Provisioning x64 version x.x.x.x
Answer (MacroView Provisioner)
If you are after the MacroView Provisoner console app the installer is called
MacroView.Solutions.Provisioning Standalone x64 version x.x.x.x
The more information about MacroView Provisioner please go to the following link
MacroView Provisioner (formerly MVSP Standalone)
Question
Why, after deploying a custom set of XML files, does MVSP load a different set of custom XML files?
Answer
If you are using the Central Configuration Location setting in DMF client and a set of custom XML files has been stored in this location, then the locally deployed custom XML files will be overridden on DMF client start-up.
New version of custom XML files
The new custom XML files will need to be uploaded to the Central Configuration Location and will replace the previous set of custom XML files stored in that location.
Question
Where are the Release Custom XML files deployed?
Answer
The release custom XML files are deployed to:
%AppData%\MacroView DMF\Store\Extensions\MVSP
Example
C:\Users\[username]\AppData\Roaming\MacroView DMF\Store\Extensions\MVSP
Question
Where are the Built-in XML files located?
Answer
The built-in XML files are located in
%ProgramFiles%\MacroView\MVSP\XML
Example
C:\Program Files\MacroView\MVSP\XML
Note
The functions.xml file is also stored in this location
Question
Why are provisioning options missing?
Answer
MVSP filters out provisioning options if the requisite licence code is not in one of the licence files in the DMF Licence folder on the local file system.
Licence folder location on file system
%AppData%\MacroView DMF\Licence
Another reason is if the site collection already has DMF / Message site columns and content types then the provisioning options not related to the DMF / Message solution will be filtered out.
Answer
To see the exact reason why an option has been filtered out, see the diagnostic log files located at:
%LocalAppData%\MacroView DMF\Tracing\MVSP\Diagnostics\
Example
C:\Users\[username]\AppData\Local\MacroView DMF\Tracing\MVSP\Diagnostics
More Information
See the "How does UI filtering work?" question below for more details regarding UI filtering.
Fix
In DMF Explorer / Message go to File > Options > Support and click the Refresh Licences button.
Question
What permission is required to create Term Sets and create Site Collections in SharePoint Online?
Answer
The Office 365 Tenant Administrator account is required to create Term Sets and Site Collections.
Question
What permission is required to provision MacroView Case and Matter or MacroView Project in a Site Collection?
Answer
Site Collection Administration permission is required in order to provision MacroView Case and Matter or MacroView Project as Site Collection Level Features have to be enabled.
Fix
Browse to the Site Collection Administrators web page for the Site Collection by going to the site collection and then append the following relative URL.
/_layouts/15/mngsiteadmin.aspx
Example
https://macroview365.sharepoint.com/sites/dash01/_layouts/15/mngsiteadmin.aspx
Then add the account to the Site Collection Administrators.
Question
How does UI filtering work?
Answer
The UI filtering does a number of checks to determine whether to include or exclude a provisioning option. Some of the checks include:
- If the option is disabled in the custom UI.xml file then the option is filtered out.
- If there is a pre-existing solution in the site collection, then only options belonging to that solution are included, all the other options for the other solutions are filtered out.
- If the licence code for a solution does not exist in one of the licence files in the DMF Licences folder then the option is filtered out.
- If the option has dependencies which do not exist in the site collection then the option is filtered out. For example you cannot create a DMF library if the DMF site columns and content types have not been provisioned.
- If the option clashes with a pre-existing component in a site then the option is filtered out. For example you cannot provision a "second" Matters List if the Matters List already exists.
- If the option cannot be provisioned due to discrepancies then the option is filtered out. For example a site collection may already have a site column with the same internal name but with a different ID to the ID defined in the XML file.
Question
Where are the Log Files located?
Answer
The log files are located at:
%LocalAppData%\MacroView DMF\Tracing\MVSP\Logs
The diagnostic log files are located at:
%LocalAppData%\MacroView DMF\Tracing\MVSP\Diagnostics\
Example
C:\Users\[username]\AppData\Local\MacroView DMF\Tracing\MVSP\Diagnostics
C:\Users\[username]\AppData\Local\MacroView DMF\Tracing\MVSP\Logs
Question
How to turn on / off the Create Template from Library command?
Answer
Go to MacroView DMF / Message > Options > Settings > General tab
Note: this settings also controls the MacroView DMF / Message built-in Create Library command.
Question (*Update: repair checkbox has been removed)
*Update: the repair checkbox has been removed as library provisioning now has built-in backwards compatibility.
What does the Repair checkbox in the Add Site Collection Components dialog actually do?
Answer
It checks the existing site columns and content types in the root site of the site collection against the XML definitions of the site columns and content types, and if required, it updates them to reflect the XML definitions.