infinias S-IMS-A Intelli-M Installation And User Manual page 118

APPENDIX B: TROUBLESHOOTING FAQ
Having User Account Control enabled while not logging in as Administrator could prevent the install from succeeding.
—
The system was unable to reboot and automatically restart the computer.
—
In any of these cases, you should be able to follow the instructions provided in the window to resolve the issue. If you are
unable to resolve your issue, please contact infinias Tech Support for more assistance.
Q
SQL Server installation failed, and I was asked whether or not to continue the installation.
What should I do?
A
Click No to abort the installation. If you already clicked Yes, you can still abort the installation if it's still running, or uninstall
it through the Control Panel. After the system is returned to its pre-installed state, view the SQL Server install logfiles to
determine the cause of the problem. The log files can be found in the "C:\Program Files\Microsoft SQL Server\100\Setup
Bootstrap\Log" folder. Inside that folder will be a folder whose name is a semi-readable form of the time and date that the
installation was attempted. The format of the folder name is "<this_year><two-digit-month><two-digit-day>_<six_
digit_time>". For example, "20130601_102434" indicates 6/1/2013 at 10:24:34 AM.
Open the folder whose name represents the most recent installation attempt. Inside the folder, inspect the two files named:
Summary_<computer_name>_ <install_folder_name>_GlobalRules.txt. Depending on how far the SQL installation
—
proceeded before the error, this file may not exist.
Summary_<computer_name>_<install_folder_name>_Component Update.txt
—
Open the "GlobalRules" file first. The top of the file has a block of text whose label is "Overall Summary." In that text block,
you'll see the result codes that occurred, and an "Exit Message" which contains a description of what caused SQL Server
installation to fail. If this file shows no errors near the top, then open the file whose name contains "ComponentUpdate."
The most common problem is that the system has a pending reboot, probably caused by a previous install or a Windows
Update that is pending. To resolve this problem, reboot the computer, then restart the Intelli-M Access installation. The
Intelli-M Access Prerequisite Manager attempts to discover a pending reboot before you start the installation, but SQL Server
uses a different pending reboot logic.
Another common (group of) error message(s) occurs when installing SQL 2008 with an earlier version of SQL Server pre-
installed. Depending on what SQL Server tools are already installed, you may have to manually uninstall older SQL tools and
utilities so they can be replaced by the newer ones found in the new SQL installation. You don't need to uninstall the entire
SQL Server or modify or remove existing databases. You may need to uninstall only the older SQL utilities that are replaced by
newer ones and which are backward compatible to your previous SQL installation.
If the error message is not clear, contact infinias Tech Support with a description of the problem to help resolve the issue.
112
www.infinias.com