Welcome to MSDN Blogs Sign in | Join | Help

SQL Server 2008 Discovery Report

How can i tell what SQL Server features and version do I have installed? This question has been asked a lot recently.  Starting in SQL Server 2008, we added a SQL Server discovery report as an option on the Tools page on the Installation Center.  When you click on the link below, SQL Server will be started to discover the SQL Server features.

The Installation Center can be launched from the Start Menu, under the SQL Server 2008 entry:

image

 

Click on the “Installed SQL Server features discovery report”

image

 

Here is the report:

image

The SQL Server Discovery Report is saved to %ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\Log\<last Setup Session>

Options:

  • You can also generate the Discovery report through the command line. Run “Setup.exe /Action=RunDiscovery” from a command prompt
  • If you add “/q” to the command line above no UI will be shown, but the report will still be created in %ProgramFiles%\Microsoft SQL Server\100\Setup Bootstrap\Log\20091112_082147.
Posted by petersad | 0 Comments
Filed under:

How to Install SQL Server 2008 R2 (Express Edition) – November CTP

Overview:

With the release of the SQL Server 2008 R2 November CTP, we have simplified the SQL Server Express (all editions and package) installation process.  In this release, we have completed the following:

  1. Reduced the number of clicks by 50% when performing an install.
  2. All inputs are defaulted on Vista and above operating systems.  (many inputs are defaults on Windows XP and Windows 2003, except for the service accounts)
  3. Skip (auto advance) through the UI, meaning non-essential dialogs will still be skipped.
  4. Reduced the size of the Express basic package

 

For more detailed information on the SQL Server Express release, see: http://www.microsoft.com/downloads/details.aspx?FamilyID=c772467d-e45b-43e1-9208-2c7b663d7ad1&displaylang=en 

 

The primary SQL Server Express downloads:

 

 


1. Launch the package, you will then see the contents extracted to a temporary location.

image

 

2. SQL Server Setup checks to determine pre-reqs are installed. If not, you will be prompted to install.

 image

3. The Installation Center will then launch. Click on “New installation or add feature to an existing installation” to start the Installation Wizard.

image

 

4. Accept the license terms.

image

 

5. Review the features to installed and where SQL Server will be installed. Make any changes that are necessary for your environment.

image

 

6. Review the Instance Name and change if necessary.

image

 

7. Review the credentials that will be used for the services that will be created. 

image

 

8. Review the Authentication Mode and the administrators that will be added to the Database Engine.

image

 

9. Review the Error Reporting settings. We encourage you to keep this option checked, as we review the product feedback on an ongoing basic.  This helps us to continually improve SQL Server.

image

 

10. That’s it!

image

 

Support/Feedback

If you have further questions or feedback, you have a few options:

Posted by petersad | 1 Comments
Filed under:

Embedding SQL Server Express Survey

Microsoft is committed to making the SQL Server the best database in the industry for embedding with your application. For us to achieve this goal, we need your candid feedback on your experience with embedding SQL Server Express.  If you have used several different versions of SQL Server Express, focus on the latest version that you have used.  When SQL Server 2008 Customer Technical Preview 3 is released, feel free to complete this survey again since several installation improvements have been made.  This information will be used to improve our future releases including SQL Server 2008 R2 and SQL Server 11.  This survey will be available until the end of November.

Instructions:

To register for the ISVs embedding SQL Express Survey, follow this link.*   Once your registration is complete, click here and then click on “Respond to this Survey” to complete the profile.

*If you are already registered on Microsoft Connect, visiting the link will prompt you to login with the Windows Live ID e-mail address associated with your account (note that the email address we used to contact you regarding this invitation is not necessarily your account e-mail address). If you are not already registered on Microsoft Connect, visiting the link above will prompt you to register.

Posted by petersad | 0 Comments

General SQL Server Express Survey

