SQL Server 2005 SP1 Client Components Failure
When attempting to install SQL Server 2005 SP1, I receive the error, "a recently applied update, KB913090, failed to install." The Installation complete dialog shows the Client Components product Status as "Failure" with the description detail, "Unable to install Windows Installer MSP file". My Operating System is Windows Server 2003 SP1.
Please advise as to risks and fix.
Thanks,
Rob
View Complete Forum Thread with Replies
Related Forum Messages:
SQL Server 2005 Installation Woes For Workstation Components And Client Tools
Hello, I have installed successfully Microsoft SQL server 2005 in MSCS. However the set up did not install Workstation components (client tools - SSMS etc). I have successfully installed workstation components in one node of cluster. However setup is giving following error while installing workstation components on other node. (From this node MS SQL server 2005 was installed). Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. I did "C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, /setup". It executed but no error, no output. Any gues, help in isolating issue? Any more information required.(Media is ok. Setup has been tried after reboot. There is enough disk space.) Regards. Mahesh =========== Setup 1) Microsoft Cluster of two nodes. 2) Hardare - HP Blade servers 3) OS - Windows 2003 EE with SP2 4) SQL Server 2005 Standard Edition with SP2. ============================= MSI (s) (B0:7C) [17:40:20:390]: Note: 1: 1722 2: SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A 3: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe 4: /setup MSI (s) (B0:7C) [17:47:23:609]: Product: Microsoft SQL Server 2005 Tools -- Error 1722. There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor. Action SqlWbSetup.5F46584E_060D_4BCB_ADEE_BD15A7BFCC2A, location: C:Program FilesMicrosoft SQL Server90ToolsBinnVSShellCommon7IDESqlWb.exe, command: /setup MSI (s) (B0:7C) [17:47:35:921]: Note: 1: 1729 MSI (s) (B0:7C) [17:47:35:921]: Product: Microsoft SQL Server 2005 Tools -- Configuration failed. MSI (s) (B0:7C) [17:47:35:953]: Cleaning up uninstalled install packages, if any exist MSI (s) (B0:7C) [17:47:35:953]: MainEngineThread is returning 1603 MSI (s) (B0:A0) [17:47:36:062]: Destroying RemoteAPI object. MSI (s) (B0:80) [17:47:36:062]: Custom Action Manager thread ending.
View Replies !
Unable To Install Native Client Components In SQL Server 2005 Enterprise Evaluation Version
Hi all, I have downloaded Microsoft SQL Server 2005 Enterprise Evaluation Edition ISO from the following site and burned it onto a DVD. http://www.microsoft.com/downloads/details.aspx?FamilyId=6931FA7F-C094-49A2-A050-2D07993566EC&displaylang=en Prior to this I have installed Visual Studio 2005 Professional Edtion. During setup I have selected all the native client components i.e. Management Studio, Business Intelligense Studio. But after the install I am not able to see them under All Programs-> Microsoft SQL Server 2005. On further searching I have come across this link http://channel9.msdn.com/ShowPost.aspx?PostID=142941 First of all, there is no sqlrun_tools.msi under setup folder of the dvd. And also when I tried to change component from Add/Remove programs and following the instructions as specified on clicking Change Installed components all that I see are: Connectivity Components and Software Development kit. Could someone tell me how can I install Management Studio/ Business Intelligence Studio seperately? I don't want to go through the process of re-installation.
View Replies !
SQLServer 2005 Service Pack 2 &&"Client Components&&" Is Failing To Install
I have Windows XP Professional Version 2002 Service Pack2. I Have: Microsoft SQL Server Management Studio 9.00.2047.00 Microsoft Analysis Services Client Tools 2005.090.2047.00 Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158) Microsoft MSXML 2.6 3.0 5.0 6.0 Microsoft Internet Explorer 7.0.5730.11 Microsoft .NET Framework 2.0.50727.42 Operating System 5.1.2600 Service Pack is failing to Install CLIENT COMPONENTS; message is: Product : Client Components Product Version (Previous): 2047 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQLTools9_Hotfix_KB921896_sqlrun_tools.msp.log Error Number : 29549 Error Description : MSP Error: 29549 Failed to install and configure assemblies c:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.sqlserver.notificationservices.dll in the COM+ catalog. Error: -2147024894 Error message: The system cannot find the file specified. Error description: Could not load file or assembly 'System.EnterpriseServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified. This situation, I am guessing, also preventing me to run import/export from the SQLServer Client. Any help is appreciated. Thanks.
View Replies !
Warning Messages && Failure Installing MSSQL 2005 Enterprise Client Tools
I am trying to install the client tools for management purposes only on a IBM T42 laptop which meets all the hardware and software requirements listed on MS support including the HCL list, the Readme, the forums and MSDN but the install still shows the following log messages when the install fails. AdminMessage = Setup requires user to be in the administrator group in order to continue the installation process. Setup is aborting as the current user is not in the administrator group. (I am an adminsistrator on this machine) Property(S): SupportedOSMessage = Installation of this product failed because it is not supported on this operating system. For information on supported configurations, see the product documentation. Property(S): SupportedProcTypeMessage = This Microsoft SQL Server Native Client package is not supported on the current processor type. Any help would be appreciated.
View Replies !
Sql Client Components
I have a question about client components. I read someplace where if sql client components are preinstalled (if you delete sql express-client components cannot install, even if they are preinstalled I have sql express default installation from vs 2008 pro I have not installed sql express (client components, database components I wish to install cd standard edition on my computer for reporting services Also wanted to add enterprise server so I need report manager office 2007 installed by myself. I came across this article kb909967. Is there anyway to check make sure I can install client components installs on standard edition I also read kb 964164 installing sql on vs 2008 vista ultimate Thanks
View Replies !
Cannot Install Client Components On X64 System
I'm building a new server and am having a problem witht he SQL install. It's a Dell 2905 running Windows 2003 SP1 x64 and SQL 2005 x64. I'm able to install everything except for the Client Components, and even upgrade to SQL SP2. I keep getting the following error: "There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information" TITLE: Microsoft SQL Server 2005 Setup ------------------------------ There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information. For help, click: http://go.microsoft.com/fwlink?LinkID=20476&ProdName=Microsoft+SQL+Server&ProdVer=9.00.1399.06&EvtSrc=setup.rll&EvtID=50000&EvtType=packageengine%5cinstallpackageaction.cpp%40InstallToolsAction.10%40sqls%3a%3aInstallPackageAction%3a%3aperform%400x643 ------------------------------ BUTTONS: OK ------------------------------ The problem is that I can't find any solutions to this so far. Anyone recognize or have any insight into this?
View Replies !
Unattended Install Of Client Components
I'm trying to do an unattended install of the client components for SLQ2005. I have read the document on doing a install from the command prompt but when I use the "ADDLOCAL" switches I get some components that I don't require. For example, I am using the following command to run the setup - "start /wait <path>setup.exe ADDLOCAL=Client_Components,SQL_Tools90,Connectivity". When I look at the Add/Remove Programs list I can see that it has installed "MSXML 6.0 Parser", "SQL 2005 Backward Compatibilty" and "Office 2003 Web Components". The only components I require are the "SQL Support Files", "SQL Server Native Client" and " CLient Tools". If I run "start /wait <path>setup.exe REMOVE=SQLXML,TOOLS_BC_DEP" it will remove "Office 2003 Web Components" and "SQL 2005 Backward Compatibilty" but not the "MSXML 6.0 Parser". How can I get rid of this? Thanks for any help.
View Replies !
Oracle Client And Networking Components
hi all. In my SSIS project, i have to retrieve data from an oracle 10g database. On my personal laptop it works, but on our test-env i get the error below, when i try to test my connection to the oracle datasource. Could this because i have oracle XE installed yet on my personal laptop, and it is not installed on the computer of our test environment where the SSIS runs? If that's the reason, it sounds very strange, because it would mean i have to install an oracle environment also on the computer with SSIS, just to make a connection to another oracle server... Error: TITLE: Connection Manager ------------------------------ Test connection failed because of an error in initializing provider. Oracle client and networking components were not found. These components are supplied by Oracle Corporation and are part of the Oracle Version 7.3.3 or later client software installation. Provider is unable to function until these components are installed. ------------------------------ BUTTONS: OK ------------------------------
View Replies !
Changing Client Components Location Issue
When running the GUI client, I chose to install the SQL Server 2005 'Client Components' on F:Program FilesMicrosoft SQL Server, the installation put over 700MB of files on my C: drive, but there were less than 400MB of files in the location I specified. Only about 1/2 of the files I expected were put in the location I specified. Why? How can I redirect all of the 'shared' files and other misc. development pieces to install somewhere other than my boot drive? There is no way to specify this when using the GUI, can it be done with a command line install? Thanks, Tommy Thompson Thrivent Financial
View Replies !
Microsoft SQL Server 2005 DTS Designer Components
Hi, I learned this from one of SSIS book-Migrating from Data Transformation Services to Integration Services in SQL. For the design time components, Microsoft has created a special distribution called the Microsoft SQL Server 2005 DTS Designer Components. The Designer Components distribution replaces the components that get uninstalled when you upgrade your last instance of SQL Server 2000. If you want to upgrade all your SQL Server 2000 instances, this is the best and only option for recovering the DTS designer. Is anybody heard of this 2005 DTS Designer component? Where to download? How it works? Any experience to will be appreciated. Thanks, Charley
View Replies !
Changing Components After A SQL Server 2005 SP2 Upgrade
I have SQL Server 2005 installed on a machine that was recently upgraded to SP2 (build 3042). The server never had the replication feature installed on it. I attempt to add replication to it and I get an error because (I think) I am installing from the initial version media (CD-ROM, build 1399) and the setup appears to want an MSI file for SP2. Any help is appreciated. I followed the exact procedures in online help How to: Change Components in an Existing Instance of SQL Server 2005 (Setup), but after I get the Ready to Update page, I get the error box: An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package SqlRun_SQL.msi. Here is a partial output of the SQLSetupxxxx_ComputerName_Core.log file: Action 17:44:25: ResolveSource. Action start 17:44:25: ResolveSource. MSI (c) (E4!D4) [17:44:25:200]: Resolving source. MSI (c) (E4!D4) [17:44:25:200]: User policy value 'SearchOrder' is 'nmu' MSI (c) (E4!D4) [17:44:25:200]: User policy value 'DisableMedia' is 0 MSI (c) (E4!D4) [17:44:25:200]: Machine policy value 'AllowLockdownMedia' is 0 MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Media enabled only if package is safe. MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Looking for sourcelist for product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Adding {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C}; to potential sourcelist list (pcode;disk;relpath). MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Media is enabled for product. MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Attempting to use LastUsedSource from source list. MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing net source list. MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNNet 3: 2 MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing media source list. MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Trying media source H:ServersSetup. MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 2203 2: H:ServersSetupSqlRun_SQL.msi 3: -2147287037 MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Source is invalid due to missing/inaccessible package. MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4!D4) [17:44:25:200]: SOURCEMGMT: Processing URL source list. MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNURL 3: 2 MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4!D4) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:25:200]: User policy value 'SearchOrder' is 'nmu' MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Media enabled only if package is safe. MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Prompting user for a valid source. MSI (c) (E4:7C) [17:44:25:200]: Machine policy value 'DisableBrowse' is 0 MSI (c) (E4:7C) [17:44:25:200]: Machine policy value 'AllowLockdownBrowse' is 0 MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Browsing is enabled. MSI (c) (E4:7C) [17:44:25:200]: Font created. Charset: Req=0, Ret=0, Font: Req=MS Shell Dlg, Ret=MS Shell Dlg MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Media is enabled for product. MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Attempting to use LastUsedSource from source list. MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing net source list. MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNNet 3: 2 MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing media source list. MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Trying media source SQLSTDSEL;. MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:25:200]: SOURCEMGMT: Processing URL source list. MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1402 2: UNKNOWNURL 3: 2 MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: -2147483647 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:25:200]: Note: 1: 1706 2: 3: SqlRun_SQL.msi MSI (c) (E4:7C) [17:44:44:388]: SOURCEMGMT: Trying source H:SetupSqlRun_SQL.msi. MSI (c) (E4:7C) [17:44:44:388]: Cloaking enabled. MSI (c) (E4:7C) [17:44:44:388]: Attempting to enable all disabled priveleges before calling Install on Server MSI (c) (E4:7C) [17:44:44:403]: SOURCEMGMT: Resolved source to: 'H:Setup' MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Now checking product {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Media is enabled for product. MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Attempting to use LastUsedSource from source list. MSI (c) (E4!D4) [17:44:44:403]: Note: 1: 1706 2: 3: SqlRun_SQL.msi MSI (c) (E4!D4) [17:44:44:403]: SOURCEMGMT: Failed to resolve source MSI (c) (E4!D4) [17:44:44:419]: Transforming table Error. MSI (c) (E4!D4) [17:44:44:419]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error. MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error. MSI (c) (E4!D4) [17:44:44:435]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error. MSI (c) (E4!D4) [17:44:44:435]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (E4!D4) [17:44:44:435]: Transforming table Error. MSI (c) (E4!D4) [17:44:44:435]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (E4:7C) [17:44:44:435]: Transforming table Binary. MSI (c) (E4:7C) [17:44:44:435]: Note: 1: 2262 2: Binary 3: -2147287038 MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary. MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary. MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038 MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary. MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038 MSI (c) (E4:7C) [17:44:44:450]: Transforming table Binary. MSI (c) (E4:7C) [17:44:44:450]: Note: 1: 2262 2: Binary 3: -2147287038 Error 1706. An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package 'SqlRun_SQL.msi'. MSI (c) (E4!D4) [17:45:02:731]: Transforming table Error. MSI (c) (E4!D4) [17:45:02:731]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (E4!D4) [17:45:02:747]: Transforming table Error. MSI (c) (E4!D4) [17:45:02:747]: Transforming table Error. MSI (c) (E4!D4) [17:45:02:747]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (E4!D4) [17:45:02:747]: Transforming table Error. MSI (c) (E4!D4) [17:45:02:747]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (E4!D4) [17:45:02:747]: Transforming table Error. MSI (c) (E4!D4) [17:45:02:747]: Note: 1: 2262 2: Error 3: -2147287038 MSI (c) (E4!D4) [17:45:02:747]: Product: Microsoft SQL Server 2005 -- Error 1706. An installation package for the product Microsoft SQL Server 2005 cannot be found. Try the installation again using a valid copy of the installation package 'SqlRun_SQL.msi'. Action ended 17:45:02: ResolveSource. Return value 3. <EndFunc Name='ResolveInstallMediaPath' Return='1602' GetLastError='0'> <EndFunc Name='BackToBootstrap' Return='1602' GetLastError='0'> PerfTime Stop: BackToBootstrap : Fri Mar 21 17:45:02 2008 Gathering darwin properties for failure handling. <EndFunc Name='LaunchFunction' Return='1602' GetLastError='0'> Action ended 17:45:03: BackToBootstrap.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 2. MSI (c) (E4:98) [17:45:03:013]: Doing action: UserExit Action 17:45:03: UserExit. Action start 17:45:03: UserExit. MSI (c) (E4:98) [17:45:03:013]: Transforming table CustomAction. MSI (c) (E4:98) [17:45:03:013]: Note: 1: 2262 2: CustomAction 3: -2147287038 MSI (c) (E4:98) [17:45:03:028]: Transforming table CustomAction. MSI (c) (E4:98) [17:45:03:044]: Transforming table CustomAction. MSI (c) (E4:98) [17:45:03:044]: Note: 1: 2262 2: CustomAction 3: -2147287038 MSI (c) (E4:98) [17:45:03:044]: Transforming table CustomAction. MSI (c) (E4:98) [17:45:03:044]: Note: 1: 2262 2: CustomAction 3: -2147287038 MSI (c) (E4:98) [17:45:03:044]: Transforming table CustomAction. MSI (c) (E4:98) [17:45:03:044]: Note: 1: 2262 2: CustomAction 3: -2147287038 MSI (c) (E4:7C) [17:45:03:044]: Transforming table Binary. MSI (c) (E4:7C) [17:45:03:044]: Note: 1: 2262 2: Binary 3: -2147287038 MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary. MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary. MSI (c) (E4:7C) [17:45:03:059]: Note: 1: 2262 2: Binary 3: -2147287038 MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary. MSI (c) (E4:7C) [17:45:03:059]: Note: 1: 2262 2: Binary 3: -2147287038 MSI (c) (E4:7C) [17:45:03:059]: Transforming table Binary. MSI (c) (E4:7C) [17:45:03:059]: Note: 1: 2262 2: Binary 3: -2147287038 Action 17:45:03: UserExit. Dialog created Action ended 17:45:04: UserExit. Return value 2. Action ended 17:45:04: INSTALL. Return value 2. MSI (c) (E4:98) [17:45:04:622]: Destroying RemoteAPI object. MSI (c) (E4:64) [17:45:04:637]: Custom Action Manager thread ending. Property(C): ProductCode = {130A3BE1-85CC-4135-8EA7-5A724EE6CE2C} Property(C): ProductLanguage = 1033 Property(C): Manufacturer = Microsoft Corporation Property(C): ProductVersion = 9.2.3042.00 Property(C): MEDIAPACKAGEPATH = Setup Property(C): ALLUSERS = 1 Property(C): NULLGUID = {00000000-0000-0000-0000-000000000000} Property(C): ASPNetVersion = 2.0.50727 Property(C): ARPHELPLINK = http://go.microsoft.com/fwlink/?LinkId=52152 Property(C): ARPPRODUCTICON = ARPIcon.ico Property(C): ARPNOREPAIR = 1 Property(C): ARPSYSTEMCOMPONENT = 1
View Replies !
SQL SAC Return No SQL Server 2005 Components Error
Hi all, I have installed SQL Server 2005 Express with advanced services on Windows XP SP2. I am trying to connect through visual studio express to a DB which I setup and I found out the I had to configure TCP/IP for sql server to accept connections. Following a number of forums and notes I ended up trying to run SQL 2005 Surface Area Configuration tool, but whenever I try to open it I am getting; No SQL Server 2005 components were found on the specified computer. Either no components are installed, or you are not an administrator on this computer. (SQLSA) I am logged on as an administrator and I even installed sql server 2005 sp2, but still I haven't reached anywhere. I looked at the services I have but there are now SQL services - not sure if this is a problem. I even tried installing everything on another machine, this time with a Server 2003 OS, but I still ended up in the same situation. There must me something that I am not setting but WHAT ??? Any ideas out there please ?
View Replies !
Missing Some Components In SQL Server 2005 Surface Area Configuration
I was studying the SQL Server 2005 Surface Area Configuration tool to see how i could increase security. I cannot find some of the components in âSurface area Configuration of Featuresâ?. For example DAC appears to be missing. This is a dedicated administrator connection that allows an administrator to connect to a server. Is this because I have SQL 2005 express instead of the professional version or could it even be to do with the operating system (XP home) Only the following components are listed under "Database Engine": Ad Hoc Remote Queries CLR Integration Native XML Web Services OLE Automation Service Broker Xp_cmdshell Thanks
View Replies !
List Of Supported Components For SQL Server 2005 Standard Edition?
Please can someone give me a url or even their own list of support / unsupported components in SQL server 2005 Standard edition. I know fuzzy lookup is not supported. Is a slowly changing dimension supported? Its a bit difficult to tell when I get bizzare "Product level is insufficient" error for even a basic derived column transformation when executing a package using SSIS unless it is executed using a scheduled job.... thanks, Nicole
View Replies !
Adding 'unaware' SQL Server 2005 Components To Existing Windows 2003 Cluster
This is a fresh install of SQL Server 2005 (64bit) on a Windows 2003 R2 SP2 64bit OS. The Cluster has been built and SQL 2005 has been installed (Database Engine(clustered), Analysis Server(clustered), Notification Server, Integration Server, Reporting Services). SQL 2005 SP2 has been installed. Now, I want to install Notification Server, Integration Server and Reporting Services on the second node for high availability. When I select 'Install New Components' from Add/Remove Programs, the System Configuation Checker tells me theres a version difference and to: To change an existing instance of Microsoft SQL Server 2005 to a different edition of SQL Server 2005, you must run SQL Server 2005 Setup from the command prompt and include the SKUUPGRADE=1 parameter. I'm using the same binaries as the original install. Could this be a result of installing SQL 2005 SP2? Can someone help me out with this. I'd prefer using the setup interface instead of a command line script.
View Replies !
SQL Server 2005 Express Installation Problem: Incompatible Components From Beta Version Of .NET Framework
Hi all, Yesterday, I just downloaded the SQL Server 2005 Express (SQLEXPR.EXE) and tried to install it in my Windows XP Pro PC that is on Microsoft NT 4 LAN System. I got the following error: Microsoft SQL Server 2005 CTP setup The Microfost .NET Framework 2.0 is not installed. Please install before running setup. This morning, I downloaded the NET Framework Version 2.0 Redistributable Package Beta 2 (x86) from the Microsoft Download Center and installed it in my Windows XP Pro PC. Then I tried to install the SQL Server 2005 Express (SQLEXPR.EXE) again. This time I got a new error: 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. I am confused and lost in this installation problem. Was the .NET Framework Version 2.0 Redistributable Package Beta 2 (x86) a wrong Microsoft .NET Framework 2.0 I downloaded and installed in my PC? Where is the right Microsoft .NET Framework 2.0 for the SQL Server 2005 Express? Please help and advise. Thanks in advance, Scott Chang
View Replies !
SQL Server 2005 Install Failure Over 2005 Express CTP
with the following log: Microsoft SQL Server 2005 Setup beginning at Wed Jun 28 19:02:06 2006 Process ID : 1220 E:Serverssetup.exe Version: 2005.90.1399.0 Running: LoadResourcesAction at: 2006/5/28 19:2:5 Complete: LoadResourcesAction at: 2006/5/28 19:2:5, returned true Running: ParseBootstrapOptionsAction at: 2006/5/28 19:2:5 Loaded DLL:E:Serversxmlrw.dll Version:2.0.3604.0 Complete: ParseBootstrapOptionsAction at: 2006/5/28 19:2:6, returned false Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run: Could not parse command line due to datastore exception. Source File Name: utillibpersisthelpers.cpp Compiler Timestamp: Fri Jul 29 01:13:55 2005 Function Name: writeEncryptedString Source Line Number: 124 ---------------------------------------------------------- writeEncryptedString() failed Source File Name: utillibpersisthelpers.cpp Compiler Timestamp: Fri Jul 29 01:13:55 2005 Function Name: writeEncryptedString Source Line Number: 123 ---------------------------------------------------------- Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified. Source File Name: cryptohelpercryptsameusersamemachine.cpp Compiler Timestamp: Mon Jun 13 14:30:00 2005 Function Name: sqls::CryptSameUserSameMachine::ProtectData Source Line Number: 50 2 Could not skip Component update due to datastore exception. Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "1220"} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupBootstrapOptionsScope.InstallMediaPath Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupBootstrapOptionsScope" Running: ValidateWinNTAction at: 2006/5/28 19:2:6 Complete: ValidateWinNTAction at: 2006/5/28 19:2:6, returned true Running: ValidateMinOSAction at: 2006/5/28 19:2:6 Complete: ValidateMinOSAction at: 2006/5/28 19:2:6, returned true Running: PerformSCCAction at: 2006/5/28 19:2:6 Complete: PerformSCCAction at: 2006/5/28 19:2:6, returned true Running: ActivateLoggingAction at: 2006/5/28 19:2:6 Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run: Datastore exception while trying to write logging properties. Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupStateScope.primaryLogFiles Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupStateScope" 00D9CFC4Unable to proceed with setup, there was a command line parsing error. : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified. Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupBootstrapOptionsScope.InstallMediaPath Source Line Number: 44 Class not registered. Failed to create CAB file due to datastore exception Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "1220"} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupBootstrapOptionsScope.HostSetup Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupBootstrapOptionsScope" Message pump returning: 2
View Replies !
SQL Server 2005 Job Failure
I have an Integration Services package running fine when i execute it manually. However, when i schedule the package in SQL Server Agent. it fails to execute. The only message i get "package execution failed. the step failed" i changed the job owner to local administrator's account and the sa login but it still failed.
View Replies !
SQL Server 2005 SP1 Failure
My upgrade to SP1 for SQL Server 2005 failed and I have yet to find a reason or a solution. I have read many articles describing file security problems, registry problems etc. I have been through these and looked at all of the different aspects and still cannot find a fix other than to unistall SQL and reinstall SQL. Since this is a production server and is used 24/7 I would rather avoid this. The installation is on a windows 2003 server with SP1 that was upgraded from Windows 2000. SQL was originally installed fresh on 2000. There is 21GB of HD space left. Below is the last few lines from the SQL Log Property(S): AdminUser = 1 Property(S): SystemLanguageID = 1033 Property(S): SQL200532Hotfix2047 = \PDC1c$14773e1faf9d288841d5552a40HotFixSQLFilessqlrun_sql.msp Property(S): UPGRESDATABASES = 1 Property(S): SqlActionManaged = 3 Property(S): BrowseAuto.2FC2D269_8625_4826_BB3F_F9059090CB38 = 2 Property(S): UPGDISTDATABASES = 1 Property(S): InstallNgenTicks = 110000 Property(S): Sql_sqlSqlUpgradeSequence = 74948000 Property(S): HotfixScript = 1 Property(S): DebugClsid.CC1A8C58_27D1_4D38_BF1B_C0A5CBB90616 = {3044D882-D138-432F-9A13-A20ED7C33C23} Property(S): SQLBROWSERACCOUNT = NT AUTHORITYSYSTEM MSI (s) (64:EC) [15:37:54:500]: Product: Microsoft SQL Server 2005 - Update 'Service Pack 1 for SQL Server Database Services 2005 ENU (KB913090)' could not be installed. Error code 1603. Additional information is available in the log file C:WINNTHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log. MSI (s) (64:EC) [15:37:54:515]: Note: 1: 1729 MSI (s) (64:EC) [15:37:54:515]: Transforming table Error. MSI (s) (64:EC) [15:37:54:515]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (64:EC) [15:37:54:515]: Transforming table Error. MSI (s) (64:EC) [15:37:54:515]: Transforming table Error. MSI (s) (64:EC) [15:37:54:515]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (64:EC) [15:37:54:515]: Transforming table Error. MSI (s) (64:EC) [15:37:54:515]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (64:EC) [15:37:54:515]: Transforming table Error. MSI (s) (64:EC) [15:37:54:515]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (64:EC) [15:37:54:515]: Transforming table Error. MSI (s) (64:EC) [15:37:54:515]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (64:EC) [15:37:54:515]: Transforming table Error. MSI (s) (64:EC) [15:37:54:515]: Transforming table Error. MSI (s) (64:EC) [15:37:54:515]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (64:EC) [15:37:54:515]: Transforming table Error. MSI (s) (64:EC) [15:37:54:515]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (64:EC) [15:37:54:515]: Transforming table Error. MSI (s) (64:EC) [15:37:54:515]: Note: 1: 2262 2: Error 3: -2147287038 MSI (s) (64:EC) [15:37:54:515]: Product: Microsoft SQL Server 2005 -- Configuration failed. MSI (s) (64:EC) [15:37:54:531]: Attempting to delete file C:WINNTInstaller3438c.msp MSI (s) (64:EC) [15:37:54:531]: Unable to delete the file. LastError = 32 MSI (s) (64:EC) [15:37:54:546]: Cleaning up uninstalled install packages, if any exist MSI (s) (64:EC) [15:37:54:546]: MainEngineThread is returning 1603 MSI (s) (64:DC) [15:37:54:546]: Destroying RemoteAPI object. MSI (s) (64:84) [15:37:54:546]: Custom Action Manager thread ending. === Logging stopped: 11/27/2006 15:37:54 === MSI (c) (EC:2C) [15:37:54:656]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1 MSI (c) (EC:2C) [15:37:54:656]: MainEngineThread is returning 1603 === Verbose logging stopped: 11/27/2006 15:37:54 ===
View Replies !
Developing Custom Components By Extending The SSIS Stock Data Flow Components
Everything I've read says that custom data flow components are built by inheriting from the Microsoft.SqlServer.Dts.Pipeline.PipelineComponent class. But the stock components such as the Derived Column data flow transformation must each be implemented by their own class. So how do I base my custom components on those classes? The documentation for the PipelineComponent class doesn't list any such subclasses.
View Replies !
SQL SERVER AGENT 2005 Job Failure
I have scheduled a job in SQL Server Agent, as it executes it fails Immediatly. The error history displays the following error details, which i copied from the log file "Description: Unable to load the package as XML because of package does not have a valid XML format. A specific XML parser error will be posted. The system cannot find the path specified.". This happens when loading a package and the file cannot be opened or loaded correctly into the XML document. This can be the result of either providing an incorrect file name was specified when calling LoadPackage or the XML file was specified and has an incorrect format. End Error ... The package could not be f... The step failed." I am using the File System Type to load my package. Please assisst me in finding the solution Regards ZeEsHaN
View Replies !
Failure To Apply SP2 To SQL Server 2005 EE
I am running SQL Server Enterprise Edition Build 9.0.1399 as a default instance on a Windows Server 2003 Enterprise Edition SP2. Whenever I try to apply Service Pack 2, I obtain the following error: A recently applied update, KB921896, failed to install I looked into the other threads but they either discuss community versions of SQL Server or named instances - niether or which apply to me. I also looked but there are no folders named MSSQLSERVER on this machine. Can somebody Please Help as this is preventing me from deploying a major solution. Thanks!
View Replies !
SQL Server 2005 Install Failure.
SQL Server 2005 Enterprise Edition X64 keeps failing during the install. Every single compnent installes EXCEPT the actual database engine. The only error message I get is that the server failed to install because of a fatal error. This happens when the installer is trying to set "internal parameters" on the database engine install phase. I have tried uninstaling everything and even used the Windows Install Clean up tool to clean out bogus references after my 1st attempt to install the DB server, but nothing has helped. I hope someone has some ideas on how to proceed. The server is a brand new Dell PowerEdge 1900 SC running 2 Quad Core Xeon 2.0 GHz processors, 8 GB of RAM and Windows Server 20003 RC2 X64 factory installed from Dell. I attempted to post the verbose setup log in this post, but it was to long. I can email the text file or upload it to our web server and link it in here if some one wants to see it. It wasn't a whole lot of help to me.
View Replies !
SQL Server 2005 SP1 Failure - 'dm_exec_query_resource_semaphores'
Hi Sam, In my case, the components in sp1 were installed successfully except the database engine. And the following messages were captured from the setup log. Please advise me. Thank you in advances, Kasemchai ---------------------------------------------- Action start 15:24:23: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. <Func Name='LaunchFunction'> MSI (s) (5C!10) [15:24:23:494]: Transforming table _sqlAction. MSI (s) (5C!10) [15:24:23:494]: Note: 1: 2262 2: _sqlAction 3: -2147287038 MSI (s) (5C!10) [15:24:23:494]: Transforming table _sqlAction. MSI (s) (5C!10) [15:24:23:494]: Transforming table _sqlAction. MSI (s) (5C!10) [15:24:23:494]: Note: 1: 2262 2: _sqlAction 3: -2147287038 MSI (s) (5C!10) [15:24:23:494]: Transforming table _sqlAction. MSI (s) (5C!10) [15:24:23:494]: Note: 1: 2262 2: _sqlAction 3: -2147287038 MSI (s) (5C!10) [15:24:23:494]: Transforming table _sqlAction. MSI (s) (5C!10) [15:24:23:494]: Note: 1: 2262 2: _sqlAction 3: -2147287038 Function=CommitSqlUpgrade MSI (s) (5C!10) [15:24:23:494]: Transforming table _sqlAction. MSI (s) (5C!10) [15:24:23:494]: Note: 1: 2262 2: _sqlAction 3: -2147287038 MSI (s) (5C!10) [15:24:23:494]: Transforming table _sqlAction. MSI (s) (5C!10) [15:24:23:494]: Transforming table _sqlAction. MSI (s) (5C!10) [15:24:23:494]: Note: 1: 2262 2: _sqlAction 3: -2147287038 MSI (s) (5C!10) [15:24:23:494]: Transforming table _sqlAction. MSI (s) (5C!10) [15:24:23:494]: Note: 1: 2262 2: _sqlAction 3: -2147287038 MSI (s) (5C!10) [15:24:23:494]: Transforming table _sqlAction. MSI (s) (5C!10) [15:24:23:494]: Note: 1: 2262 2: _sqlAction 3: -2147287038 <Func Name='SetCAContext'> <EndFunc Name='SetCAContext' Return='T' GetLastError='0'> Doing Action: CommitSqlUpgrade PerfTime Start: CommitSqlUpgrade : Tue Nov 21 15:24:23 2006 <Func Name='ComponentUpgrade'> There was a failure during installation search up in this log file for this message: SQL Server Setup has encountered the following problem: [Microsoft][SQL Native Client][SQL Server]Cannot find the object 'dm_exec_query_resource_semaphores', because it does not exist or you do not have permission.. To continue, correct the problem, and then run SQL Server Setup again. <EndFunc Name='ComponentUpgrade' Return='15151' GetLastError='0'> PerfTime Stop: CommitSqlUpgrade : Tue Nov 21 15:24:23 2006 Gathering darwin properties for failure handling. <EndFunc Name='LaunchFunction' Return='15151' GetLastError='0'> MSI (s) (5C:F0) [15:24:23:900]: Transforming table InstallExecuteSequence. MSI (s) (5C:F0) [15:24:23:900]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038 MSI (s) (5C:F0) [15:24:23:900]: Transforming table InstallExecuteSequence. MSI (s) (5C:F0) [15:24:23:900]: Transforming table InstallExecuteSequence. MSI (s) (5C:F0) [15:24:23:900]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038 MSI (s) (5C:F0) [15:24:23:915]: Transforming table InstallExecuteSequence. MSI (s) (5C:F0) [15:24:23:915]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038 MSI (s) (5C:F0) [15:24:23:915]: Transforming table InstallExecuteSequence. MSI (s) (5C:F0) [15:24:23:915]: Note: 1: 2262 2: InstallExecuteSequence 3: -2147287038 Action ended 15:24:23: CommitSqlUpgrade.D20239D7_E87C_40C9_9837_E70B8D4882C2. Return value 3. Action ended 15:24:23: INSTALL. Return value 3.
View Replies !
Failure Installing SQL Server 2005 SP 1
Windows XP Pro SQL Server 2005 Express SQL Server 2005 Standard I installed the service pack for SQL Server Express first. Then I tried to install the service pack for SQL Server. I got the error message, "A recently applied update, KB913090, failed to install.", while it was upgrading the Setup Support Files. Jonathan Allen Log follows... 04/22/2006 10:52:34.781 ================================================================================ 04/22/2006 10:52:34.875 Hotfix package launched 04/22/2006 10:53:47.546 Attempting to install instance: SQL Server Native Client 04/22/2006 10:53:47.578 Attempting to install target: RADICALJAY 04/22/2006 10:53:47.593 Attempting to install file: sqlncli.msi 04/22/2006 10:53:47.687 Attempting to install file: \RADICALJAYc$1f5502657526de4ed0cHotFixSqlncliFilessqlncli.msi 04/22/2006 10:53:47.687 Creating MSI install log file at: C:WINDOWSHotfixRedist9LogsRedist9_Hotfix_KB913090_sqlncli.msi.log 04/22/2006 10:53:47.703 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 04/22/2006 10:53:47.718 Failed to read registry key: Debug 04/22/2006 10:53:49.578 MSP returned 0: The action completed successfully. 04/22/2006 10:53:49.765 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 04/22/2006 10:53:49.781 Failed to read registry key: Debug 04/22/2006 10:53:49.781 Successfully installed file: \RADICALJAYc$1f5502657526de4ed0cHotFixSqlncliFilessqlncli.msi 04/22/2006 10:53:49.796 Successfully installed target: RADICALJAY 04/22/2006 10:53:49.812 Successfully installed instance: SQL Server Native Client 04/22/2006 10:53:49.828 04/22/2006 10:53:49.828 Product Status Summary: 04/22/2006 10:53:49.843 Product: SQL Server Native Client 04/22/2006 10:53:49.859 SQL Server Native Client (RTM ) - Success 04/22/2006 10:53:49.859 04/22/2006 10:53:49.875 Product: Setup Support Files 04/22/2006 10:53:49.890 Setup Support Files (RTM ) - Not Applied 04/22/2006 10:53:49.890 04/22/2006 10:53:49.906 Product: Database Services 04/22/2006 10:53:49.921 Database Services (RTM 1399 ENU) - Not Applied 04/22/2006 10:53:49.937 Analysis Services (RTM 1399 ENU) - Not Applied 04/22/2006 10:53:49.937 Reporting Services (RTM 1399 ENU) - Not Applied 04/22/2006 10:53:49.953 04/22/2006 10:53:49.968 Product: Database Services 04/22/2006 10:53:49.968 Database Services (SP1 2047 ENU) - NA 04/22/2006 10:53:49.984 Details: Instances of SQL Server Express cannot be updated by using this Service Pack installer. To update instances of SQL Server Express, use the SQL Server Express Service Pack installer. 04/22/2006 10:53:50.000 04/22/2006 10:53:50.015 Product: Notification Services 04/22/2006 10:53:50.015 Notification Services (RTM 1399 ENU) - Not Applied 04/22/2006 10:53:50.031 04/22/2006 10:53:50.046 Product: Integration Services 04/22/2006 10:53:50.046 Integration Services (RTM 1399 ENU) - Not Applied 04/22/2006 10:53:50.062 04/22/2006 10:53:50.078 Product: Client Components 04/22/2006 10:53:50.093 Client Components (RTM 1399 ENU) - Not Applied 04/22/2006 10:53:50.093 04/22/2006 10:53:50.109 Product: MSXML 6.0 Parser 04/22/2006 10:53:50.125 MSXML 6.0 Parser (RTM ) - Not Applied 04/22/2006 10:53:50.125 04/22/2006 10:53:50.140 Product: SQLXML4 04/22/2006 10:53:50.156 SQLXML4 (RTM ) - Not Applied 04/22/2006 10:53:50.171 04/22/2006 10:53:50.171 Product: Backward Compatibility 04/22/2006 10:53:50.187 Backward Compatibility (RTM ) - Not Applied 04/22/2006 10:53:50.203 04/22/2006 10:53:50.203 Product: Microsoft SQL Server VSS Writer 04/22/2006 10:53:50.218 Microsoft SQL Server VSS Writer (RTM ) - Not Applied 04/22/2006 10:53:50.234
View Replies !
Failure To Install SQL Server 2005 SP1
I am trying to apply MS SQL Server 2005 SP1 onto a 2 node cluster running Windows Server 2003, but it fails for SQL and the Analysis Services components of SQL Server, the error I am getting is MSP returned 1603 for both components. I have tried rebooting the machines but still get the same issue, the only additional dependency for SQL that I have added is for a 2nd physical disk. log details are below. Many thanks in advance for any help you can provide on this problem. 01/15/2007 12:26:26.937 ================================================================================ 01/15/2007 12:26:26.953 Hotfix package launched 01/15/2007 12:26:27.703 Product discovery successfully completed during the install process for MSSQLSERVER 01/15/2007 12:26:27.703 SP Level check successfully completed during the install process for MSSQLSERVER 01/15/2007 12:26:27.734 Product language check successfully completed during the install process for MSSQLSERVER 01/15/2007 12:26:27.750 Product version check successfully completed during the install process for MSSQLSERVER 01/15/2007 12:26:27.765 Command-line instance name check completed during the install process 01/15/2007 12:26:27.781 Baseline build check completed during the install process 01/15/2007 12:29:31.734 Attempting to install instance: MSSQLSERVER 01/15/2007 12:29:31.750 Enumerating passive cluster nodes 01/15/2007 12:29:31.765 Patching available passive node: GBCONV1A002N03 01/15/2007 12:29:31.781 Attempting to patch running passive node: GBCONV1A002N03 01/15/2007 12:29:31.796 Waiting for first successfully completed passive node 01/15/2007 12:29:31.812 Successfully created remote folder for product instance target \GBCONV1A002N03 01/15/2007 12:29:45.859 Successfully transferred payload to remote product instance target \GBCONV1A002N03 01/15/2007 12:29:45.921 Successfully transferred payload to remote product instance target \GBCONV1A002N03 01/15/2007 12:29:45.953 Successfully created new scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:29:46.562 Successfully saved new scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:29:46.625 Successfully created scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:29:46.640 Successfully started scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:29:46.656 Successfully started scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:30:28.671 Scheduled task for product instance target has completed 01/15/2007 12:30:28.687 Waiting for exit code from scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:30:33.718 Received exit code 0 from scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:30:33.734 Result code for scheduled task for product instance target has been received 01/15/2007 12:30:33.734 Removed scheduled task for product instance target \GBCONV1A002N03 01/15/2007 12:30:33.921 Successfully removed remote folder for product instance target \GBCONV1A002N03 01/15/2007 12:30:33.953 Remote process completed for product instance target 01/15/2007 12:30:33.968 Exit code for passive node: GBCONV1A002N03 = 0 01/15/2007 12:30:36.812 First successful passive node has been completed 01/15/2007 12:30:36.828 Attempting to install target: GBCONV1A002N01 01/15/2007 12:30:36.843 Attempting to check for locked files: sqlrun_as.msp 01/15/2007 12:30:36.890 Attempting to check for locked files: \GBCONV1A002N01d$bf7e520a98fb7a70c268b90HotFixASFilessqlrun_as.msp 01/15/2007 12:30:36.906 Creating MSP locked file check log at: C:WINDOWSHotfixOLAP9LogsOLAP9_Hotfix_KB913090_sqlrun_as.msp.out 01/15/2007 12:30:41.015 MSP returned 1603: A fatal error occurred during installation. 01/15/2007 12:30:41.140 Unable to check MSP file: \GBCONV1A002N01d$bf7e520a98fb7a70c268b90HotFixASFilessqlrun_as.msp 01/15/2007 12:30:41.156 The following exception occurred: Unable to install Windows Installer MSP file Date: 01/15/2007 12:30:41.156 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 689 01/15/2007 12:30:41.187 Attempting to finalize cluster instance: MSSQLSERVER 01/15/2007 12:30:41.203 Waiting for all running passive nodes to complete their patch 01/15/2007 12:30:41.218 All running passive nodes have completed their patch 01/15/2007 12:30:41.234 Successfully finalized cluster instance: MSSQLSERVER 01/15/2007 12:30:41.234 Failed to install instance: MSSQLSERVER 01/15/2007 12:30:41.250 01/15/2007 12:30:41.281 Product Status Summary: 01/15/2007 12:30:41.296 Product: SQL Server Native Client (64-bit) 01/15/2007 12:30:41.312 SQL Server Native Client (64-bit) (RTM ) - Success 01/15/2007 12:30:41.312 01/15/2007 12:30:41.328 Product: Setup Support Files (64-bit) 01/15/2007 12:30:41.343 Setup Support Files (64-bit) (RTM ) - Success 01/15/2007 12:30:41.359 01/15/2007 12:30:41.375 Product: Database Services (64-bit) 01/15/2007 12:30:41.390 Database Services (64-bit) (SP1 2047 ENU GBCONV1A002V03) - Failure 01/15/2007 12:30:41.406 Analysis Services (64-bit) (RTM 1399 ENU GBCONV1A002V04) - Failure 01/15/2007 12:30:41.406 01/15/2007 12:30:41.421 Product: Integration Services (64-bit) 01/15/2007 12:30:41.437 Integration Services (64-bit) (SP1 2047 ENU) - Not Applied 01/15/2007 12:30:41.453 01/15/2007 12:30:41.468 Product: MSXML 6.0 Parser (64-bit) 01/15/2007 12:30:41.484 MSXML 6.0 Parser (64-bit) (RTM ) - Not Applied 01/15/2007 12:30:41.484 01/15/2007 12:30:41.515 Product: Backward Compatibility (64-bit) 01/15/2007 12:30:41.531 Backward Compatibility (64-bit) (RTM ) - Not Applied 01/15/2007 12:30:41.546 01/15/2007 12:30:41.546 Product: Microsoft SQL Server VSS Writer (64-bit) 01/15/2007 12:30:41.578 Microsoft SQL Server VSS Writer (64-bit) (RTM ) - Not Applied 01/15/2007 12:30:41.593 01/15/2007 12:48:34.562 Hotfix package closed
View Replies !
SQL Server 2005 Authentication Failure
Hi, not sure if this is the right place to raise this question. If not please move this message. I configured a Sql-Server 2005 installation -that is running on my computer for test purposes- with "Windows Authentication". I had to change my Windows password recently and it seems as if SQL-Server does not accept my account anymore. The event viewer told me that service startups failed because user or password are unkown. Does anybody know how I may get access again? The problem seems to be that I cannot change back to my old password -unless I change it six or more times... Thanks for helping me out!
View Replies !
Sql Server 2005 Job Failure Information
Hi, I have scheduled a job that runs every minute. If the job does not succeed, then I would like my front end application to be notified. I am not sure if this is a reasonable way but I am thinking of somehow populating a table (Only if the scheduled job fails) in sql server and then read that table every minute from the front end application. So, is it possible to populate a table if a job fails? I do not see any options for this in the properties of the job. Thanks
View Replies !
Sql Server 2005 Restore Failure
Hi, I have a SQL Server 2005 Database that I would like to export to SQL Server Express. How do I go about this? I've tried backing it up, creating a new (blank) SQL Server Express Database and trying to restore it, but get the following message ------------------------------ Restore failed for Server 'PRODSOL-LAPTOP1SQLEXPRESS'. (Microsoft.SqlServer.Smo). ------------------------------ ADDITIONAL INFORMATION: System.Data.SqlClient.SqlError: The backup set holds a backup of a database other than the existing 'test' database. (Microsoft.SqlServer.Smo) please help Regrds T.Anantha Krishnan
View Replies !
An Error Has Occurred While Establishing A Connection To The Server. When Connecting To SQL Server 2005, This Failure May Be Cau
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this I use Microsoft Windows Vista Home Professional I have already installed to my computer Microsoft SQL Server 2005 and SQL Serves Express. I used to be successful to connect to the SQL Server but now I CAN NOT. Not: I try to run SQL Server 2005 but I can not, even I logged on to my computer with an administrator rights. On the other hand I can start and stop the SQL Server Express easily. As a result, how can I solve this problem. Thanks in advance. Bilgin Kılıç Additional Details An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
View Replies !
When Connecting To SQL Server 2005, This Failure May Be Caused By The Fact That Under The Default Settings SQL Server Does Not A
My environment: Home PC Vista Ultimate SQL Server Developer 2005 I'm about to go absolutely nuts. I've tried so many things including: 1) Of course making sure Remote connections and both TCP/IP and named pipes are enabled for SQL 2005 2) Verified my connection string works. I even tested it in Enterprise Library using the tool and it connects successfully via windows authentication 3) Made sure of course my logged in user is a member of the administrator group and that my user in SQL 2005 logins has db_owner and full rights to the DB I am connecting to. I also made sure the NT AUTHORITY as well as the 3 sql service users have db_owner rights as well as the adminstrator in the SQL Server logins all have db_owner to the DB 4) Started the SQL Server Browser service, SQL Server DB engine, and SQL Server Agent 5) Made sure my site is setup right in IIS 7. I checked the connection string in there as well as it shows up in IIS7 in one of the sections. Using Windows authentication and it is enabled for my site 6) Tried running the .net site using both localhost (IIS) and also tried using the Visual Studio built-in web server. Both give this message still Error Details: Server Error in '/' Application. An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +800131 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +186 System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +737554 System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +114 System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +381 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +181 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +173 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +357 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +30 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +494 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.SessionState.SqlStateConnection..ctor(SqlPartitionInfo sqlPartitionInfo) +79 [HttpException (0x80004005): Unable to connect to SQL Server session database.] System.Web.SessionState.SqlSessionStateStore.ThrowSqlConnectionException(SqlConnection conn, Exception e) +227 System.Web.SessionState.SqlStateConnection..ctor(SqlPartitionInfo sqlPartitionInfo) +349 System.Web.SessionState.SqlSessionStateStore.GetConnection(String id, Boolean& usePooling) +285 System.Web.SessionState.SqlSessionStateStore.SetAndReleaseItemExclusive(HttpContext context, String id, SessionStateStoreData item, Object lockId, Boolean newItem) +178 System.Web.SessionState.SessionStateModule.OnReleaseState(Object source, EventArgs eventArgs) +476 System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92 System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64 Version Information: Microsoft .NET Framework Version:2.0.50727.1433; ASP.NET Version:2.0.50727.1433
View Replies !
Sql Client In Sql Server 2005
HI allGurus i am struck up in sql 2005.I am new to sql 2005.I have my serverinstalled on one machine.Now what do i download so that i am able toregister it.Now i want to connect to that machine thru enterprise manager or clientlike we do in sql server 2000 thru query analyzer..Will sql 2005 express help.?Please helpRegards
View Replies !
Error Installing Notification Services, Integration Services && Workstation Components For SQL Server 2005 Standard
After upgrading from SQL Express to 2005 Standard, installation of Notification Services, Integration Services or Workstation Components results in errors: Error for NS: Failed to install and configure assemblies C:Program FilesMicrosoft SQL Server90NotificationServices9.0.242Binmicrosoft.notificationservices.dll in the COM+ catalog. Error: -2147024893 Error Message: They system cannot find the path specified. Error description: Could not load file or assembly 'System.EnterpriseServices.Wrapper.dll' or one of it's dependencies. The system cannot find the path specified. <Abort><Retry><Ignore> Database Engine, Analysis Services & Reporting Services installed/upgraded fine. Any thoughts/suggestions? Thanks J
View Replies !
SQL Server 2005 Remote Connection Failure
I'm having a big problem with a SQL 2K5 cluster (using standard edition). I can get onto the box and connect to the sql server locally fine. However when I try to connect remotely I get errors. Let's call the two sides of the cluster, CL1 and CL2 and the "virtual server" is CL3. Locally I can connect without any problem at all to the SQL server, but I just can't connect to it from any remote machine. The server in question is instance name LMS_PRD running on CL3, port 10051. TCP/IP is definitely enabled for local and remote connections (I have checked this in the SQL server surface area configuration). I can connect locally without any problem. Also, locally, if I do, telnet CL3 10051 it connects fine From a SQL 2000 box - when I try to connect from sql query analyzer, I get "Unable to connect to server LMS_PRD Server Msg 17 ... SQL server does not exist or access denied" Client network utility shows server alias - LMS_PRD, TCP/IP, CL3LMS_PRD,10051 [I can connect to other SQL 2005 servers OK from this same server using this same method] On this box, when I do telnet CL3 10051 , I get "Connecting to CL3...Could not open a connection to host on port 10051 : Connect failed" [When I do a similar one for another SQL 2005 box, "telnet U01 10051", it connects fine] From another SQL 2005 box - when I try to register the server, I get "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP provider, error 0 - No connection could be made because thew target machine actively refused it.) (Microsoft SQL Server, Error: 10061)" IN the SQL native client configuration it shows alias name - CL3LMS_PRD, server=CL3LMS_PRD, protocol tcp, parameters 10051 Again if I do telnet CL3 10051, I get the error above. From this same box I can register another SQL 2005 server without any problem and do the telnet to it OK Just to emphasise: (a) The SQL server configuration manager shows that TCP/IP is enabled, and that 10051 is the port (in IPALL, TCP port). Also I have checked the SQL server errorlog - it is definitely using 10051 as the port. (b) The SQL server surface area configuration shows under local and remote connections using both TCP/IP and named pipes selected (I've tried both this and the using tcp/ip only option) (c) SQL server browser is running (d) There are NO firewalls etc involved Any help or advice MUCH appreciated Any thoughts anyone?
View Replies !
SQL Server 2005 OWC11 Installation Failure
I'm getting a setup failure for OWC11 when I try and install SQL Server 2005 Standard or Enterprise on a brand new machine with XP SP2. I have tried installing OWC beforehand, but this doesn't make a difference - SQL setup doesn't appear to check whether this component is already installed. Interestingly, SQL Server Express installs without a hitch. Belowis the releveant part of the error log. It appears that setup isn't putting the OWC MSI in the right place in the temporary setup area. Any help would be much appreciated! MSI (s) (C4:C8) [19:03:59:921]: Executing op: ComponentRegister(ComponentId={2B9CB878-8D8B-41C8-BDD4-17D80DC4FC5D},KeyPath=<Microsoft.Office.Interop.Owc11,Version="11.0.0.0000",Culture="neutral",PublicKeyToken="71e9bce111e9429c",FileVersion="11.0.5530.0",State=3,,Disk=1,SharedDllRefCount=0,BinaryType=0) MSI (s) (C4:C8) [19:03:59:921]: MSCOREE already loaded, using loaded copy MSI (s) (C4:C8) [19:03:59:937]: Executing op: ActionStart(Name=RemoveODBC,Description=Removing ODBC components,) MSI (s) (C4:C8) [19:03:59:937]: Executing op: ODBCDriverManager(,BinaryType=0) MSI (s) (C4:C8) [19:03:59:937]: Executing op: ODBCDriverManager(,BinaryType=1) MSI (s) (C4:C8) [19:03:59:937]: Executing op: ActionStart(Name=CreateFolders,Description=Creating folders,Template=Folder: [1]) MSI (s) (C4:C8) [19:03:59:937]: Executing op: FolderCreate(Folder=C:,Foreign=0,) MSI (s) (C4:C8) [19:03:59:937]: Executing op: ActionStart(Name=InstallFiles,Description=Copying new files,Template=Copying file: [1]) MSI (s) (C4:C8) [19:03:59:937]: Executing op: SetTargetFolder(Folder=C:Program FilesMicrosoft OfficeOFFICE11) MSI (s) (C4:C8) [19:03:59:937]: Executing op: SetSourceFolder(Folder=1FILESPFILESMSOFFICEOFFICE11|FILESProgram FilesMicrosoft OfficeOFFICE11) MSI (s) (C4:C8) [19:03:59:937]: Executing op: ChangeMedia(MediaVolumeLabel=OFFICE11,MediaPrompt=Please insert the disk: Microsoft Office 2003 Web Components,MediaCabinet=1PA800302.CAB,BytesPerTick=32768,CopierType=1,,,SignatureRequired=0,,,IsFirstPhysicalMedia=1) MSI (s) (C4:C8) [19:03:59:937]: Executing op: AssemblyCopy(SourceName=OWC11PIA.DLL|Microsoft.Office.Interop.Owc11.dll,SourceCabKey=OWC11PIA.DLL,DestName=Microsoft.Office.Interop.Owc11.dll,Attributes=1024,FileSize=461416,PerTick=32768,,VerifyMedia=1,,,,,ComponentId={2B9CB878-8D8B-41C8-BDD4-17D80DC4FC5D},IsManifest=1,,,AssemblyMode=0,) MSI (s) (C4:C8) [19:03:59:937]: Resolving source. MSI (s) (C4:C8) [19:03:59:937]: User policy value 'SearchOrder' is 'nmu' MSI (s) (C4:C8) [19:03:59:937]: User policy value 'DisableMedia' is 0 MSI (s) (C4:C8) [19:03:59:937]: Machine policy value 'AllowLockdownMedia' is 0 MSI (s) (C4:C8) [19:03:59:937]: SOURCEMGMT: Media enabled only if package is safe. MSI (s) (C4:C8) [19:03:59:937]: SOURCEMGMT: Looking for sourcelist for product {90A40409-6000-11D3-8CFE-0150048383C9} MSI (s) (C4:C8) [19:03:59:937]: SOURCEMGMT: Adding {90A40409-6000-11D3-8CFE-0150048383C9}; to potential sourcelist list (pcode;disk;relpath). MSI (s) (C4:C8) [19:03:59:937]: SOURCEMGMT: Now checking product {90A40409-6000-11D3-8CFE-0150048383C9} MSI (s) (C4:C8) [19:03:59:937]: SOURCEMGMT: Media is enabled for product. MSI (s) (C4:C8) [19:03:59:937]: SOURCEMGMT: Attempting to use LastUsedSource from source list. MSI (s) (C4:C8) [19:03:59:937]: SOURCEMGMT: Trying source C:SWWORKMOSOURCEBCMOWC11. MSI (s) (C4:C8) [19:03:59:937]: Note: 1: 2203 2: C:SWWORKMOSOURCEBCMOWC11OWC11.MSI 3: -2147287037 MSI (s) (C4:C8) [19:03:59:937]: SOURCEMGMT: Source is invalid due to missing/inaccessible package. MSI (s) (C4:C8) [19:03:59:937]: Note: 1: 1706 2: -2147483647 3: OWC11.MSI MSI (s) (C4:C8) [19:03:59:937]: SOURCEMGMT: Processing net source list. MSI (s) (C4:C8) [19:03:59:937]: Note: 1: 1706 2: -2147483647 3: OWC11.MSI MSI (s) (C4:C8) [19:03:59:937]: SOURCEMGMT: Processing media source list. MSI (s) (C4:C8) [19:03:59:937]: Note: 1: 2203 2: 3: -2147287037 MSI (s) (C4:C8) [19:03:59:937]: SOURCEMGMT: Source is invalid due to missing/inaccessible package. MSI (s) (C4:C8) [19:03:59:937]: Note: 1: 1706 2: -2147483647 3: OWC11.MSI MSI (s) (C4:C8) [19:03:59:937]: SOURCEMGMT: Processing URL source list. MSI (s) (C4:C8) [19:03:59:937]: Note: 1: 1402 2: UNKNOWNURL 3: 2 MSI (s) (C4:C8) [19:03:59:937]: Note: 1: 1706 2: -2147483647 3: OWC11.MSI MSI (s) (C4:C8) [19:03:59:937]: Note: 1: 1706 2: 3: OWC11.MSI MSI (s) (C4:C8) [19:03:59:937]: SOURCEMGMT: Failed to resolve source MSI (s) (C4:C8) [19:04:30:953]: Product: Microsoft Office 2003 Web Components -- Error 1706. Setup cannot find the required files. Check your connection to the network, or CD-ROM drive. For other potential solutions to this problem, see C:Program FilesMicrosoft OfficeOFFICE111033SETUP.CHM.
View Replies !
Install Failure SQL Server Express 2005
I am unable to install SQL server that came with Visual Studio 2005 (academic edition). The log file "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFiles" is pasted below. Any ideas? thanks -------------- Microsoft SQL Server 2005 Setup beginning at Sun Apr 08 23:36:19 2007 Process ID : 2072 c:527d97359b188f6e74be1dsetup.exe Version: 2005.90.1399.0 Running: LoadResourcesAction at: 2007/3/8 23:36:18 Complete: LoadResourcesAction at: 2007/3/8 23:36:18, returned true Running: ParseBootstrapOptionsAction at: 2007/3/8 23:36:18 Loaded DLL:c:527d97359b188f6e74be1dxmlrw.dll Version:2.0.3604.0 Complete: ParseBootstrapOptionsAction at: 2007/3/8 23:36:19, returned false Error: Action "ParseBootstrapOptionsAction" failed during execution. Error information reported during run: Could not parse command line due to datastore exception. Source File Name: utillibpersisthelpers.cpp Compiler Timestamp: Fri Jul 29 01:13:55 2005 Function Name: writeEncryptedString Source Line Number: 124 ---------------------------------------------------------- writeEncryptedString() failed Source File Name: utillibpersisthelpers.cpp Compiler Timestamp: Fri Jul 29 01:13:55 2005 Function Name: writeEncryptedString Source Line Number: 123 ---------------------------------------------------------- Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified. Source File Name: cryptohelpercryptsameusersamemachine.cpp Compiler Timestamp: Mon Jun 13 14:30:00 2005 Function Name: sqls::CryptSameUserSameMachine:rotectData Source Line Number: 50 2 Could not skip Component update due to datastore exception. Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "InstallMediaPath" {"SetupBootstrapOptionsScope", "", "2072"} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupBootstrapOptionsScope.InstallMediaPath Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupBootstrapOptionsScope" Running: ValidateWinNTAction at: 2007/3/8 23:36:19 Complete: ValidateWinNTAction at: 2007/3/8 23:36:19, returned true Running: ValidateMinOSAction at: 2007/3/8 23:36:19 Complete: ValidateMinOSAction at: 2007/3/8 23:36:19, returned true Running: PerformSCCAction at: 2007/3/8 23:36:19 Complete: PerformSCCAction at: 2007/3/8 23:36:19, returned true Running: ActivateLoggingAction at: 2007/3/8 23:36:19 Error: Action "ActivateLoggingAction" threw an exception during execution. Error information reported during run: Datastore exception while trying to write logging properties. Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "primaryLogFiles" {"SetupStateScope", "", ""} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupStateScope.primaryLogFiles Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupStateScope" 00E5CFC4Unable to proceed with setup, there was a command line parsing error. : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified. Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupBootstrapOptionsScope.InstallMediaPath Source Line Number: 44 Class not registered. Failed to create CAB file due to datastore exception Source File Name: datastorecachedpropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: CachedPropertyCollection::findProperty Source Line Number: 130 ---------------------------------------------------------- Failed to find property "HostSetup" {"SetupBootstrapOptionsScope", "", "2072"} in cache Source File Name: datastorepropertycollection.cpp Compiler Timestamp: Fri Jul 29 01:13:50 2005 Function Name: SetupBootstrapOptionsScope.HostSetup Source Line Number: 44 ---------------------------------------------------------- No collector registered for scope: "SetupBootstrapOptionsScope" Message pump returning: 2
View Replies !
SQL Server 2005 Installation Failure On Vista
Help! I'm trying to install SQL Server 2005 on 32-bit Vista RTM. Have tried several editions (Developer, Standard, Enterprise). Have tried installing while logged in as domain user account in machine administrator group as well as built-in Administrator user. Running SETUP program with elevated privilges. Certain portions (Analysis services, Notification services) install correctly, but never the database engine. Always fails consistently with the same error reported. Machine has Visual Studio 2005 installed already, but NOT SQL Server 2005 Express Edition. Error logs reports are below ({computer name} is the name of my machine) UI error reported: TITLE: Microsoft SQL Server 2005 Setup ------------------------------ SQL Server Setup failed to execute a command for server configuration. The error was [Microsoft][SQL Native Client][SQL Server]Windows NT user or group '{computer name}SQLServer2005MSSQLUser${computer name}$MSSQLSERVER' not found. Check the name again.. Refer to the server error logs and Setup logs for detailed error information. Portion of Setup error log reports: SQL_SUCCESS_WITH_INFO (1) in OdbcConnection::connect sqlstate=01000, level=-1, state=-1, native_error=5701, msg=[Microsoft][SQL Native Client][SQL Server]Changed database context to 'master'. sqlstate=01000, level=-1, state=-1, native_error=5703, msg=[Microsoft][SQL Native Client][SQL Server]Changed language setting to us_english. SQL_SUCCESS_WITH_INFO (1) in OdbcStatement::execute_batch sqlstate=01000, level=0, state=1, native_error=5701, msg=[Microsoft][SQL Native Client][SQL Server]Changed database context to 'master'. SQL_SUCCESS_WITH_INFO (1) in OdbcStatement::execute_batch sqlstate=01000, level=0, state=1, native_error=15457, msg=[Microsoft][SQL Native Client][SQL Server]Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install. SQL_SUCCESS_WITH_INFO (1) in OdbcStatement::execute_batch sqlstate=01000, level=0, state=1, native_error=15457, msg=[Microsoft][SQL Native Client][SQL Server]Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install. sqlstate=01000, level=0, state=1, native_error=15457, msg=[Microsoft][SQL Native Client][SQL Server]Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install. SQL_SUCCESS_WITH_INFO (1) in OdbcStatement::execute_batch sqlstate=01000, level=0, state=1, native_error=15457, msg=[Microsoft][SQL Native Client][SQL Server]Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install. SQL_ERROR (-1) in OdbcStatement::execute_batch sqlstate=42000, level=11, state=1, native_error=15401, msg=[Microsoft][SQL Native Client][SQL Server]Windows NT user or group '{computer name}SQLServer2005MSSQLUser${computer name}$MSSQLSERVER' not found. Check the name again. sqlstate=42000, level=16, state=1, native_error=15007, msg=[Microsoft][SQL Native Client][SQL Server]'{computer name}SQLServer2005MSSQLUser${computer name}$MSSQLSERVER' is not a valid login or you do not have permission. Error Code: 0x80073c29 (15401) Windows Error Text: Source File Name: libodbc_statement.h Compiler Timestamp: Mon Jun 13 14:30:24 2005 Function Name: OdbcStatement::execute_batch@CnfgSQL@80 Source Line Number: 91
View Replies !
SQL Server 2005 SP1 Database Services Failure
Hi, I was trying to upgrade SQL server 2005 to SP1, to be able to install Team Foundation Server. However, I get a failure at the Database Services part. It sends an error report to Microsoft. Any help would be very much appreciated... Here's the logging: http://www.invenso.com/Logs.zip And these are the basic errors: 01/25/2007 13:00:07.234 ================================================================================ 01/25/2007 13:00:07.250 Hotfix package launched 01/25/2007 13:00:08.437 Product discovery successfully completed during the install process for MSSQLSERVER 01/25/2007 13:00:08.437 SP Level check successfully completed during the install process for MSSQLSERVER 01/25/2007 13:00:08.453 Product language check successfully completed during the install process for MSSQLSERVER 01/25/2007 13:00:08.468 Product version check successfully completed during the install process for MSSQLSERVER 01/25/2007 13:00:08.484 Command-line instance name check completed during the install process 01/25/2007 13:00:08.484 Baseline build check completed during the install process 01/25/2007 13:00:44.125 Attempting to install instance: MSSQLSERVER 01/25/2007 13:00:44.140 Attempting to install target: PESERVER1 01/25/2007 13:00:44.187 Attempting to stop service: MSSQLServer 01/25/2007 13:00:48.203 Successfully stopped service: MSSQLServer 01/25/2007 13:00:48.203 Attempting to check for locked files: sqlrun_sql.msp 01/25/2007 13:00:48.296 Attempting to check for locked files: \PESERVER1c$7df9321a724c583a5f25c26f2a35HotFixSQLFilessqlrun_sql.msp 01/25/2007 13:00:48.312 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out 01/25/2007 13:01:06.859 MSP returned 1602: The user cancels installation. 01/25/2007 13:01:06.921 Successfully checked file: \PESERVER1c$7df9321a724c583a5f25c26f2a35HotFixSQLFilessqlrun_sql.msp 01/25/2007 13:01:06.953 Successfully opened registry key: SystemCurrentControlSetControlSession Manager 01/25/2007 13:01:06.968 Failed to read registry key: PendingFileRenameOperations 01/25/2007 13:01:07.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll 01/25/2007 13:01:07.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll 01/25/2007 13:01:07.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll 01/25/2007 13:01:07.046 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll 01/25/2007 13:01:07.062 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnlhtml.dll 01/25/2007 13:01:07.078 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll 01/25/2007 13:01:07.078 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe 01/25/2007 13:01:07.093 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll 01/25/2007 13:01:07.109 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe 01/25/2007 13:01:07.125 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll 01/25/2007 13:01:07.140 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll 01/25/2007 13:01:07.156 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll 01/25/2007 13:01:07.156 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll 01/25/2007 13:01:07.171 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll 01/25/2007 13:01:07.187 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL 01/25/2007 13:01:07.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll 01/25/2007 13:01:07.203 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll 01/25/2007 13:01:07.218 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplrec.dll 01/25/2007 13:01:07.218 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM plisapi.dll 01/25/2007 13:01:07.234 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:WINDOWSassemblyGAC_32Microsoft.SqlServer.Replication9.0.242.0__89845dcd8080cc91Repl.dll 01/25/2007 13:01:07.250 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll 01/25/2007 13:01:07.250 Failed to read version information for the following file: C:Program FilesCommon FilesMicrosoft SharedDatabase ReplicationResources10332005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall plhtfin.sql 01/25/2007 13:01:07.265 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe 01/25/2007 13:01:07.281 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMsnapshot.exe 01/25/2007 13:01:07.281 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplmerg.exe 01/25/2007 13:01:07.296 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90COM ablediff.exe 01/25/2007 13:01:07.296 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe 01/25/2007 13:01:07.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe 01/25/2007 13:01:07.328 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources30822005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources2052sqlevn70.rll 01/25/2007 13:01:07.343 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10422005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1041sqlevn70.rll 01/25/2007 13:01:07.359 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10402005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1036sqlevn70.rll 01/25/2007 13:01:07.375 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10332005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1031sqlevn70.rll 01/25/2007 13:01:07.390 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources10282005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033XPStar90.RLL 01/25/2007 13:01:07.406 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 01/25/2007 13:01:07.406 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 01/25/2007 13:01:07.421 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 01/25/2007 13:01:07.437 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn6.6.3.5 C:Program FilesMicrosoft SQL Server90Sharedmsxmlsql.dll 01/25/2007 13:01:07.437 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2.0.3609.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlrw.dll 01/25/2007 13:01:07.437 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 01/25/2007 13:01:07.453 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 01/25/2007 13:01:07.468 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 01/25/2007 13:01:07.500 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLBOOT.dll 01/25/2007 13:01:07.546 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxplog70.dll 01/25/2007 13:01:07.609 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn2005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnatchp~1.dll 01/25/2007 13:01:07.625 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 01/25/2007 13:01:07.625 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 01/25/2007 13:01:07.640 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 01/25/2007 13:01:07.656 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 01/25/2007 13:01:07.656 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 01/25/2007 13:01:07.656 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 01/25/2007 13:01:07.671 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 01/25/2007 13:01:07.687 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 01/25/2007 13:01:07.687 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 01/25/2007 13:01:07.703 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 01/25/2007 13:01:07.703 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 01/25/2007 13:01:07.718 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 01/25/2007 13:01:07.734 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90SharedResources10339.0.2047.0 C:Program FilesMicrosoft SQL Server90Sharedmsmdrdir.dll 01/25/2007 13:01:07.750 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0 C:Program FilesCommon FilesSystemole dbxmlrw.dll 01/25/2007 13:01:07.765 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 01/25/2007 13:01:07.781 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 01/25/2007 13:01:07.781 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 01/25/2007 13:01:07.796 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 01/25/2007 13:01:07.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 01/25/2007 13:01:07.828 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 01/25/2007 13:01:07.843 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 01/25/2007 13:01:07.859 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 01/25/2007 13:01:07.875 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 01/25/2007 13:01:07.890 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml 01/25/2007 13:01:07.890 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll 01/25/2007 13:01:07.906 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll 01/25/2007 13:01:07.921 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033 C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml 01/25/2007 13:01:07.937 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 01/25/2007 13:01:07.953 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 01/25/2007 13:01:07.968 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 01/25/2007 13:01:07.984 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 01/25/2007 13:01:07.984 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 01/25/2007 13:01:08.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 01/25/2007 13:01:08.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 01/25/2007 13:01:08.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 01/25/2007 13:01:08.046 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 01/25/2007 13:01:08.062 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0 C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 01/25/2007 13:01:08.062 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0 C:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe 01/25/2007 13:01:08.093 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsvc~1.dll 01/25/2007 13:01:08.093 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 01/25/2007 13:01:08.109 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 01/25/2007 13:01:08.125 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 01/25/2007 13:01:08.140 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 01/25/2007 13:01:08.156 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 01/25/2007 13:01:08.171 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 01/25/2007 13:01:08.187 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 01/25/2007 13:01:08.187 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 01/25/2007 13:01:08.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 01/25/2007 13:01:08.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 01/25/2007 13:01:08.234 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 01/25/2007 13:01:08.250 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 01/25/2007 13:01:08.265 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe 01/25/2007 13:01:08.265 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0 C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll 01/25/2007 13:01:08.296 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 01/25/2007 13:01:08.296 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 01/25/2007 13:01:08.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 01/25/2007 13:01:08.328 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll 01/25/2007 13:01:08.343 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL 01/25/2007 13:01:08.359 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL 01/25/2007 13:01:08.375 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll 01/25/2007 13:01:08.390 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 01/25/2007 13:01:08.406 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 01/25/2007 13:01:08.421 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 01/25/2007 13:01:08.421 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll 01/25/2007 13:01:08.437 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll 01/25/2007 13:01:08.453 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll 01/25/2007 13:01:08.484 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll 01/25/2007 13:01:08.500 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll 01/25/2007 13:01:08.515 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlSAC.exe 01/25/2007 13:01:08.531 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedMicrosoft.SqlSac.Public.dll 01/25/2007 13:01:08.593 Attempting to install file: sqlrun_sql.msp 01/25/2007 13:01:08.640 Attempting to install file: \PESERVER1c$7df9321a724c583a5f25c26f2a35HotFixSQLFilessqlrun_sql.msp 01/25/2007 13:01:08.656 Creating MSP install log file at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log 01/25/2007 13:01:08.671 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 01/25/2007 13:01:08.687 Failed to read registry key: Debug 01/25/2007 13:02:47.859 MSP returned 1603: A fatal error occurred during installation. 01/25/2007 13:02:47.937 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 01/25/2007 13:02:47.953 Failed to read registry key: Debug 01/25/2007 13:02:47.968 Unable to install MSP file: \PESERVER1c$7df9321a724c583a5f25c26f2a35HotFixSQLFilessqlrun_sql.msp 01/25/2007 13:02:47.984 The following exception occurred: Unable to install Windows Installer MSP file Date: 01/25/2007 13:02:47.984 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 856 01/25/2007 13:02:48.078 01/25/2007 13:02:48.093 Product Status Summary: 01/25/2007 13:02:48.109 Product: SQL Server Native Client 01/25/2007 13:02:48.125 SQL Server Native Client (RTM ) - Success 01/25/2007 13:02:48.187 01/25/2007 13:02:48.203 Product: Setup Support Files 01/25/2007 13:02:48.218 Setup Support Files (RTM ) - Success 01/25/2007 13:02:48.234 01/25/2007 13:02:48.265 Product: Database Services 01/25/2007 13:02:48.281 Database Services (RTM 1399 ENU) - Failure 01/25/2007 13:02:48.281 Details: Unable to install Windows Installer MSP file 01/25/2007 13:02:48.296 Analysis Services (SP1 2047 ENU) - Not Applied 01/25/2007 13:02:48.312 Reporting Services (SP1 2047 ENU) - Not Applied 01/25/2007 13:02:48.328 01/25/2007 13:02:48.328 Product: Notification Services 01/25/2007 13:02:48.343 Notification Services (SP1 2047 ENU) - Not Applied 01/25/2007 13:02:48.359 01/25/2007 13:02:48.375 Product: Integration Services 01/25/2007 13:02:48.375 Integration Services (SP1 2047 ENU) - Not Applied 01/25/2007 13:02:48.390 01/25/2007 13:02:48.406 Product: Client Components 01/25/2007 13:02:48.421 Client Components (SP1 2047 ENU) - Not Applied 01/25/2007 13:02:48.437 01/25/2007 13:02:48.453 Product: MSXML 6.0 Parser 01/25/2007 13:02:48.468 MSXML 6.0 Parser (RTM ) - Not Applied 01/25/2007 13:02:48.484 01/25/2007 13:02:48.500 Product: SQLXML4 01/25/2007 13:02:48.515 SQLXML4 (RTM ) - Not Applied 01/25/2007 13:02:48.515 01/25/2007 13:02:48.531 Product: Backward Compatibility 01/25/2007 13:02:48.531 Backward Compatibility (RTM ) - Not Applied 01/25/2007 13:02:48.546 01/25/2007 13:02:48.562 Product: Microsoft SQL Server VSS Writer 01/25/2007 13:02:48.578 Microsoft SQL Server VSS Writer (RTM ) - Not Applied 01/25/2007 13:02:48.593 01/25/2007 13:11:46.921 Hotfix package closed
View Replies !
SQL Server 2005 Remote Connection Failure
I'm having a big problem with a SQL 2K5 cluster (using standard edition). I can get onto the box and connect to the sql server locally fine. However when I try to connect remotely I get errors. Let's call the two sides of the cluster, CL1 and CL2 and the "virtual server" is CL3. Locally I can connect without any problem at all to the SQL server, but I just can't connect to it from any remote machine. The server in question is instance name LMS_PRD running on CL3, port 10051. TCP/IP is definitely enabled for local and remote connections (I have checked this in the SQL server surface area configuration). I can connect locally without any problem. Also, locally, if I do, telnet CL3 10051 it connects fine From a SQL 2000 box - when I try to connect from sql query analyzer, I get "Unable to connect to server LMS_PRD Server Msg 17 ... SQL server does not exist or access denied" Client network utility shows server alias - LMS_PRD, TCP/IP, CL3LMS_PRD,10051 [I can connect to other SQL 2005 servers OK from this same server using this same method] On this box, when I do telnet CL3 10051 , I get "Connecting to CL3...Could not open a connection to host on port 10051 : Connect failed" [When I do a similar one for another SQL 2005 box, "telnet U01 10051", it connects fine] From another SQL 2005 box - when I try to register the server, I get "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP provider, error 0 - No connection could be made because thew target machine actively refused it.) (Microsoft SQL Server, Error: 10061)" IN the SQL native client configuration it shows alias name - CL3LMS_PRD, server=CL3LMS_PRD, protocol tcp, parameters 10051 Again if I do telnet CL3 10051, I get the error above. From this same box I can register another SQL 2005 server without any problem and do the telnet to it OK Just to emphasise: (a) The SQL server configuration manager shows that TCP/IP is enabled, and that 10051 is the port (in IPALL, TCP port). Also I have checked the SQL server errorlog - it is definitely using 10051 as the port. (b) The SQL server surface area configuration shows under local and remote connections using both TCP/IP and named pipes selected (I've tried both this and using the tcp/ip only option) (c) SQL server browser is running (d) There are NO firewalls etc involved Any help or advice MUCH appreciated
View Replies !
SQL Server 2005 Instance Connection Failure
This has me totally baffled. I have a default instance of SQL Server 2005 on a server and I installed a second instance on the same server. It worked fine until I rebooted the server. Now I cannot connect to the second instance. The error message mentions remote connections but I'm not trying to connect to the instance remotely. The entire error message is below. Has anyone come across this? =================================== Cannot connect to SERVERINSTANCENAME. =================================== An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - No connection could be made because the target machine actively refused it.) (.Net SqlClient Data Provider) ------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10061&LinkId=20476 ------------------------------ Error Number: 10061 Severity: 20 State: 0 ------------------------------ Program Location: at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server) at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
View Replies !
SQL Server Express 2005 Install Failure
I am attempting to install SQL Server express on an XP (SP2) machine with a Pentium processor. The .NET framework version is 2.0. All previous versions of SQL server and related components have been uninstalled, and all related files deleted. Also, during installation, I installed SQL Express using the local service account (vs. network service) per a suggestion in a related thread. I have installed/unistalled numerous times, and continue to receive the same error. At this point, this is becoming a critical issue related to a client ASP.NET application using a SQL express 2005 database. I was hoping by now that MS would have released a new version or patch that would solve this problem, but that does not seem to be the case, that I'm aware of. Summary Log: Microsoft SQL Server 2005 9.00.3042.00 ============================== OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600) Time : Tue Aug 21 14:59:31 2007 Machine : DEBASER1 Product : Microsoft SQL Server Setup Support Files (English) Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQLSupport_1.log -------------------------------------------------------------------------------- Machine : DEBASER1 Product : Microsoft SQL Server Native Client Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQLNCLI_1.log -------------------------------------------------------------------------------- Machine : DEBASER1 Product : Microsoft SQL Server VSS Writer Product Version : 9.00.3042.00 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SqlWriter_1.log -------------------------------------------------------------------------------- Machine : DEBASER1 Product : MSXML 6.0 Parser (KB933579) Product Version : 6.10.1200.0 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_MSXML6_1.log -------------------------------------------------------------------------------- Machine : DEBASER1 Product : SQL Server Database Services Error : 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." -------------------------------------------------------------------------------- Machine : DEBASER1 Product : Microsoft SQL Server 2005 Express Edition Product Version : 9.2.3042.00 Install : Failed Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQL.log Last Action : InstallFinalize Error String : 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 (3) The system cannot find the path specified. Error Number : 29503 -------------------------------------------------------------------------------- SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%Microsoft SQL Server90Setup BootstrapLOGSummary.txt. Time : Tue Aug 21 15:15:34 2007 List of log files: C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_Core(Local).log C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQLSupport_1.log C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQLNCLI_1.log C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SqlWriter_1.log C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_MSXML6_1.log C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SQL.log C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_Datastore.xml C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_.NET Framework 2.0.log C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_Support.log C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_Core.log C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSummary.txt C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_SCC.log C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_WI.log Core Log: Microsoft SQL Server 2005 Setup beginning at Tue Aug 21 14:59:31 2007 Process ID : 2960 c:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe Version: 2005.90.3042.0 Running: LoadResourcesAction at: 2007/7/21 14:59:31 Complete: LoadResourcesAction at: 2007/7/21 14:59:31, returned true Running: ParseBootstrapOptionsAction at: 2007/7/21 14:59:31 Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapxmlrw.dll Version:2.0.3609.0 Complete: ParseBootstrapOptionsAction at: 2007/7/21 14:59:31, returned true Running: ValidateWinNTAction at: 2007/7/21 14:59:31 Complete: ValidateWinNTAction at: 2007/7/21 14:59:31, returned true Running: ValidateMinOSAction at: 2007/7/21 14:59:31 Complete: ValidateMinOSAction at: 2007/7/21 14:59:31, returned true Running: PerformSCCAction at: 2007/7/21 14:59:31 Complete: PerformSCCAction at: 2007/7/21 14:59:31, returned true Running: ActivateLoggingAction at: 2007/7/21 14:59:31 Complete: ActivateLoggingAction at: 2007/7/21 14:59:31, returned true Running: DetectPatchedBootstrapAction at: 2007/7/21 14:59:31 Complete: DetectPatchedBootstrapAction at: 2007/7/21 14:59:31, returned true Action "LaunchPatchedBootstrapAction" will be skipped due to the following restrictions: Condition "EventCondition: __STP_LaunchPatchedBootstrap__2960" returned false. Action "BeginBootstrapLogicStage" will be skipped due to the following restrictions: Condition "Setup is running locally." returned true. Running: PerformDotNetCheck2 at: 2007/7/21 14:59:31 Complete: PerformDotNetCheck2 at: 2007/7/21 14:59:31, returned true Running: InvokeSqlSetupDllAction at: 2007/7/21 14:59:31 Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlspars.dll Version:2005.90.3042.0 <Func Name='DwLaunchMsiExec'> Examining 'sqlspars' globals to initialize 'SetupStateScope' Opening 'MachineConfigScope' for [DEBASER1] Trying to find Product Code from command line or passed transform If possible, determine install id and type Trying to find Instance Name from command line. No Instance Name provided on the command line If possible, determine action Machine = DEBASER1, Article = WMIServiceWin32OSWorking, Result = 0 (0x0) Machine = DEBASER1, Article = WMIServiceWin32CompSystemWorking, Result = 0 (0x0) Machine = DEBASER1, Article = WMIServiceWin32ProcessorWorking, Result = 0 (0x0) Machine = DEBASER1, Article = WMIServiceReadRegWorking, Result = 0 (0x0) Machine = DEBASER1, Article = WMIServiceWin32DirectoryWorking, Result = 0 (0x0) Machine = DEBASER1, Article = WMIServiceCIMDataWorking, Result = 0 (0x0) Machine = DEBASER1, Article = XMLDomDocument, Result = 0 (0x0) Machine = DEBASER1, Article = Processor, Result = 0 (0x0) Machine = DEBASER1, Article = PhysicalMemory, Result = 0 (0x0) Machine = DEBASER1, Article = DiskFreeSpace, Result = 0 (0x0) Machine = DEBASER1, Article = OSVersion, Result = 0 (0x0) Machine = DEBASER1, Article = OSServicePack, Result = 0 (0x0) Machine = DEBASER1, Article = OSType, Result = 0 (0x0) Machine = DEBASER1, Article = AdminShare, Result = 0 (0x0) Machine = DEBASER1, Article = PendingReboot, Result = 0 (0x0) Machine = DEBASER1, Article = IEVersion, Result = 0 (0x0) Machine = DEBASER1, Article = DriveWriteAccess, Result = 0 (0x0) Machine = DEBASER1, Article = COMPlus, Result = 0 (0x0) Machine = DEBASER1, Article = ASPNETVersionRegistration, Result = 0 (0x0) Machine = DEBASER1, Article = MDAC25Version, Result = 0 (0x0) Machine = DEBASER1, Article = SKUUpgrade, Result = 0 (0x0) ******************************************* Setup Consistency Check Report for Machine: DEBASER1 ******************************************* Article: WMI Service Requirement, Result: CheckPassed Article: MSXML Requirement, Result: CheckPassed Article: Operating System Minimum Level Requirement, Result: CheckPassed Article: Operating System Service Pack Level Requirement, Result: CheckPassed Article: SQL Compatibility With Operating System, Result: CheckPassed Article: Minimum Hardware Requirement, Result: CheckPassed Article: Pending Reboot Requirement, Result: CheckPassed Article: Default Installation Path Permission Requirement, Result: CheckPassed Article: Internet Explorer Requirement, Result: CheckPassed Article: Check COM+ Catalogue, Result: CheckPassed Article: ASP.Net Registration Requirement, Result: CheckPassed Article: Minimum MDAC Version Requirement, Result: CheckPassed Article: Edition Upgrade Check, Result: CheckPassed <Func Name='PerformDetections'> 0 <EndFunc Name='PerformDetections' Return='0' GetLastError='0'> <Func Name='DisplaySCCWizard'> CSetupBootstrapWizard returned 1 <EndFunc Name='DisplaySCCWizard' Return='0' GetLastError='183'> Loaded DLL:c:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.3042.0 <EndFunc Name='DwLaunchMsiExec' Return='0' GetLastError='0'> Complete: InvokeSqlSetupDllAction at: 2007/7/21 15:0:29, returned true Running: SetPackageInstallStateAction at: 2007/7/21 15:0:29 Complete: SetPackageInstallStateAction at: 2007/7/21 15:0:29, returned true Running: DeterminePackageTransformsAction at: 2007/7/21 15:0:29 Complete: DeterminePackageTransformsAction at: 2007/7/21 15:0:30, returned true Running: ValidateSetupPropertiesAction at: 2007/7/21 15:0:30 Complete: ValidateSetupPropertiesAction at: 2007/7/21 15:0:30, returned true Running: OpenPipeAction at: 2007/7/21 15:0:30 Complete: OpenPipeAction at: 2007/7/21 15:0:30, returned false Error: Action "OpenPipeAction" failed during execution. Running: CreatePipeAction at: 2007/7/21 15:0:30 Complete: CreatePipeAction at: 2007/7/21 15:0:30, returned false Error: Action "CreatePipeAction" failed during execution. Action "RunRemoteSetupAction" will be skipped due to the following restrictions: Condition "Action: CreatePipeAction has finished and passed." returned false. Running: PopulateMutatorDbAction at: 2007/7/21 15:0:30 Complete: PopulateMutatorDbAction at: 2007/7/21 15:0:30, returned true Running: GenerateRequestsAction at: 2007/7/21 15:0:30 SQL_Engine = 3 SQL_Data_Files = 3 SQL_Replication = -1 SQL_FullText = -1 SQL_SharedTools = 3 SQL_BC_DEP = -1 Analysis_Server = -1 AnalysisDataFiles = -1 AnalysisSharedTools = -1 RS_Server = -1 RS_Web_Interface = -1 RS_SharedTools = -1 Notification_Services = -1 NS_Engine = -1 NS_Client = -1 SQL_DTS = -1 Client_Components = -1 Connectivity = -1 SQL_Tools90 = -1 SQL_WarehouseDevWorkbench = -1 SDK = -1 SQLXML = -1 Tools_Legacy = -1 TOOLS_BC_DEP = -1 SQL_SSMSEE = -1 SQL_Documentation = -1 SQL_BooksOnline = -1 SQL_DatabaseSamples = -1 SQL_AdventureWorksSamples = -1 SQL_AdventureWorksDWSamples = -1 SQL_AdventureWorksASSamples = -1 SQL_Samples = -1 Complete: GenerateRequestsAction at: 2007/7/21 15:0:32, returned true Running: CreateProgressWindowAction at: 2007/7/21 15:0:32 Complete: CreateProgressWindowAction at: 2007/7/21 15:0:32, returned true Running: ScheduleActionAction at: 2007/7/21 15:0:32 Complete: ScheduleActionAction at: 2007/7/21 15:0:33, returned true Skipped: InstallASAction.11 Skipped: Action "InstallASAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.18 Skipped: Action "InstallASAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.22 Skipped: Action "InstallASAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "as", install will be skipped as a result. Skipped: InstallASAction.9 Skipped: Action "InstallASAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "as", install will be skipped as a result. Skipped: InstallDTSAction Skipped: Action "InstallDTSAction" was not run. Information reported during analysis: No install request found for package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.11 Skipped: Action "InstallDTSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.12 Skipped: Action "InstallDTSAction.12" was not run. Information reported during analysis: No install request found for package: "sqlncli", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.18 Skipped: Action "InstallDTSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.22 Skipped: Action "InstallDTSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "dts", install will be skipped as a result. Skipped: InstallDTSAction.9 Skipped: Action "InstallDTSAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "dts", install will be skipped as a result. Skipped: InstallNSAction Skipped: Action "InstallNSAction" was not run. Information reported during analysis: No install request found for package: "ns", install will be skipped as a result. Skipped: InstallNSAction.11 Skipped: Action "InstallNSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.12 Skipped: Action "InstallNSAction.12" was not run. Information reported during analysis: No install request found for package: "sqlncli", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.18 Skipped: Action "InstallNSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.22 Skipped: Action "InstallNSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "ns", install will be skipped as a result. Skipped: InstallNSAction.9 Skipped: Action "InstallNSAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "ns", install will be skipped as a result. Skipped: InstallRSAction.11 Skipped: Action "InstallRSAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "rs", install will be skipped as a result. Skipped: InstallRSAction.18 Skipped: Action "InstallRSAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "rs", install will be skipped as a result. Skipped: InstallRSAction.22 Skipped: Action "InstallRSAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "rs", install will be skipped as a result. Running: InstallSqlAction.11 at: 2007/7/21 15:0:33 Installing: sqlsupport on target: DEBASER1 Complete: InstallSqlAction.11 at: 2007/7/21 15:11:8, returned true Running: InstallSqlAction.12 at: 2007/7/21 15:11:8 Installing: sqlncli on target: DEBASER1 Complete: InstallSqlAction.12 at: 2007/7/21 15:11:17, returned true Skipped: InstallSqlAction.18 Skipped: Action "InstallSqlAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "sql", install will be skipped as a result. Running: InstallSqlAction.21 at: 2007/7/21 15:11:17 Installing: sqlwriter on target: DEBASER1 Complete: InstallSqlAction.21 at: 2007/7/21 15:11:22, returned true Skipped: InstallSqlAction.22 Skipped: Action "InstallSqlAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "sql", install will be skipped as a result. Running: InstallSqlAction.9 at: 2007/7/21 15:11:22 Installing: msxml6 on target: DEBASER1 Complete: InstallSqlAction.9 at: 2007/7/21 15:11:24, returned true Skipped: InstallToolsAction.11 Skipped: Action "InstallToolsAction.11" was not run. Information reported during analysis: No install request found for package: "sqlsupport", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.12 Skipped: Action "InstallToolsAction.12" was not run. Information reported during analysis: No install request found for package: "sqlncli", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.13 Skipped: Action "InstallToolsAction.13" was not run. Information reported during analysis: No install request found for package: "PPESku", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.18 Skipped: Action "InstallToolsAction.18" was not run. Information reported during analysis: No install request found for package: "owc11", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.20 Skipped: Action "InstallToolsAction.20" was not run. Information reported during analysis: No install request found for package: "BOL", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.22 Skipped: Action "InstallToolsAction.22" was not run. Information reported during analysis: No install request found for package: "bcRedist", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.23 Skipped: Action "InstallToolsAction.23" was not run. Information reported during analysis: No install request found for package: "ssmsee", referred by package: "tools", install will be skipped as a result. Skipped: InstallToolsAction.9 Skipped: Action "InstallToolsAction.9" was not run. Information reported during analysis: No install request found for package: "msxml6", referred by package: "tools", install will be skipped as a result. Skipped: InstallNSAction.10 Skipped: Action "InstallNSAction.10" was not run. Information reported during analysis: No install request found for package: "sqlxml4", referred by package: "ns", install will be skipped as a result. Running: InstallSqlAction at: 2007/7/21 15:11:25 Installing: sql on target: DEBASER1 Failed to install package Fatal error during installation. Setting package return code to: 29503 Complete: InstallSqlAction at: 2007/7/21 15:15:29, returned false Error: Action "InstallSqlAction" failed during execution. Error information reported during run: Target collection includes the local machine. Invoking installPackage() on local machine. Skipped: InstallToolsAction.10 Skipped: Action "InstallToolsAction.10" was not run. Information reported during analysis: No install request found for package: "sqlxml4", referred by package: "tools", install will be skipped as a result. Skipped: InstallASAction Skipped: Action "InstallASAction" was not run. Information reported during analysis: No install request found for package: "as", install will be skipped as a result. Skipped: InstallRSAction Skipped: Action "InstallRSAction" was not run. Information reported during analysis: No install request found for package: "rs", install will be skipped as a result. Skipped: InstallToolsAction Skipped: Action "InstallToolsAction" was not run. Information reported during analysis: No install request found for package: "tools", install will be skipped as a result. Skipped: RepairForBackwardsCompatRedistAction Skipped: Action "RepairForBackwardsCompatRedistAction" was not run. Information reported during analysis: Action: "RepairForBackwardsCompatRedistAction" will be skipped due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Error: Action "UninstallForMSDE2000Action" failed during execution. Error information reported during run: Action: "UninstallForMSDE2000Action" will be marked as failed due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Installation of package: "patchMSDE2000" failed due to a precondition. Error: Action "UninstallForSQLAction" failed during execution. Error information reported during run: Action: "UninstallForSQLAction" will be marked as failed due to the following condition: Condition "sql was successfully upgraded." returned false. Condition context: sql failed to upgrade and so the uninstall of the upgraded product will not occur. Installation of package: "patchLibertySql" failed due to a precondition. Skipped: UninstallForRS2000Action Skipped: Action "UninstallForRS2000Action" was not run. Information reported during analysis: Action: "UninstallForRS2000Action" will be skipped due to the following condition: Condition "Action: InstallRSAction was skipped." returned true. Error: Action "ExposeVistaClusteredResources" failed during execution. Error information reported during run: Action: "ExposeVistaClusteredResources" will be marked as failed due to the following condition: Condition "The Clustered SQL Server instance that hosts is installed." returned false. Running: ReportChainingResults at: 2007/7/21 15:15:29 Error: Action "ReportChainingResults" threw an exception during execution. One or more packages failed to install. Refer to logs for error details. : 3 Error Code: 0x80070003 (3) Windows Error Text: The system cannot find the path specified. Source File Name: sqlchainingsqlchainingactions.cpp Compiler Timestamp: Thu Nov 16 20:31:57 2006 Function Name: sqls::ReportChainingResults:erform Source Line Number: 3521 ---- Context ----------------------------------------------- sqls::HostSetupPackageInstallerSynch:ostCommit sqls::HighlyAvailablePackage:reInstall led due to cancel code received from cancel source: 29539 Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DEBASER1_.NET Framework 2.0.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code : 2 Running: UploadDrWatsonLogAction at: 2007/7/21 15:15:42 Message pump returning: 3 Any ideas ... ? Carlo
View Replies !
SQL Server 2005 Express : Installation Failure !
When i try to install SQL server 2005 Express, French version (after installation of : Framework 2.0, Visual Web Developper), i get the following error : "Le programme d'installation de SQL server 2005 a dĂ©tectĂ© des composants incompatibles des versions bĂȘta de visual studio, de .NET Framework ou de SQL server 2005. Supprimer ces composants Ă l'aide de Ajout ou suppression de programmes, puis exĂ©cuter Ă nouveau le programme d'installation de SQL server 2005. Pour des instructions dĂ©taillĂ©es sur la dĂ©sinstallation de SQL Server 2005, voir le fichier lisez-moi de SQL server 2005." I removed all old versions ! Thank's for help
View Replies !
An Error Has Occurred While Establishing A Connection To The Server. When Connecting To SQL Server 2005, This Failure May Be Caused By The Fact That Under The Default Settings SQL Server Does Not Allow Remote Connections. (provider: SQL Network Interfa
I get the following error and have been trying to figure out why I keep getting it. Initially, I had placed my project under wwwroot folder and ran it under IIS and it gave this error. Then I moved it to my local C drive and same thing. I am sharing this project with two other co-workers and all our config files and code files are same...they don't get this error but I do. I checked that SQL Server Client Network Utility has TCP/IP and the 'Named Pipes' enabled. I thought maybe I have setting in the Visual Studio 2005 that I'm not aware of that's causing this problem...it can't be the server since my co-workers aren't having this error and can't be anything in the code since all of us are sharing this project through vss. I dont' think using different version of .net framework can create this error. I changed the version from 2.0 to use 1.1x and it gave same error... Any help would be greatly appreciated. Thanks in advance. Server Error in '/RBOdev' Application. An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)Source Error: An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below. Stack Trace: [SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +739123 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) +685966 System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) +109 System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) +383 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +181 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +130 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84 System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197 System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider.GetConnectionHolder() +16 System.Web.UI.WebControls.WebParts.SqlPersonalizationProvider.LoadPersonalizationBlobs(WebPartManager webPartManager, String path, String userName, Byte[]& sharedDataBlob, Byte[]& userDataBlob) +195 System.Web.UI.WebControls.WebParts.PersonalizationProvider.LoadPersonalizationState(WebPartManager webPartManager, Boolean ignoreCurrentUser) +95 System.Web.UI.WebControls.WebParts.WebPartPersonalization.Load() +105 System.Web.UI.WebControls.WebParts.WebPartManager.OnInit(EventArgs e) +497 System.Web.UI.Control.InitRecursive(Control namingContainer) +321 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Control.InitRecursive(Control namingContainer) +198 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +692 Version Information: Microsoft .NET Framework Version:2.0.50727.832; ASP.NET Version:2.0.50727.832
View Replies !
Using Composition To Create New Specialised Components From Multiple Sub-components?
Hi, In another thread Jamie Thomson very informatively said "The components in SSIS are deliberately atomic (i.e. they do something very specific) so that its easy to put them together to build something greater than the sum of the parts". Which does make a lot of sense. However, I've been finding that I end up having to create exactly the same "pattern" of combined transform components again and again in order to solve the same problem but in different dataflows (or even within the same dataflow). Cut-and-paste-tastic! In order to obtain real re-use, it seems to me like SSIS is crying out for an easy way to create new components by using composition - i.e. the ability to take commonly-used combinations of existing components and create new "super" components (without having to write Custom Transform Components in C#/VB.Net and handle everything in code). Does anyone know if this sort of functionality is likely to make it into SSIS in the forseeable future? Regards, Lawrie
View Replies !
|
TRACKER
