Frequently Asked Questions - Questions About Connection to SharePoint

1. Start MetaVis,
2. Go to Help> Profile Manager> Global Variables>
3. Find an option called "Enable browser connect" and set that dropdown to 'True'.  Click Apply
4. Close and restart MetaVis
5. After you've re-started MetaVis Click the "Connect to Site" button on the ribbon. 
6. Type in the project name and the url for your site.  Click the Finish button.
7. An authentication box will pop up. Leave the fields blank and click the "Claims" button.  A browser window will pop up.
8. Enter your claims based credentials in this window and sign in.
9. The tool should now connect and begin loading the site.

This error is commonly generated when there is a need to specify a different home folder location. For example, when a user has roaming Windows profile or the user home directory does not have letter mapping but accessible by UNC path like \\server\drive\folder\folder. MetaVis does not support this setup and requires letter mapping for user home directory. When these cases are encountered an error similar to the one pictured below is displayed.

1.) Shut down MetaVis, if it is currently running

2.) Create a new folder in your local drive (for example, c:/MetaVis)

3.) Navigate to “c:\Program Files\MetaVis Technologies\metavis\configuration” and open the file “config.ini” *Note* This file may be hidden, so you may need to show hidden files. (open the file using WordPad, not Notepad). You may need to start WordPad using "Run as Administrator" option to overcome Windows security settings.

4.) Edit the last line of this file, changing it:

a) From: osgi.instance.area.default=@user.home/Metavis

b) To: osgi.instance.area.default=c:/MetaVis {or the folder path that was created in step 2} {also note the forward slash instead of the back slash}

5.) Save and close config.ini

6.) Restart MetaVis

By default, MetaVis uses Windows Integrated scheme to connect to SharePoint. In case the SharePoint server supports only basic authentication, MetaVis behavior should be changed via a parameter in the ini file. Please follow these steps to modify this comment:

1) Go to C:\Program Files (x86)\MetaVis Technologies\metavis folder.

2) Edit (WordPad) the MetaVis ini.**

3) Add the following line at the bottom of the file: -Dhttp.auth.preference=Basic

4) Save file and restart Metavis and try to connect

To connect to SharePoint site with Kerberos authentication you need to know two parameters of your network:

1. Kerberos Key Distribution Center (KDC) which in the case of Windows domains is the Windows domain controller
2. Kerberos Realm

KDC server in case of Windows netowork could be detected by running command prompt (Start / Run / cmd) and executing the following command:

echo %logonserver%

Kerberos Realm should be learned from network administrator.

Download ZIP file with MetaVis Kerberos configuration files using this link: http://www.metavistech.com/~metavis/kerberos/KerberosConfiguration.zip . Copy two files:  krb5.conf and login.conf in the root of drive c:. Edit krb5.conf to replace REALM with your Kerberos Realm and DOMAINCONTROLLER with your domain controller. Replace MetaVis.ini file located in MetaVis installation folder on your hard drive (default location is c:\Program Files\MetaVis Technologies\metavis) with the one from archive. In case you copied krb5.conf and login.conf to different locations edit MetaVis.ini file to reflect the new location of these files. In all cases use Wordpad for editing since Notepad would not display new line characters correctly.

After this start MetaVis and try to connect. If connection does not work then add the following registry settings:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos\
Value Name: AllowTGTSessionKey
Value Type: REG_DWORD
Value: 0x01

To do this open registry editor (Start / Run / then type regedit ). In the registry editor expand HKEY_LOCAL_MACHINE node, then SYSTEM, then CurrentControlSet / Control / Lsa / Kerberos. Right click on the right side, select New  / DWORD (32 bit) Value, enter name AllowTGTSessionKey, click Ok, double click on new record and enter 1 as a value. It should finally look like this:

For server computers make the same registry entry but in the following registry section:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\Kerberos\Parameters

After registry setting is modified try to connect to the site again. In case it still does not connect check the realm and domain controller information in krb5.conf file and run MetaVis in debug mode to diagnose Kerberos negotiation. To do this right click on MetaVis icon on the desktop and add parameter -consolelog after the double quote character of the Target field of the shortcut properties. After this save the properties and run MetaVis from this shortcut. MetaVis will startup together with black windows that will display the log. Connect to the SharePoint site and send us the content of the black window. To do this, right click on the black window title bar, select Edit / Select All. It will select all text inside this window. Then press <Enter> to copy this text into clipboard. Paste it into the email message ans send it to support@metavistech.com

