Need SQL Server service packs installation procedure

Hey Guys,
I am in the process of installing service packs to my SQL Server 2008 and R2 editions, I was searching for the installation procedure in technet for this but nothing was provided for this, I tried to read the
"readme" and setup documentation provided in the SP 4 download page but its useless since its redirecting again to some other page which again points to same download page, It makes me wonder if there are any procedures provided by Microsoft for
this. Let me know if anyone has it. I don't want to follow any third party websites/ individual bloggers providing best practices/installation procedures.
My Environment: SQL SERVER 2008/ R2 (STANDARD) and these are standalone
machines.
OS: Windows server 2008 R2 STANDARD
With regards,
Gopinath.
With regards, Gopinath.

Copy the patch files to the server
Run the patch file and follow the on-screen instructions
Select the instances that you wish to patch
Allow the patch to finish
Reboot if a reboot is required (the patch will tell you if there were any locked files)
For more info refer this link
Please Mark this as Answer if it solved your issue
Please vote this as Helpful information if it helps to solve your issue

Similar Messages

MSCS SQL Server Service Pack Installation

Dear All,
We are using Microsoft Cluster and i completed Microsoft SQL Server 2005 Installation on Cluster.
Now when i am trying to Install Service Pack 2 of SQL Server i can't get success when both node are running.
But when i swhiched off Node 2 and did installation on Node 1 i get success.
But after finishing Installation on Service Pack 2 i can't get that service pack on Node 2.
Here i want to confirm that i have to do installation of Service Pack 2 on both node ?
Regards,
Nikunj Thaker.

Hi,
Have you run the SQL 2K5 SP2 upgrade on the other node. What happens is that you upgrade the SQL Server binaries on the Clustered instances but not the local files.
If you run SP2 on the "Passive" node it will upgrade server compoments that are not cluster aware (like SSIS). I normally upgrade the Client Components first on the passive node, reboot and then upgrade all components on the active node afterwards.
On a standalone machine - all components are upgraded at the same time - both per instance and the server components so you won't have that issue.
--Kishore

SAP List of Supported SQL Server Service Packs and Cumulative Updates

Does SAP provide a list of SQL Server Service Packs and Cumulative Updates that will work with BPC 7.0 and 7.5? I see that CU 12 is out for SP1 and CU 2 is out for SP2. I would like to know if I can move the SP2 CU2 or SP1 CU12. My install docs are outdated specifying SP1 CU6.
Any direction is appreciated.
Joe

Hi,
Please take a look at the below list of the supported OS: This excerpt is from the installation guide.
SP04 or later: Windows Server 2008 R2 Standard or Enterprise Edition with or without Hyper-V
Windows Server 2008 Standard or Enterprise Edition with or without Hyper-V, or
Windows Server 2008 Data Center with or without Hyper-V
Windows Server 2003 Standard or Enterprise Edition SP2
Windows Server 2003 Standard configured on the SQL database or OLAP server components only
Windows Server 2003 R2 Standard or Enterprise Edition SP2
SAP recommends using Windows Server 2008 64 bit over Windows Server 2003 64 bit. Otherwise, supportability is limited.
I am not sure what did you mean by the front end. Having said that, 32 bit is supported both on the server and the client machines.
Hope this helps.

Steps involved in Uninstalling SQL Server service packs

Hi,
Came to know that we can uninstall sql server service packs from SQL 2008 SP1 onwards.
Question is, for suppose i have installed SQL 2008 SP3 and found problem. Now I want to uninstall SP3, what are the steps involved to uninstall a service pack? Can we also uninstall QFE, Cummulative updates and hotfix's as well?
How does sql server does the rollback or uninstall of service pack behind the scenes?
Appreciate your help.
Thank you.

Hello,
@Cheer08: When SP1 CU3 and SP1 CU4 were released we found that some SQL Server users had issues with SSIS and SSRS, when these CUs were
uninstalled we found the issues continue, and we were back to normal when we reapplied SP1 or SP1 CU2.
@Samantha: About the Resource DB, it certainly plays a factor on applying updates and upgrading process, which is explained
here. About how it is used to allow rollback of updates
in SQL Server, the Resource DB seems to be used to copy back the objects and semantics to system databases as explained in the following article.
http://extremeexperts.com/sql/yukon/resourcedatabase.aspx
@Samantha: no official documents to my knowledge, I just have a real world experience on this as I mentioned to @Cheer08.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server Service Pack Support

An existing customer running PO 2.3.4 in production would like to upgrade their database servers from the base SQL Server 2008 R2 installation to either SP1 or SP2. Since these are not explicitly called out as supported in the product documentation, the customer would like to confirm that by applying a service pack they will not be considered to be running an unsupported configuration.
This is a SP customer running orchestration developed as part of a custom AS engagement, so they are not running out-of-the-box IAC content. So the question is being posed from a PO product support standpoint.
Thanks for any information you can provide.

The specific answer for you is yes it is supported. The general answer for MSSQL DB support is that we only document to the R level (MSSQL 2008 or MSSQL 2008 R2) in the compatibility matrix and service packs are supported but not necessarily tested as they come out.

Error with DQS after Installing SQL Server Service Pack 2

When I open the DQS client, I get this error message:
Message Id: VerificationFrameworkVersionNotCompatible
A new version of .NET or Data Quality Services was installed on this machine. In order to continue to work with DQS please run 'DqsInstaller.exe -upgrade'.
However, when I run DQSInstaller.exe, I get this message:
DQS Installer has detected a previous DQS installation under this SQL server instance. Running DQS installer will remove the previous installation, together with all the knowledge stored in it.
Will I lose all my knowledge bases? Is there an upgrade path?