Microsoft is committed to making the SQL Server Express installation experience the best in industry. For us to achieve this goal, we need your candid feedback on your experience with installing SQL Server Express.  If you have used several different versions of SQL Server Express, focus on the latest version that you have used.  When SQL Server 2008 Customer Technical Preview 3 is released, feel free to complete this survey again since several installation improvements have been made.  This information will be used to improve our future releases including SQL Server 2008 R2 and SQL Server 11.  This survey will be available until the end of November.

Instructions:

To register for the General Express Usage Survey, follow this link.*   Once your registration is complete, click here and then click on “Respond to this Survey” to complete the profile.

*If you are already registered on Microsoft Connect, visiting the link will prompt you to login with the Windows Live ID e-mail address associated with your account (note that the email address we used to contact you regarding this invitation is not necessarily your account e-mail address). If you are not already registered on Microsoft Connect, visiting the link above will prompt you to register.

Posted by petersad | 0 Comments

Invoke or BeginInvoke cannot be called on a control until the window handle has been created.

We have been hearing that customers installing SQL Server 2008 and SQL Server 2008 August CTP are hitting the following error:

“Invoke or BeginInvoke cannot be called on a control until the window handle
has been created.”

This issue is occurring due to .NET behavior on Win7 change that is exposing a bug in how we close UI dialogs. Generally, if you just rerun it won't hit the issue again.

 

Fix information:

This issue will be addressed in SQL Server 2008 R2 and a future SQL Server 2008 CU.

Posted by petersad | 1 Comments
Filed under: ,

Microsoft SQL Server 2008 R2 August CTP

The August CTP of Microsoft SQL Server 2008 R2 is now published: http://technet.microsoft.com/en-us/evalcenter/ee315247.aspx. Give it a try and give us feedback!!!

 

This release does not have many changes around the Express when compared to SQL Server 2008.  But the next CTP will contains several improvements as a result of your feedback. Here are some of the changes that will be in the SQL Server 2008 R2 Express product:

  • The Express runtime package is smaller
  • Setup UI Changes
    • All user input defaulted (Vista and above): Therefore you can just click Next through the Installation Wizard. The features are selected and the service accounts are defaulted. Less choices means better chance for success!
    • All features selected by default: When you run Express, all the features within the package would be selected to be installed.
    • Number of clicks and screens: The number of steps or clicks to install have been reduced by 50%.
    • Pre-reqs: Clearer messaging whether .NET or MSI needs to be installed before proceeding with the installation and a direct link to the download
Posted by petersad | 0 Comments

Microsoft Update Guidance for SQL Server

I have written several blogs covering SQL Server update being deployed though Microsoft Update.  See here for these blogs.  I thought it would be good, this time, to cover some general best practices obtaining SQL Server updates through Microsoft Update.

 

General:

  • Any security update for SQL Server 2000, SQL Server 2005, SQL Server 2008, SQL Server 2008 R2 would always be deployed through Automatic Update. Meaning, the update would be deployed to the system based on the Windows Update settings.
  • Updates through Microsoft Update will always be deployed without UI intervention(unattended), except for patching a SQL Server 2005 cluster. See below for more information in the clustering section.
  • SQL Server updates through Microsoft Update will upgrade all instances. For example, if you have two instances of SQL Server 2005 that are running on the computer, both instances will be upgraded to SQL Server 2005 SP3. If you don’t want to patch all instance, you will need to obtain the update through the Download Center. See the following links for more information:

Clustering:

      It is recommended that you set the Windows Update setting to “Download and notify” to prevent accident installation or downtime

  • SQL Server 2005
    • As it is necessary to provide credentials for the service pack or update to run on the passive node. It is recommended that you run the update on the ACTIVE NODE first, which will patch the instance on the PASSIVE NODE and then run the update on the passive node to ensure all other components are patched.
  • SQL Server 2008, including SQL Server 2008 R2 (when released)

