:::: MENU ::::

Posts Categorized / Deployment

  • Feb 22 / 2012
  • 0
dbDigger, Deployment, SQL Server Error messages, System Administration, Windows Server

Role management tool to install or configure .Net framework on Windows Server 2008

While installing SQL Server 2008 on Windows Server 2008 R2, i got following error message at initial stage in process.

Error message in SQL Server 2008 setup related to Role management tool

Windows was up to date and required version of .Net framework was installed on it. Opened Server Manager for Windows Server 2008 and clicked on features in left panel. Then by clicking Add Features link in right panel another panel was opened with several features available there for installation. I checked the box for my required .Net framework feature and Clicked on Next button to proceed with the installation.

Service Manager in Windows Server 2008 for .Net Framework features

The .Net feature was installed and SQL Server 2008 installation ended successfully.

  • Dec 14 / 2011
  • 0
DBA Interview questions, dbDigger, Deployment, SQL Server Training, SQL Server versions and editions, Windows Server

SQL Server editions and Windows platform

Each of SQL Server release like SQL Server 2000, SQL Server 2005 and SQL Server 2008 is further categorized in editions based on their features and capabilities. For example, edition of a specific release may be any of following

  • Data center edition
  • Enterprise edition
  • Standard edition
  • Developer edition
  • Express edition
  • Apart from these there may be some other editions like run time edition or web edition. Some editions like Data center edition or enterprise edition can only be installed on Server OS while others may be installed on both server or client OS.
    For windows platform the term Server OS refers to different editions of

  • Windows server 2000
  • Windows server 2003
  • Windows server 2008
  • Windows server 2008 R2
  • While for windows platform, client OS would be any edition of following

  • Windows 2000
  • Windows XP
  • Windows vista
  • Windows 7
  • So while installing any SQL Server version, do consult the requirements related to OS.

    • Jan 15 / 2011
    • 1
    dbDigger, Deployment, PowerShell

    Setup cannot proceed. windows management framework core is already installed on your system

    Few weeks back, I uninstalled PowerShell from Windows Server 2003 due to some requirement and continued to use PowerShell on my lpatop (Windows 7). Today i was again required to install PowerShell 2.0 on Windows Server 2003. I downloaded the PowerShell for Windows Server 2003. As setup file was executed following error frame was generated

    windows management framework core is already installed

    The error statement was as under

    Setup cannot proceed. Windows management framework core is already installed on your system.

    If you also get this error message then Go to “Add Remove Program” window in control panel and make sure that check box for Show Updates is checked. There you can find the installed Windows Management Framework. Remove this update and you can now proceed with installation process of PowerShell 2.0.
    Such issue may also be there when you are trying to upgrade from PowerShell 1.0 to PowerShell 2.0.

    • Dec 14 / 2010
    • 0
    dbDigger, Deployment

    Error messages when installing SQL Server 2008 R2 on Windows Server 2008 or Windows 7

    In a previous blogpost, i mentioned that SQL Server 2008 R2 halted when trying to install over SQL Server 2011 Denali. After uninstalling Denali when i again run SQL Server 2008 R2 following error message was generated

    SQL Server 2008 set up error messages on installation

    Method not found: ‘Boolean Microsoft.SqlServer.Configuration.MsiExtension.MsiExtensionMetadata.get_IsSlipstreamOrPatch()’..

    Failing in clean install of SQL Server 2008 R2, i tried to upgrade an existing SQL Server 2005 instance to SQL Server 2008 R2. But upgrade process also generated following error message

    sql server 2008 set up error message on upgrade

    Method not found: ‘Microsoft.SqlServer.Configuration.Sco.SqlEdition Microsoft.SqlServer.Configuration.SetupExtension.PidPublicConfigObject.
    GetRequiredEditionFromMedia(Microsoft.SqlServer.Chainer.Infrastructure.ServiceContainer)’..
    After some googling and little research on set up log. I found following two solutions that worked for both the clean installation and upgrade operations.
    1. Remove 100 folder from ‘C:/ProgramData/Microsoft/Microsoft%20SQL%20Server/’. It may be left by any previous failed installation or uninstall of SQL Server R2.
    2. Run SQL Server 2008 R2 set up by Admin rights on Windows Server 2008 or Windows 7. You may do it by right clicking the set up file.
    • Dec 14 / 2010
    • 0
    dbDigger, DENALI Technology Preview, Deployment

    Set up halts when trying to install SQL Server 2008 R2

    Recently i have installed SQL Server 2011 (Denali) on Windows Server 2008. I had previously SQL Server 2005 and SQL Server 2008 instances already installed on same windows. Denali was successfully installed and now three versions were working fine.
    During test process of one of my articles for MSSQLTips.com, i uninstalled SQL Server 2008 instance and again tried to install it.

    After confirmation of existence of required components and selection of required SQL Server features, set up got hanged without any progress or message. I waited for some time and also tried to prioritize the set up process through task manager but all in vain.
    So as a final solution i uninstalled Denali and installed SQL Server 2008 without any problem.

    • Aug 09 / 2008
    • 0
    DBA best practices, dbDigger, Deployment

    DBA Best Practices for Installation

    For installation process following check list will be helpful

    1. Always fully document installs so that your SQL Server instances can easily be reproduced in an emergency.
    2. If possible, install and configure all of your SQL Server instances consistently, following an agreed-upon organization standard.
    3. Don’t install SQL Server services you don’t use, such as Microsoft Full- Text Search, Notification Services, or Analysis Services.
    4. For best performance of SQL Server running under Windows, turn off any operating system services that aren’t needed.
    5. For optimum SQL Server performance, you want to dedicate your physical servers to only running a single instance of SQL Server, no other applications.
    6. For best I/O performance, locate the database files (.mdf) and log files (.ldf) on separate arrays on your server to isolate potentially conflicting reads and writes.
    7. If tempdb will be used heavily, also put it on its own separate array.
    8. Do not install SQL Server on a domain controller.
    9. Be sure that SQL Server is installed on an NTFS partition.
    10. Don’t use NTFS data file encryption (EFS) and compression on SQL Server database and log files.

    Chosen from SQL Server DBA best practices By Brad M.mcGehee

    Consult us to explore the Databases. Contact us