Quest® Notes Migrator for SharePoint

Version 5.2.1

Release Notes

October 2009

 


Contents

Welcome to Notes Migrator for SharePoint

New in this Release

Resolved Issues And Enhancements

Known Issues

Upgrade and Compatibility

System Requirements

Global Operations

Getting Started

History of Changes in Previous Releases

For More Information

 


Welcome to Notes Migrator for SharePoint

Thank you for installing Notes Migrator for SharePoint 5.2.1.  This is a patch release that provides miscellaneous fixes to 5.2 as well as enhancements such as new command line arguments for overriding views and selection formulas.

Notes Migrator for SharePoint allows organizations to safely and effectively migrate Lotus Notes, Domino, QuickPlace or Domino.Doc data to Microsoft SharePoint.

Please review the release closely.  We are still adding features so please send your suggestions, comments, and bug reports to

support@quest.com.

We suggest that you check the KnowledgeBase at http://support.quest.com for additional samples, Tech Notes and answers to Frequently Asked Questions.

 

Notes Terminology

Notes Migrator for SharePoint supports Notes, QuickPlace, and Domino.Doc. This documentation applies to all three versions and indicates those portions that are specific to one product or another.  Since QuickPlace and Domino.Doc use Notes databases for data storage, this document often uses the terms "Notes" and "Notes databases" generically to cover all three data sources.

 

Distribution

Notes Migrator for SharePoint is distributed as MSI installation programs (NotesMigratorForSharePoint-Clients-5.x.msi for the new NMSP Console and the Designer which is the bulk migration client,  NotesMigratorForSharePoint-Services-32bit-5.x.msi for the optional services components and NotesMigratorForSharePoint-Desktop-Only-5.x.ms for the Desktop which is the ad hoc migration client).  For installation instructions, see NotesMigratorForSharePoint.chm.

 


New in This Release

This release of Notes Migrator for SharePoint is a patch release that includes the following enhancements.

 

Add -formula and -view options to NMSPCMD

These new arguments for the NMSP command line allow whatever view or selection formula is specified in the current job to be overridden. This will provide a good deal of flexibility in scripting complex migration tasks using external tools.
The following example command line overrides both the view and the formula in a job:
"\Program Files\Quest Software\Notes Migrator For SharePoint 5.2\bin\NMSPCMD.exe" -job "C:\Documents and Settings\All Users\Application Data\Quest Software\Notes Migrator For SharePoint\5.0\Job Files\
DocLibrary to List.pmjob" -view "($All)" -formula "subject='Florida'"

 

Log server-side events to Windows Event Log

Exceptions, warnings and other selected information messages are now written to the Windows Event Log when using the Import Service. These events will show up in the Windows Event Viewer under "Notes Migrator for SharePoint".
By default, this logging will not be enabled. In order to turn on the logging, you must edit the Web.config file for the Import Service. In the "appSettings" section, there are four new settings. The "writeToErrorLog" setting controls whether or not any events are written to the event log. You can decide which types of events you want to be logged by setting "logErrors", "logWarnings", or "logInformationMessages" to true.

IDs for the "problem" events are as follows:
GeneralSharePointException = 101,
GeneralApplicationException = 102,
GeneralCommunicationException = 106,
TestSessionFailure = 110,
SessionInitializationFailure = 111,
SessionTerminationFailure = 112,
ShareFolderFailure = 113,
BinaryFileTransmissionFailure = 114,
ContentMigrationFailure = 115,
SiteProvisioningFailure = 116,
MemberProvisioningFailure = 117,

IDs for the "normal" events are as follows:
GeneralApplicationMessage = 103,
SessionInitializationMessage = 104,
SessionCompletionMessage = 105,
 

 

Back to Top


Resolved Issues and Enhancements

The following is a list of issues addressed and enhancements implemented in this release of Quest® Notes Migrator for SharePoint.