How will updates be deployed by Windows Update (Automatic Update):

  • SQL Server 2005
    • The service packs for SQL Server 2005 Express Editions are deployed through Automatic Update
    • The service pack for all other SQL Server 2005 Editions are not deployed through Automatic Update, meaning you need to manually scan for the update
  • SQL Server 2008 and SQL Server 2008 R2
    • Currently Service Pack 1 (SP1) is not deployed through Automatic Update, but this may change in the future. See for here for details.

image

Additional References can be found:

Posted by petersad | 0 Comments
Filed under: ,

SQL Server on Windows 7

SQL Server is supported on Windows 7, but you may need to apply the latest Service Pack level to be supported. 

 

Here are the supported products and SP levels:

  • SQL Server 2005: SP3 is required
  • SQL Server 2008: SP1 is required
  • SQL Server 2008 R2 CTP3:Supported without any additional updates

The service pack for each of these products are available through Microsoft Update, as mentioned in these blogs:

Known Issues:

  • “Invoke or BeginInvoke cannot be called on a control until the window handle has been created.”  error. Details are posted here.

 

Other comments:

Additional information can be found in KB 955725, which is being updated to reflect the final Windows 7 Release.

Troubleshooting .NET 2.0/3.5 Installation errors

The installation of .NET 3.5 can fail for several reasons. Sometimes the .NET 3.5 install fails and sometime SQL Server Setup fails to detect .NET is already on the machine.

 

If you view the %temp%\sqlsetup.log you can determine whether the .NET 3.5 installation failed or SQL Server Setup incorrectly detected .NET was already installed.

 

Here is an example were .NET 3.5 SP1 failed to install.

05/21/2008 07:32:55.750 ======================================================================
05/21/2008 07:32:55.765 Setup launched
05/21/2008 07:32:55.765 Attempting to determine media source
05/21/2008 07:32:55.765 Media source value not specified on command line argument.
05/21/2008 07:32:55.765 Setup is launched from media directly so default the value to the current folder.
05/21/2008 07:32:55.765 Media source: \\sqlbuilds\Improvements\clusterRefresh\10.00.1441.12\retail\SQLFULL_ENU\
05/21/2008 07:32:55.765 Attempt to determine media layout based on file '\\sqlbuilds\Improvements\clusterRefresh\10.00.1441.12\retail\SQLFULL_ENU\mediainfo.xml'.
05/21/2008 07:32:55.796 Media layout is detected as: Full
05/21/2008 07:32:55.796 Local setup.exe not found, so continuing to run setup.exe from media.
05/21/2008 07:32:55.796 /? or /HELP or /ACTION=HELP specified: false
05/21/2008 07:32:55.796 Help display: false
05/21/2008 07:32:55.796 Checking to see if we need to install .Net version 3.5
05/21/2008 07:32:55.796 .Net version 3.5 needs to be installed from media: \\sqlbuilds\Improvements\clusterRefresh\10.00.1441.12\retail\SQLFULL_ENU\
05/21/2008 07:32:55.796 Attempting to find media for .Net version 3.5
05/21/2008 07:32:55.796 Attempting to install .Net version 3.5
05/21/2008 07:35:36.725 Received exit code -1073741818 from installing .Net version 3.5
05/21/2008 07:35:36.725 .Net version 3.5 installation failed, so setup will close. Error code: -1073741818

05/21/2008 07:35:36.725 Setup closed with exit code: 0x84C40013
05/21/2008 07:35:36.725 ======================================================================

When .NET failed to install, your next step is to look at the .NET log files. The logs produced by the .NET Framework 3.5 setup wrapper:

  • %temp%\dd_dotnetfx35install.txt
  • %temp%\dd_dotnetfx35error.txt
  • %temp%\dd_depcheck_netfx*.txt

You should review these log to determine the cause for failure. If you still need help look at these resources:

Posted by petersad | 0 Comments
Filed under:

SQL Server 2008: “Could not fix registry key” Issue and how to resolve

In SQL Server 2008, we added a tool to fix some registry keys to address some known issues.  We recently discovered this tool can fail on rare occasions when it does not have permissions to all required registry keys.

 