Hi Adolfo Socorro,
According to your description, when you install SQL Server 2012 Service Pack2, the error of
Data Quality Services (DQS) will occur. The cause is that Product Updates will not update the schema of the DQS catalogs, any related MDS catalogs, and the SQL CLR assemblies kept the DQS catalogs. Therefore, extra steps may be required
if the DQS catalog schema needs to be upgraded, or the DQS CLR assemblies have been upgraded by the product update.
If you have previously run the DQSInstaller.exe to build the DQS_MAIN, DQS_PROJECTS, and DQS_Staging_Data catalogs in one or more of the updated instances, you
may need to continue to do the necessary upgrade steps to upgrade the database schemas, such as launch CMD as Administrator
cd "C:\Program Files\Microsoft SQL Server\MSSQL11.InstanceName\MSSQL\Binn" DQSInstaller.exe –upgrade
There is an article about upgrading DQS, you can review the following article.
http://social.technet.microsoft.com/wiki/contents/articles/8442.upgrade-dqs-installing-cumulative-updates-or-hotfix-patches-on-data-quality-services.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

KB2977326 - Security Update for SQL Server Service Pack 1 repeatedly fails to install

This update fails to install every day when I shut down my computer. Here is the WindowsUpdate.Log:
2014-12-02 15:50:11:469
420 44c
AU #########
2014-12-02 15:50:11:469
420 44c
AU # Initiating install at shutdown
2014-12-02 15:50:11:469
420 44c
AU # Approved updates = 1
2014-12-02 15:50:11:516
420 44c
AU <<## SUBMITTED ## AU: Install updates / installing updates [CallId = {685C12BB-7AA9-4A31-9620-8F306EEE31C3}]
2014-12-02 15:50:11:516
420 44c
Shutdwn InstallAtShutdown starts.
2014-12-02 15:50:11:516
420 1528
Agent *************
2014-12-02 15:50:11:516
420 1528
Agent ** START ** Agent: Installing updates [CallerId = AutomaticUpdates]
2014-12-02 15:50:11:516
420 1528
Agent *********
2014-12-02 15:50:11:516
420 1528
Agent * Updates to install = 1
2014-12-02 15:50:11:531
420 1528
Agent * Title = Security Update for SQL Server 2012 Service Pack 1 (KB2977326)
2014-12-02 15:50:11:531
420 1528
Agent * UpdateId = {E0D65CC4-3B13-4352-BD89-A28C5F4C5017}.200
2014-12-02 15:50:11:531
420 1528
Agent * Bundles 1 updates:
2014-12-02 15:50:11:531
420 1528
Agent * {C076E757-1A4F-44DB-823B-CFFC07CD7D38}.200
2014-12-02 15:50:11:547
420 16d8
Shutdwn InstallAtShutdown got install progress.
2014-12-02 15:50:12:327
420 d4c
Report CWERReporter finishing event handling. (00000000)
2014-12-02 15:50:20:548
420 44c
AU WARNING: Pending directive, 'Install Approval', is not applicable
2014-12-02 15:50:24:417
420 16d8
Shutdwn InstallAtShutdown got install progress.
2014-12-02 15:50:24:432
420 16d8
Shutdwn InstallAtShutdown got install progress.
2014-12-02 15:50:24:432
420 1528
DnldMgr Preparing update for install, updateId = {C076E757-1A4F-44DB-823B-CFFC07CD7D38}.200.
2014-12-02 15:50:25:119
2052 608
Misc =========== Logging initialized (build: 7.6.7600.320, tz: -0600) ===========
2014-12-02 15:50:25:119
2052 608
Misc = Process: C:\Windows\system32\wuauclt.exe
2014-12-02 15:50:25:119
2052 608
Misc = Module: C:\Windows\system32\wuaueng.dll
2014-12-02 15:50:25:119
2052 608
Handler :::::::::::::
2014-12-02 15:50:25:119
2052 608
Handler :: START :: Handler: Command Line Install
2014-12-02 15:50:25:119
2052 608
Handler :::::::::
2014-12-02 15:50:25:119
2052 608
Handler : Updates to install = 1
2014-12-02 15:50:25:119
420 16d8
Shutdwn InstallAtShutdown got install progress.
2014-12-02 15:52:23:991
420 44c
AU AU setting next sqm report timeout to 2014-12-03 21:52:23
2014-12-02 15:54:39:587
2052 608
Handler : WARNING: Command line install completed. Return code = 0x84b20001, Result = Failed, Reboot required = false
2014-12-02 15:54:39:587
2052 608
Handler : WARNING: Exit code = 0x8024200B
2014-12-02 15:54:39:587
420 16d8
AU >>## RESUMED ## AU: Installing update [UpdateId = {E0D65CC4-3B13-4352-BD89-A28C5F4C5017}]
2014-12-02 15:54:39:587
2052 608
Handler :::::::::
2014-12-02 15:54:39:587
2052 608
Handler :: END :: Handler: Command Line Install
2014-12-02 15:54:39:587
2052 608
Handler :::::::::::::
2014-12-02 15:54:39:587
420 16d8
AU # WARNING: Install failed, error = 0x80070643 / 0x84B20001
2014-12-02 15:54:39:587
420 16d8
Shutdwn InstallAtShutdown got install progress.
2014-12-02 15:54:39:711
420 1528
Report REPORT EVENT: {DFA9CDC8-334A-4E57-9588-77B8E980833D}
2014-12-02 15:54:39:587-0600 1
198 101
{E0D65CC4-3B13-4352-BD89-A28C5F4C5017}
200 80070643
AutomaticUpdates Failure
Content Install Installation Failure: Windows failed to install the following update with error 0x80070643: Security Update for SQL Server 2012 Service Pack 1 (KB2977326).
2014-12-02 15:54:39:727
420 1528
Report CWERReporter::HandleEvents - WER report upload completed with status 0x8
2014-12-02 15:54:39:727
420 1528
Report WER Report sent: 7.6.7600.320 0x80070643 E0D65CC4-3B13-4352-BD89-A28C5F4C5017 Install 101 Unmanaged
2014-12-02 15:54:39:727
420 1528
Report CWERReporter finishing event handling. (00000000)
2014-12-02 15:54:39:805
420 1528
Agent *********
2014-12-02 15:54:39:805
420 16d8
AU Install call completed.
2014-12-02 15:54:39:805
420 1528
Agent ** END ** Agent: Installing updates [CallerId = AutomaticUpdates]
2014-12-02 15:54:39:805
420 16d8
AU # WARNING: Install call completed, reboot required = No, error = 0x00000000
2014-12-02 15:54:39:805
420 1528
Agent *************
2014-12-02 15:54:39:805
420 16d8
AU #########
2014-12-02 15:54:39:805
420 16d8
AU ## END ## AU: Installing updates [CallId = {685C12BB-7AA9-4A31-9620-8F306EEE31C3}]
2014-12-02 15:54:39:805
420 16d8
AU #############
jim...

