Question
I am having trouble installing the Metalogix Extensions Web Service. Are there any steps I can take to troubleshoot?
Answer
Yes, there are some steps you can take to troubleshoot installation issues for the Metalogix Extensions Web Service.
The first thing that you want to check is that the account that is being used to install the Metalogix Extensions Web Service has all the necessary permissions. This user account needs to be able to run the STSADM commands on the installing system, and also needs the following permissions:
·SharePoint Site Collection Administrator
·Farm Administrator
·Read/Write access to the Content Database (DB)
·Administrator on the installing system
In some cases users can receive a message saying "Could not deploy SharePoint solution: Cannot open SPAdminV4 service on computer." when they try to install the Metalogix Extensions Web Service. There are two possible methods for working around this issue.
1.Navigate to the folder containing the Metalogix Extensions Web Service installation EXE file. Right-click on this file and choose Run as Administrator. The Web Service should now be able to install. Some instances of Windows will automatically block services from being registered fully. In these cases, running as administrator should get around this issue.
2.In some cases, users are not able to use the Run as Administrator command, or this does not solve the issue, then there is a second workaround method that can be used. The alternate solution is to turn off the User Access Control (UAC) and reboot the server. This should allow the installing account to correctly install and deploy the Metalogix Extensions Web Service. Once installed and deployed you can re-enable UAC.
After the Web Service has been installed, there is a check that can be made to see if the Web Service can be detected on any given machine. For more information on running this check please see the After Installing the Metalogix Extensions Web Service section of the Installing the Metalogix Extensions Web Service page.
Question
I want to have more control over installing the Metalogix Extensions Web Service, and only install it on some systems. Is this possible?
Answer
Yes this is possible, however, the method for this will change slightly depending on the version of the Metalogix Extensions Web Service you are trying to install. The Metalogix Extensions Web Service installation file contains and deploys a WSP solution file throughout a SharePoint farm.
If you are trying to install version 5.1.0.0 or later:
1.Open a Command Prompt window, and set the directory to the same directory that the EXE installer file is located in.
2.Enter the name of the EXE installer file followed by /v and /a. For example, Metalogix Extensions Web Service Setup v.5.1.X.X /v /a (replacing the "X" with the version number). It is important to make sure there is a space between the "/v" and "/a" values.
NOTE: A "/?" value can be entered after the name of the EXE file to see a list of the command line parameters.
3.This will open the InstallShield, but will not actually install the Metalogix SharePoint Extensions Web Service. Instead it will allow you to select a desired extraction location and it will extract the WSP file and the MSI file.
If you are trying to install a version before v.5.1.0.0 you can (extracting from the WSP file):
1.Open a Command Prompt window, and set the directory to the same directory that the EXE installer file is located in.
2.Then enter the command: msiexec /a "Metalogix SharePoint Extensions Web Service - vX.X.XX.XX.msi" (replacing the "X" with the version number).
3.This will open the Install wizard, but will not actually install the Metalogix Extensions Web Service. Instead it will allow you to select a desired extraction location and it will extract the WSP file to that location.
After the files are extracted users can install the files as they choose.
Question
I am trying to migrate a SharePoint list from my source, and pasting it as a folder within an existing list on my target. The list is a "Custom List" template, and I am preserving item IDs. I am not seeing the results I was expecting, and it looks like content may have been overwritten or deleted. What could cause this issue?
Answer
If migrating a custom list as a folder, or migrating folders within a custom list, while using the Overwrite and Preserve IDs on items/folders in Lists options, any existing folders or items on the target that have the same ID as the folders/items migrating from the source will be deleted in order to preserve the IDs for this migrating content. This is expected behaviour.
For example, if you are more concerned with maintaining the items and folder structure, you can turn off the Preserve IDs on items/folders in Lists option, which will allow the folders and items to be properly added to the list, without overwriting any content.
Question
Before I can install the Metalogix SharePoint Extensions Web Service I need to know specifically what files are installed, and where. Can this information be provided?
Answer
Yes, we can provide some information on what files are installed.
The Metalogix Extensions Web Service installs as a SharePoint solution (.WSP file) that is automatically deployed by the Web Service installer, and pushed out to all Web Front Ends (WFE's) in the farm. Inside the solution file are the necessary files for the Web Service. These files are:
·An ASMX file and two ASPX files, which are put in the SharePoint hive. These three files will be listed under a folder that is added for that specific version of the Web Service. For example, three files will be listed under: C:\Program Files\Common Files\Microsoft shared\Web Server Extensions\[hive_number]\ISAPI\ML\5.0.0.6.
·A DLL file, which gets deployed to the Global Assembly Cache (GAC).
After installation the Metalogix Extensions Web Service sits idle on the server until requests are made to it, by the Metalogix Content Matrix client. For more information about the Metalogix Extensions Web Service, please see the Installing the Metalogix Extensions Web Service page.
© 2021 Quest Software Inc. ALL RIGHTS RESERVED. Feedback Terms of Use Privacy