Can't get certain products to install on server

Vampdee 0 Newbie Poster

14 Years Ago

I have a server that I just did a clean install on with Server 2008 Enterprise x-64. I have been having issues installing certain applications and unfortunately, I am at a loss as to why.
I installed SQL Server 2008 Std, which went fine, but SQL Server management studio will not install. It fails with no error message given. Also, there is no error in either the Application or the system log. I will post the installation log at the end of my post.
Another issue, and I am wondering if these are related, hence why I am posting this, is I am trying to install Access and Excel 2007 on the server (I know, that is not normal. Please don’t ask me to explain myself because you will be wasting my time). When I run this installer, it too fails with the following message: “Microsoft Office Professional 2007 encountered an error during setup”. Once again, nothing in the application or the system logs. This failure occurs almost immediately after the installation process begins – it doesn’t even create the directory to install the software.

Here is the log from the Management Studio install:

Overall summary:
Final result: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Exit code (Decimal): -2068052413
Exit facility code: 1212
Exit error code: 1603
Exit message: SQL Server installation failed. To continue, investigate the reason for the failure, correct the problem, uninstall SQL Server, and then rerun SQL Server Setup.
Start time: 2011-12-08 10:51:26
End time: 2011-12-08 10:54:53
Requested action: Install
Log with failure: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111208_105010\trin_aide_Cpu32_1.log
Exception help link: http://go.microsoft.com/fwlink?LinkId=20476&ProdName=Microsoft+SQL+Server&EvtSrc=setup.rll&EvtID=50000&ProdVer=10.50.1600.1

Machine Properties:
Machine name: ADFS02
Machine processor count: 4
OS version: Windows Server 2008
OS service pack: Service Pack 1
OS region: United States
OS language: English (United States)
OS architecture: x64
Process architecture: 64 Bit
OS clustered: No

Product features discovered:
Product Instance Instance ID Feature Language Edition Version Clustered
Sql Server 2008 R2 MEDSHAPE MSSQL10_50.MEDSHAPE Database Engine Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 MEDSHAPE MSRS10_50.MEDSHAPE Reporting Services 1033 Standard Edition 10.50.1600.1 No
Sql Server 2008 R2 Client Tools Connectivity 1033 10.50.1600.1 No
Sql Server 2008 R2 Client Tools Backwards Compatibility 1033 10.50.1600.1 No
Sql Server 2008 R2 Client Tools SDK 1033 10.50.1600.1 No

Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL Server 2008 R2
Type: RTM
Version: 10
SPLevel: 0
Installation location: F:\x64\setup\
Installation edition: STANDARD

User Input Settings:
ACTION: Install
ADDCURRENTUSERASSQLADMIN: False
AGTSVCACCOUNT: <empty>
AGTSVCPASSWORD: *****
AGTSVCSTARTUPTYPE: Manual
ASBACKUPDIR: Backup
ASCOLLATION: Latin1_General_CI_AS
ASCONFIGDIR: Config
ASDATADIR: Data
ASDOMAINGROUP: <empty>
ASLOGDIR: Log
ASPROVIDERMSOLAP: 1
ASSVCACCOUNT: <empty>
ASSVCPASSWORD: *****
ASSVCSTARTUPTYPE: Automatic
ASSYSADMINACCOUNTS: <empty>
ASTEMPDIR: Temp
BROWSERSVCSTARTUPTYPE: Disabled
CONFIGURATIONFILE: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111208_105010\ConfigurationFile.ini
CUSOURCE:
ENABLERANU: False
ENU: True
ERRORREPORTING: True
FARMACCOUNT: <empty>
FARMADMINPORT: 0
FARMPASSWORD: *****
FEATURES: SSMS,ADV_SSMS
FILESTREAMLEVEL: 0
FILESTREAMSHARENAME: <empty>
FTSVCACCOUNT: <empty>
FTSVCPASSWORD: *****
HELP: False
IACCEPTSQLSERVERLICENSETERMS: False
INDICATEPROGRESS: False
INSTALLSHAREDDIR: D:\Program Files\Microsoft SQL Server\
INSTALLSHAREDWOWDIR: D:\Program Files (x86)\Microsoft SQL Server\
INSTALLSQLDATADIR: <empty>
INSTANCEDIR: D:\Program Files\Microsoft SQL Server
INSTANCEID: MEDSHAPE
INSTANCENAME: MEDSHAPE
ISSVCACCOUNT: NT AUTHORITY\NetworkService
ISSVCPASSWORD: *****
ISSVCSTARTUPTYPE: Automatic
NPENABLED: 0
PASSPHRASE: *****
PCUSOURCE:
PID: *****
QUIET: False
QUIETSIMPLE: False
ROLE: <empty>
RSINSTALLMODE: FilesOnlyMode
RSSVCACCOUNT: <empty>
RSSVCPASSWORD: *****
RSSVCSTARTUPTYPE: Automatic
SAPWD: *****
SECURITYMODE: <empty>
SQLBACKUPDIR: <empty>
SQLCOLLATION: SQL_Latin1_General_CP1_CI_AS
SQLSVCACCOUNT: <empty>
SQLSVCPASSWORD: *****
SQLSVCSTARTUPTYPE: Automatic
SQLSYSADMINACCOUNTS: <empty>
SQLTEMPDBDIR: <empty>
SQLTEMPDBLOGDIR: <empty>
SQLUSERDBDIR: <empty>
SQLUSERDBLOGDIR: <empty>
SQMREPORTING: False
TCPENABLED: 0
UIMODE: Normal
X86: False