Hello,
Please examine the Summary.txt log file. The following article may help you locate the file on disk:
http://msdn.microsoft.com/en-us/library/ms143702(v=sql.110).aspx
If you find the sentence “A failure was detected for a previous installation” on the Summary.txt log file, please repair SQL Server using the following article:
http://msdn.microsoft.com/en-us/library/Cc646006(v=sql.110).aspx
If you find other errors, please share the content of the Summary.txt log file with us.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

SQL Server Service Packs (2008, 2008R2, 2012)

Hi all,
it appears that no one took care of installing Service Packs for our SQL Servers from WSUS and now i have to do it. What i have:
MS SQL Server 2008 R2 Service Pack 1
MS SQL Server 2008 Service Pack 1,2,3
MS SQL Server 2012 Service Pack 1,2
As you could see some of them a really old.
1. The fact that everything is running so far without any problems and complains bring the question: Do I have to install Service Packs?
2. Is it ok if I go directly to the latest Service Pack for each Server or i have to go the "entire road" installing one after another.
3. What is the best way to do the updates: Install all other security and critical updates, restart the server, then install the service pack and restart again the server.
Actually my knowledge for SQL Server and Updates for it are not so big that's why i want to apologies for the stupid questions. Thanks in advance

1. The fact that everything is running so far without any problems and complains bring the question: Do I have to install Service Packs?
Hi,
Yes very much recommended if your SQL server 2008 is not at SP/Sp4 it would not come under extended support purview. If you have 2008 r2 not with SP3 again you are out of extended support. For 2012 as well apply Sp2 .Mainstarem support for 2008/2008
R2 has already ended
2. Is it ok if I go directly to the latest Service Pack for each Server or i have to go the "entire road" installing one after another.
Hi,
Yes you can directly upgrade to SQL
Server 2008 SP4 because SP are cumulative and latest SP will include all fixes present in one released before it . As a fact you can always apply latest SP for any SQL server version for fact that it is cumulative. Dont go for SP3 go for SP4 in 2008 and
SP3 for 2008 r2
3. What is the best way to do the updates: Install all other security and critical updates, restart the server, then install the service pack and restart again the server.
Best way can be referred from below docs
http://msdn.microsoft.com/en-us/library/dd638062%28v=sql.100%29.aspx
http://social.technet.microsoft.com/wiki/contents/articles/25632.how-to-install-sql-server-2012-sp2-on-standalone-sql-server-instance.aspx
Just above doc is for 2012 but will hold true for 2008 as well. SP might require restart of Windows machine on which SQL Server resides.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

SQL Server Service Pack Install and SSRS Scale Out Environment

We have an error in our SSRS environment that looks to be addressed in SQL Server 2008 R2 SP3. Our set up is a scale out environment, 2 SSRS app servers and 1 SSRS database server. For simplicity as we are moving to 2012 soon, I would like to only install
the service pack on one of the SSRS app servers. Anyone aware of any reason besides keeping servers consistent to not do this? I don't want to go through the time to upgrade the SSRS SQL Server if I don't have to.
Thanks

Hello,
If you apply the service pack on the database server first, front-ends may not be able to provide service again until you
apply the SP to them too. I have no knowledge of other possible issue.
Remember to backup SSRS databases and encryption key before applying the service pack.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

AveConnect driver error after SQL Server service pack upgrade

I am currently testing aveConnect 3.0 (connection optimized) for SQL Server 2000 on a machine we have here.We updated SQL Server with Service Pack 2 & 3 this morning and since then we've been getting the exception below.This is only since we added the service packs to SQL Server,before it worked fine.
java.sql.SQLException: [Avenir][JDBC SQL Server Driver] Connection refused: connect
I also tested it with the older version of AveConnect (2.2) which we've been using until recently,and it returned the same error.
I am currently testing aveConnect 3.0 for SQL Server 2000 on a machine we have here.We updated SQL Server with Service Pack 2 & 3 this morning and since then we've been getting the exception below.This is only since we added the service packs to SQL Server,before it worked fine.If anyonecould provide any advice I would be very grateful,as this is pretty urgent.