To fix "Authentication Failure" error that appears during connection to SharePoint change the following setting on the Windows computer that runs MetaVis (Mostly applies to Win7 and Win2008 R2):

1. Open Control Panel

2. System and Security

3. Administrative Tools

4. Local Security Policy (can take a minute to load)

5. Local Policies

6. Security Options

7. Network security: LAN Manager authentication level 8. Change the setting to be: "Send LM & NTLM - use NTLMv2 session security if negotiated"

After changing this property try to reconnect to the site again.

In the  case Local Security Policy is not available on the computer (for example, in case of Windows 7 Home Premium Edition), run registry editor (type regedit in the command line or in Run... prompt). Find the node:

HKEY_LOCAL_MACHINE / System  / CurrentControlSet / Control / Lsa

Click on Lsa node and create there a New DWORD (32-bit) Value LmCompatibilityLevel with the value 1. It will have the same effect as setting local security policy in Win7 Professional. It should resolve Authentication Failure issue. Below is the picture of registry editor with this value already set.

All products from MetaVis Architect Suite require account credentials to connect to SharePoint.

MetaVis Architect and Migrator require this account to have at least Designer permissions. MetaVis Classifier requires the account to have at least Contributor permissions.

In this case we need to diagnose the issue by looking through your log. Please follow these steps:

1) Go to Help ribbon and turn on Debug Mode
2) Try to connect to SharePoint..
3) Return to the Help ribbon and turn off Debug Mode
4) Press on Log Manager Button and then select a location to store log files.  Then press the Save Environment button. 
5) Please send the zip file created in step 4 back to us at support@metavistech.com or if it too large please use the following drop box: http://dropbox.yousendit.com/MetaVisSupport121114118

If you have valid privileges to your SharePoint environment, but still receiving this error "The Sever sent HTTP status code 401: Unuathorized" then the problem is likely due to MetaVis authentication methodology.

If the workstation on which MetaVis is installed on is logged into a valid domain, the application automatically picks up these credentials and tries to log in. However, if this account does not have sufficient privileges the "Unauthorized" error is shown. There are several work-arounds:

1) Re-start MetaVis under "Run As" - Hold down the shift key and click with your mouse on the MetaVis shortcut. Select Run As and type in either the admin account or any other account that has no rights to the SharePoint environment. If you do the later, you will be prompted to enter credentials when connecting to SharePoint.

See these Resources for further information:
http://support.microsoft.com/kb/294676

2) Relogin into the computer with a local account or a domain account with no SharePoint privileges. You will be prompted to enter credentials when connecting to SharePoint.

If you use MetaVis Architect (either full edition or Trial), the user that you use to connect to SharePoint should have at least Design privileges (Full Control will also work).

If you use MetaVis Classifier or Migrator products (check what it has in the application title bar) then the user that you use to connect to SharePoint should have at least Contribute privileges on the site you connect to (Anything better than Contribute like Design or Full Control will also work).

MetaVis Architect Trial Edition that you receive when you select "Try Now" on www.metavistech.com requires at least Design privileges because it includes Architect product.

MetaVis Architect Products support the following versions of SharePoint

* SharePoint Server 2010: Intranet
* SharePoint Server 2010: Internet/Extranet
* SharePoint Foundation 2010
* Microsoft Office SharePoint Server (MOSS) 2007
* Windows SharePoint Services (WSS) v3
* Microsoft Online (BPOS) and other SharePoint Hosting Providers
* Office 365
* SharePoint Portal Server (SPS) 2003 (source only)
* Windows SharePoint Services (WSS) v2 (source only)
* FAT/NTFS File System (source only)
* Outlook (source only)
* Exchange Public Folders (source only)

Hosted SharePoint environment often has mapping of user email to an internal user names on the provider's local domain. In order to learn the exact user name used by SharePoint do the following:

If you are connecting to Office 365, enter the same email address and password you use to login to Office 365 through your web browser.

If you are connecting to BPOS or other hosted SharePoint
* Login to your hosted Microsoft Online, BPOS or other hosted SharePoint
* Click on your "Welcome " on the top of the page
* Select My Settings
* Look at the Account property
* Use Account as a user on the MetaVis connection wizard to connect to SharePoint
* You can use the complete domain\user account name in the user field or type user in the user field and domain in the domain field