Configuration file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111208_105010\ConfigurationFile.ini

Detailed results:
Feature: Management Tools - Complete
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x1603
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111208_105010\trin_aide_Cpu32_1.log
MSI error description:
Configuration status: Passed

Feature: Management Tools - Basic
Status: Failed: see logs for details
MSI status: Failed: see details below
MSI error code: 0x1603
MSI log file location: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111208_105010\trin_aide_Cpu32_1.log
MSI error description:
Configuration status: Passed

Rules with failures:

Global rules:

Scenario specific rules:

Rules report file: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20111208_105010\SystemConfigurationCheck_Report.htm

1 Contributor
0 Replies
227 Views

Dani AI

Generated 7 Months Ago

: the SQL Management Studio MSI failures and the Office 2007 installer aborting immediately suggest an installer/environment problem (Windows Installer, permissions/UAC, pending reboot, temp-folder access, antivirus or missing prerequisite) rather than a product bug. The following focused checks are ranked by likelihood and effort; apply them in order and capture logs at the failing step.

Quick, high-value checks (run as an elevated/local Administrator account):

Reboot the server to clear pending operations.

Check for a pending reboot marker:

reg query "HKLM\SYSTEM\CurrentControlSet\Control\Session Manager" /v PendingFileRenameOperations

Ensure Windows Installer is healthy: re-register and restart it:

msiexec /unregister
msiexec /regserver
net stop msiserver
net start msiserver

Clean and verify temp folders (%TEMP% and %SYSTEMROOT%\Temp) exist and are writable by the installing account. Empty them before retrying.
Temporarily disable antivirus/endpoint protection and any software restriction policies.
Confirm .NET prerequisites for SQL management tools are present (common requirement: .NET 3.5.x for SQL 2008/R2 tools).
Install from a local, short path (extract media to C:\Install) rather than a network share or deeply nested folder.

Gather verbose logs if the problem persists:

For general MSI activity use:

msiexec /i "path\package.msi" /l*v C:\logs\msi_verbose.log

For SQL Server, capture the Setup Bootstrap logs (the Setup log folder) and the System Configuration Check report before posting.

Product-specific notes:

If performing an unattended SQL install, make sure the configuration file explicitly accepts the license (IACCEPTSQLSERVERLICENSETERMS=TRUE) and verify INSTALLSHAREDDIR/permissions if installing to a nonstandard drive.
For Office 2007, run the installer elevated from a local extracted source and capture an MSI log for the core MSI (extract if needed). If the setup exits before creating any folders, Procmon will show which access failure stops the process.

If logs are available after these steps, attach the MSI verbose log(s) and the SQL Setup Bootstrap log so the failure point can be identified precisely.

Be the first to reply

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.