July 31, 2011 at 10:34 pm
hi
recently in my interview one question i faced that is while installing sqlserver in the middle installation failed .
question is 1) what we will do then how to rectify that problem
2) where will see the reason for that failure i mean where we will get that log file or information regarding installation failure
plz help me
August 1, 2011 at 2:59 am
srik780 (7/31/2011)
hirecently in my interview one question i faced that is while installing sqlserver in the middle installation failed .
question is 1) what we will do then how to rectify that problem
2) where will see the reason for that failure i mean where we will get that log file or information regarding installation failure
plz help me
1) It depends on the error
2) C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log and subfolders
100 stands for 2008/2008R2.
90 is for 2005
Hope this helps
Gianluca
-- Gianluca Sartori
August 2, 2011 at 6:39 am
If the failure happens while the setup support files are being installed, you may find the log files in a Temp folder, either the system temp folder or your personal temp folder.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
August 3, 2011 at 2:28 am
Answer 1: find the cause of the problem. Then think of solutions. Specific solutions cant be given as there are too many things that can go wrong to answer your question. I'll provide 2 examples further on.
Finding the cause of the problem: analyze windows logs and go after log/txt files and their contents.
No clue where to find 'm ? Do a file search on *.log and *.txt. Still nothing ? Do a file search on all files that have changed last day (as setup files contain their original date they wont obscure your overview).
Examples:
Example 1: corrupt installfiles.
The deinstall didn't work and the install didn't want to work anymore as the product was already installed. Log files weren't much of an help in this case. Solution: i went to cleaning up the registry, files etc. It took a while before i found out the source was the issue as the setup didn't check it's own files and finished but things (files) were missing... (sql 2005 btw)
Example 2:
A 2nd situation i had was that .Net was corrupt. The install went weird (i forgot details). After a long search i noticed compile errors for .Net. Fixed .net and then the install of sql went flawless.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply