Knowledge Base >> Troubleshooting alarmVM Install Problems

Troubleshooting alarmVM Install Problems - Confio Article 1610

Confio Article:	1610	Published:	Sep 07 2011 12:34 PM
Version:		Topic(s):	Install and Setup VMware
Product(s):	Ignite
Database(s):	VMware

Troubleshooting alarmVM Install Problems

alarmVM installs SQL Server Express 2008 R2 to use as a repository for monitoring data. The SQL Server Express installation can run into several problems. This KB article will primarily be focused on SQL Server install problems.

Background

The alarmVM install includes the install for SQL Server Express 2008 R2 with the following settings:

Creates a SQL Server instance called "CONFIO". By default, alarmVM is configured to connect to the "localhost\CONFIO" instance.
Enable TCP/IP and Named Pipe connections.

Troubleshooting

The SQL Server installer writes log files to:

<program files>\Microsoft SQL Server\100\Setup Bootstrap\Log
In the above directory, you will find a file called "summary.txt" as well as a timestamped directory name for each SQL Server install attempt. The timestamped directory contains files with detailed information about the error.

The following sections list the common SQL Server install issues and possible workarounds.

If you cannot resolve the SQL Server issue and you already have a SQL Server instance, you can connect alarmVM to it. To do so, see KB article 1611.

ISSUE: SQL Server install failed message during alarmVM install

Symptom:

During the alarmVM install, a dialog appears saying "The installation of Microsoft SQL Server 2005 Express appears to have failed. Do you want to continue the installation?"

Probable Workaround:

Stop the install by answering "No" to the install question, then reboot the machine and restart the install.

ISSUE: alarmVM gives error after its initial setup screen

Symptoms:

alarmVM gives error "Server localhost host no instance named CONFIO".
SQL Server appears to have installed successfully, and the SQL Server Configuration Manager shows that the "SQL Server (CONFIO)" service is running.
Restarting the "SQL Server (CONFIO)" service fails.
If you look in the Windows Event Viewer, you see an Application log entry that the system cannot find the file "e:\sql10_main_t.obj.x86fre\sql\mkmastr\databases\objfre\i386\MSDBLog.ldf".