CR70680 Non-fixed width table may not display entire contents when migrated to HTML. Notes tables set with "Fit to margins" may clip part of the right edge of the table when the table is indented.
CR70981 Error loading Source Data Definition files >5KB.
CR72042, 72432 QuickPlace/Domino.Doc member provisioning not working since support for expanded groups for Notes data sources was added in 5.2. When you use the Console to provision site members for a QuickPlace, you get an "Object reference not set to an instance of an object" exception.
CR72043 If a SharePoint web application is configured to use SSL, then the Link Tracking redirector URLs don't work (because those URLs use "http:" instead of "https:").
CR72044 Unfinalized links marked as Finalized. If you choose you are finalizing, and you select "Leave as dynamic links" for unmigrated documents, then any documents that contain links to unmigrated documents shouldn't be marked in the table as being "Finalized". This will allow you to finalize those links later after the documents have been migrated. (During finalization, we ignore any records that are marked as "Finalized".)
CR72050 Log server-side events to Windows Event Log. See the 'New in this Release' section above for details.
CR72047 Increased the default values for the WCF Session timeouts (sendTimeout, receiveTimeout, and idleTimeout) from 30 to 90 minutes.
CR72063 Add -formula and -view options to NMSPCMD. See the 'New in this Release' section above for details.
CR71366 The Data Document count in the Quickplace data analysis should be dropping QuickPlace system documents.
CR71631 Error writing attachments with duplicate names on Japanese Windows system.
CR72706 Notes document with images migrated to SharePoint as MS Word doc display the broken image icon when opened directly from the browser via URL, or when opened via a hyperlink from another document.

 


Known Issues

The following is a list of issues known to exist at the time of Notes Migrator for SharePoint release.

 

Feature

Known Issue

Change Request

<General>

 

Notes Rich Text -> HTML Conversion - In the case where you are converting a Notes document that is stored in a Lotus' native rich text (CD) format to HTML for storing in SharePoint, there are currently some limitations in the quality of the HTML that is generated.  In particular: 

·       Images work, but image borders and ALT text do not

·       Tables work, but some table styles do not.

·       Font mapping is at a 90% level of quality

·       The following features are not yet supported at all:

o      Hide-when formulas

o      Computed text

o      Sections

o      Embedded views

o      Css Styles

o      Tabbed tables

 
Extracting Embedded OLE Objects - Quest has tested this feature with many different OLE server applications, including all Office applications, and has tried to engineer the best possible conversion behavior for the most popular object types.  If you migrate object types that were not specifically handled by Quest development, a default conversion behavior will be applied and the migrated files will have the .obj extension.  If you have a case that you feel could be handled better, please send a small sample Notes database with your embedded objects to support@quest.com.  
User can still transfer documents using NMSP Desktop after the Quest Transfer feature has been deactivated in the SharePoint site collection. CR54546
Console

When using a class rule to automatically assign SharePoint Target Sites, it is possible to end up with multiple databases targeting the same site URL, and thus the same SharePoint site.  This is perfectly legal as far as our tool is concerned and is sometimes very useful, but it may or may not be what you intended.  In the most extreme case, you could have several entire QuickPlaces (each with multiple lists and sub-rooms) all being merged into a single SharePoint site. 

In particular, the default Class Rule for QuickPlace sites uses Application Name to generate Relative URLs for the corresponding Site Creation plans.  Thus, if two QuickPlaces have the same name (or names that differ only by the case of the characters) this could result in the above condition.  Possible workarounds are: 

  • Manually override the Target Site URLs for the conflicting QuickPlaces and all of its descendants.   

  • Change the class rule to use something other than Application Name to generate Relative URLs (for example, ReplicaId or File Name are more likely to yield unique values)

  • Create an alternate Class Rule and carefully apply the alternate one to the conflicting QuickPlaces.

 

Domino.doc Limitations

While Cabinet level access control rules and Document level access control rules are migrated properly to the equivalent security constructs in SharePoint, Binder level security is currently ignored.

 

QuickPlace Limitations

“Word Art” images embedded in pages are not migrated properly.

Req2687

Installation

The installation program prompts the user for the Notes program and data directories using values derived from registry settings on the local machine.  Because the registry settings on the local machine may not be set correctly, please double check them and correct them manually if needed.  Also, there is no directory browser available to assist the user in locating these directories.

 

