June 10, 2013 at 2:09 pm
Hello
I am running SQL Server Enterprise 2008 RTM and need to upgrade to service pack 3 to support a database on a 32 bit server (Windows Server 2008 standard sp2).
I tried installing SP3 first but it failed.
I then tried installing SP2 and received a message to install the .NET 4.0 framework
The framework was installed and I have a one hour window tommorow to install SP3.
I'm going to have SP1 ready too in case I need to run them consecutively.
I am new to service packs - the one experience I had was to make sure reporting services was running. I suspected the reason for the error this time was also related to Report Services because the log in the bootstrap folder (C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20130610_121337 on mine) stops listing the instance ID.
I don't know why SP3 would stop at report services while SP2 let me know I needed the .NET framework. (why didn't sp3 tell ask for the framework?)
It says to check the logs so I assume they mean the bootstrap logs. I don't see anything in the SQL logs through SSMS.
It also seems unusual that the INSTANCENAME reads <empty.
User Input Settings:
ACTION: Patch
ALLINSTANCES: False
CLUSTERPASSIVE: False
CONFIGURATIONFILE:
HELP: False
INDICATEPROGRESS: False
INSTANCENAME: <empty>
QUIET: False
QUIETSIMPLE: False
X86: False
Could you please offer advice installing patches/trouble shooting? Am I supposed to stop services? ( I tried it, didn't work)
Thanks in advance
Dave
June 11, 2013 at 12:35 am
I can't help you because in our environment I have never installed SP3 on a fresh installation. But an installation will record all actions in files in the ...\setup bootstrap\log\{datetime} folder. It is a lot of reading and sometimes not really clear, but the error is mentioned in these files.
One hard-found issue we had when rolling out SP3 is all the default path's (for data-, log- and back-up) defined in the SQL instance must exist.
June 11, 2013 at 8:39 am
Thank you for replying - I found this link
I'm not sure if it was from the boot log after applying SP2 or SP3.
I'm not sure what is involved with uninstalling the SQL Server Native Client - sounds like it would cause problems.
I'm going to try SP2 again since the .Net famework was installed like it asked.
I may have another opportunity at lunch and will try then. Any other advice is appreciated.
Thanks
Dave
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply