MZ@ !L!This program cannot be run in DOS mode. $Oy   ,y ,k ,o Rich PELlcOC! I .rsrc@@.reloc@B@xhdefgh(@5XpS~0H`x !"#$%& '8(P)h*+,-./0A(B@CXp04H5`6x785 6 7 8 9 : 8Ph               0  @  P  `  p                        0  @  P  `  p                        0  @  P  `  p                        0  @  P  ` @!BVw*y(~hH(php640H(<  8Xb   $)&1 >vOblHvVz  P h lh (h D X$NCPclvP (@Pp0h0 ؎@Ȁ @Microsoft SQL Server 2005 SetupTahomaP I &accept the licensing terms and conditionsP 2&PrintP2&Next >P2CancelDP0P P PPV$dP PP#@P@@Ȁ @Microsoft SQL Server 2005 SetupTahomaDP0P P PPV$dP PP#@P@P msctls_progress32PA&InstallPA&Cancel(~:  l}ƅǃņȇʅɃȊ͑҆nfmnnoopqqoo~kǃˁ˅̈ɈɃωӊ†|bfqsqsppsng{iyʅ̅̆̅̓wmwukhlktvqqm退mx~ÃɃ̃ψnɨyw{toruvo瀀¿p‚~}Ƈ֕ۧ錼wpusp䀀Ϙv~€ņ͔ܔ߄̔ⅲ{}unk}{ȿЗtŋӛވɀֻٙԞ۔ҁ{z{pv瀀їtŋי~ŒƩէۧҕϛ֜ٝڞܑ~zwx怀Ҡчߔ݄~ÔǔĔĞ˩֟Γȗқ֙ќڠؚ֜ءۤ܋unμ|σƉ•ǗȐŋČÚ̯ܬ֛ȕ͜؞إݙ՗آۡݟޜߏֆĈ¢~މӁȂǘȕǓƍŒǫٲݟϓϙ؟ڬݴܖڣߝܖ؝ޯڼ뀀ݾۦڪ݌ȇĘɛ˓ɓȩٲܟΕЛ١ڲۚۚۢ뀀ۑːƒǒȘ˰ۺާНҤުܹӞݱ退ۏ̌œȲӤЬ۵ܕΩԼ۴Ԭӯضڹ怀ۯѮӳٶؽꀀޱϬбԽ뀀رάΰϾ̩ƭɵͺ耀۪Ƿ瀀ǜƽ瀀١屒qÐ褎瀀䵇耀֐몄耀…zї減耀鹃︖耀ˁﮏ︙耀躑聀΃{|﷬˾耀ɾ耀װѶϺy聀耀耀耀耀耀耀ݬ耀耀耀耀耀耀耀耀耀耀耀耀耀耀耀耀I%Vf(  B %`51)%`)%`*)`*)B( }}z̙Ϟ}yqyqΦ}j[èɥŽؽ3O@ALM N"Q&Y0\3]4f@iCiDpLsPtQwUyX`…fĉlŋnƍpٛ|ǐtɒw˗}̙ϠѢӦ鼥׮֭ٳܹݻŷɻug`ʽyqǻƾžuibY5vɼqu`ؠ̙{wqfŸŤsx2N¦Ȼ 4 f3333f333ff3fffff3f3f̙3ffffffffff!___www(@ }}z̙Ϟ}yqyqΦ}j[èɥŽؽ3O@ALM N"Q&Y0\3]4f@iCiDpLsPtQwUyX`…fĉlŋnƍpٛ|ǐtɒw˗}̙ϠѢӦ鼥׮֭ٳܹݻŷɻug`ʽyqǻƾžuibY5vɼqu`ؠ̙{wqfŸŤsx2N¦Ȼ 4 f3333f333ff3fffff3f3f̙3ffffffffff!___www~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~(XxYyZy\{hp'K0R<^BcGhPoYwf+5 C!C,L~$)' #>W>Sk}AP!    ( S[[bV]IPY`PYBJKSNVFM;tB>|F8o?6k=+U22d;-Z5,a7ʒsӚ٩٭ݲ#I,_pSblGvRxϞӣէת5J4|G7JCYI_9zJMc@PUk.[9^sIYp{o6%u;-D+zA9T5LD]?V=REY9mGYeB`J "#8422/.==;::: &$"8D4110A>>?: (&#M6B1A-->>= )&%JLM62EE?>< *HHLMF!LM?@< $HHGKLKKL?@-(&HHIJKB3-(&#HGL41B)%HIK95BHHHHHJ5C HHHH77C ++*)(''&3 ,,,+++$   h4VS_VERSION_INFOZw w?.StringFileInfo 040904b02 PlatformNT INTEL X86LCompanyNameMicrosoft Corporation.FileDescriptionSQL Server Component Update Resources LibraryBFileVersion2005.090.1399.00,InternalNamesqlcur'LegalCopyright Microsoft Corp. All rights reserved.sLegalTrademarksMicrosoft is a registered trademark of Microsoft Corporation. Windows(TM) is a trademark of Microsoft Corporation< OriginalFilenamesqlcu.rllJProductNameMicrosoft SQL Server> ProductVersion9.00.1399.062 CommentsNT INTEL X86DVarFileInfo$Translation  10;Courier9;Tahoma&Finish&Next >TError %d installing %s. See <A HREF='%s'>log file</A> for more detailed information.There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information. Cannot launch %s %s >Could not find a package to install on the installation media.The number of transforms in the .ini file exceeds the maximum combined length of 1,024 characters. To proceed, reduce the number of transforms, and then run SQL Server Setup again.%Setup cannot upgrade SQL Instance %s.Failed to load SqlSpars.dllFailed to load SqlCu.dllMultiple hardware profiles are enabled. All SQL Server services must have only the current Hardware Profile logon property profile enabled. To proceed, see the Sqlrunxx.log file for details.iUnable to create setup log files. Free up space on the drive or verify that you have write permission on 'Setup cannot reinstall SQL Instance %s.Scc Failed to Initialize:5The WMI MSI Provider is not installed on the machine.TMSXML DomDocument could not be created. Please make sure MSXML is installed properlyUnable to read license file(Errors occurred during the installation:Error %d installing %s.GCreateFile call to open an existing pipe on remote/host machine failed.&Cannot obtain SKU info from setup.dll.cFailed to connect to the specified machine through WMI Check machine name, user name and password.Unable to process the check.kAn internal error occurred during install (failed to load package id). Contact Microsoft Technical Support.iDefault error for SCC check article. This value is set for all SCC check articles before they are called.6The SCC article check function returned an error code.=Failed to receive the specified registry value for SCC value.=Failed to receive the specified registry types for SCC value.7Failed to get the specified WMI property for SCC value.4Failed to get the specified WMI class for SCC value.9Failed to open the specified WMI namespace for SCC value.LThe SCC check article type passed to SccAddCheckArticle function is invalid.RThere is no SCC check article in SccPerformer but SccRunCheck function was called.yCoCreateInstance failed to create CLSID_WbemLocator. WMI is not installed on the machine or CoInitialize was not called.TAn application SCC callback function returned zero value and stopped SCC performing.qThe SCC property value definition for a SCC value check article passed to SccAddCheckArticle function is invalid.qThe SCC registry value definition for a SCC value check article passed to SccAddCheckArticle function is invalid.bThe SCC value type for a SCC value check article passed to SccAddCheckArticle function is invalid.ZThe SCC generic check article definition passed to SccAddCheckArticle function is invalid.ZThe SCC service check article definition passed to SccAddCheckArticle function is invalid.XThe SCC class check article definition passed to SccAddCheckArticle function is invalid.hDefault error for SCC check value. This value is set for all SCC check values before they are collected.XThe SCC value check article definition passed to SccAddCheckArticle function is invalid.'%s' Target: '%s'8Source file or directory missing or cannot be read: '%s')CreateNamedPipe failed to create the pipe0Run was unable to create thread to run process. LCMultiProcessCtrl::Init failed, typically caused by mem allocation failure. bCMultiProcessCtrl::Init has not been called yet, should be called before using CMultiProcessCtrl. \CMultiProcessCtrl::GetProcessObjectForComputer could not find the associated CRemote object.1The license mode information provided is invalid.Setup failed to perform required operations on at least one cluster node. Refer to Setup logs for more information. To view SQL Server Setup log files, see the SQL Server Books Online topic, How to View SQL Server Setup Log Files.An error occurred while creating virtual server resources for your SQL Server cluster. This error could be the result of transient network conditions. Possible workarounds are restarting the nodes of the cluster, and changing the SQL Virtual Server name and IP addresses. Setup will now roll back the installation. Refer to the Setup and Cluster logs, and Windows Event Viewer for more detailed information. To view Setup log files, see the SQL Server Books Online topic, How to View SQL Server Setup Log Files. An error occurred while modifying virtual server resources for your SQL Server cluster. Refer to Setup and Cluster logs, and to the Windows Event Viewer for more detailed information. For log file details, see How to View Setup Log Files in SQL Server Books Online.An error occurred while removing virtual server resources for your SQL Server cluster. For more information, refer to Setup and Cluster logs, and Windows Event Viewer.mInstallation ended prematurely because of an error. Click Finish to exit the SQL Server Installation Wizard.AThe setup help file could not be loaded or help is not available. Setup Error#An error has occurred during setup.An error has occurred while performing the following setup action. Please select help for more information about this error. You may be able to skip this action by selecting ignore, or retry the action by selecting retry. Selecting cancel will end the installation of SQL Server.Remote setup failed."Setup cannot upgrade SQL Instance.1Setup failed. Refer to the Setup log for details..An invalid parameter was passed to a function.SQL Server Setup unexpectedly failed. For more information, review the Setup summary log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt. cFailed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS).Unable to process the check.Unable to process the check.Unknown article Result.Unknown articleSetup has detected a problem with Microsoft .Net Framework installation and cannot proceed. Microsoft .Net Framework 2.0 is either not installed on this system or is corrupt.cFailed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS).cFailed to find the ASP.Net Version Registration with Microsoft Internet Information Services (IIS).XThe Microsoft .Net Framework 2.0 is not installed. Please install before running setup. The sa / report server database password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements. CThe feature(s) specified are not valid for any SQL Server products.`Your operating system does not meet Service Pack level requirements for this SQL Server release. Install the Service Pack from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=50380, and then run SQL Server Setup again. For system requirements, see Hardware and Software Requirements, in the readme or in SQL Server Books Online.SQL Server Setup could not run. Another instance of SQL Server Setup is already running. The running instance must complete before you can run SQL Server Setup again.cTo run SQL Server Setup, log on to this computer with an account that has administrator privileges.7The account is not a admin account on the cluster node.6The instance specified was not installed on a cluster.SQL Server Setup uses administrative shares to copy files to each cluster node. Verify that administrative shares are available to each node in your cluster, and then run SQL Server Setup again..The minimum hardware requirements are not met.1The recomended hardware requirements are not met.-Must reboot the machine before running setup.YThe user running the setup does not have write permissions to the specified install path.;The minimum IE Version is not met for Sqlworkbench feature.GThe current user does not have write permissions to the specified path.-Hardware profile is disabled for the service.0The group already contains a SQL Virtual Server.1The group does not contain any valid shared disk.sInstance names can contain from 1-16 characters, and must follow the rules of SQL Server non-delimited identifiers.:The user name and password is not correct for the account.3The name you entered already exists on the network.mThe IP address does not match the subnet mask. To proceed, enter the IP address that matches the subnet mask. The IP Address is already in useThe IP Address is invalid@The instance cannot be maintained because of different language.:The instance cannot be maintained because of a lesser SKU.(SQL identifier cannot be a blank string."SQL identifier exceded max length."Virtual directory name is invalid.aVirtual root name is invalid. The Virtual root name specified exceeds the maximum length allowed.?Virtual root already exists and can't be used for installation.FThe feature(s) specified are not valid for this edition of SQL Server.?SQL Server 2005 Setup has detected incompatible components from beta versions of Visual Studio, .NET Framework, or SQL Server 2005. Use Add or Remove Programs to remove these components, and then run SQL Server 2005 Setup again. For detailed instructions on uninstalling SQL Server 2005, see the SQL Server 2005 Readme.The current system does not meet processor architecture requirements for this SQL Server release. To continue, install SQL Server 2005 on a supported configuration. For detailed hardware requirements, see the readme file or SQL Server Books Online.Another version of this product is already installed. To continue remove the existing version of %s, use Add/Remove Programs on the Control Panel.BThe instance cannot be maintained because it is of higher version.;The minimum IE Version is not met for Sqlworkbench feature.A parameter in the .ini settings file is not valid or unrecognized. Check the settings you have specified in the .ini settings file, and then run SQL Server Setup again.SQL Server Setup has detected that the following required component is not installed: Microsoft Windows Installer 3.1. To proceed, download and install the Windows Installer 3.1 Redistributable from http://go.microsoft.com/fwlink/?LinkId=50380 , and then run SQL Server Setup again.aWarning: In this release of SQL Server 2005, side-by-side installations of SQL Server 2005 (64-bit) with any 32-bit version of SQL Server installed to WOW64 may succeed, but will not be supported. Uninstallation of any SQL Server instance from side-by-side configurations of 64-bit and 32-bit SQL Server instances will disable the remaining instances. Recommended Hardware RequirementThe current system does not meet recommended hardware requirements for this SQL Server release. For detailed hardware requirements, see the readme file or SQL Server Books Online.The current system does not meet the recommended hardware requirements for this SQL Server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online.fSetup failed to start on the remote machine. Check the Task scheduler event log on the remote machine.iSQL Server Setup is unable to run on this node as it is unavailable due to a SCC failure or other reason.SQL Server Setup is unable to run. Either the owning node or all nodes that are currently part of the virtual server are not available. Review any SCC failures and validate that all nodes are online.iAll resources did not come online and therefore you will need to manually set the cluster restart option.SQL Server 2005 Setup cannot continue because the installation package could not be opened. The installation package has a missing file, or you are running a 32-bit only Setup program on a 64-bit computer. To continue, verify the SQL Server 2005 package you are running is supported on WOW64. If you are certain that you are running a supported SQL Server 2005 package, and you continue to see this message, contact the application vendor.Unsupported OS version.Unsupported OS type.Required higher OS SP.!Unsupported OS type for this SKU.%s Setup[SQL Server Setup requires access to the CD. Reinsert your %s installation media to proceed.BLook in Books Online topic: Running Setup from the Command Prompt. autorun.infquietnonebasicreducedfullThe log file path specified in your .ini settings file is too long. The maximum expanded length for the log file path is 260 characters, including environment variables.The DISPLAY option in the .ini settings file is not valid. Valid options are quiet one, basic educed, or full. Reset the DISPLAY option for your installation, and then run SQL Server Setup again. Tahoma,9,1The log file path (%s) is invalid. * The path may contain invalid characters. * The file may exist but not be writable, the folder may not exist, the folder may be located on an unavailable volume or protected with a password, or the path may contain environment variables that are not set (e.g. %TEMP%). To proceed, make sure that the log file path is valid, writable, and available, and then run SQL Server Setup again.`Your operating system does not meet Service Pack level requirements for this SQL Server release. Install the Service Pack from the Microsoft Download Center at http://go.microsoft.com/fwlink/?LinkId=50380, and then run SQL Server Setup again. For system requirements, see Hardware and Software Requirements, in the readme or in SQL Server Books Online.SUnable to install %s font. Setup will continue, but some screens may look odd. %s Setup has detected unbalanced quotation marks in your properties list: %s. To proceed, verify that the properties list in your .ini file or command-line syntax contains balanced pairs of quotation marks, and then run SQL Server Setup again.=SQL Server Setup is scanning your computer's configuration...`The system needs to be rebooted. Do you want to reboot? Click Yes to reboot. Click No to cancel.qThe value entered for Upgrade= in the .ini settings file or command line is incorrect. The only valid value is 1.This version of SQL Server Setup is older than the version used for the last installation. You must use the same version of Setup for maintenance as you used for the last installation. To proceed, insert the product CD from the last installation, and then run SQL Server Setup again.Windows Management Instrumentation (WMI) is not enabled on this computer. To continue, enable the WMI service, and then run SQL Server Setup again.UInvalid INI file. Make sure the file exists, have access and has the correct entries.Invalid command line.This version of SQL Server Setup is older than the version used for the last installation. You must use the same version of Setup for maintenance as you used for the last installation. To proceed, insert the product CD from the last installation, and then run SQL Server Setup again.Microsoft SQL Server 2005 SetupGMicrosoft SQL Server 2005 Setup was unable to install on your computer.GMicrosoft SQL Server 2005 Setup has encountered a problem and will end.End User License AgreementInstalling PrerequisitesEInstalls software components required prior to installing SQL Server.&Are you sure you want to cancel Setup?Microsoft SQL Server 2005Windows Installer 2.0-Microsoft SQL Server 2005 Setup Support Files.NET FrameworkClick Install to continue.Configuring components... Cancelling...+The installation was cancelled by the user.MThe installation completed. A reboot is required. Click Finish to exit Setup.4The required components were installed successfully.`SQL Server Component Update will install the following components required for SQL Server Setup:/Invalid UPGRADE option a valid value is only 1.SThe version of MDAC on this computer is not supported by Microsoft SQL Server 2005. Node is downAn installation with the same instance name already exists. Instance names may not be duplicated across the entire cluster namespace.AWindows installer is not present or has not the required version.'Not a domain user for cluster security.TSQL identifier can start with a letter, sign (@), number sign (#) or underscore (_)./SQL identifier must not be a SQL reserved word.Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.Upgrades are not supported yetgMaintenance is disallowed until Service Pack has been applied to nodes added to other Virtual Server(s)SKU upgrades are not supported1The format of the Virtual Server name is invalid.qYou cannot maintain this Virtual Server because you are running an older build or lesser SKU of SQL Server Setup./There are no IP addresses for the specified VS.Group name is invalid.The data files for this instance are located on a cluster disk resource, which is owned by another node of the cluster, and is not accesible from this node.0You can not remove and add nodes simultaneously.:Specified a different service account for add/remove node. Invalid Disk?There are no ProductID or DigitalProductID on the cluster nodesThis Virtual Server is invalid.!Upgrades are not implemented yet.!Upgrades are not implemented yet.Service Pack has been applied!Upgrades are not implemented yet.!Upgrades are not implemented yet.All nodes on the virtual server must be at the same Service Pack level. To ensure proper failover functionality, install the same Service Pack level on each node of the virtual server before continuing.YSetup is performing required operations on cluster nodes. This may take a few minutes...-Microsoft Cluster Services is not installed eSetup is performing cleanup operations on cluster nodes and will exit once the cleanup is complete...}The installation wizard has successfully configured Microsoft SQL Server 2005. Click Finish to exit the installation wizard.The installation wizard has successfully configured Microsoft SQL Server 2005. Reboot of following node(s) is required for changes to take effect. Click Finish to exit the installation wizard.<Setup is creating Virtual Server resources on the cluster...>Setup is removing Virtual Server resources from the cluster...=Setup is modifying Virtual Server resources on the cluster...!Upgrades are not implemented yet.!Upgrades are not implemented yet.UpgradeMaintain Copying filesInstallation of SQL Server is not complete. If you exit the Installation Wizard now, SQL Server will not be installed, and your system will be rolled back to its previous state. Are you sure you want to cancel SQL Server Setup?Microsoft SQL Server 2005InstanceReasonLocal InstanceVirtual ServerTo install a new Virtual Server or Local Instance choose 'Start a new installation'. To modify a previous server installation choose 'Work with an existing installation'.No message Text Setup TypePAdd node for Virtual Servers can be performed only if Setup has the same versionTo install or maintain SQL Server on a local computer click Local Computer. For remote installation click Remote Computer and enter the remote computer name with logon credentials.Choose the type of Setup.8Setup is unable to verify the logon credentials entered.$Installing Microsoft SQL Server 2005lPlease wait while the Installation Wizard installs Microsoft SQL Server 2005. This may take several minutes.6The program features you selected are being installed. Setup ModeTo install a new instance of SQL Server click 'Start a new installation'. To modify a previous server installation choose 'Work with an existing installation'.$Choose the mode of setup to perform.Change or RemoveBSelect whether to change or remove the installation of SQL Server.5Add or remove features of this existing installation.ERemove all features of this existing installation from your computer.CancelISetup is updating .Net Framework components. This may take a few minutes.TSetup failed to upgrade Microsoft .Net Framework components. Setup can not continue.Microsoft SQL Server 2005 Setup System Configuration Consistency Security Certificate ConsistencyCluster ConsistencyThe node is down or unavailable. To proceed, make each node available to SQL Server Setup by starting up the computer or enabling the cluster service, and then run SQL Server Setup again.The current operating system is not supported for this SQL Server release. For hardware and software requirements, see the readme file or SQL Server Books Online.]The current operating system does not meet Service Pack level requirements for this SQL Server release. Install the most recent Service Pack from the Microsoft download center at http://go.microsoft.com/fwlink/?LinkId=50380, and then run SQL Server Setup again. For hardware and software requirements, see the readme file or SQL Server Books Online.*Operating System Minimum Level Requirement#Minimum Physical Memory Requirement#Minimum Free Disk Space RequirementThe current system does not meet the minimum hardware requirements for this SQL Server release. For system requirements, see Hardware and Software Requirements, in the readme file or in SQL Server Books Online.Windows Management Instrumentation (WMI) is not enabled on this computer. To proceed, enable the WMI service and then run SQL Server Setup again.*Check machine name, user name and passwordHSetup completed successfully. The following computers must be rebooted: Reboot of the remote computer is required for the changes to take effect. Do you want setup to attempt to reboot the remote computer?FinishyThe installation wizard has successfully removed Microsoft SQL Server 2005. Click Finish to exit the installation wizard.The installation wizard has successfully removed Microsoft SQL Server 2005. Reboot of the remote computer is required for the changes to take effect. Click Finish to exit the installation wizard.Node: Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online. Windows Management Instrumentation (WMI) is not enabled on this computer. To proceed, enable the WMI service and then run SQL Server Setup again. For more information on how to enable the WMI service, see How to Enable Windows Management Instrumentation (WMI), in SQL Server Books Online.Windows Management Instrumentation (WMI) is not enabled on this computer. To proceed, enable the WMI service and then run SQL Server Setup again. For more information on how to enable the WMI service, see How to Enable Windows Management Instrumentation (WMI) in SQL Server Books Online.The current operating system is not supported for this SQL Server release. For hardware and software requirements, see the readme file or SQL Server Books Online.]The current operating system does not meet Service Pack level requirements for this SQL Server release. Install the most recent Service Pack from the Microsoft download center at http://go.microsoft.com/fwlink/?LinkId=50380, and then run SQL Server Setup again. For hardware and software requirements, see the readme file or SQL Server Books Online.Cannot obtain SKU info fromCannot obtain SKU info.Some components of this edition of SQL Server are not supported on this operating system. For details, see 'Hardware and Software Requirements for Installing SQL Server 2005' in Microsoft SQL Server Books Online.3WMI is not installed on the machine or is disabled.7Failed to connect to the specified machine through WMI.0Operating System Service Pack Level Requirement.1SQL Server Edition Operating System Compatibility Check Passed Upgrade to Windows 2000 or later]The current operating system does not meet Service Pack level requirements for this SQL Server release. Install the most recent Service Pack from the Microsoft download center at http://go.microsoft.com/fwlink/?LinkId=50380, and then run SQL Server Setup again. For hardware and software requirements, see the readme file or SQL Server Books Online. Install it by running setup.exe.)IIS dependency is not met on the machine.IIS Feature RequirementMicrosoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.Microsoft Internet Information Services (IIS) is either not installed or is disabled. IIS is required by some SQL Server features. Without IIS, some SQL Server features will not be available for installation. To install all SQL Server features, install IIS from Add or Remove Programs in Control Panel or enable the IIS service through the Control Panel if it is already installed, and then run SQL Server Setup again. For a list of features that depend on IIS, see Features Supported by Editions of SQL Server in Books Online.WMI Service RequirementRPlease make sure Windows Management Instrumentation (WMI) is functioning properly. Windows Management Instrumentation (WMI) is not enabled on this computer. To proceed, enable the WMI service and then run SQL Server Setup again. For more information on how to enable the WMI service, see How to Enable Windows Management Instrumentation (WMI), in SQL Server Books Online.!Administrative Shares RequirementNo administrative shares were found. Verify that administrative shares are available to each node in your cluster, and then run SQL Server Setup again.SQL Server Setup uses administrative shares to copy files to each cluster node. Verify that administrative shares are available to each node in your cluster, and then run SQL Server Setup again.Minimum Hardware RequirementThe current system does not meet minimum hardware requirements for this SQL Server release. For detailed hardware requirements, see the readme file or SQL Server Books Online.The current system does not meet the minimum hardware requirements for this SQL Server release. For detailed hardware and software requirements, see the readme file or SQL Server Books Online.'Performance Monitor Counter RequirementThe System Configuration Check for Performance Monitor counter registry value has failed. For details, see How to: Increment the Counter Registry Key for Setup in SQL Server 2005, in the readme file or in SQL Server Books Online.The System Configuration Check for Performance Monitor counter registry value has failed. For details, see How to: Increment the Counter Registry Key for Setup in SQL Server 2005, in the readme file or in SQL Server Books Online.Pending Reboot Requirement/Reboot the machine before continuing the setup.A previous installation required a reboot of the machine for changes to take effect. To proceed, restart your computer and then run SQL Server Setup again.0Default Installation Path Permission RequirementcTo run SQL Server Setup, log on to this computer with an account that has administrator privileges.bTo run SQL Server Setup, log on to this computer with an account that has administrator privleges.Internet Explorer RequirementMicrosoft Internet Explorer 6.0, Service Pack 1 is not installed, but is required by some SQL Server features. Without Internet Explorer, some SQL Server features will not be available for installation. To install all SQL Server features, install Microsoft Internet Explorer 6.0, Service Pack 1, and then run SQL Server Setup again. For a list of features that depend on Internet Explorer, see Features Supported by Editions of SQL Server in Books Online.Microsoft Internet Explorer 6.0, Service Pack 1 is not installed, but is required by some SQL Server features. Without Internet Explorer, some SQL Server features will not be available for installation. To install all SQL Server features, install Microsoft Internet Explorer 6.0, Service Pack 1, and then run SQL Server Setup again. For a list of features that depend on Internet Explorer, see Features Supported by Editions of SQL Server in SQL Server Books Online.MSXML RequirementUnable to co-create the DomDocument class. Make sure that Microsoft XML Core Services (MSXML) is running before continuing SQL Server Setup.The Microsoft XML Core Services (MSXML) XML Parser Document Object (DOMDocument) could not be created. To proceed, exit SQL Server Setup, restart your computer, and then run SQL Server Setup again.Higher version.CThe instance cannot be reinstalled because it is of higher version."Improper usage/invalid parameters.)Need Adminstrative rights to (un)install.4Installation of Windows Installer components failed.Cannot open MSI Database.Cannot read from MSI Database.Cannot get Temp directory.7Windows Installer is not installed properly on machine.Beta components detected.$Framework pair is already installed.Reboot is required.CreateMutex failed.-Another instance of setup is already running.Temp directory too long.Source directory too long.Cannot write to log.FThe Darwin service is hung and requires a reboot in order to continue.IAn internal error occurred while trying to initialize the Darwin Service.+A prerequisite for this product is missing.?The detected operating system is not supported by this product.]The product is already installed as an operating system component (.NET Framework SLD setup).HError processing the .ini file (syntax error or missing mandatory entry)HA fatal error occurred. The installation of Dotnetfx.exe cannot proceed.hNo nodes to operate on were specified by the user. Please run setup and specify the nodes to install on.)Setup finished with a reboot requirement. Microsoft Data Access ComponentsMicrosoft Data Access Components 9.0 is already installed. Uninstall Microsoft Data Access Components from Add/Remove programs.m Setup succeeded with the installation, inspect the log file completely for status on all the components. COM Plus Catalog Requirement7To install Microsoft SQL Server 2005, COM+ should work.If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.If SQL Server Setup fails, Setup will roll back the installation but may not remove all .manifest files. The workaround is to rename the files and then rerun Setup. For more information, see How to: Work Around COM+ Check Failure in SQL Server Setup.Microsoft SQL Native ClientqMicrosoft SQL Native Client is already installed. Uninstall Microsoft SQL Native Client from Add/Remove programs.SQL Server setup is complete.P The following computer(s) must be rebooted to finalize configuration changes: Refer to the setup error logs for information describing any failure(s) that occurred during setup. Click Finish to exit the installation wizard.*Completing Microsoft SQL Server 2005 Setup=Setup has finished configuration of Microsoft SQL Server 2005LSQL Server setup is preparing to make the requested configuration changes...The drop location is missing file(s) that allow setup to determine how a multi instance product should be installed. Setup cannot continue, please repair the drop and try again.VersionLanguage PackageSetup finished Summary Log SQL Server Setup was interrupted. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt. SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt. Version Upgrades Not SupportedUpgrading the version of an installation is not yet supported. This rule is expected to fail and will be removed when implementation is done.SKU Upgrades Not SupportedUpgrading the SKU of an installation is not yet supported. This rule is expected to fail and will be removed when implementation is done.Virtualization Not SupportedYour upgrade is blocked because of cluster upgrade rules. Upgrades are not allowed from standalone to cluster installations or cluster to standalone installations. To proceed, click on back and change the option to install as failover cluster.SKU Supported for UpgradesNThe SKU of this be installation is in the set of those allowed to be upgraded.Maintenance Version CheckkThe version of the installation must match that of SQL Setup in order to perform any maintenance operation.(Version of this installation must be %s.Version check:Your upgrade is blocked because of version requirements. For more information about upgrade support, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.8The version of this installation must be >= %s and < %s.Maintenance SKU CheckbThe SKU of this installation must that of SQL Setup in order to perform any maintenance operation.Language CheckDThe Language of this installation is supported for setup operations.^Setup is English, this installation is English, or this installation is the same as Setup, %d. - Status - PASSED - Status - FAILED - Description: - Expected: Same Version CheckNThe version of the SQL Setup product must equal that of the installed product.Build version check: Your upgrade is blocked because the existing component is a later version than the version you are trying to upgrade to. To modify an existing SQL Server component, go to Add or Remove Programs in Control Panel, select the component you would like to modify, and then click Change/Remove.Service pack requirement check: Your upgrade is blocked because of service pack requirements. To proceed, apply the required service pack and then rerun SQL Server Setup. For more information about upgrade support, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.Same Language CheckOThe language of the SQL Setup product must equal that of the installed product.Different Language Check[The language of the SQL Setup product must be different from that of the installed product.Language check:Your upgrade is blocked because of cross-language compatibility rules. For more information about cross-language support, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.Different SKU CheckeThe SKUs of the installed and SQL Setup products must be different, as expected during a SKU upgrade.Loss of Features Warning:<Warning: If you continue, you may lose SQL Server features. The instance you are upgrading supports more features than the SQL Server edition you are upgrading to. For more information, see the Features Supported by the Editions of SQL Server 2005 topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.Edition check:Your upgrade is blocked because of edition upgrade rules. For more information about edition upgrades, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.0 Setup finished with a configuration requirementTo minimize the server surface area of SQL Server 2005, some features and services are disabled by default for new installations. To configure the surface area of SQL Server, use the Surface Area Configuration tool.Maintain InstallationUpgrade Installation VersionUpgrade Installation EditionUpgrade Installation LanguageUpgrade Warning NeededVirtualize Installation(ASP.Net Version Registration Requirement64-bit ASP.Net is Registered.k64-bit ASP.Net is Registered. Required 32-bit ASP.Net to install Microsoft Reporting Services 2005(32-bit).k64-bit ASP.Net is Registered. Required 32-bit ASP.Net to install Microsoft Reporting Services 2005(32-bit).k32-bit ASP.Net is Registered. Required 64-bit ASP.Net to install Microsoft Reporting Services 2005(64-bit).32-bit ASP.Net is Registered.k32-bit ASP.Net is Registered. Required 64-bit ASP.Net to install Microsoft Reporting Services 2005(64-bit).k32-bit ASP.Net is Registered. Required 64-bit ASP.Net to install Microsoft Reporting Services 2005(64-bit).Microsoft Reporting Services 2005(32-bit) version exist. Microsoft Reporting Services 2005(64-bit) Cannot be installed side by sideMicrosoft Reporting Services 2005(64-bit) version exist. Microsoft Reporting Services 2005(32-bit) Cannot be installed side by side,Report Server Platform bitness check failed.*ASP.Net Version Registration check failed.The log file path (%s) is invalid. * The path may contain invalid characters. * The file may exist but not be writable, the folder may not exist, the folder may be located on an unavailable volume or protected with a password, or the path may contain environment variables that are not set (e.g. %TEMP%). To proceed, make sure that the log file path is valid, writable, and available, and then run SQL Server Setup again.kThe SQL Server System Configuration Checker cannot be executed due to WMI configuration on the machine %s. kWMI Win32 classes are not working properly. Please make sure WMI is in working condition before continuing.kWMI Win32 classes are not working properly. Please make sure WMI is in working condition before continuing.kWMI Win32 classes are not working properly. Please make sure WMI is in working condition before continuing.pWMI stdRegProv classes are not working properly. Please make sure WMI is in working condition before continuing.uWMI directory /data classes not functioning properly. Please make sure WMI is in working condition before continuing.ZThe %s service is not enabled. Please make sure that service is enabled before continuing..The perfmon counter registry key is corrupted.uXML DomDocument object is not functioning properly. Please make sure MSXML is in working condition before continuing.@The specified install path is not a valid path for installation.kSQL identifier can contain letters, numbers, sign (@), dollar sign ($), number sign (#) and underscore (_).7The number of instances is already at the maximum (50).gThe value entered was incorrect. Enter the number of SQL Server licenses as a number greater than zero.;WMI Win32 Operating System Class functioning on the machine:WMI Win32 Computer System Class functioning on the machine;WMI Win32 Processor System Class functioning on the machine-WMI Registry Class functioning on the machinek64-bit ASP.Net is Registered. Required 32-bit ASP.Net to install Microsoft Reporting Services 2005(32-bit).,Version Upgrade Check for Clustered InstallsYour upgrade is blocked because of cluster upgrade version requirements. For more information about upgrade support, see the Version and Edition Upgrades topic in SQL Server 2005 Setup Help or SQL Server 2005 Books Online.)Check for SQL Server a repository of OlapYour upgrade is blocked because the SQL Server Database services instance that you have selected is a repository to Analysis Services. To proceed uninstall Analysis Services and install the SQL Server Database services.OLAP uses SQL ServerYour upgrade is blocked because the existing instance of SQL Server cannot be upgraded since Analysis services 8.0 exists that uses the SQL server as the repository. The Analysis services need to be upgraded to SQL Server 2005 before SQL Server can be upgraded.Warning: Setup found that the following components that already exist are at a different service pack level than the components being installed. Instance aware components: Common components:rAfter completing setup, you must download and apply the latest SQL Server 2005 service pack to all the components.Warning: Setup found that the following nodes of the failover cluster instance are at a different version than the newly added node.After completing setup, you must download and apply the latest SQL Server 2005 patch and bring all nodes to the same version and patch level.Warning: Setup found that some existing components of the instance are at a different service pack level than the components being installed. After completing setup, you must download and apply the latest SQL Server 2005 service pack to all the components.ASP.Net Account RequirementqSetup has detected that the Web service account information for ASP.NET is encrypted in the registry, which prevents Setup from installing Reporting Services in the default configuration. To install Reporting Services, you must choose the files-only installation option. This option requires you to run the Reporting Services Configuration tool after Setup is complete.qSetup has detected that the Web service account information for ASP.NET is encrypted in the registry, which prevents Setup from installing Reporting Services in the default configuration. To install Reporting Services, you must choose the files-only installation option. This option requires you to run the Reporting Services Configuration tool after Setup is complete.+Failed to find ASP.Net Account information.Please insert Disc 1.Please insert Disc 2.SQL Server Setup cannot proceed because the component you have selected has already been uninstalled. Refer to books online for getting SQL Server 2005 assistance.@SQL Server Setup has determined that the following property was not specified: 'GROUP'. The property specifies the cluster group that contains the SQL Server resources and the disk to which the shared data files are to be written. To proceed, refer to the template.ini and set the property to a valid cluster group name.You must use the control panel to modify an existing SQL Server 2005 installation. To proceed, go to Add or Remove Programs in Control Panel, select the SQL Server 2005 entry, and then click Change/Remove. To perform a new installation, run setup.exe from the installation media.Installing components... Minimum MDAC Version RequirementThe system does not have the required version of Microsoft Data Access Components (MDAC) for this SQL Server release. For details, see Hardware and Software Requirements for Installing SQL Server 2005 in Microsoft SQL Server Books Online.The system does not have the required version of Microsoft Data Access Components (MDAC) for this SQL Server release. For details, see Hardware and Software Requirements for Installing SQL Server 2005 in Microsoft SQL Server Books Online.SQL Server Setup cannot continue because an earlier version of Office Web Components is already installed on this computer. Uninstall Office Web Components, and then run SQL Server Setup again.IThe volume %s is currently not accessible. Please select another volume.bError getting file attributes for %s. Please make sure that the drive is formatted and accessible.GThe setup failed to get IID_IIMSAdminBase object. The error code is %s.@The setup failed to read IIsWebSite table. The error code is %s.?The setup failed to read IIsWebDir table. The error code is %s.FThe setup failed to read IIsWebVirtualDir table. The error code is %s.?The setup failed to read IIsFilter table. The error code is %s.@The setup failed to start IIS transaction. The error code is %s.JThe setup failed to schedule install of webs on IIS. The error code is %s.UThe setup failed to schedule install of web directories on IIS. The error code is %s.YThe setup failed to schedule install of virtual directories on IIS. The error code is %s.MThe setup failed to schedule install of filters on IIS. The error code is %s.LThe setup failed to schedule uninstall of webs on IIS. The error code is %s.WThe setup failed to schedule uninstall of web directories on IIS. The error code is %s.[The setup failed to schedule uninstall of virtual directories on IIS. The error code is %s.OThe setup failed to schedule uninstall of filters on IIS. The error code is %s.IThe setup failed to begin metabase transaction: %s. The error code is %s.@The setup failed to open metabase key: %s. The error code is %s.BThe setup failed to create metabase key: %s. The error code is %s.IThe setup failed to write data to metabase key: %s. The error code is %s.EThe setup failed to create web application: %s. The error code is %s.BThe setup failed to delete metabase key: %s. The error code is %s.@The setup failed to read IIsMimeMap table. The error code is %s.@The setup failed to read IIsAppPool table. The error code is %s.NThe setup failed to schedule install of AppPools on IIS. The error code is %s.PThe setup failed to schedule uninstall of AppPools on IIS. The error code is %s.AThe setup failed to read IIsProperty table. The error code is %s.PThe setup failed to schedule install of properties on IIS. The error code is %s.RThe setup failed to schedule uninstall of properties on IIS. The error code is %s.To continue, you must provide a strong sa password. To review strong password requirements, click Help on the Authentication Mode page.The sa password must meet SQL Server password policy requirements. For strong password guidelines, see Authentication Mode, in SQL Server Books Online.KThe logon account cannot be validated. Verify that the password is correct.The data location that you have specified has system databases that are attached to an already existing instance. To proceed, specify a different location.%A previous build of the instance was uninstalled with the option to save data. The data location that you have specified has system databases that were saved by such an operation. To attach the database to the installed instance, click OK. To specify a different data location click Cancel.The installation location that you have specified for SQL Server 2005 Tools has previously installed components. To proceed, specify a different location for SQL Server 2005 Tools.gSQL Server Setup has determined that the following account properties are not specified: '%s' . The properties specify the startup account for the services that are installed. To proceed, refer to the template.ini and set the properties to valid account names. If you are specifying a windows user account, you must also specify the password for the account.SQL Server Setup cannot continue because SQL Server 2005 Standard Edition supports no more than two nodes for a SQL Server failover cluster. To continue, make sure that you have specified a maximum of two nodes for your SQL Server failover cluster, and then click Next. Setup files have been altered. Setup failed to load the appropriate package ID. You cannot change the edition that SQL Server Setup will install. To proceed, contact Microsoft Product Support.The instance could not be created. An instance with the same name is already installed on one or more nodes of the cluster. To proceed SQL Server Setup, provide a unique instance name.nYou have chosen to re-install, and therefore overwrite the system databases. Are you sure you want to proceed?YSQL Server Setup cannot perform the upgrade because the component is not installed on the computer. To proceed, verify that the component to be upgraded is currently installed, and that the component to be upgraded is specified in the ADDLOCAL property. For more information, see Running Setup from the Command Prompt in SQL Server Books Online.Full text search installation requires the startup account and password of the upgraded SQL Server service. To proceed, use the SQLACCOUNT and SQLPASSWORD properties to specify the user account and password of the SQL Server service.The specified collation '%s' is not a valid collation for the installation. To proceed, provide a valid collation for the SQLCOLLATION or OLAPCOLLATION property, and then run SQL Server Setup again.This version of SQL Server requires Internet Explorer version 6.0 with SP1 or later. To proceed, install or upgrade to a required version of Internet Explorer, and then run SQL Server Setup again.IThe authentication mode specified is not valid for this operating system.\Passwords can contain from 1 to 128 characters, including any letters, symbols, and numbers.SQL Server Setup cannot write to removable media. To continue, specify a directory on a hard disk attached to the computer where SQL Server will be installed.{{ Installation path %s is not supported.}}The computer running SQL Server Setup does not meet minimum system requirements for this SQL Server release.%s is not supported on this operating system. For details, see Hardware and Software Requirements in the readme or in SQL Server Books Online.Maintainance of a SQL Server clustered instance is provided by the SQL Server Installation Wizard. To make changes to your SQL Server cluster, run SQL Server Setup.exe.An application is currently using a file required by SQL Server Setup. Reboot your computer, and then run SQL Server Setup again.The SQL Server product key is not valid. To proceed, re-enter the product key values from the SQL Server installation CD sleeve.The specified Report Manager virtual directory can't be used for installation. It is already in use by another application. To proceed, enter a unique value for the virtual directory.wThe specified Report Manager virtual directory name is not valid. To proceed, remove special characters from the name.The specified Report Manager virtual directory can't be used for installation. It is already in use by another application. To proceed, enter a unique value for the virtual directory.The specified Report Manager virtual directory can't be used for installation. It is already in use by another application. To proceed, enter a unique value for the Report Manager virtual directory.Virtual directory names for the Report Server and the Report Manager cannot be the same. To proceed, enter unique names for each virtual directory.SQL Server Setup must be able to connect to and modify the Internet Information Services (IIS) administrative service, but cannot connect to IIS. To proceed, verify that IIS is installed and that the IIS administrative service is running, and then run SQL Server Setup again.The instance name provided is already in use for this SQL Server installation. To proceed, provide a unique name for this SQL Server instance. For instance naming rules, see Instance Name, in SQL Server Books Online.dSQL Server cannot be installed by running the MSI. To install SQL Server, run SQL Server Setup.exe.Reporting Services must connect to a SQL Server instance. To proceed, select a SQL Server instance to use as the host for your report server database.The Report Server database can be attached to instance %s, which is currently being installed, or to an existing SQL Server instance, but not both. To proceed, specify a single SQL Server instance as the Report Server data repository.The Username field, required for Report Server database Setup, is blank. To proceed, provide a SQL Server login for the RSSETUPACCOUNT property, and then run SQL Server Setup again.Cannot connect to the SQL server instance %s. Reporting Services must be able to connect to a SQL Server instance, but cannot do so at this time. Verify that you provided Setup with the correct SQL Server instance name, and make sure that the SQL Server service is running. For more information, see How to: Verify a Successful Installation of SQL Server 2005 Services in SQL Server Books Online.The current account does not have sysadmin rights for the SQL Server 2000 instance that hosts the Report Server database. To proceed, log on with an account that has administrator privileges for the existing SQL Server 2000 instance, and then run SQL Server Setup again.The SQL Server database identified by the RSATTACHDATABASE property does not exist. Report Server uses a SQL database as a repository. If, during an unattended installation, the user specifies an existing SQL database for the Report Server repository, the SQL Server database must already exist within the SQL Server instance. The repository database must also be the same version as the Report Server version. To proceed, make sure that a repository database exists within the SQL Server instance, and then run SQL Server Setup again.wA SQL Server instance was not specified. Select a SQL Server instance to use as the data source for your report server.The Report Server database name exceeds the maximum length. To proceed, provide a Report Server database name that is 16 characters or less in length. For a complete list of instance naming rules, see Instance Name, in SQL Server Books Online.The Report Server database name must meet all SQL Server identifier requirements, and cannot be a reserved keyword. For details, see Instance Name, in SQL Server Books Online.The Report Server database name must meet all SQL Server identifier requirements, and cannot be a reserved keyword. For details, see Instance Name, in SQL Server Books Online.Data files were detected in the %s directory for the specified Report Server database. Setup cannot reuse the data files. To proceed, clean up the directory by moving the files, and then run SQL Server Setup again.The Username field, required for Report Server database Setup, is blank. To proceed, provide a SQL Server login for the Report Server database.The Report Server database account cannot be validated because the logon information is incorrect. To proceed, verify the user name and password.VThe Report Server Database account doesn't have permission to access the SQL instance.XThe Report Server Database account doesn't have assigned any SQL login for the instance.The SQL Server database identified by the RSATTACHDATABASE property does not exist. Report Server uses a SQL database as a repository. If, during an unattended installation, the user specifies an existing SQL database for the Report Server repository, the SQL Server database must already exist within the SQL Server instance. The repository database must also be the same version as the Report Server version. To proceed, make sure that a repository database exists within the SQL Server instance, and then run SQL Server Setup again.The name of the Report Server database is not valid and cannot be used for this installation. To proceed, rename the Report Server database. For more information, see Instance Name, in SQL Server Books Online.SQL Server Setup was not able to connect to the local or remote computer. For Reporting Services to use a SQL Server database on a remote computer, SQL Server Setup must validate the Report Server Database files. To proceed, verify that the user currently running Setup has administrator privileges on the local and remote computers. If you are using SQL Server Authentication, provide a username and password that can connect to the SQL Server instance on the remote computer.The SQL Server database identified by the RSATTACHDATABASE property does not exist. Report Server uses a SQL database as a repository. If, during an unattended installation, the user specifies an existing SQL database for the Report Server repository, the SQL Server database must already exist within the SQL Server instance. The repository database must also be the same version as the Report Server version. To proceed, make sure that a repository database exists within the SQL Server instance, and then run SQL Server Setup again.Setup cannot install Reporting Services in the default configuration because report server database files already exist for this instance name. To proceed, drop or rename the current report server database and click Retry. You can also choose a different installation option.NReporting Services must be able to connect to a SQL Server instance, but cannot do so at this time. The Reporting Services login credentials you provided do not match the login credentials of the specified SQL Server instance. To proceed, verify that the Reporting Services login credentials are valid for this instance of SQL Server.The Report Server Database name is longer than the 16-character maximum. To proceed, provide a Report Server database name that is no longer than 16 characters. For a complete list of instance naming rules, see Instance Name, in SQL Server Books Online.Reporting Services failed to connect to SQL Server. The Reporting Services login credentials contain invalid characters. Verify the login credentials and re-enter them.The Report Server database username cannot be a SQL Server reserved keyword. For strong password guidelines and a list of reserved keywords, see Authentication Mode, in SQL Server Books Online.kThe Report Server database security mode does not match the mode used by SQL Server. They must be the same.|The sa passwords entered for SQL Server Authentication do not match. To proceed, type the same sa password in each text box.The service account provided for Report Server does not have permission to access the network and therefore cannot be used to access a Report Server database hosted on the remote computer %s. You have the following options: you can continue SQL Server Setup and then use Configuration Manager to set the database credentials for Report Sever to access the remote computer, you can go back to the service accounts page in SQL Server Setup to provide a different service account, or you can choose a local instance of SQL Server to host the report server database %s. Do you want to continue SQL Server Setup and set the database credentials later?There is not enough space on the destination disk for the current SQL Server installation. To proceed, free up disk space to make room for the selected features, select fewer features for this installation, or install the selected features to a different drive.8The required version of .NET Framework is not installed.The Report Server database password must meet SQL Server password policy requirements. For strong password guidelines, see Authentication Mode, in SQL Server Books Online.The sa passwords entered for the Report Server database do not match the SQL Server sa password. To proceed, type the SQL Server sa password in each Report Server database password field.SQL Server Setup is running under an account that does not have write permissions for the path %s. To proceed, grant the current user account write access to the directory, or login with an administrator account, then run SQL Server Setup again.SQL Server Setup cannot install files to the compressed or encrypted folder: %s. To continue, make sure that your installation directories are not compressed or encrypted, or specify a different directory, and then run SQL Server Setup again.SQL Server Setup has determined that the UPGRADE property is set to an unknown value. The UPGRADE property specifies which component to upgrade. To proceed, refer to the template.ini and set the UPGRADE property to a valid component name.SQL Server Setup cannot upgrade one or more components because they have an Internet Information Services (IIS) dependency, and IIS is not installed. To continue, install IIS and then run SQL Server Setup again. For more information on installing IIS, see the SQL Server Books Online topic, How to: Install Microsoft Internet Information Services.{{ SQL Server Setup cannot perform the upgrade on %s because %s depends on Internet Information Services (IIS).}}Upgrades are not supported yet.SQL Server Setup cannot upgrade the instance because the upgrade scenario is not supported. For more information, see Version and Edition Upgrades, in SQL Server Books Online.SQL Server Setup cannot upgrade the instance because the upgrade scenario is not supported. For more information, see Version and Edition Upgrades, in SQL Server Books Online.SQL Server Setup cannot upgrade the instance because the upgrade scenario is not supported. For more information, see Version and Edition Upgrades,c in SQL Server Books OnlineNo features were selected for installation. Setup cannot proceed since no effective change is being made to the machine. To continue, select features to install.RReport Server virtual directory name specified exceeds the maximum length allowed.SReport Manager virtual directory name specified exceeds the maximum length allowed.<A positive numeric value for number of licenses is required.#You must select collation settings.IVerify that the SQL Server username and password you entered are correct.pSQL Server Setup could not validate the service accounts. Either the service accounts have not been provided for all of the services being installed, or the specified username or password is incorrect. For each service, specify a valid username, password, and domain, or specify a built-in system account.{{ The logon account cannot be validated for the service %s.}}SQL Server 2005 Setup requires administrator permissions on every cluster node. To continue, update permissions for the account currently running Setup, or log in with an account that has administrator permissions on every cluster node, and then run SQL Server Setup again.The Virtual Server name you provided is not valid. To proceed, provide a virtual server name. For more information, see Instance Name, in SQL Server Books Online.,Select a SQL Server service to be clustered.pThe specified Virtual Server name already exists on the network. To proceed, enter a unique Virtual Server name.mThe IP address does not match the subnet mask. To proceed, enter the IP address that matches the subnet mask.!The IP Address is already in use.The IP Address is invalid.Unable to proceed with Setup, the current account needs to be a domain account with administrative privileges on all nodes of the cluster. To continue, log on using a domain account with administrator credentials, and then run SQL Server Setup again. When upgrading a SQL Server instance configured to use SQL Server Authentication, SQL Server Setup requires a SQL Server login account. To continue, provide a SQL Server login account and password that SQL Server Setup can use to connect to the instance to upgrade.SQL Server Setup supports cluster maintenance to add or remove nodes from a virtual server, but you cannot do both during the same setup process. To proceed, either add nodes or remove nodes, and then run SQL Server Setup again to run additional maintenance tasks.An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name.The instance name specified is not valid. To proceed, provide an instance name that complies with instance naming guidelines. For more information, see Instance Name, in SQL Server Books Online.The drive specified cannot be used for shared data location. Data files must be installed on a valid cluster disk resource of the cluster. The valid values are %sThe drive specified cannot be used for program location. Program files must be installed on a valid local disk available on all cluster nodes. The valid values are %sThese is not enough disk space on the destination disk for the current SQL Server data files. To proceed, free up disk space to make room for data files, or install the data files to a different drive.,The path '%s' contains an invalid character.SQL Server Setup requires administrator permissions for the upgraded SQL Server instance. To continue, log in with an administrator account.&Transaction canceled by primary setup.There is already an existing Report Server database %s. You must either remove the existing database or select a new database name.A Report Server temporary database with this name already exists %s. You can either reuse the existing temporary database or change the name of the Report Server database that you specified during Setup. Do you want to reuse the temporary database and delete its contents?Setup has detected that some components will be installed in an encrypted folder. Installing components into an encrypted folder is not supported. Refer to the product documentation for more information. SQL Server Setup requires administrator permissions in order to install sample databases. To continue, add administrator permissions to the login account, or log in with an administrator account. Then run SQL Server Setup again.{{ Error: %s.}}cThe setup doesn't have sysadmin or dbcreator rights for the SQL server to install Sample Databases.Sample databases are higher version than SQL server instance specified. Sample databases cannot be attached to older SQL instance.>Sample database '%s' already exists in SQL instance specified.MSetup cannot access data directory to install Sample databases. Directory: %sSQL Server Setup cannot write sample databases to the folder you specified because it contains databases from a previous installation. To continue, move the databases, or specify a different folder for installation. Then run SQL Server Setup again.{{ File: %s.}}Setup failed to install Samples databases because specified SQL Server instance is not a local instance. Specified instance: %sIn order to activate the node(s) added to the Virtual Server definition, Service Pack will have to be applied after Setup is completed.SQLExpress is not a valid instance name for this SKU of SQL Server. This instance name is reserved for use by SQL Server Express only.&Using a non-admin account for XP SP1. Please use an admin account when installing on XP SP1 Systems. Setup cannot proceed with non-admin accounts on XP SP1 systems. Refer to the product documentation for more information.None of the selected features can be installed or upgraded. Setup cannot proceed since no effective change is being made to the machine. To continue, click Back and then select features to install. To exit SQL Server Setup, click Cancel.zThe specified instance of SQL Server does not meet the minimum database compatibility level requirement to host Reporting Services databases. Reporting Services installation requires that the compatibility level of the master database in the SQL Server instance must be 80 or higher. Refer to product documentation for more information on handling database compatibility levels.aSQL Server setup could not connect to the database to validate upgrade options. The error was: %sSQL Server Setup cannot write system databases to %s, because it contains files from a previous installation. To continue, move the databases from the specified folder, or specify a different installation folder. Then run SQL Server Setup again.Setup failed because Service %s is disabled for the current hardware profile. Services must be set with the current Hardware Profile logon property profile enabled. For more information on how to enable the hardware profile logon property refer to the product documentation.JInvalid DISABLENETWORKPROTOCOLS option. Valid values are only 0 or 1 or 2.SQL Server Setup requires access to the service %s, currently in use by another application. To continue, close the application or restart Windows to free the locked process, and then run SQL Server Setup again..UpgradeAdvisor blocked Upgrade. Message: %shMICROSOFT##SSEE is not a valid instance name for this SKU of SQL Server. This instance name is reserved.The Report Server virtual directory (%s) can't be used for installation. It is already in use by another application. Setup is defaulted to Files Only install.The Report Manger virtual directory (%s) can't be used for installation. It is already in use by another application. Setup is defaulted to Files Only installService accounts have not been provided for all the services being installed. To proceed, select each service and specify a domain user account and password or choose a built in system account and then click Next.AThe instance of Report Server cannot be upgraded because either the report Server or the report manager virtual directory is not configured. To proceed, use the Report Server Configuration Manager, configure the report server virtual directory and report manager virtual directory and then run the SQL Server Setup again.A component that you have specified in the ADD_LOCAL property is already installed. To upgrade the existing component, refer to the template.ini and set the UPGRADE property to the name of the component.An instance with the same name is already installed on this computer. To proceed with SQL Server Setup, provide a unique instance name. To upgrade the existing instance, refer to the template.ini and set the UPGRADE property to the name of the component.Warning: SQL Server Setup cannot install this feature because a different edition of this feature is already installed. For more information, see 'Version and Edition Upgrades' in SQL Server Books Online.Failover cluster installation requires the service accounts of clustered services to be domain user accounts. To proceed, specify a valid domain user account as the log on account for the clustered services.7Warning: Setup found that component(s) on existing node(s) of the failover cluster instance will be at a different version than the newly added node. After completing setup, you must download and apply the latest SQL Server 2005 service pack and/or patch and bring all nodes to the same version and patch level.SQL Server Setup failed to obtain system account information for the ASPNET account. To proceed, reinstall the .NET Framework, and then run SQL Server Setup again.SQL Server Setup could not validate the service accounts. Either SQL Server 2005 cannot run the service account as a Local Service account or Network Service account on a domain controller or this edition of SQL Server 2005 cannot run the service account as a Local Service account or Network Service. For more information, see Setting Up Window Service Accounts in SQL Server Books Online.{ The logon account cannot be validated for the service %s.}SQL Server Setup cannot upgrade service %s. SQL Server 2005 cannot run a service account as a Local Service account or Network Service account on a domain controller.SQL Server installation in a failover cluster requires the startup account of the clustered services to be a member of the built-in Administrators group on all nodes. The accounts you have specified are not a member of the built-in Administrators group. To proceed, specify a domain account that is already a member of the administrators group or add the specified account to the administrators group.*A domain group is missing for one or more services. To install SQL Server 2005 as a failover cluster, domain groups must be specified for all the clustered services being installed .To proceed, enter the missing domain group information. { The domain group cannot be validated for the service %s.}hOne or more domain groups could not be verified. Check the domain and group name for each clustered service, and specify it in the format: DomainName\GroupName. If necessary, ask your domain administrator for the names of existing domain groups, or to create domain groups for your failover cluster. { The domain group cannot be validated for the service %s.}/You do not have privileges to add accounts to the domain groups specified for this failover cluster. Ask your domain administrator for privileges to add new accounts to the domain groups, or log on using an account that does have permission. { The domain group cannot be validated for the service %s.}DInstallation of the Microsoft Data Access Components package failed.-Unable to determine system default collation.;Failed to delimit property. Could not read database values.The SQL Server service failed to start. For more information, see the SQL Server Books Online topics, How to: View SQL Server 2005 Setup Log Files and Starting SQL Server Manually.{{ The error is (%s) %s.}}SQL Server Setup failed to parse the SQL script %s. The error code is {{(%s) }}%s. To continue, correct the problem, and then run SQL Server Setup again.3Failure setting security rights on user account %s.SQL Server Setup failed to modify security permissions on file %s for user %s. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that %s exists on the destination drive.+SQL Server Setup failed to modify security permissions on registry key %s for user %s. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that the registry key %s exists on the destination drive.,NetShareAdd failed to create a new share %s. Failure creating local group %s.:SQL Server Setup was unable add user %s to local group %s.SQL Server Setup Failed to compile the Managed Object Format (MOF) file %s. To proceed, see Troubleshooting an Installation of SQL Server 2005 or How to: View SQL Server 2005 Setup Log Files in SQL Server 2005 Setup Help documentation.&Failure setting configuration file %s. SQL Server Setup could not connect to the database service for server configuration.{ The error was: %s} Refer to server error logs and setup logs for more information. For details on how to view setup logs, see How to View Setup Log Files in SQL Server Books Online.!SQL Server Setup failed to modify security permissions on WMI namespace %s. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that the WMI namespace %s exists on the destination drive.ISQL Server Setup failed to execute a command for server configuration. %sSQL Server Setup was not able to connect to the remote computer. For Reporting Services to use a SQL Server database on a remote computer, SQL Server Setup must validate the remote computer's operating system version. To proceed, verify that the user currently running Setup has administrator privileges on the local and remote computers. If you are using SQL Server Authentication, provide a username and password that can connect to the SQL Server instance on the remote computer.SQL Server Setup failed to obtain system account information for the Report Server Database account. A file is missing or corrupt. To proceed, reinstall the .NET Framework, and then run SQL Server Setup again.SQL Server Setup failed to execute a command for server configuration. The error was %s. Refer to the server error logs and Setup logs for detailed error information.1Cannot connect to the SQL server instance %s.%s%szSQL Server Setup cannot upgrade the instance because the uninstall file is missing or corrupted. The error code is (%s) %sAThe setup help file could not be loaded or help is not available.tThe setup has encountered an unexpected error. The error code is %s. Custom action %s not found in _sqlAction table.vSQL Server Setup requires write permissions to the resource database so that it can be overwritten. The %s file does not exist, or the account running SQL Server Setup does not have administrator permissions to overwrite the resource database. To continue, verify that the file exists, and run SQL Server Setup from an administrator account.{{ The error code is (%s) %s.}}^The setup has encountered an unexpected error in datastore. The action is %s. The error is :%sHThe setup has encountered an unexpected error while %s. The error is: %skCan't set the default settings for Client SuperSocketNetLib registry key. The returned error code is %s%s%sdFailed to set registry settings for server network libraries. The action is %s. The error is %s (%s)WThe setup has encountered an unexpected error while %s. The error type %s. The error %stUnable to establish connection to SQL Server %s. Verify the the server exists and the connection can be established.Service '%s' could not be stopped. Verify that you have sufficient privileges to stop system services. The error code is (%s) %sService '%s' could not be started. Verify that you have sufficient privileges to start system services. The error code is (%s) %spCan't disable the network protocols for server SuperSocketNetLib registry key. The returned error code is %s%s%sSQL Server Setup has encountered the following problem: {{ Failed to execute the Transact-SQL statement: %s Script file: %s The error was: }}%s. To continue, correct the problem, and then run SQL Server Setup again.SQL Server Setup has encountered the following problem: {{ Failed to execute the Transact-SQL statement: %s Script file: %s The error was: }}%s. To continue, correct the problem, and then run SQL Server Setup again.@SQL Server Setup did not have the administrator permissions required to rename a file: %s. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.{{ The error code is (%s) %s.}}<Some of the dependencies for this package have not been met.|Failed to register instance under HKLM\Software\Microsoft\Microsoft SQL Server\Instance Names\SQL. The error code is (%s) %s Invalid secure connection level.'Invalid report service property length.Your upgrade is blocked. For more information about upgrade support, see the Version and Edition Upgrades and Hardware and Software Requirements topics in SQL Server 2005 Setup Help or SQL Server 2005 Books Online. %sdError exporting data from SQL Server 2000 Analysis Services server.{ Error: %s}{ Error message: %s}bError importing data to SQL Server 2005 Analysis Services server.{ Error: %s}{ Error message: %s}>SQL Server Setup did not have the administrator permissions required to copy a file: %s. To continue, verify that the file exists, and either grant administrator permissions to the account currently running Setup or log in with an administrator account. Then run SQL Server Setup again.{{ The error code is (%s) %s.}}JUpgrade Failed due to the following Error.The error code is :%s.Message:%sBSetup failed to retrieve Analysis Services Service( %s ) Argument.zFailed to install and configure assemblies %s in the COM+ catalog. Error: %s{ Error message: %s}{ Error description: %s}hThe setup has encountered an error while %s. The error: %s{ Error message: %s}{ Error description: %s}>Failed to launch UpgradeAdvisor. Error: %s . Error message:%s/UpgradeAdvisor returned %s . Error message:%s6Unable to find UgradeAdvisor in the Install MediaPath.+Perfmon Counter(%s) not Replaced in file %s%Unable to create the application pool/Unable to set the report manager's web identity.Unable to set the report server's web identity3Unable to configure the share point exclusion path.SQL Server Setup failed to modify security permissions on service %s for user %s. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that %s exists on the destination drive.qSetup has detected that the Web service account information for ASP.NET is encrypted in the registry, which prevents Setup from installing Reporting Services in the default configuration. To install Reporting Services, you must choose the files-only installation option. This option requires you to run the Reporting Services Configuration tool after Setup is complete.=SQL Server Setup failed to retrieve the SSL Certificate Name.0 *H 01 0 +0h +7Z0X03 +70% <<<Obsolete>>>0!0 +U1B/d fK 00-GߍRFCmH 10  *H 01 0 UZA10U Western Cape10U Durbanville10 U Thawte10U Thawte Certification10UThawte Timestamping CA0 031204000000Z 131203235959Z0S1 0 UUS10U VeriSign, Inc.1+0)U"VeriSign Time Stamping Services CA0"0  *H 0 ʲ }uNgadڻ30X~k6xw~o< hlʽR-H=]_/kLR`@~ ?Ǵ߇_zj1.G 1s W-x43h/Š*Ë!fXWou<&]'x1"ijGC_^|}bM "Vͮv M٠h;004+(0&0$+0http://ocsp.verisign.com0U00AU:0806420http://crl.verisign.com/ThawteTimestampingCA.crl0U% 0 +0U0$U0010U TSA2048-1-530  *H JkXD1y+LͰXn)^ʓR G'/8ɓN"b?7!Op18UN$ҩ'NzaA*^ݻ+>W~ +;R8'?J00 +)2 ^v0  *H 0S1 0 UUS10U VeriSign, Inc.1+0)U"VeriSign Time Stamping Services CA0 031204000000Z 081203235959Z0W1 0 UUS10U VeriSign, Inc.1/0-U&VeriSign Time Stamping Services Signer0"0  *H 0 P(HhzDfu]~ĸc&=C|8%Usu'iN \ *UV!a3kݣ7e S\|f5_EvNS \0"7LB U?R,z򢪍5]j=k㿖`@DQn*(P{J 0kX@( ~|vqiOG05!b<+َ*{\{❥o<00<<>c@0  *H 0p1+0)U "Copyright (c) 1997 Microsoft Corp.10U Microsoft Corporation1!0UMicrosoft Root Authority0 970110070000Z 201231070000Z0p1+0)U "Copyright (c) 1997 Microsoft Corp.10U Microsoft Corporation1!0UMicrosoft Root Authority0"0  *H 0 p;N(x^0ꢩ%_L >|Q`2kBdyvT뜆fkzb#<Ŀ-fh&:, X&F >8,(9IBlUa|`-wL陴d;P1$+=c`Xe7RӿUE:TNzmtN̖ (!W`i7Kc@0  *H  5$w\`2 >:!W,Gb;;Z6Ti$m?̪|1=pjOiCZ Ob{+7%-e%cT!RnC2gl QRǽ0 1 )M[WeIRT(~ū7,zwvj?6A5jj5EZ38nM b T?FUp:uҠ00j O "}ly~0  *H 0p1+0)U "Copyright (c) 1997 Microsoft Corp.10U Microsoft Corporation1!0UMicrosoft Root Authority0 020523080000Z 110925080000Z01 0 UUS10U Washington10URedmond10U Microsoft Corporation1+0)U "Copyright (c) 2000 Microsoft Corp.1#0!UMicrosoft Code Signing PCA0 0  *H  0 >Pz$%v!*VNʜ5y-ĨcɷֱRƽŨkSPdԂh@xD8NcQ=7c#;q@4GkF's"BQRӣ?qm!D_Bəd 4D{/ߛ!X1AU8~XYy%*/?8x>Bh~"hJxDRGOg{ }q<+f-+4He<&Ro*0&0U% 0 +0U0[pir#Q~Mˡr0p1+0)U "Copyright (c) 1997 Microsoft Corp.10U Microsoft Corporation1!0UMicrosoft Root Authority<<>c@0 +70U%+K]rT*S0 +7  SubCA0 UF0U00  *H dJti'ZS'сsκꓗ܏:.tt;@Q_<2OY(rq/5B/b11BO8pA8` < +VKJ"oD+pN,:q2X5Rۑ@o)Bp}loۜ^,_³{;St*g'u@ Fr6mkfS5jrE]f,a Yf ;|00ɠ aXZ0  *H 01 0 UUS10U Washington10URedmond10U Microsoft Corporation1+0)U "Copyright (c) 2000 Microsoft Corp.1#0!UMicrosoft Code Signing PCA0 050105232019Z 060405233019Z0t1 0 UUS10U Washington10URedmond10U Microsoft Corporation10UMicrosoft Corporation0"0  *H 0 8'^̪:;b1FFӳŸLg(C;uyj3azy]hpw/u/JA||ˇCt@WXՒ$qIU|e8#>)lƞp[}7gw ΅N45S2W(l@ I67I*k̎ֆFzJESx/.5kL$iin>LAb]~\L'1kVLq=*qM@0<0U0U4wh424c10U% 0 +0U#0%+K]rT*Str0p1+0)U "Copyright (c) 1997 Microsoft Corp.10U Microsoft Corporation1!0UMicrosoft Root Authorityj O "}ly~0JUC0A0?=;9http://crl.microsoft.com/pki/crl/products/CodeSignPCA.crl0  *H   &t<J'GrQKBQ#;e-LP8W^:sO3-%;YЮ R dwwu6 l3`/m)۵k"@+2Pƶ6w)T>~qYʄ/D"!H cro,+:YJ!埩bPuv_ؠ~W҉}C10001 0 UUS10U Washington10URedmond10U Microsoft Corporation1+0)U "Copyright (c) 2000 Microsoft Corp.1#0!UMicrosoft Code Signing PCA aXZ0 +0 *H  1  +70 +7 10  +70# *H  1uO9Ɩj7߼҄>-0X +7 1J0H*(Microsoft SQL Serverhttp://www.microsoft.com0  *H M5dS9DVPŔ[ThtF7C_Mޔ znp=4s)t_ Ăٰ,[9 |>&R%oק? U'koʍɿmX2Ӧtسk.ar2s|@@ERa}Ǥ8 A8bevPq@?rHƿSƌzZBT2L˰R 'vz+*K S=o)<40 *H  100g0S1 0 UUS10U VeriSign, Inc.1+0)U"VeriSign Time Stamping Services CA +)2 ^v0 *H Y0 *H  1  *H 0 *H  1 051014104849Z0 *H  1_T38yҥ0  *H B=혌4"JawdJL$^{4wUߎ+/^9n4٣#Dv\g kC:Q7D'v~s]>-ov ]3ES~ޔ&y"hX(pѸ>.>{B*a_FL_Mr4"`XMQBNG6szA=QƄOX/ȩ^NsXgoӾUG׬%ڑR8!