All data are conducted in the time zone of the local machine.  All Notes date/time values in Notes documents will be correctly converted to "local" time and saved as such in SharePoint, but the time zones used in the original Notes documents are lost.  (A workaround for this would be to use @formulas to retrieve time zone information separately.

 

When installing Notes Migrator for SharePoint Services, if you click on ‘License Info’ in the About Box, the Registration.config file may get created in such a way that the Application Pool Identity for the Import Service (e.g. ‘NETWORK SERVICE’) will not be able to write to that file. If the Application Pool Identity is not able to write to the Registration.config file, you will receive 'Unauthorized access' errors while migrating documents. To avoid this, add the Application Pool Identity to the list of users who are given permission to write to that file. If you do not click on ‘License Info’ in the About Box, the Registration.config file will be created during the first migration and the permissions should be set correctly.

CR54151
If MOSS is removed from the machine before removing NMSP, the NMSP Services will not uninstall properly. Uninstall NMSP before uninstalling MOSS. CR57655
When running Lotus Notes on Vista, you may receive the following error in the Setup Wizard when the NMSP Console is launched for the first time: 'Can't initialize Notes session'

Below are the links to the IBM documents describing the support for Notes on Vista:

http://www-01.ibm.com/support/docview.wss?uid=swg21252343

http://www-01.ibm.com/support/docview.wss?uid=swg21269041

The current workaround is:

1) Turn off the UAC on Vista.
2) Install our product.
3) Turn UAC back on.

CR61026

 


Upgrade and Compatibility

For upgrading Notes Migrator for SharePoint 4.x or 5.x to version 5.2.1, uninstall your current version of Notes Migrator for SharePoint. Then follow the installation instructions in the NotesMigratorForSharePoint.chm document included with this release. Use the NMSP Install Checklist.doc document as your installation guide.

 

If you are upgrading from a 5.0 Quest NMSP Repository database and you need the new Quickr classification rules, you must do one of the following:

1) Open both your Quest NMSP Repository database and the QuestRepository.ntf template in Notes and copy the documents containing the Quickr classification rules from the template to your Repository database.

2) Create a copy of DefaultTechnicalClasses.xml and remove all of the classification rules other than the Quickr ones. Then use this xml file to import those rules into the Console (using Classification Rules->Technical Classification Rules->Import classes).

 

The Quickr classification rules are part of the QuestRepository.ntf and the DefaultTechnicalClasses.xml that we are shipping with 5.1. If you are upgrading from 4.x, these rules will be included in your new Repository database along with the other delivered classification rules.

 

NOTE