If a rule fails with the following message:

“The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix.” you might be hitting this issue. See below to determine whether you are encountering this issue and how to address.

 

If you view the “SystemConfigurationCheck_Report.htm” that is located in %programfiles%\Microsoft SQL Server\100\Setup Bootstrap\Log\<latest session>, you will see this error, as shown below:

image

If you view the Summary*GlobalRules.txt, you will see:

image

If you view the Summary*GlobalRules.txt, you will see:

 

This error happens since some registry keys that need to be fixed do not have administrator access. In this log file, the Lpc key does not have administrator access:

2009-07-31 14:34:16 Slp: Could not fix registry key HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\MICROSOFTBCM\MSSQLServer\SuperSocketNetLib\Lpc.
2009-07-31 14:34:16 Slp: System.UnauthorizedAccessException: Attempted to perform an unauthorized operation.

2009-07-31 14:34:16 Slp:    at Microsoft.SqlServer.Configuration.FixSqlRegistryKey.Program.OpenKey(String keyName)
2009-07-31 14:34:16 Slp:    at Microsoft.SqlServer.Configuration.FixSqlRegistryKey.Program.FixRegistryKey(String keyName)
2009-07-31 14:34:16 Slp:    at Microsoft.SqlServer.Configuration.FixSqlRegistryKey.Program.FixRegistryKeyAndSubKeys(RegistryKey key)

2009-07-31 14:34:17 Slp: Error: Action "RunStandaloneRules" threw an exception during execution.
2009-07-31 14:34:17 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix registry keys. ---> Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngineRuleFailureException: The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix registry keys.
2009-07-31 14:34:17 Slp:    at Microsoft.SqlServer.Configuration.RulesEngineExtension.RunRulesAction.ExecuteAction(String actionId)
2009-07-31 14:34:17 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2009-07-31 14:34:17 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2009-07-31 14:34:17 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2009-07-31 14:34:17 Slp:    --- End of inner exception stack trace ---
2009-07-31 14:34:17 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2009-07-31 14:34:18 Slp: Received request to add the following file to Watson reporting: C:\Documents and Settings\hoffman\Local Settings\Temp\tmp346.tmp
2009-07-31 14:34:18 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2009-07-31 14:34:18 Slp: Inner exceptions are being indented
2009-07-31 14:34:18 Slp:
2009-07-31 14:34:18 Slp: Exception type: Microsoft.SqlServer.Configuration.RulesEngineExtension.RulesEngineRuleFailureException
2009-07-31 14:34:18 Slp:     Message:
2009-07-31 14:34:18 Slp:         The SQL Server registry keys from a prior installation cannot be modified. To continue, see SQL Server Setup documentation about how to fix registry keys.
2009-07-31 14:34:18 Slp:     Data:
2009-07-31 14:34:18 Slp:       DisableWatson = true
2009-07-31 14:34:18 Slp:     Stack:
2009-07-31 14:34:18 Slp:         at Microsoft.SqlServer.Configuration.RulesEngineExtension.RunRulesAction.ExecuteAction(String actionId)
2009-07-31 14:34:18 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2009-07-31 14:34:18 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2009-07-31 14:34:18 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2009-07-31 14:34:20 Slp:
2009-07-31 14:34:20 Slp: ----------------------------------------------------------------------
2009-07-31 14:34:20 Slp:
2009-07-31 14:34:20 Slp: Error result: -2067922433
2009-07-31 14:34:20 Slp: Result facility code: 1214
2009-07-31 14:34:20 Slp: Result error code: 511

 

Workaround:

Open up the registry and navigate to the registry key with the issue can give the administrator access to the registry key. 

 

As always, use extreme caution when modifying the windows registry.

Posted by petersad | 0 Comments

SQL Server 2008 continually asking you to reboot even after you just rebooted

There have been reports that SQL Server 2008 will ask you to reboot after just rebooting.  This problem is happening because several applications are marking files in such a way that SQL Server 2008 Setup interprets as a reboot is needed.

 