Hi,
I just contacted the driver vendor (Atinav Inc).heard that aveconnect jdbc driver is now updated to work with latest SQL server fixes from microsoft.
FYI, aveconnect jdbc driver link http://www.atinav.com/products/aveconnect/aveconnect.htm
HTH,
-ashraff.

Unable to install SQL 2005 Service Pack 3 (Unable to install Windows Installer MSI file)

I'm unable to install SQL 2005 Service Pack 3. This results in the following error message: Unable to install Windows Installer MSI file.
Could someone please help me. Thanks in advance!
=== Verbose logging started: 3-4-2009 9:33:00 Build type: SHIP UNICODE 4.05.6001.00 Calling process: d:\5ddfa356349ddf2e676c336d95c5\hotfix.exe ===
MSI (c) (E0:88) [09:33:00:404]: Resetting cached policy values
MSI (c) (E0:88) [09:33:00:404]: Machine policy value 'Debug' is 0
MSI (c) (E0:88) [09:33:00:404]: ******* RunEngine:
           ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
           ******* Action:
           ******* CommandLine: **********
MSI (c) (E0:88) [09:33:00:404]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (E0:88) [09:33:00:404]: Grabbed execution mutex.
MSI (c) (E0:88) [09:33:00:419]: Cloaking enabled.
MSI (c) (E0:88) [09:33:00:419]: Attempting to enable all disabled privileges before calling Install on Server
MSI (c) (E0:88) [09:33:00:419]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (28:28) [09:33:01:747]: Running installation inside multi-package transaction C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
MSI (s) (28:28) [09:33:01:747]: Grabbed execution mutex.
MSI (s) (28:CC) [09:33:02:029]: Resetting cached policy values
MSI (s) (28:CC) [09:33:02:029]: Machine policy value 'Debug' is 0
MSI (s) (28:CC) [09:33:02:029]: ******* RunEngine:
           ******* Product: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
           ******* Action:
           ******* CommandLine: **********
MSI (s) (28:CC) [09:33:02:685]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (28:CC) [09:33:03:450]: File will have security applied from OpCode.
MSI (s) (28:CC) [09:33:03:841]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi' against software restriction policy
MSI (s) (28:CC) [09:33:03:841]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi has a digital signature
MSI (s) (28:CC) [09:33:04:841]: SOFTWARE RESTRICTION POLICY: C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi is permitted to run at the 'unrestricted' authorization level.
MSI (s) (28:CC) [09:33:04:888]: End dialog not enabled
MSI (s) (28:CC) [09:33:04:888]: Original package ==> C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
MSI (s) (28:CC) [09:33:04:888]: Package we're running from ==> C:\WINDOWS\Installer\3d3a713.msi
MSI (s) (28:CC) [09:33:05:497]: APPCOMPAT: looking for appcompat database entry with ProductCode '{53F5C3EE-05ED-4830-994B-50B2F0D50FCE}'.
MSI (s) (28:CC) [09:33:05:497]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (28:CC) [09:33:05:685]: MSCOREE not loaded loading copy from system32
MSI (s) (28:CC) [09:33:05:825]: Note: 1: 2203 2: C:\WINDOWS\Installer\2f1994e.msi 3: -2147287038
MSI (s) (28:CC) [09:33:05:825]: Opening existing patch 'C:\WINDOWS\Installer\e6ba0.msp'.
MSI (s) (28:CC) [09:33:05:825]: Note: 1: 2203 2: C:\WINDOWS\Installer\e6ba0.msp 3: -2147287038
MSI (s) (28:CC) [09:33:05:825]: Couldn't find local patch 'C:\WINDOWS\Installer\e6ba0.msp'. Looking for it at its source.
MSI (s) (28:CC) [09:33:05:825]: Resolving Patch source.
MSI (s) (28:CC) [09:33:05:825]: User policy value 'SearchOrder' is 'nmu'
MSI (s) (28:CC) [09:33:05:825]: User policy value 'DisableMedia' is 0
MSI (s) (28:CC) [09:33:05:825]: Machine policy value 'AllowLockdownMedia' is 0
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Media enabled only if package is safe.
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Looking for sourcelist for product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Adding {EE92F683-5F5C-4970-BB0B-9AC591B60268}; to potential sourcelist list (pcode;disk;relpath).
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Now checking product {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Media is enabled for product.
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Attempting to use LastUsedSource from source list.
MSI (s) (28:CC) [09:33:05:825]: SOURCEMGMT: Trying source \\NF04\d$\3db7739bf5c1bb9c50076c418420\HotFixSqlSupport\Files\.
MSI (s) (28:CC) [09:33:06:607]: Note: 1: 2203 2: \\NF04\d$\3db7739bf5c1bb9c50076c418420\HotFixSqlSupport\Files\SqlSupport.msp 3: -2147287037
MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.
MSI (s) (28:CC) [09:33:06:607]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Processing net source list.
MSI (s) (28:CC) [09:33:06:607]: Note: 1: 1706 2: -2147483647 3: SqlSupport.msp
MSI (s) (28:CC) [09:33:06:607]: SOURCEMGMT: Processing media source list.
MSI (s) (28:CC) [09:33:07:654]: SOURCEMGMT: Resolved source to: 'SqlSupport.msp'
MSI (s) (28:CC) [09:33:37:732]: Note: 1: 1314 2: SqlSupport.msp
MSI (s) (28:CC) [09:33:37:732]: Unable to create a temp copy of patch 'SqlSupport.msp'.
MSI (s) (28:CC) [09:33:37:732]: Searching provided command line patches for patch code {EE92F683-5F5C-4970-BB0B-9AC591B60268}
MSI (s) (28:CC) [09:33:37:763]: Note: 1: 1708
MSI (s) (28:CC) [09:33:37:763]: Product: Microsoft SQL Server Setup Support Files (English) -- Installation failed.
MSI (s) (28:CC) [09:33:37:763]: Windows Installer installed the product. Product Name: Microsoft SQL Server Setup Support Files (English). Product Version: 9.00.4035.00. Product Language: 1033. Installation success or error status: 1635.
MSI (s) (28:CC) [09:33:37:779]: MainEngineThread is returning 1635
MSI (s) (28:28) [09:33:37:888]: No System Restore sequence number for this installation.
This patch package could not be opened. Verify that the patch package exists and that you can access it, or contact the application vendor to verify that this is a valid Windows Installer patch package.
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\Cache\SQLSupport\x86\1033\SqlSupport.msi
MSI (s) (28:28) [09:33:37:888]: User policy value 'DisableRollback' is 0
MSI (s) (28:28) [09:33:37:888]: Machine policy value 'DisableRollback' is 0
MSI (s) (28:28) [09:33:37:888]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (28:28) [09:33:37:904]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\Rollback\Scripts 3: 2
MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (28:28) [09:33:37:919]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Installer\InProgress 3: 2
MSI (s) (28:28) [09:33:37:919]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (s) (28:28) [09:33:37:919]: Restoring environment variables
MSI (c) (E0:88) [09:33:37:935]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (E0:88) [09:33:37:935]: MainEngineThread is returning 1635
=== Verbose logging stopped: 3-4-2009 9:33:37 ===

This post should definitely help you
http://blogs.msdn.com/sqlserverfaq/archive/2009/01/30/part-1-sql-server-2005-patch-fails-to-install-with-an-error-unable-to-install-windows-installer-msp-file.aspx?CommentPosted=true
Feroz
Mark as Answer if it helps. This posting is provided "AS IS" with no warranties and confers no rights.

Stopping sql server services while applying Service pack On SQL server 2008 and 2008 R2

Hi,
I am planning to apply service pack 3 for SQL 2008 R2 and Service pack 4 for SQL server 2008. This is my first time and I am applying first QA and DEV environment. I have one confusion. In cluster once you fail over sql resources to active node all of the
sql services including SQLSERVER and Agent are automatically stopped in passive node where we apply service pack. But in Stand alone, The services are not automatically stopped. Do I need to manually stop those services like SQLSERVER, Agent, Browser
and others if any before I start applying service pack?
Early Response is highly appreciated.
Thanks In Advance

Hello,
You don’t need to stop SQL Server services. Let SQL Server setup do it as needed.
Please read the following article for the cluster you would like to update:
https://support.microsoft.com/kb/958734?wa=wsignin1.0
The following article may be useful too:
http://www.sqlcoffee.com/Tips0014.htm
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

Service accounts rights in Sql Server 2008 clustered installation.

I have to install Sqlserver 2008 in a 2 node clustered environment in
Windows Server 2008 R2. For that I have set up 4 less privileged
a/c in domain for Db engine, Sql agent, Reporting services and Analysis
service. During the installation I plan to specify these a/c's in the
domain to run the above 4 services under these a/c. I understand the sql server agent
a/c should have 6 rights in the local computer security policy
ie a)Adjust memory quotas for process,b)Act as a part of os,c)Bypass
traverse chechking,d)Log on as a batch job and e)Log on as a service.
Will these rights get automatically assigned during installation
or should it be manually assigned in each node under its local security
policy. Also what are rights for the other 3 service a/c and do these
rights get assigned automatically during installation.

