Windows Small Business Server 2011 Premium includes  SQL Server 2008 R2 https://www.microsoft.com/sbs/en/us/editions-overview.aspx. This version is feature by feature the same as SQL 2008 R2 Standard with the difference that it must be installed in an Small Business Server domain or, if purchased separately, an environment with certain characteristics. But, what does that mean?

SQL 2008 R2 Standard for Small Business is supported for installation in a small business domain,
which includes installing on one of the following Windows Server® 2008 R2 editions:

• • Windows® Small Business Server 2011
  • Windows Server® 2008 R2 Standard (must be configured in a
    small business domain configuration). To install this product on Windows Server 2008 R2 Standard edition, the server must be joined to a Small Business Server 2008 R2 domain or a domain that has Active Directory configured in the following way:
    • It must be joined to a domain where a single server in the domain must contain all the flexible single master operations (FSMO) roles and is the root of the Active Directory forest,
    • The domain cannot have trust relationships with any other domains,
    • The domain cannot have any child domains, and
    • The sum of user and device licenses in the domain cannot exceed 75.
    • The customer may not run instances of the server software, separately licensed or otherwise, at the same time in another operating system environment within the same domain..

If the check fails, you will see the a failed check in the "Operating system supported for edition” topic.

Clicking in the Failed status shows the following message:

---------------------------
Rule Check Result
---------------------------
Rule "Operating system supported for edition" failed.
This SQL Server edition is not supported on this operating system. See SQL Server
Books Online for information about supported operating systems for SQL Small
Business Server edition.
---------------------------

SQL Server 2008 R2 setup logs (check SQL Server detail.txt installation file available on C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log)

2011-07-08 15:52:32 Slp: Rule evaluation message: The SQL Server 2005 Express Tools are not installed.
2011-07-08 15:52:32 Slp: Send result to channel : RulesEngineNotificationChannel
2011-07-08 15:52:32 Slp: Initializing rule : Operating system supported for edition
2011-07-08 15:52:32 Slp: Rule applied features : ALL
2011-07-08 15:52:32 Slp: Rule is will be executed : True
2011-07-08 15:52:32 Slp: Init rule target object: Microsoft.SqlServer.Configuration.SetupExtension.EditionRequirementCheck
2011-07-08 15:52:33 Slp: O destino de uma invocação accionou uma excepção.
2011-07-08 15:52:33 Slp: em System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
em System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
em System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
em System.RuntimeType.InvokeMember(String name, BindingFlags bindingFlags, Binder binder, Object target, Object[] providedArgs, ParameterModifier[] modifiers, CultureInfo culture, String[] namedParams)
em Microsoft.SqlServer.Configuration.SetupExtension.EditionRequirementCheck.CheckSBSEnvironment()
em Microsoft.SqlServer.Configuration.SetupExtension.EditionRequirementCheck.Microsoft.SqlServer.Configuration.RulesEngineExtension.IRuleInitialize.Init(String ruleId)
em Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngine.Execute(Boolean stopOnFailure)
2011-07-08 15:52:33 Slp: Rule initialization failed - hence the rule result is assigned as Failed
2011-07-08 15:52:33 Slp: Send result to channel : RulesEngineNotificationChannel
2011-07-08 15:52:33 Slp: Initializing rule : Previous releases of Microsoft Visual Studio 2008
2011-07-08 15:52:33 Slp: Rule applied features : IS;BIDS;Tools;SSMS
2011-07-08 15:52:33 Slp: Rule is will be executed : True

In this case setup was running under local non-domain account. In order to avoid this problem:

• The SQL setup must be run while logged in to the domain with valid
  domain credentials. The user needs to have domain administrator and local administrator rights.

SQLPort is a community without any economical interest of affiliation with Microsoft that  main goal is to unify and  support all SQL Server professionals and self training analysts. Main objective is to promote and develop knowledge on that area.