If you experiencing this issue, you can add the following command line to the Setup:

/SKIPRULES=RebootRequiredCheck

 

You should only use this command line if you are experiencing the issue describe above.

Posted by petersad | 0 Comments
Filed under: ,

SQL Server 2008 Service Pack (SP) 1 on Microsoft Update as a Required Automatic Update

[Update on September 4th, 2009] We are still discussing when to make SQL Server 2008 SP1 available through Automatic Update. At this time, it would be released through Automatic Update in September. 

SQL Server 2008 SP1 started to be deployed through Microsoft Update on April 28th. We are now considering making the update available through Automatic Update in September the future, see here to better understand Automatic Update.

If an update is flagged as an automatic update (AU) the logic will honor the Windows Update settings for deploying the update.  This means, you do not need to manually scan for updates through the Windows Update web page or Control Pane and you let Windows control the installation.

Here are the Windows (Vista) settings that will tell an AU update how to behave:

clip_image001

We would like to make this change to easily bring SQL Server 2008 instances up to the latest Service Pack.

Additionally, SQL Server 2008 SP1 is required when running SQL Server 2008 on a Windows 7 system.

SQL Server 2008 Failover Clustering Whitepaper has been published

 

Summary: This white paper complements the existing documentation on planning, implementation, and administration of a SQL Server 2008 failover cluster, which can be found in Microsoft SQL Server 2008 Books Online. There are links to relevant existing content throughout the paper, which is intended primarily for a technical audience. This white paper covers failover cluster architecture and concepts for Windows Server (2003 and 2008) and SQL Server 2008; installation of a SQL Server 2008 failover cluster; upgrades and updates to SQL Server 2008 failover clustering; and maintenance and administration of SQL Server 2008.

 

For further information please download the SQL Server 2008 Failover Clustering whitepaper.

SQL Server 2005 SP3 Microsoft Update release for Windows 7

On June 23rd, 2009 the following SQL Server 2005 Service Pack 3 (SP3) updates will be available for Windows 7 through Microsoft Update (MU). 

 

Update Name

Available through Automatic Update

Microsoft SQL Server 2005 Service Pack 3 (KB955706)

 

Microsoft SQL Server 2005 Service Pack 3 Failover Clustering (KB955706)

 

Microsoft SQL Server 2005 Express Edition Service Pack 3 (KB955706)

Yes

Microsoft SQL Server 2005 Express Edition with Advanced Services Service Pack 3 (KB955706)

Yes

Microsoft SQL Server 2005 Express Edition Toolkit Service Pack 3 (KB955706)      

Yes

 

There are no changes to the actual SP3 update, this was just a change to the Microsoft Update detection logic to offer to Windows 7.  Everything else is the same.

 

What is Automatic Update?

Creating a merged (slipstreamed) drop containing SQL Server 2008 RTM + Service Pack 1

[Updated on April 7th, along with the availability of SQL Server 2008 SP1]

Today, I am going to show you how to create new source media that will slipstream the original source media and SQL Server 2008 Service Pack 1. Once you have created this drop, you can install SQL Server 2008 SP1 in a single step! These instructions are included with the Service Pack 1 release but there are some issues with the documentation that will be addressed in the next revision of the on-line documentation. There is not a lot of user interface that indicates you are slipstreaming, but there are a few clues, see at the bottom for screen shots.

These steps will take a little longer to perform than the steps for the basic slipstream describe here, but once completed you will be able to run a slipstream installation from the same location. It is recommended you verify you can complete a slipstream installation from the new drop on a test machine before deploying into production.

These instructions are for English SQL Server but will work with any language of SQL Server if you obtain the correct service package language.

1. Copy your original SQL Server 2008 source media to c:\SQLServer2008_FullSP1