The location of the job files has changed in 5.0. In 4.x, NMSP looked for job files in the same path in which the data definitions were stored.  By default, this path was C:\Documents and Settings\All Users\Application Data\Quest Software\Notes Migrator For SharePoint\4.0\Data Definitions (This path can be configured in the Options settings, so you may have set it to refer to a different location. In 5.0, you can configure separate locations for your job files and data definitions. By default, the path for the job files is C:\ Documents and Settings\All Users\Application Data\Quest Software\Notes Migrator For SharePoint\5.0\Job Files. You must either update this new Options setting to point to where you currently store your job files or move your job files to this new location.

 

 

 


System Requirements

Before installing Notes Migrator for SharePoint, ensure your system meets the following minimum hardware and software requirements:

 

Notes Data Extraction*:

 

SharePoint Data Load*:

 

NMSP Console

 

* Notes Data Extraction and SharePoint Data Load may occur simultaneously in a single process or may occur in different processes on different machines.

 


Global Operations

This section contains information about installing and operating this product in non-English configurations, such as those needed by customers outside of North America. This section does not replace the materials about supported platforms and configurations found elsewhere in the product documentation.

 

This release is Unicode-enabled and supports any character set. It supports simultaneous operation with multilingual data. This release is targeted to support operations in the following regions: North America, Western Europe and Latin America, Central and Eastern Europe, Far-East Asia, Japan.

 


Getting Started

Contents of the Release Package

The Notes Migrator for SharePoint release package contains the following products:

  1. Quest Notes Migrator for SharePoint 5.2 Console for 32-bit workstations and SharePoint servers
  2. Quest Notes Migrator for SharePoint 5.2 Designer for 32-bit workstations and SharePoint servers
  3. Quest Notes Migrator for SharePoint 5.2 Services for 32-bit SharePoint servers
  4. Quest Notes Migrator for SharePoint 5.2 Services for 64-bit SharePoint servers
  5. Quest Notes Migrator for SharePoint 5.2 Desktop
  6. Product Documentation, including:

The table below can be used to help determine which clients you will need:

 

 

Designer

Console

Command line

Desktop Toolbar

LotusScript API

Discover and Analysis Notes databases

 

 

 

 

Design migration jobs

 

 

 

Run migration jobs

Automates target and migration job assignments

 

 

 

 

Runs many migration jobs in batches

 

 

 

Provision SharePoint lists & libraries

Provision SharePoint sites & sub-sites

 

 

 

 

Supports direct SharePoint connections (32 bit SharePoint only)

 

 

Supports remote SharePoint connections (requires Import Service)

Supports use of intermediate XML data files

 

 

 

Manage migration project and track progress

 

 

 

 

Reports, charts and data export

 

 

 

 

Integrates with Notes client

 

 

 

Intended for I.T. pros and consultants

 

 

Intended for end-users

 

 

 

Supports scripting

 

 

 

Requires custom development

 

 

 

 

Which installer?

All Clients

Desktop Only

 

Installation Instructions

Security Access Requirements

Notes Migrator for SharePoint requires access to various Notes/Domino program and data files.  Make sure that the Windows login account you are using has Full Control rights to access the Notes/Domino Program and Data directories.  In addition, your account will need access to SharePoint as well as rights to access certain Windows registry keys (under the HKLM\Software\Quest Software key).

Notes/Domino  Configuration

While the local copy of Lotus Notes or Domino does not need to be running to use Notes Migrator for SharePoint, it does need to be properly configured.  If this is a new Notes/Domino installation, you will need to run it one time to complete the setup process and make sure that it is properly configured within your organization's Domino domain.  This automated process includes assigning a Notes ID file, setting up a local address book, and creating connections to other Domino servers.

If later you find that Notes Migrator for SharePoint cannot connect to a particular Domino server or database, you may want to run the Notes client again to verify that it can connect to the desired destination and, if not, make the needed configurations there.

 

Refer to NotesMigratorForSharePoint.chm for complete installation instructions:

 


History of Changes in Previous Releases

 

Version 5.1

This release of Notes Migrator for SharePoint includes:

The following bugs were fixed in this release:

CR60940 License validation should be done at the time of adding a license to the Console
CR60989 Installer should warn in the beginning of the process when installing 32-bit binary on a 64-bit machine
CR61026 Getting Initialization error in the Console Set Up wizard on Vista
CR61127 The "Allow Deletion of SharePoint records" checkbox needs to be available in the Console Advanced Configuration Options
CR61131 The default QP-Discussion job associated with the QuickPlace Classes (in our Notes template) now properly preserves response hierarchy in all cases.
CR61142 Fixed zeroing out of analysis properties DesignDocs and DataDoc when Discovery process is repeated
CR61149 Descriptions given to SharePoint groups created for ACL roles when using the "Map ACL Roles to SharePoint Site Groups" job option don't make sense in 5.0.
CR61266 Japanese characters are being encoded as “%e9” in one place and “%E9” in another place hence the SharePoint site name has 'Tofu' characters
CR61808 The Select Site window needs to automatically select the new target site when a new site is added.
CR61864 Fixed cases where certain “Excluded Users” were not being excluded from usage analysis
CR61943 HTML Rendering:  fixed rendering of margins in nested tables and rich text fields inside a table and fixed rendering of hotspots (including doc links) inside sections
CR62244 When importing a migration job into a Classification Rule that doesn't have a source data definition, the user receives an exception
CR62379 Fixed hang bug in certain long running operations (especially discovery of QuickPlaces). Fixed rare crash bug with error message “The following operation is not valid because the class View has shut down
CR59916 HTML Rendering:  support for “pop-up” hotspots and “hover-over” hotspots
CR53959 When auto-generating SharePoint columns from Source columns, handle reserved names such as “Type” correctly.
CR60696 “Trial Mode” does not show up when first launch the Designer but shows up when loading a job. This was corrected so “Trial Mode” shows up first time.
  Creating MIME documents from plain text fields now works correctly.
CR62794 Doc Links within sections now migrate correctly.
CR63899 Attachment MIME parts are named incorrectly if the attachment name contains XML encoded characters
CR63552 Attachment MIME parts are named incorrectly if the attachment name contains a non-ASCII character

 

Version 5.0

This release of Notes Migrator for SharePoint includes a new client called the NMSP Console. The NMSP Console provides a higher level view of your migration process than the NMSP Designer does. Rather than focusing on designing and running one migration job for one Notes database, the console looks across many databases (potentially all the databases in your organization) and helps you control the entire migration process.

The following bugs were fixed in this release:

CR49904 When a Domino.Doc binder name contains a forward slash it results in a SharePoint folder cut off at the slash, and a subfolder named with what followed the slash. Do not convert "/" characters in binder names into subfolders for Domino.Doc.
CR54630 Designer exits after user clicks Cancel in the 'Save Transfer Job' dialog. Clicking cancel to a Save operation should take user back to Designer.
CR54021 "Index was outside the bounds of the array" error when migrating repeating calendar entry
CR55883 "Map Event/Recurrence Data" option gets re-enabled when loading job
CR55574 All-day repeating events in older Notes templates are not migrated correctly
CR57464 "Invalid character" errors when mapping ACL entries containing multi-byte characters
CR57440 Error parsing EntityName when migrating to InfoPath form
CR57291 Migrated calendar shows duplicate entries for certain recurring events
CR56438 Recurring events are not being migrated to SharePoint correctly
CR56693 "Index was outside the bounds of the array" error migrating calendar entries
CR56440 "Unexpected error" opening recurring calendar items in SharePoint
CR56439 Calendar items with yearly recurrences are not migrated correctly
CR55726 Repeating events using certain intervals are not migrated correctly
CR55883 "Map Event/Recurrence Data" option gets re-enabled when loading job

Version 4.5

This release of Notes Migrator for SharePoint includes a new mode of migrating documents, known as Ad Hoc Migration. In contrast to the bulk application content migration provided by the NMSP Designer, the NMSP Desktop client enables ad hoc, self-service transfer of Notes documents to SharePoint directly from the user’s desktop. Now end-users can select the Notes documents they want to push to SharePoint and drag them to Windows toolbar icons, which represent predefined sets of rules for converting data and writing them to specific SharePoint targets. Similarly, Notes developers can use NMSP’s LotusScript APIs to plug this functionality right into existing Notes client applications, giving them complete control of the end user experience and any associated business rules.

The new NMSP Jobs Gallery is a specialized document library on your SharePoint site that allows you to upload complete migration job definitions for use by NMSP Desktop users. Unlike the Notes Migrator for SharePoint Designer, which is typically used by IT personal and other power users to design migration jobs and migrate entire Notes applications, NMSP Desktop is typically integrated into Notes applications for use by many users using shared Job Definitions.

For more information, please see the Notes Migrator for SharePoint Desktop chapter of the NotesMigratorForSharePoint.chm document included with this release.

The Notes Migrator for SharePoint User Guide is now delivered as a CHM file (Compiled HTML). The CHM file gives you features such as Table of Contents, indices to different topics, and search capability.

The following bugs were fixed in this release:

CR53185 "Value does not fall within the expected range" error migrating calendar to French version of SharePoint
CR53135 Import Service has problems with SharePoint list names containing accented characters
CR43190 Error when using a Notes field other than "WindowsName" in User Mapping Notes database
CR53049 "Failed to allocate a managed memory buffer" exception when migrating documents with large amounts of data
CR50623 Various "Object reference not set to an instance of an object" exceptions when SharePoint returns a null site collection in its enumeration of site collections in a web application
CR53045 "Delete current SharePoint List items" doesn't delete the SQL records for items in folders
CR53114 The Notes/Domino Data Files Folder field in the setup is too short
CR51067 ACL entries not specifically marked as Person or Group should be attempted to map as both User and Group before failing
CR52872 Duplicate document handling options don't work unless NMSP provisions a new SharePoint field
REQ2590 The tool now detects when Source Definitions, Target Definitions, or Job Definitions have been modified in the user interface and will prompt the user to save them.
REQ2595 The Test User Mapping now shows the complete chain of events:
1. Input Notes Name
2. Input Translation method used
3. Result of Input Translation
4. Lookup method used
5. Result of the lookup
6. Result of validating the above name as a Windows account

The Test User/Group Mapping is now available from the Import Service configuration page

REQ2601 Logging improvements - Logging summary statistics at end of a job and counting warnings
REQ2599 Designer UI improvements:
  1. Added the ability to go to the database/SharePoint list in Select Database and Select List dialogs.
  2. Launch Help File from Console
  3. Improve log viewer. When opening an error log file that contains a summary element, the dialog now shows two tabs: a "friendly" summary view showing one line per document, and a detailed view.
  4. Modify "Select SharePoint List" dialog
  • Add icons for web applications, sites/subsites, lists.
  • When expanding a tree node for a SharePoint site, display a "Site Content" node (for the parent of the lists in the site) and a node for each subsite.
  • If the tree node for a site has a parent, display the site "Title" (instead of a relative URL). (In the remote load case, we want to display an URL for the top-level site to display an URL, but the Title for subsites).
  • When expanding a node that contains items you are not authorized to access, just filter them out; don't show an exception dialog.
  • For the direct load case, when expanding a web application node, don't add a node for each site collection. Instead, add a node for the root web of each site collection.
  • For the remote load case, don't assume that the URL is a site collection URL; treat it as a site URL instead.
  • Change the default selection for the "Show Lists of Type" selector to be "<All>".
REQ2704 Match Default Data Definitions for R7, R8 Templates
REQ2857 Services should be configured per-Site Collection (not per-Web Application)
REQ2896 Validate support for Windows 2008

Back to Top


For More Information

Contacting Quest Software:

Email info@quest.com
Mail Quest Software, Inc.
World Headquarters
5 Polaris Way
Aliso Viejo, CA 92656
USA
Web

http://www.quest.com

Refer to our web site for regional and international office information.

Contacting Quest Support:

Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract.
Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at http://support.quest.com/.

From SupportLink, you can do the following:

View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures.
The guide is available at: http://support.quest.com/pdfs/Global%20Support%20Guide.pdf.

 


 

© 2009 Quest Software, Inc.

ALL RIGHTS RESERVED.

 

This document contains proprietary information protected by copyright. The software described in this document is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser’s personal use without the written permission of Quest Software, Inc.

 

If you have any questions regarding your potential use of this material, contact:

Quest Software World Headquarters
LEGAL Dept
5 Polaris Way
Aliso Viejo, CA 92656

 

http://www.quest.com/

Email: legal@quest.com

Refer to our web site for regional and international office information.

 

Trademarks

Quest, Quest Software, the Quest Software logo, Aelita, AppAssure, Benchmark Factory, Big Brother, DataFactory, DeployDirector, ERDisk,   Foglight, Funnel Web, I/Watch, Imceda, InLook, IntelliProfile, Internet Weather Report, InTrust, IT Dad, JClass, Jint, JProbe, LeccoTech, LiteSpeed, LiveReorg, NBSpool, NetBase, Npulse, PerformaSure, PL/Vision, Quest Central, RAPS, SharePlex, Sitraka, SmartAlarm, Spotlight, SQL LiteSpeed, SQL Navigator, SQLab, SQL Watch, Stat, Stat!, StealthCollect, Tag and Follow, Toad, T.O.A.D., Toad World, Vintela, Virtual DBA, Xaffire, and XRT are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners.

 

Third Party Contributions

Copyright (c) 2003, Jeff Lee, All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

 

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

 

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

 

Disclaimer

The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document.