This group will be a member of SQL Pass world wide community is near future. A couple of initiatives are already in place and first event schedule for 11 May 2010 (more details at https://www.sqlport.com/sql-server/eventos/i-encontro-da-comunidade-sqlport)

Summary:

-SQL Server 2008/2008 R2 patching and upgrade
-Introduction to High Availability and Disaster Recovery
-SQL Server Always On Technologies
-Developing your Availability solutions

Session slides:

Session Slides

Session labs/demos:

Demos

Webcast:

https://www112.livemeeting.com/cc/microsoft/view?id=F9TBZ9

Summary:

- SQL Server 32 bits vs 64 bits
- SQL Server IO considerations
- Troubleshooting using Perfmon and Profiler
- SSMS Tips
- Visualizing Schemas
- Performance troubleshooting using MDW

Session slides:

Session Slides

Session labs/demos:

Demos

Webcast

https://www112.livemeeting.com/cc/microsoft/view?id=3ZSBCN

We have seen several issues where installation of Service Pack/Hotfix/GDR/CU fails to install on one or more components of SQL Server 2005. In this blog , I have tried to include few troubleshooting tips and tricks for these kinds of installation failures.

Whenever a hotfix installation fails, we start troubleshooting  with the log file usually located at  %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\Summary.txt

I am demonstrating an example to troubleshoot an issue where KB954606 (Security Update MS08-052) failed to install .

First , go to %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\ and see Summary.txt :

----------------------------------------------------------------------------------

Product Installation Status

Product                   : SQL Server Database Services 2005 (MSSQLSERVER)

Product Version (Previous): 3073

Product Version (Final)   :

Status                    : Failure

Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB954606_sqlrun_sql.msp.log

Error Number              : 1635

Error Description         : Unable to install Windows Installer MSP file

----------------------------------------------------------------------------------

Above error is for SQL Server Database Services 2005 , so in this example I will display troubleshooting steps for Database Engine only.

To troubleshoot this issue, I like to analyze verbose log which is usually located at %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KBnnnnnn_sqlrun_sql.msp.log .

[Where KBnnnnnn is a placeholder for the hotfix number which is failing to install. In our example, it is SQL9_Hotfix_KB954606_sqlrun_sql.msp.log .]

Partial Contents of SQL9_Hotfix_KB954606_sqlrun_sql.msp.log :

=== Verbose logging started: 1/18/2009  05:21:19  Build type: SHIP UNICODE 3.01.4000.4042  Calling process: c:\cf7b299b237d95aef330b0000d8d947f\hotfix.exe ===

MSI (c) (AC:D0) [17:45:28:483]: Resetting cached policy values

MSI (c) (AC:D0) [17:45:28:483]: Machine policy value 'Debug' is 0

MSI (c) (AC:D0) [17:45:28:483]: ******* RunEngine:

           ******* Product: {2373A92B-1C1C-4E71-B494-5CA97F96AA19}

           ******* Action:

           ******* CommandLine: **********

MSI (c) (AC:D0) [17:45:28:483]: Client-side and UI is none or basic: Running entire install on the server.

MSI (c) (AC:D0) [17:45:28:483]: Grabbed execution mutex.

MSI (c) (AC:D0) [17:45:28:515]: Cloaking enabled.

MSI (c) (AC:D0) [17:45:28:515]: Attempting to enable all disabled priveleges before calling Install on Server

MSI (c) (AC:D0) [17:45:28:530]: Incrementing counter to disable shutdown. Counter after increment: 0

MSI (s) (D0:F8) [17:45:28:546]: Grabbed execution mutex.

MSI (s) (D0:F4) [17:45:28:546]: Resetting cached policy values

MSI (s) (D0:F4) [17:45:28:546]: Machine policy value 'Debug' is 0

MSI (s) (D0:F4) [17:45:28:546]: ******* RunEngine:

******* Product: {2373A92B-1C1C-4E71-B494-5CA97F96AA19}

           ******* Action:

           ******* CommandLine: **********

MSI (s) (D0:F4) [17:45:28:546]: Machine policy value 'DisableUserInstalls' is 0

MSI (s) (D0:F4) [17:45:28:546]: Adding MSIINSTANCEGUID to command line.

MSI (s) (D0:F4) [17:45:28:546]: Warning: Local cached package 'C:\WINDOWS\Installer\638de4.msi' is missing.

MSI (s) (D0:F4) [17:45:28:546]: User policy value 'SearchOrder' is 'nmu'

MSI (s) (D0:F4) [17:45:28:546]: User policy value 'DisableMedia' is 0

MSI (s) (D0:F4) [17:45:28:546]: Machine policy value 'AllowLockdownMedia' is 0

MSI (s) (D0:F4) [17:45:28:546]: SOURCEMGMT: Media enabled only if package is safe.

MSI (s) (D0:F4) [17:45:28:546]: SOURCEMGMT: Looking for sourcelist for product {2373A92B-1C1C-4E71-B494-5CA97F96AA19}

:

:

:

:

:

MSI (s) (D0:F4) [17:45:47:452]: Opening existing patch 'C:\WINDOWS\Installer\9be677.msp'.

MSI (s) (D0:F4) [17:45:47:452]: Note: 1: 2203 2: C:\WINDOWS\Installer\9be677.msp 3: -2147287038

MSI (s) (D0:F4) [17:45:47:452]: Couldn't find local patch 'C:\WINDOWS\Installer\9be677.msp'. Looking for it at its source.

MSI (s) (D0:F4) [17:45:47:452]: Resolving Patch source.

MSI (s) (D0:F4) [17:45:47:452]: User policy value 'SearchOrder' is 'nmu'

MSI (s) (D0:F4) [17:45:47:452]: SOURCEMGMT: Media enabled only if package is safe.

MSI (s) (D0:F4) [17:45:47:452]: SOURCEMGMT: Looking for sourcelist for product {4A35EF4A-D868-4B15-A84D-3E8925AA9558}

MSI (s) (D0:F4) [17:45:47:452]: SOURCEMGMT: Adding {4A35EF4A-D868-4B15-A84D-3E8925AA9558}; to potential sourcelist list (pcode;disk;relpath).

MSI (s) (D0:F4) [17:45:47:452]: SOURCEMGMT: Now checking product {4A35EF4A-D868-4B15-A84D-3E8925AA9558}

MSI (s) (D0:F4) [17:45:47:452]: SOURCEMGMT: Media is enabled for product.

MSI (s) (D0:F4) [17:45:47:452]: SOURCEMGMT: Attempting to use LastUsedSource from source list.

MSI (s) (D0:F4) [17:45:47:452]: SOURCEMGMT: Trying source d:\05ba72b40ba6b4d61d14cd3c3283\HotFixSQL\Files\.

MSI (s) (D0:F4) [17:45:47:452]: Note: 1: 2203 2: d:\05ba72b40ba6b4d61d14cd3c3283\HotFixSQL\Files\sqlrun_sql.msp 3: -2147287037

MSI (s) (D0:F4) [17:45:47:452]: SOURCEMGMT: Source is invalid due to missing/inaccessible package.

MSI (s) (D0:F4) [17:45:47:452]: Note: 1: 1706 2: -2147483647 3: sqlrun_sql.msp

MSI (s) (D0:F4) [17:45:47:452]: SOURCEMGMT: Processing net source list.

MSI (s) (D0:F4) [17:45:47:452]: Note: 1: 1706 2: -2147483647 3: sqlrun_sql.msp

MSI (s) (D0:F4) [17:45:47:452]: SOURCEMGMT: Processing media source list.

MSI (s) (D0:F4) [17:45:47:452]: Note: 1: 2303 2: 87 3: E:\

MSI (s) (D0:F4) [17:45:47:452]: Note: 1: 2303 2: 87 3: E:\

MSI (s) (D0:F4) [17:45:47:452]: SOURCEMGMT: Resolved source to: 'sqlrun_sql.msp'

MSI (s) (D0:F4) [17:46:19:702]: Note: 1: 1314 2: sqlrun_sql.msp

MSI (s) (D0:F4) [17:46:19:702]: Unable to create a temp copy of patch 'sqlrun_sql.msp'.

MSI (s) (D0:F4) [17:46:19:702]: Note: 1: 1708

MSI (s) (D0:F4) [17:46:19:702]: Note: 1: 2729

MSI (s) (D0:F4) [17:46:19:702]: Note: 1: 2729

MSI (s) (D0:F4) [17:46:19:702]: Product: Microsoft SQL Server 2005 -- Installation failed.

MSI (s) (D0:F4) [17:46:19:718]: MainEngineThread is returning 1635

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:\SQLSETUP\Servers\Setup\SqlRun_SQL.msi

MSI (c) (AC:D0) [17:46:19:827]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied.  Counter after decrement: -1

MSI (c) (AC:D0) [17:46:19:827]: MainEngineThread is returning 1635

=== Verbose logging stopped: 1/20/2009  17:46:19 ===

1. The very first error I see in the above log is Local cached package 'C:\WINDOWS\Installer\638de4.msi' is missing. This file 638de4.msi is the cached msi file for sqlrun_sql.msi i.e. the main installation (RTM) of an instance of SQL Server Database Engine. During installation of RTM product, ..\Servers\Setup\SqlRun_SQL.msi is cached to %windir%\Installer folder for future use such as un-installation etc. Cached file has a different name which is a randomized alphanumeric name generated by the installer , this is because if you have multiple instances then multiple ‘Sqlrun_sql.msi’ has to be cached and hence a name conflict may occur. Anyways, if you know the GUID (ProductCode) of the instance , you can find the name of this cached file , go to

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\<GUID>\InstallProperties

In the right pane , look for the value of “LocalPackage” .

2. Now that we knew 'C:\WINDOWS\Installer\638de4.msi' is missing , we need to put it back to C:\Windows\Installer. To do so , locate your main installation setup of SQL Server (viz. CD media or setup folder copied on local disk) , copy Servers\Setup\SqlRun_SQL.msi and paste it into C:\Windows\Installer , rename it to the cached filename , in our case we have to rename it to 638de4.msi. Double check that C:\WINDOWS\Installer\638de4.msi is available now.

3. Let’s look for the next error in the log file and that is Couldn't find local patch 'C:\WINDOWS\Installer\9be677.msp'. Looking for it at its source .The filename 9be677.msp employs it is a MSP file means a patch , not a main product. I want to make it clear here that If we apply any patch , installer looks for the cached files of previously applied patche(s) as well as the cached msi file. So this cached msp file is also missing and we need to put it back. But the challenge is how to find which patch is this ? It is explained in following steps.

4. In the following lines in log file, we see : Looking for sourcelist for product {4A35EF4A-D868-4B15-A84D-3E8925AA9558} means the PatchCode for missing msp file 9be677.msp is {4A35EF4A-D868-4B15-A84D-3E8925AA9558}. Also, from ******* Product: {2373A92B-1C1C-4E71-B494-5CA97F96AA19} , we know the ProductCode i.e. GUID is {2373A92B-1C1C-4E71-B494-5CA97F96AA19} .

So we have below info till this point :

GUID          = {2373A92B-1C1C-4E71-B494-5CA97F96AA19}

PatchCode     = {4A35EF4A-D868-4B15-A84D-3E8925AA9558}

The GUID and PatchCode are stored in registry in encrypted format. Search* (See Search Hints below) them ,open regedit , go to

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\<GUID>\Patches\<PatchCode>

In the right pane , see the value of “DisplayName” . In our case , it was like below :

DisplayName = Service Pack 2 for SQL Server Database Services 2005 ENU (KB921896)

So DisplayName explains that {4A35EF4A-D868-4B15-A84D-3E8925AA9558} is Patch Code for KB921896 i.e. SP2 .

5. Recall Step 3 , we found the missing msp file i.e. 9be677.msp is for KB921896 . In order to put his cached msp file back , download KB921896 , extract it at a command prompt using switch /extract , go to extracted directory of KB921896 and copy ..\ hotfixsql\files\sqlrun_sql.msp , paste it in C:\Windows\Installer and rename it to 9be677.msp . Double check that 'C:\WINDOWS\Installer\9be677.msp' exists now.

6. Now that we have made available both the missing files (msi and msp) , apply the patch (in our case KB954606) again which failed to install .It should succeed now. However , in case if it fails again, that may be due to the fact that it might be looking for some other patch which might have been applied previously and is missing now. If so, failure installation will again generate verbose log , open the verbose log (like SQL9_Hotfix_KB954606_sqlrun_sql.msp.log) , look at 15-20 lines above the bottom of the log file , you may find Couldn't find local patch , put the appropriate cached msp file back to C:\Windows\Installer , rename it appropriately and re-try the setup.

[It’s expected that log file after performing above steps won’t complain for ‘*.msi file is missing’ anymore .]

7. For other failing components like AS, RS, NS, Tools, IS  etc please follow the troubleshooting method as explained in step1 to step6 looking at the appropriate verbose log file. Please note that GUID, msp filename and msp file path in the extracted folder would be different for different components. Choose carefully.

Hope this helps !

*Search Hints  :

1.          As ‘Note’ of KB article 938321 explains , to locate the specific Product Code registry subkey, search for the ProductName registry entry that has the value of "Microsoft SQL Server 2005 (InstanceName)"

under the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\S-1-5-18\Products\ registry subkey.

2.          Alternatively, see this link , very useful in locating GUID in registry .

Additionally, you may see these errors as well in Summary.txt under Hotfix folder :

----------------------------------------------------------------------------------

Error Number              : 1642

Error Description         : Unable to install Windows Installer MSP file

----------------------------------------------------------------------------------

Error Number              : 1612

Error Description         : Unable to install Windows Installer MSP file

----------------------------------------------------------------------------------

Error Number              : 1646

Error Description         : Unable to install Windows Installer MSP file

----------------------------------------------------------------------------------

Please see KB304888 for a list of error codes and error messages for Windows Installer processes.

Some More Information :

Service Pack/Hotfix/GDR/CU contains MSP files as compared to RTM product which has MSI files.

What is MSP ?

--------------------

A MSP (Microsoft Software Patch) is basically a set of transforms (modifications) against a baseline MSI (Microsoft Software Installer) file.  When a MSP is installed, instead of updating the contents of the cached MSI (modifying it according to the transforms included in the MSP), Windows Installer simply caches the MSP.  Then each time the MSI is run, the cached MSP is applied on the fly again.  The reason it works this way is to simplify the authoring and building of MSPs, so that each MSP can be built only against RTM and not have to know about all the possible MSPs that have been released since then.  For example, when SP2 is applied the SP1 patch is obsolete and Windows Installer just applies SP2 directly against the cached contents of the RTM product.

(credits for this article - Prashant Kumar SE, Microsoft SQL Server)

SQL Server 2008

Technical Overview

High Availability and Performance Optimization

From 12 to 13 November 2009

Session summary:

Day 1

SQL Server 2008 High availability and performance troubleshooting

•    SQL Server 2008 Log Shipping Setup/Configuration
•    SQL Server 2008 Mirror Setup/Configuration
•    SQL Server 2008 Cluster Setup/Configuration
•    SQL Server 2008 high availability/reliability
•    SQL Server 200x upgrade to SQL Server 2008
•    SQL Server 2008 Performance Monitoring
•    Overview of new performance monitor tools/functionalities
•    Find and diagnose active performance issues
•    Analyze performance issues in offline mode

Technical Highlights

•    SQL Cluster versus SQL mirror implementation
•    Advantages and tradeoffs of most common SQL high availability scenarios
•    Mirror setup and configuration
•    Log shipping planning and implementation
•    Mixed scenarios combining cluster and mirror
•    Maintenance and backup strategies
•    Disaster recovery options
•    SQL Server 200x upgrade discussion based on most common scenarios
•    Data Collector
•    Management Data Warehouse
•    Performance and Configuration Reports
•    Activity Monitor
•    Graphical ShowPlan
•    SQL Server Profiler
•    Resource Governor
•    XEvents
•    Dynamic Management Views
•    Database Engine Tuning Advisor

Day 2

SQL Server 2008 technical overview

•    SQL Server 2008 Declarative Management Framework
•    SQL Server 2008 Peer to Peer Replication
•    SQL Server 2008 Power Shell Integration
•    SSMS Intellisense
•    Transparent Data Encryption
•    SQL Server 2008 Auditing
•    Data compression
•    SQL Server 2008 Management Data Warehouse
•    SQL Server 2008 Resource governor
•    Virtualization with SQL Server 2008
•    SQL Server File Stream

Technical Highlights

•    Peer to Peer Replication improvements
•    Benefits and cautions using TDE
•    Improve compliance and security using Auditing
•    Data compression versus backup compression
•    Using Resource governor to control and prioritize workloads
•    Using data collector to easily identify performance problems
•    SQL Server 2008 virtualization benefits and precautions
•    File Stream benefits, recommendations and best practices

Session slides:

SQL Server 2008 Premier Session Porto.zip

Check the if the following key exists and remove it or change value to 1 and reboot machine:

Hive: HKEY_LOCAL_MACHINE
Key: SYSTEM\CurrentControlSet\Services\LanManServer\Parameters
Name: AutoShareServer
Data Type: REG_DWORD
Value: 0

https://en.wikipedia.org/wiki/Administrative_share – Administrative share

SQL installation log file last lines should be:

(...)
10/15/2009 00:32:13.207 Patching available passive node: node_name
10/15/2009 00:32:13.238 Waiting for first completed passive node
10/15/2009 00:32:13.254 Patching passive node: node_name

Normal installation log:

(...)
11/13/2008 17:05:07.428 Patching available passive node: remote_nome_name
11/13/2008 17:05:07.429 Patching passive node: remote_nome_name
11/13/2008 17:05:07.530 Task Scheduler: Created remote folder for product instance target \\remote_nome_name
(…)

SQL Server error log last lines are listed below and no further info is displayed after resource database build info:

SQL Server error log:

(…)
2009-09-18 11:48:45.28 spid6s SQL Trace ID 1 was started by login "sa".
2009-09-18 11:48:45.28 spid6s Starting up database 'mssqlsystemresource'.
2009-09-18 11:48:45.34 spid6s The resource database build version is 10.00.2531. This is an informational message only. No user action is required.

(…)

No messages are logged on event viewer and process needs to be killed manually using task manager. Capturing a memory dump shows at least 2 threads with similar callstack:

(…)

Child-SP Child-BSP RetAddr Call Site
(…)

00000000`287ed940 00000000`287f0c58 00000000`01125610 sqlservr!EventInternal<Spinlock<149,1,0> >::Wait+0x250
00000000`287ed940 00000000`287f0be0 00000000`01867d20 sqlservr!FInitDCOM+0x260
00000000`287ed9b0 00000000`287f0bb0 00000000`05116d50 sqlservr!CreateInfoSetReaderExNoCheck+0x50
00000000`287ed9d0 00000000`287f0b78 00000000`05118080 sqlservr!CreateInfoSetReaderEx+0x50
00000000`287eda00 00000000`287f0b10 00000000`05a68230 sqlservr!CTraceETW::FindTemplate+0x670
00000000`287eda70 00000000`287f0a98 00000000`76b0b040 sqlservr!CTraceETW::ControlCallback+0x310
00000000`287edbd0 00000000`287f0a38 00000000`76b16800 ntdll!RegisterGuidsApiCallback+0x140
00000000`287edc30 00000000`287f09b8 00000000`76b16960 ntdll!EtwpUpdateEnableInfoAndCallback+0x180
00000000`287edc70 00000000`287f0958 00000000`76b1ae50 ntdll!EtwpRegisterProvider+0x120
00000000`287edd20 00000000`287f0918 00000000`76b135e0 ntdll!EtwNotificationRegister+0x90
00000000`287edd20 00000000`287f0898 00000000`05a68d80 ntdll!EtwRegisterTraceGuidsW+0x140
00000000`287edda0 00000000`287f0820 00000000`05a6ae80 sqlservr!CTraceETW::Startup+0x620
00000000`287ef9b0 00000000`287f0808 00000000`019b7dc0 sqlservr!CTraceETW::StartupTask+0x20
(…)

(…)
Child-SP Child-BSP RetAddr Call Site
00000000`164ae3c0 00000000`164b2300 00000000`76b37940 ntdll!RtlpWaitOnCriticalSection+0x3e0
00000000`164ae410 00000000`164b22c0 00000000`76b1adf0 ntdll!RtlEnterCriticalSection+0x180
00000000`164ae410 00000000`164b2280 00000000`76b135e0 ntdll!EtwNotificationRegister+0x30
00000000`164ae410 00000000`164b2200 000006fa`fd503b60 ntdll!EtwRegisterTraceGuidsW+0x140
00000000`164ae490 00000000`164b2190 000006fa`fdc57ee0 shell32!DllMain+0x180
00000000`164ae4b0 00000000`164b2138 000006fa`fdc582d0 shell32!__DllMainCRTStartup+0x220
00000000`164ae5d0 00000000`164b2108 00000000`76b247c0 shell32!_DllMainCRTStartup+0x50
00000000`164ae5d0 00000000`164b2020 00000000`76b280c0 ntdll!LdrpRunInitializeRoutines+0x440
00000000`164ae740 00000000`164b1f68 00000000`76b27300 ntdll!LdrpLoadDll+0x620
00000000`164ae9d0 00000000`164b1ed0 00000000`76a0fed0 ntdll!LdrLoadDll+0x1e0
00000000`164aec40 00000000`164b1e48 000006fa`fed061f0 kernel32!LoadLibraryExW+0x670
00000000`164aecb0 00000000`164b1de8 000006fa`fed05ca0 ole32!CClassCache::CDllPathEntry::LoadDll+0x190
00000000`164aecb0 00000000`164b1d60 000006fa`fed03f00 ole32!CClassCache::CDllPathEntry::Create_rl+0xe0
00000000`164aece0 00000000`164b1ce0 000006fa`fed0a350 ole32!CClassCache::CClassEntry::CreateDllClassEntry_rl+0x1e0
00000000`164aef20 00000000`164b1c60 000006fa`fed09ad0 ole32!CClassCache::GetClassObjectActivator+0x4d0
00000000`164aef50 00000000`164b1c08 000006fa`fed0d6e0 ole32!CClassCache::GetClassObject+0x90
00000000`164aef90 00000000`164b1be8 000006fa`fed0f850 ole32!CCGetClassObject+0x40
00000000`164aef90 00000000`164b1b20 000006fa`feeb8ea0 ole32!CServerContextActivator::GetClassObject+0x470
00000000`164af010 00000000`164b1ab8 000006fa`fed12280 ole32!ActivationPropertiesIn::DelegateGetClassObject+0x440
00000000`164af040 00000000`164b1a78 000006fa`fed110d0 ole32!CApartmentActivator::GetClassObject+0xe0
00000000`164af050 00000000`164b1a30 000006fa`fed10ff0 ole32!CProcessActivator::GCOCallback+0xb0
00000000`164af060 00000000`164b19d8 000006fa`fed10cd0 ole32!CProcessActivator::AttemptActivation+0x70
00000000`164af060 00000000`164b1950 000006fa`fed10a00 ole32!CProcessActivator::ActivateByContext+0x110
00000000`164af070 00000000`164b1918 000006fa`feeb8ea0 ole32!CProcessActivator::GetClassObject+0xe0
00000000`164af080 00000000`164b18b0 000006fa`fed0edb0 ole32!ActivationPropertiesIn::DelegateGetClassObject+0x440
00000000`164af0b0 00000000`164b1840 000006fa`feeb8ea0 ole32!CClientContextActivator::GetClassObject+0x1f0
00000000`164af300 00000000`164b17d0 000006fa`fed155c0 ole32!ActivationPropertiesIn::DelegateGetClassObject+0x440
00000000`164af330 00000000`164b16c8 000006fa`fecfdf30 ole32!ICoGetClassObject+0x9c0
00000000`164afd10 00000000`164b1600 000006fa`fecfe910 ole32!CComActivator::DoGetClassObject+0x2d0
00000000`164afd20 00000000`164b15c0 00000000`01126000 ole32!CoGetClassObject+0x50
00000000`164afd20 00000000`164b15a0 00000000`0112bd40 sqlservr!GetLuxorClassFactory+0x70
00000000`164afd30 00000000`164b1560 00000000`04297a80 sqlservr!LoadDCOM+0x1e0
00000000`164afd40 00000000`164b1520 00000000`0612e2d0 sqlservr!StartUp::WaitForTempdbLocked+0x120
00000000`164afd50 00000000`164b13c0 00000000`019b7dc0 sqlservr!initCM+0x610
(….)

0:026> !locks
CritSec ntdll!LdrpLoaderLock+0 at 0000000076d18e20
WaiterWoken No
LockCount 3
RecursionCount 2
OwningThread 1064
EntryCount 0
ContentionCount 8
*** Locked
CritSec ntdll!EtwProvCritSect+0 at 0000000076d1d940
WaiterWoken No
LockCount 1
RecursionCount 1
OwningThread 120c à thread 26
EntryCount 0
ContentionCount 1
*** Locked

So basically second thread that is responsible to initialize DCom and signal it but that was locked because ETW logging critical section was owned by second thread. Second thread acquired ETW critical section but was waiting for DCom to be signaled. Basically a deadlock scenario between these 2 threads.

There are 2 possible workarounds, first is to disable ETW tracing and enabling it after SQL has been started however in case SQL restarts or needs to failover that procedure needs to be manually applied.

Another workaround would be to delete or rename the ETW configuration file (etwcnf.xml) located under the SQL Server instance BINN folder. This should disable SQL Server ETW trace. The ETW callback will fail before reaching the point where it waits for DCOM initialization. You should see the following error in SQL Server errorlog. SQL Server should start normally though.

2009-09-22 10:38:29.03 Server      Error: 8352, Severity: 16, State: 1.
2009-09-22 10:38:29.03 Server      Cannot find the requested trace template: id = 1.

This problem should be addressed on SQL Server 2008 SP1 Cumulative Update 5

Summary:

– Higher Availability and scalability (Fail-over clustering, mirroring)

– Manageability and Administration (Resource governor, Policy Based Management and Server Group Management)

– Virtualization, Storage Savings (virtualization, Data Compression and TDE)

– Performance and Auditing(Partitioning, Partition Aligned Indexed Views, Auditing, File Stream)

–Troubleshooting and Optimization (Performance Data Collection, X-Events, Data Tuning Wizard)

Session slides:

SQL Server 2008 Deep Dive Slides.zip

Session labs/demos:

SQL Server 2008 Deep Dive Demos.zip

To find out the amount of memory consumed by this token cache, you can query the DMV’s as follows:

SELECT SUM(single_pages_kb + multi_pages_kb) AS "SecurityTokenCacheSize(kb)"

FROM sys.dm_os_memory_clerks

WHERE name = 'TokenAndPermUserStore'

Typical symptoms:

1. Queries which normally finish faster take a long time

2. CPU usage of SQL Server process is relatively higher. CPU usage could come down after remaining high for a period of time.

3. Connections from your applications keep increasing (specifically in connection pool environments)

4. You encounter connection or query timeouts

Possible workarounds (assuming that you are running SQL Server 2005 SP2 build >= 9.00.3179:

1. Use Trace flag -T4618 to restrict the number of entries maintained in the TokenAndPermUserStore cache. This trace flag was introduced in SQL Server 2005 SP2. You can use Trace Flag –T4610 in conjunction with –T4618 to relax the limit on number of entries in the cache. Also -T4610 increases the number of buckets in the hash tables used to maintain this cache.

2. Execute the command DBCC FREESYSTEMCACHE ('TokenAndPermUserStore') at regular intervals to obtain relief (this is useful to prove that you area really experiencing TokenAndPermUserStore cache grow problem)

3. Use some of the best practices mentioned in the above articles to reduce the cache growth (e.g. Parameterize ad-hoc queries, forced parameterization, avoiding recompiles, etc).

With SP3 there is a new option to control TokenAndPermUserStore cache store and avoid this problem. Please see more details on the following KB article:

959823 How to customize the quota for the TokenAndPermUserStore cache store in SQL Server 2005 Service Pack 3
https://support.microsoft.com/default.aspx?scid=kb;EN-US;959823

On SQL Server 2008 this cache mechanism has been improved anyway you might noticed 2 new advanced configuration options in sp_configure named “access check cache bucket count” and “access check cache quota