IcebergX

Introduction

This installation guide contains late breaking information about the Express Installation of Iceberg. this installation uses a lightweight ASP.NET webserver called UltiDev Cassini. This means you can run Iceberg without having a copy of IIS installed, say on your home PC or laptop for quick evaluation.

As always, you first port of call should be the Iceberg Support Forum which contains real time information and solutions.

Installation Problems

If you encounter the following error during installation:

Windows Script component is not found on this computer. Please download Windows Script from Microsoft web site

Theres a detailed post in the support forums for the resolution. The solution is included here for your convenience

- Go to Start > Run (note: In Vista, enter the following text in the 'Search' area at the bottom of the start menu)
- Paste the following command and hit enter
regsvr32 c:\windows\system32\wshom.ocx
- It should say registration of wshom.ocx has succeeded if everything is OK.

Now if you restart the installation process you should find that it runs without complaint. 

Browser Timeout when clicking the link on the startup page after installation

Some people have had browser timeouts when trying to view the application for the first time. The first time the application loads, ASP.NET must perform initialisation steps (such as compiling the site) and this can take a few minutes on some machines. If you close the browser window, wait a minute, and then click the 'Iceberg' shortcut placed on your desktop by the installer, you should be presented with the login page.

Messages in the Event Log about SQL Server unavailability

The setup package will detect if you have SQL Server Express Edition installed on your PC, and if not, it will install it for you. If you already have SQL Express installed, then the setup assumes that it is active and its instance name is the default 'SQLEXPRESS'. If you see errors in the event log containing the following message:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Shared Memory Provider, error: 40 - Could not open a connection to SQL Server)

then ensure that SQL Server Express is installed and running as SQLEXPRESS. To do so, use the SQL Server Configuration Manager:

- Go to Start > All Programs > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Configuration Manager

- Select the SQL Server 2005 Services category on the left hand side of the window which appears

- Ensure that there is an entry for SQL Server (SQLEXPRESS) on the right, and that its current state is Running

- If it is not running, right click on the entry and select Start

Once the SQL Server instance is running, you can open Iceberg using the link on your desktop.