I have to install Sqlserver 2008 in a 2 node clustered environment in
Windows Server 2008 R2. For that I have set up 4 less privileged
a/c in domain for Db engine, Sql agent, Reporting services and Analysis
service. During the installation I plan to specify these a/c's in the
domain to run the above 4 services under these a/c. I understand the sql server agent
a/c should have 6 rights in the local computer security policy
ie a)Adjust memory quotas for process,b)Act as a part of os,c)Bypass
traverse chechking,d)Log on as a batch job and e)Log on as a service.
Will these rights get automatically assigned during installation
or should it be manually assigned in each node under its local security
policy. Also what are rights for the other 3 service a/c and do these
rights get assigned automatically during installation.
You should get Domain account created before starting cluster installation and specifically give these rights to the account.
Regarding rights below link might be helpful
http://blogs.msdn.com/b/askjay/archive/2011/02/28/required-rights-for-sql-server-service-account.aspx
When installing cluster make sure you use Domain account which is added as local administrator on both nodes.
It should have righst to create Computer name object(CNO) in domain where cluster is being created
Windows CNO must have complete rights on SQL server CNO.You should also take help from AD team in providing these rights and understanding if any.
Please mark this reply as the answer or vote as helpful, as appropriate, to make it useful for other readers

Sql server services give error the remote procedure call failed [0x800706be] in sql server 2008

sql server services give error the remote procedure call failed [0x800706be] in sql server 2008.
To resolve this issue, I executed the following mofcomp command in command prompt to re-register the *.mof files:
mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof".
but it does not work.
Plz give the exact soln to solve this error.

sql server services give error the remote procedure call failed [0x800706be] in sql server 2008.
To resolve this issue, I executed the following mofcomp command in command prompt to re-register the *.mof files:
mofcomp.exe "C:\Program Files (x86)\Microsoft SQL Server\100\Shared\sqlmgmproviderxpsp2up.mof".
but it does not work.
Plz give the exact soln to solve this error.
So when you tried starting SQL server service it gave the error right ? or when you click on SQL server services in SQL server configuration manager(SSCM) you get this error. Can you be more clear. As far as I read your question it has something
to do with permission. Close SSCM window and this time right click on SQL server configuration manager and select run as administrator and check if you can see SQL server services
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles

