Strange Install Error
-
On my 4th upgrade, and I get this errror:
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
The log file path (C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.ini) is invalid.
*
The path may contain invalid characters.
* The file may exist but not be writable, the folder may not exist,
the folder may be located on an unavailable volume or protected with a password, or the path may contain
environment variables that are not set (e.g. TEMP). To proceed, make sure that the log file path is valid,
writable, and available, and then run SQL Server Setup again.
For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=70341
------------------------------
BUTTONS:
OK
------------------------------
Press okay and I get this:
TITLE: Microsoft SQL Server 2005 Setup
------------------------------
Invalid INI file. Make sure the file exists, have access and has the correct entries.
------------------------------
BUTTONS:
OK
------------------------------
The path is good... But no .ini file is there... No .ini file on the other installs either... The links to MS are of no help.
Ideas appreciated.
[font="Verdana"]-- Wally
-- Reluctant DBA[/font] -
Hi Warren,
Which version of SQL 2005 are u trying to install?I believe u have backed up your db's prior to that...
Do u see an errorlog file in the installation folder?
The setup.ini file contains information regarding the install process.U can view it from the installation cd.
-
Standard Edition. This is the only thing applicable from the local install log:
Microsoft SQL Server 2005 Setup beginning at Wed Oct 04 09:42:40 2006
Process ID : 1080
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.exe Version: 2005.90.1399.0
Running: LoadResourcesAction at: 2006/9/4 9:42:40
Complete: LoadResourcesAction at: 2006/9/4 9:42:40, returned true
Running: ParseBootstrapOptionsAction at: 2006/9/4 9:42:40
Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\xmlrw.dll Version:2.0.3604.0
Complete: ParseBootstrapOptionsAction at: 2006/9/4 9:42:40, returned true
Running: ValidateWinNTAction at: 2006/9/4 9:42:40
Complete: ValidateWinNTAction at: 2006/9/4 9:42:40, returned true
Running: ValidateMinOSAction at: 2006/9/4 9:42:40
Complete: ValidateMinOSAction at: 2006/9/4 9:42:40, returned true
Running: PerformSCCAction at: 2006/9/4 9:42:40
Complete: PerformSCCAction at: 2006/9/4 9:42:40, returned true
Running: ActivateLoggingAction at: 2006/9/4 9:42:40
Complete: ActivateLoggingAction at: 2006/9/4 9:42:40, returned true
Running: DetectPatchedBootstrapAction at: 2006/9/4 9:42:40
Complete: DetectPatchedBootstrapAction at: 2006/9/4 9:42:40, returned true
Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions:
Condition "EventCondition: __STP_LaunchPatchedBootstrap__1080" returned false.
Action "BeginBootstrapLogicStage" will be skipped due to the following restrictions:
Condition "Setup is running locally." returned true.
Running: PerformDotNetCheck2 at: 2006/9/4 9:42:40
Complete: PerformDotNetCheck2 at: 2006/9/4 9:42:40, returned true
Running: InvokeSqlSetupDllAction at: 2006/9/4 9:42:40
Loaded DLL:C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\sqlspars.dll Version:2005.90.1399.0
The log file path (C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\setup.ini) is invalid.
* The path may contain invalid characters.
* The file may exist but not be writable, the folder may not exist, the folder may be located on an unavailable volume or protected with a password, or the path may contain environment variables that are not set (e.g. TEMP). To proceed, make sure that the log file path is valid, writable, and available, and then run SQL Server Setup again.
Error: Action "InvokeSqlSetupDllAction" threw an exception during execution.
Setup helper module failed to read ini file : -204
Message displayed to user
Invalid INI file. Make sure the file exists, have access and has the correct entries.
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_DEVSQL06GP3_.NET Framework 2.0.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0003.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_DEVSQL06GP3_.NET Framework 2.0 LangPack.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0003.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_DEVSQL06GP3_.NET Framework Upgrade Advisor.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0003.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_DEVSQL06GP3_.NET Framework Upgrade Advisor LangPack.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0003.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_DEVSQL06GP3_.NET Framework Windows Installer.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0003.cab" Error Code : 2
Error: Failed to add file :"C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0003_DEVSQL06GP3_.NET Framework Windows Installer LangPack.log" to cab file : "C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\SqlSetup0003.cab" Error Code : 2
Running: UploadDrWatsonLogAction at: 2006/9/4 9:42:49
Message pump returning: 4294967092
[font="Verdana"]-- Wally
-- Reluctant DBA[/font] -
I would like you to check below enviornment variables
TEMP and TMP
Make sure that they are valid. If possible change them to C:\TEMP for installation.
-
I got these errors because I was installing via remote desktop, and had copied the media to a directory on the server; see http://support.microsoft.com/?kbid=916760 if that's your problem. (client cd should be copied to a directory name 'tools', use this setup.exe to install help and client tools; copy cd1 to a directory named 'server'.
HTH, Mary Bahrami
-
That was my issue as well... Never followed-up and posted.
[font="Verdana"]-- Wally
-- Reluctant DBA[/font]
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply