You are here: Getting Started > Technical Support

## Technical Support

Most technical issues can be resolved using the various resources you have available. In addition to the product documentation and the README file, LizardTech offers a knowledge base and product updates on the LizardTech website.

###### Knowledge Base

http://www.lizardtech.com/support/kb/

The LizardTech Knowledge Base contains articles about known technical and usage issues and is frequently updated.

###### Developer Website

http://developer.lizardtech.com

The LizardTech Developer Website provides you with the tools you need to support viewing MrSID and JPEG 2000 formats within your application: downloadable C++ SDKs, technical notes and documentation and a link to additional email support.

###### Community Forums

http://www.lizardtech.com/forums/

The fora are a place to engage in intelligent discourse with the geospatial community. Ask questions, provide answers, and share product usage tips with other Lizardtech customers around the world.

###### Product Updates

http://www.lizardtech.com/products

Updated versions of LizardTech viewer tools are available for download at no cost.

###### Support Plans

http://www.lizardtech.com/purchase/other.php

Protect your investment in LizardTech software by participating in a LizartTech support plan. For more details, please contact your regional LizardTech office.

###### Contacting Technical Support

http://www.lizardtech.com/support

To contact technical support, visit the website at the above URL and follow links to the LizardTech Knowledge Base or the Product Activation page. A Contact Form is also provided for issues that require further assistance.

In an emergency, call 206-902-2845 between the hours of 8 AM and 5 PM Pacific Time.

IMPORTANT: Please have the following information available to assist in resolving your problem:

- Which version of the MrSID SDK you are running
- Other LizardTech products you have installed
- Which operating system you use
- How much free hard drive space your computer has
- How much RAM your computer has
- Version of compiler
- Copy of source code demonstrating the problem, simplified as much as possible
- Relevant test data to allow us to reproduce the problem
- Copy of compiler error messages if appropriate