2. Download Service Pack 1 from http://www.microsoft.com/downloads/details.aspx?FamilyID=66ab3dbb-bf3e-4f46-9559-ccc6a4f9dc19. The three architectures of Service Pack 1 should be included, the package names are as follows:

    • SQLServer2008SP1-KB968369-IA64-ENU.exe
    • SQLServer2008SP1-KB968369-x64-ENU.exe
    • SQLServer2008SP1-KB968369-x86-ENU.exe

3. Extract the packages as follows:

  • SQLServer2008SP1-KB968369-IA64-ENU.exe /x:c:\SQLServer2008_FullSP1\PCU
  • SQLServer2008SP1-KB968369-x64-ENU.exe /x:c:\SQLServer2008_FullSP1\PCU
  • SQLServer2008SP1-KB968369-x86-ENU.exe /x:c:\SQLServer2008_FullSP1\PCU

Ensure you complete this step for all architectures to ensure the original media is updated correctly.

4. Copy Setup.exe and Setup.rll from the PCU extracted location to original source media location

  • robocopy C:\SQLServer2008_FullSP1\PCU c:\SQLServer2008_FullSP1 Setup.exe
  • robocopy C:\SQLServer2008_FullSP1\PCU c:\SQLServer2008_FullSP1 Setup.rll

5. Copy all files not the folders, except the Microsoft.SQL.Chainer.PackageData.dll, in c:\SQLServer2008_FullSP1\PCU\<architecture> to C:\SQLServer2008_FullSP1 \<architecture> to update the original files.

  • robocopy C:\SQLServer2008_FullSP1\pcu\x86 C:\SQLServer2008_FullSP1\x86 /XF Microsoft.SQL.Chainer.PackageData.dll
  • robocopy C:\SQLServer2008_FullSP1\pcu\x64 C:\SQLServer2008_FullSP1\x64 /XF Microsoft.SQL.Chainer.PackageData.dll
  • robocopy C:\SQLServer2008_FullSP1\pcu\ia64 C:\SQLServer2008_FullSP1\ia64 /XF Microsoft.SQL.Chainer.PackageData.dll

NOTE: if you accidentally copy the Microsoft.SQL.Chainer.PackageData.dll file, you may see this error when you launch Setup.exe. If this happens, restore  Microsoft.SQL.Chainer.PackageData.dll back to the original version.

clip_image002

6. Determine if you have a defaultsetup.ini at the following locations:

  • C:\SQLServer2008_FullSP1\x86
  • C:\SQLServer2008_FullSP1\x64
  • C:\SQLServer2008_FullSP1\ia64

If you have a defaultsetup.ini, add PCUSOURCE="{Full path}\PCU".

NOTE: The {Full path} needs to be the absolute path to the PCU folder. If you will just be running from local folder it would be C:\SQLServer2008_FullSP1. If you will eventually share this folder out, {Full path} would be \\MyServer\SQLServer2008_FullSP1.

See question #11 here if you would like to use a relative path.

     ;SQLSERVER2008 Configuration File

     [SQLSERVER2008]

     ...

     PCUSOURCE="{Full path}\PCU"

If you do NOT have a defaultsetup.ini, create one with the following content:

    ;SQLSERVER2008 Configuration File

    [SQLSERVER2008]

    PCUSOURCE="{full path}\PCU"

  and copy to the following locations

    • C:\SQLServer2008_FullSP1\x86
    • C:\SQLServer2008_FullSP1\x64
    • C:\SQLServer2008_FullSP1\ia64

      This file will tell the setup program where to locate the SP1 source media that you extracted in step 3.

7. Now run setup.exe as you normally would.

       

How can I tell I am slipstreaming?

1) You should see the "Update Setup Media Language Rule" on the Installation Rules dialog:

 InstallationRules

2) You should see the Action indicate it is being slipstreamed and the Slipstream node should be shown:

ReadyToInstall

3) You should see the PCUSource being specified in the Summary log:

Summary

 

4) After installing, if you run the "SQL Server features discovery report" off of the Installation Center you will see the following versions:

image

More Posts Next page »
 
Page view tracker