Sql server service crashes a few times yesterday, however, there is no .MDMP file generated in the log folder

hi there:
I've experienced several sql server service crashes yesterday, service was brought up after a few secs as we have an autostart feature.
Today, I'd like to dig more into the errors and on the event viewer -> Application, I saw errors below
"Faulting application sqlservr.exe, version 2009.100.4302.0, time stamp 0x52f5d194, faulting module ntdll.dll, version 6.0.6001.18538, time stamp 0x4cb73957, exception code 0xc0000374, fault offset 0x00000000000a7857, process id 0x15ec, application
start time 0x01cfd7e72b2997d3.
People suggested to check dump file inside C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log
However, the lastest .mdmp file was on April 11, 2014. Do I need to turn on some settings on sql server in order to have this dump file?
Thanks
Hui
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Results after sp_readerrorlog 1
LogDate ProcessInfo
Text
2014-09-24 04:03:28.460 Server
Microsoft SQL Server 2008 R2 (SP2) - 10.50.4302.0 (X64)
Feb 7 2014 17:23:24
Copyright (c) Microsoft Corporation
Enterprise Edition (64-bit) on Windows NT 6.0 <X64> (Build 6001: Service Pack 1)
2014-09-24 04:03:28.460 Server
(c) Microsoft Corporation.
2014-09-24 04:03:28.460 Server
All rights reserved.
2014-09-24 04:03:28.460 Server
Server process ID is 5612.
2014-09-24 04:03:28.460 Server
System Manufacturer: 'IBM', System Model: 'IBM System x3650 -[7979AC1]-'.
2014-09-24 04:03:28.460 Server
Authentication mode is MIXED.
2014-09-24 04:03:28.460 Server
Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log\ERRORLOG'.
2014-09-24 04:03:28.460 Server
This instance of SQL Server last reported using a process ID of 6780 at 9/24/2014 4:03:20 AM (local) 9/24/2014 11:03:20 AM (UTC). This is an informational message only; no user action is required.
2014-09-24 04:03:28.460 Server
Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.SQL2008R2\MSSQL\DATA\mastlog.ldf
2014-09-24 04:03:28.480 Server
SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-24 04:03:28.480 Server
Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-24 04:03:28.480 Server
Cannot use Large Page Extensions: lock memory privilege was not granted.
2014-09-24 04:03:28.580 Server
Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-09-24 04:03:28.700 Server
Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2014-09-24 04:03:28.870 spid7s
Starting up database 'master'.
2014-09-24 04:03:28.940 spid7s
1 transactions rolled forward in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:28.940 spid7s
0 transactions rolled back in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:28.940 spid7s
Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-24 04:03:29.040 spid7s
CHECKDB for database 'master' finished without errors on 2014-09-20 12:00:01.697 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:29.050 spid7s
Resource governor reconfiguration succeeded.
2014-09-24 04:03:29.050 spid7s
SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2014-09-24 04:03:29.050 spid7s
SQL Server Audit has started the audits. This is an informational message. No user action is required.
2014-09-24 04:03:29.050 spid7s
FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQL2008R2'.
2014-09-24 04:03:29.070 spid7s
SQL Trace ID 1 was started by login "sa".
2014-09-24 04:03:29.070 spid7s
Starting up database 'mssqlsystemresource'.
2014-09-24 04:03:29.090 spid7s
The resource database build version is 10.50.4302. This is an informational message only. No user action is required.
2014-09-24 04:03:29.600 spid10s
Starting up database 'model'.
2014-09-24 04:03:29.600 spid7s
Server name is 'BPWDB046\SQL2008R2'. This is an informational message only. No user action is required.
2014-09-24 04:03:29.880 spid13s
A new instance of the full-text filter daemon host process has been successfully started.
2014-09-24 04:03:29.960 spid14s
Starting up database 'msdb'.
2014-09-24 04:03:29.960 spid17s
Starting up database 'DW_Detail'.
2014-09-24 04:03:29.960 spid16s
Starting up database 'ReportServer_MSSQLSSRSTempDB'.
2014-09-24 04:03:29.960 spid13s
Starting up database 'Billing_Rep'.
2014-09-24 04:03:29.960 spid15s
Starting up database 'ReportServer_MSSQLSSRS'.
2014-09-24 04:03:29.960 spid18s
Starting up database 'BCBio_DW'.
2014-09-24 04:03:29.960 spid19s
Starting up database 'ODS'.
2014-09-24 04:03:29.960 spid20s
Starting up database 'ReportServer$SQL2008'.
2014-09-24 04:03:29.970 spid21s
Starting up database 'ReportServer$SQL2008TempDB'.
2014-09-24 04:03:29.970 spid22s
Starting up database 'Billing'.
2014-09-24 04:03:29.970 spid23s
Starting up database 'Billing_Snap'.
2014-09-24 04:03:29.970 spid24s
Starting up database 'DBA'.
2014-09-24 04:03:30.000 Server
A self-generated certificate was successfully loaded for encryption.
2014-09-24 04:03:30.000 Server
Server is listening on [ 'any' <ipv6> 52328].
2014-09-24 04:03:30.000 Server
Server is listening on [ 'any' <ipv4> 52328].
2014-09-24 04:03:30.000 Server
Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\SQL2008R2 ].
2014-09-24 04:03:30.000 Server
Server local connection provider is ready to accept connection on [ \\.\pipe\MSSQL$SQL2008R2\sql\query ].
2014-09-24 04:03:30.010 Server
Server is listening on [ ::1 <ipv6> 52329].
2014-09-24 04:03:30.010 Server
Server is listening on [ 127.0.0.1 <ipv4> 52329].
2014-09-24 04:03:30.010 Server
Dedicated admin connection support was established for listening locally on port 52329.
2014-09-24 04:03:30.060 spid10s
CHECKDB for database 'model' finished without errors on 2014-09-20 12:00:17.583 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.060 spid10s
Clearing tempdb database.
2014-09-24 04:03:30.140 Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/BPWDB046.bcbio.org:SQL2008R2 ] for the SQL Server service.
2014-09-24 04:03:30.140 Server
The SQL Server Network Interface library successfully registered the Service Principal Name (SPN) [ MSSQLSvc/BPWDB046.bcbio.org:52328 ] for the SQL Server service.
2014-09-24 04:03:30.140 Server
SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-24 04:03:30.480 spid21s
CHECKDB for database 'ReportServer$SQL2008TempDB' finished without errors on 2014-09-20 16:13:10.043 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.520 spid14s
2933 transactions rolled forward in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.650 spid7s
0 transactions rolled back in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.650 spid7s
Recovery is writing a checkpoint in database 'msdb' (4). This is an informational message only. No user action is required.
2014-09-24 04:03:30.770 spid14s
CHECKDB for database 'msdb' finished without errors on 2014-09-20 12:00:18.473 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:30.950 spid10s
Starting up database 'tempdb'.
2014-09-24 04:03:30.990 spid52
Attempting to load library 'xpstar.dll' into memory. This is an informational message only. No user action is required.
2014-09-24 04:03:31.010 spid52
Using 'xpstar.dll' version '2009.100.1600' to execute extended stored procedure 'xp_sqlagent_monitor'. This is an informational message only; no user action is required.
2014-09-24 04:03:31.060 spid14s
The Service Broker protocol transport is disabled or not configured.
2014-09-24 04:03:31.060 spid14s
The Database Mirroring protocol transport is disabled or not configured.
2014-09-24 04:03:31.070 spid14s
Service Broker manager has started.
2014-09-24 04:03:31.330 spid16s
CHECKDB for database 'ReportServer_MSSQLSSRSTempDB' finished without errors on 2014-09-20 12:00:39.873 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:31.500 spid20s
2 transactions rolled forward in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:31.960 spid7s
0 transactions rolled back in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:31.960 spid7s
Recovery is writing a checkpoint in database 'ReportServer$SQL2008' (11). This is an informational message only. No user action is required.
2014-09-24 04:03:32.150 spid20s
CHECKDB for database 'ReportServer$SQL2008' finished without errors on 2014-09-20 16:13:07.583 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:33.170 spid24s
CHECKDB for database 'DBA' finished without errors on 2014-09-20 16:22:41.603 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:33.600 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 1537 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:03:34.820 spid15s
CHECKDB for database 'ReportServer_MSSQLSSRS' finished without errors on 2014-09-20 12:00:32.067 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:48.290 spid13s
Recovery of database 'Billing_Rep' (8) is 1% complete (approximately 1488 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:03:49.520 spid17s
1 transactions rolled forward in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
0 transactions rolled back in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
Recovery is writing a checkpoint in database 'DW_Detail' (7). This is an informational message only. No user action is required.
2014-09-24 04:03:50.070 spid7s
Recovery completed for database DW_Detail (database ID 7) in 5 second(s) (analysis 251 ms, redo 4314 ms, undo 44 ms.) This is an informational message only. No user action is required.
2014-09-24 04:03:50.520 spid22s
CHECKDB for database 'Billing' finished without errors on 2013-04-25 18:47:20.743 (local time). This is an informational message only; no user action is required.
2014-09-24 04:03:51.620 spid17s
CHECKDB for database 'DW_Detail' finished without errors on 2014-09-20 12:00:46.917 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:03.740 spid13s
Recovery of database 'Billing_Rep' (8) is 2% complete (approximately 1493 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:13.040 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 8052 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:23.220 spid18s
Database BCBio_DW has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:23.420 spid18s
Recovery of database 'BCBio_DW' (9) is 0% complete (approximately 4664 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.640 spid18s
Recovery of database 'BCBio_DW' (9) is 0% complete (approximately 4954 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.640 spid18s
Recovery of database 'BCBio_DW' (9) is 3% complete (approximately 74 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:25.730 spid18s
Recovery of database 'BCBio_DW' (9) is 2% complete (approximately 98 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:26.000 spid18s
Recovery of database 'BCBio_DW' (9) is 12% complete (approximately 18 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:28.000 spid19s
Database ODS has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:28.350 spid19s
CHECKDB for database 'ODS' finished without errors on 2014-09-20 16:07:22.603 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:29.370 spid18s
Recovery of database 'BCBio_DW' (9) is 19% complete (approximately 24 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:31.380 spid18s
Recovery of database 'BCBio_DW' (9) is 25% complete (approximately 22 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:32.490 spid18s
Recovery of database 'BCBio_DW' (9) is 32% complete (approximately 18 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:33.150 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 9805 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:33.860 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 04:04:33.860 Logon
Login failed for user 'ETLAdmin'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.101.33]
2014-09-24 04:04:34.040 spid18s
Recovery of database 'BCBio_DW' (9) is 39% complete (approximately 15 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:35.600 spid18s
Recovery of database 'BCBio_DW' (9) is 46% complete (approximately 13 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:36.740 spid18s
Recovery of database 'BCBio_DW' (9) is 53% complete (approximately 10 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.220 spid13s
Recovery of database 'Billing_Rep' (8) is 0% complete (approximately 10106 seconds remain). Phase 1 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.230 spid13s
Recovery of database 'Billing_Rep' (8) is 2% complete (approximately 2587 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.360 spid13s
Recovery of database 'Billing_Rep' (8) is 1% complete (approximately 3654 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:37.560 spid13s
Recovery of database 'Billing_Rep' (8) is 3% complete (approximately 1564 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:38.070 spid13s
Recovery of database 'Billing_Rep' (8) is 4% complete (approximately 1328 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:38.830 spid18s
Recovery of database 'BCBio_DW' (9) is 61% complete (approximately 8 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:40.080 spid13s
Recovery of database 'Billing_Rep' (8) is 5% complete (approximately 1268 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:40.680 spid18s
Recovery of database 'BCBio_DW' (9) is 69% complete (approximately 6 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:42.960 spid18s
Recovery of database 'BCBio_DW' (9) is 77% complete (approximately 4 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:44.870 spid18s
Recovery of database 'BCBio_DW' (9) is 85% complete (approximately 3 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:44.870 spid18s
3 transactions rolled forward in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:45.120 spid18s
Recovery of database 'BCBio_DW' (9) is 85% complete (approximately 3 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
0 transactions rolled back in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
Recovery is writing a checkpoint in database 'BCBio_DW' (9). This is an informational message only. No user action is required.
2014-09-24 04:04:46.870 spid7s
Recovery completed for database BCBio_DW (database ID 9) in 23 second(s) (analysis 2417 ms, redo 19227 ms, undo 1745 ms.) This is an informational message only. No user action is required.
2014-09-24 04:04:47.610 spid18s
CHECKDB for database 'BCBio_DW' finished without errors on 2014-09-20 14:02:10.680 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:47.820 spid23s
Database Billing_Snap has more than 1000 virtual log files which is excessive. Too many virtual log files can cause long startup and backup times. Consider shrinking the log and using a different growth increment to reduce the number of virtual log files.
2014-09-24 04:04:48.570 spid23s
CHECKDB for database 'Billing_Snap' finished without errors on 2014-09-20 16:13:11.037 (local time). This is an informational message only; no user action is required.
2014-09-24 04:04:52.970 spid13s
Recovery of database 'Billing_Rep' (8) is 6% complete (approximately 1247 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:05.540 spid13s
Recovery of database 'Billing_Rep' (8) is 7% complete (approximately 1224 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:17.980 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1202 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.450 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1196 seconds remain). Phase 2 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.450 spid13s
1 transactions rolled forward in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.560 spid13s
Recovery of database 'Billing_Rep' (8) is 8% complete (approximately 1196 seconds remain). Phase 3 of 3. This is an informational message only. No user action is required.
2014-09-24 04:05:22.710 spid13s
CHECKDB for database 'Billing_Rep' finished without errors on 2014-09-20 13:25:01.597 (local time). This is an informational message only; no user action is required.
2014-09-24 04:05:22.720 spid13s
0 transactions rolled back in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.720 spid13s
Recovery is writing a checkpoint in database 'Billing_Rep' (8). This is an informational message only. No user action is required.
2014-09-24 04:05:22.730 spid13s
Recovery completed for database Billing_Rep (database ID 8) in 109 second(s) (analysis 63983 ms, redo 45211 ms, undo 154 ms.) This is an informational message only. No user action is required.
2014-09-24 04:05:22.750 spid7s
Recovery is complete. This is an informational message only. No user action is required.
2014-09-24 07:00:06.930 spid53
Common language runtime (CLR) functionality initialized using CLR version v2.0.50727 from C:\Windows\Microsoft.NET\Framework64\v2.0.50727\.
2014-09-24 07:00:07.720 spid53
AppDomain 2 (mssqlsystemresource.sys[runtime].1) created.
2014-09-24 07:13:38.590 spid51
SQL Server blocked access to STATEMENT 'OpenRowset/OpenDatasource' of component 'Ad Hoc Distributed Queries' because this component is turned off as part of the security configuration for this server. A system administrator can enable the use of 'Ad
Hoc Distributed Queries' by using sp_configure. For more information about enabling 'Ad Hoc Distributed Queries', see "Surface Area Configuration" in SQL Server Books Online.
2014-09-24 07:13:53.870 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:53.870 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:56.560 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:56.560 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.460 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.460 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.560 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.560 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:13:57.950 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:13:57.950 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:14:04.410 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:14:04.410 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:14:04.960 Logon
Error: 18456, Severity: 14, State: 38.
2014-09-24 07:14:04.960 Logon
Login failed for user 'BCBIO\sqlservice'. Reason: Failed to open the explicitly specified database. [CLIENT: 172.20.100.6]
2014-09-24 07:34:13.330 spid54
Error: 17053, Severity: 16, State: 1.
2014-09-24 07:34:13.330 spid54
V:\log\templog.ldf: Operating system error 112(There is not enough space on the disk.) encountered.
2014-09-24 07:34:14.430 spid54
Error: 9002, Severity: 17, State: 4.
2014-09-24 07:34:14.430 spid54
The transaction log for database 'tempdb' is full. To find out why space in the log cannot be reused, see the log_reuse_wait_desc column in sys.databases
--Currently using Reporting Service 2000; Visual Studio .NET 2003; Visual Source Safe SSIS 2008 SSAS 2008, SVN --

Need SQL Server service packs installation procedure

Similar Messages

Maybe you are looking for