I am getting an error when installing SP3a of MSDE. I get the error message "The instance name specified is invalid." This is the first SQL database installed, so there is no instance name. I have tried "default" and "MSSQLSERVER" as instance names without success.
But it gets through the install, then the progress bar goes backwards and it uninstalled, I tried to enable logging and do /q+ but none of this gives usable information, i have redownloaded the MSDE SP3 install files and this has changed nothing, I know this is a common problem as I have seen a few sites mention it, but i can't seem to find the fix.
I am attempting to install SQL 2000 onto a new Win2K Advanced server and it fails. Event log shows event id:4097 with an exception error @ c0000005. Install progress achieves 99% and just hangs at that point. I cannot find anything relating to this issue, any ideas?
Now that support for SQL SP3a has been removed, how does this affect MSDE installations? We've got lots of products installed that have come with MSDE backends, all on SP3a. Is it up to the individual vendors as to whether they continue to support on this version? Backup Exec and Insight Manager are 2 that spring to mind.
Hi, I'm trying to upgrade MSDE with SP4. I used the following in command prompt. setup /upgradesp sqlrun INSTANCENAME=MSDEINSTANCE SECURITYMODE=SQL UPGRADEUSER=username UPGRADEPWD=userpassword /L*v C:MSDELog.log i got the message "Please go the control panel to install and configure system components." What does it mean? How to upgrade it?I have tried to edit the line with *V, and using the sa username and password, but i get the same message. RegardsKenneth Davidsen
I just upgraded my desktop engine MSDE 1.0 to MSDE 2000 SP3a. Everything seemed to go well, MSSQLSERVER AND SQLSERVER Agent Services are running, problem is, I can no longer see the particular instance on the network from Enterprise Manager.
The installation instructions specified that if the Instance was to accept connections from applications on other computers not to specify the DISABLENETWORKPROTOCOLS parameter, so I didn't.
I'm a little green with this, can anyone suggest a place to start troubleshooting?
The process proceeds then a pop-up says the installation failed. The log reports:
--------------- 2004-11-04 15:07:21.30 server Microsoft SQL Server 2000 - 8.00.760 (Intel X86) Dec 17 2002 14:22:05 Copyright (c) 1988-2003 Microsoft Corporation Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
2004-11-04 15:07:21.35 server Copyright (C) 1988-2002 Microsoft Corporation. 2004-11-04 15:07:21.35 server All rights reserved. 2004-11-04 15:07:21.35 server Server Process ID is 1904. 2004-11-04 15:07:21.35 server Logging SQL Server messages in file 'C:librarydataMSSQLLOGERRORLOG'. 2004-11-04 15:07:21.41 server SQL Server is starting at priority class 'normal'(1 CPU detected). 2004-11-04 15:07:21.64 server SQL Server configured for thread mode processing. 2004-11-04 15:07:21.65 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks. 2004-11-04 15:07:21.94 spid3 Warning ****************** 2004-11-04 15:07:21.94 spid3 SQL Server started in single user mode. Updates allowed to system catalogs. 2004-11-04 15:07:22.03 spid3 Starting up database 'master'. 2004-11-04 15:07:22.83 server Using 'SSNETLIB.DLL' version '8.0.766'. 2004-11-04 15:07:22.83 spid5 Starting up database 'model'. 2004-11-04 15:07:22.96 spid3 Server name is 'MJWLAP2'. 2004-11-04 15:07:22.96 spid3 Skipping startup of clean database id 5 2004-11-04 15:07:23.00 spid3 Skipping startup of clean database id 6 2004-11-04 15:07:23.00 spid3 Starting up database 'msdb'. 2004-11-04 15:07:23.51 spid5 Clearing tempdb database. 2004-11-04 15:07:24.34 spid5 Starting up database 'tempdb'. 2004-11-04 15:07:24.53 spid3 Recovery complete. 2004-11-04 15:07:24.53 spid3 SQL global counter collection task is created. 2004-11-04 15:07:24.60 spid3 Warning: override, autoexec procedures skipped. 2004-11-04 15:07:25.56 server SQL server listening on . 2004-11-04 15:07:25.58 server Error: 17826, Severity: 18, State: 1 2004-11-04 15:07:25.58 server Could not set up Net-Library 'SSNETLIB'.. 2004-11-04 15:07:25.58 server Unable to load any netlibs. 2004-11-04 15:07:25.59 server SQL Server could not spawn FRunCM thread. -------------------------
I am developing a project in Vb.net using MSDE 2000 as backend. I want to deployment my project in win98 OS PCs. is it possible to install msde 2000 in win98
We have the rtm version of SQL 2000 and have spent the last 2.5 hours trying to apply SP3a. Nothing on the microsoft support site has pointed us to the solution.
Basically, we start the install after shutting down the services, answer all the questions and then when it starts to copy files it fails with an error 'microsoft data access component failed (-1).
Looking in c:winntdatestup.log, the error is unknown. The c:winntsqlsrp.log file is not touched.
We tried renaming the odbcconf.dll file per a microsoft article and no joy.
We also restored mdac_type.exe file per microsoft article and no joy.
Trying to install SP1 and SP2 - same results.
Anyone got any ideas besides it's time to call Microsoft? :confused:
Hi,I'm trying to install MSDE Desktop SP3a SQL server on my Windows 2000 Professional Laptop.Every time I try it nearly finishes the installation and then just rollsback.Can anyone help? Is this a known issue?Thanks in advance,Jocky
It's arriving from ebuyer tomorrow for 32 quid. I already have aninstance of MSDE running on the laptop and ideally i would like SQLserver to be installed and use the current instance and not installany other additional services. [hope i got my terminology correcthere.] Basically all i would like is to use the Enterprise Managerwith my existing MSDE database. I was wondering if there is anything ishould be doing before I install. Should i shut down the service orleave it running for instance.Thanks for any tips,AndyB
Our environment is currently running on SQL 2000 sp3a (win2003) and I'm having an issue with 'max worker threads', so I opened a ticket with Microsoft. They tell me that SP3a is no longer support and I have to upgrade all our servers to SP4.
We had an issue in my previous company and I was told by a consultant that I shouldn't install SP4 because it caused a lot of issues. I'm aware of the 'AWE enabled' issue, are there any others I should watch out for?
Hi, I've downloaded the SP3a for sql server from the microsoft website. I unpackaged the files into a folder and ran the file setup.bat. I recieved an error that setupsql.exe file was not found. I think theres a folder missing called Setup under the X86 folder. Is there a way I can fix this????????
I got this message from Backup Exec for Windows Servers Environment Check 1.0 for SBS1 QUOTE
An instance of Microsoft SQL 2000 was found that is not updated to Service Pack 3a.
An instance of Microsoft SQL Server was found that is not updated to the correct service pack. Using this SQL Server instance with Backup Exec may cause errors. To install Backup Exec successfully, upgrade this SQL Server to Service Pack 3a, or select another instance.
Here's my situation:I have an ODBC DSN setup for Timberline Data (An accounting packagethat uses pervasive.sql) on my sql box. I set up a linked server usingthe supplied timberline odbc driver. I have two sql instances setup,the default instance and a named instance. On the default instance,the linked server works great no matter who is logged in using it (allauthentication is NT integrated). However on the named instance onlythe NT account that the MSSqlserver$NAMED service is logged in undercan utilize the linked server. All others get a ODBC error:"error 7399: OLE DB Provider 'MSDASQL' reported an error. AccessDenied. OLE DB error trace [OLE/DB Provider 'MSDASQL'IUnknown::QueryInterface returned 0x80070005: Access Denied.]."Far as i can tell, both instances are setup the same, except that oneis the default and one is a named instance.Why the different results for the default instance vs a named instance.Any ideas?Thanks
I installed a MSDE on a Windows XP SP2 and configured it for accepting remote connections. But It shows the "SQL Server doesnot exist or connection denied" message whenever I try to connect to this server. For more information I am adding more facts
* It is an MSDE and not a WMSDE * Firewall is turned off * Server process is listening on 0.0.0.0:1433 * TCP/IP and Named Pipes are enabled using server network utility * LoginMode=2 is set for mixed mode authentication in the registry * Tried restaring the Process and even windows after the changes.
We just upgraded 2 sql servers from sql server 2000 sp3a to sql server 2005 build 2153, and merge rep exists between these 2 servers.
However, after sql server upgrade, we had to reinitialize merge replication and now the merge agent is reporting 2 errors
1)
Error messages:
The Merge Agent failed to upgrade triggers, metadata and stored procedures on the Subscriber to versions compatible with SQL Server 2005. Restart synchronization, and if this failure continues to occur reinitialize the subscription. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199403) Get help: http://help/MSSQL_REPL-2147199403
Invalid column name 'metadata_select_proc'. (Source: MSSQLServer, Error number: 207) Get help: http://help/207
Invalid column name 'delete_proc'. (Source: MSSQLServer, Error number: 207) Get help: http://help/207
The merge process could not connect to the Publisher 'Server:database'. Check to ensure that the server is running. (Source: MSSQL_REPL, Error number: MSSQL_REPL-2147199368) Get help: http://help/MSSQL_REPL-2147199368
Another merge agent for the subscription(s) is running or the server is working on a previous request by the same agent. (Source: MSSQLServer, Error number: 21036) Get help: http://help/21036
looking inside the sp_MSensure_single_instance stored procedure, it's trying to obtain an exclusive lock on resource 'Merge Agent Name' but fails and returns -1
this is the stored procedure executed by sp_MSensure_single_instance and @retcode = -1 and thus cannot obtain exclusive lock on resource
so i think it's failing because for some reason MSmerge_PAL_role database role does not have enough rights to obtain exclusive lock on necessary resources
i've tried many things to fix this, including scripting out and dropping all merge rep, turning off replication db option and reapplying replication create scripts on the server, and even manually deleting the MSmerge_PAL_role database role but still doesn't work
Recently I witnessed a failed SQL 7 Enterprise installation due to an access error on an ado file. Apparently SQL Server was trying to copy an active x component that was already in use when the error occured. Anyone have experience with this?
I have a fresh install of MS SQL 2005 Developer Edition on my local box. I have just tried to install SP2 and the status reads "failure" for the product "Database Services", instance "MSSQLSERVER".
What could cause this? Do I need to turn of the service before applying the service pack? I supplied it the proper credentials which tested ok during the beginning of install...
Should I just try to install the patch again? How can I verify that the patch has been successfully applied?
I'm running SP2 to upgrade my current instance of SP1. At the point of "SQL Server Database Services | Configuring components..." it stops with the following error:
##### Microsoft SQL Server 2005 Setup ------------------------------ The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed #####
The setup log contains the following detail in the "LaunchFunction"
##### <Func Name='LaunchFunction'> Function=ValidateUpgrade <Func Name='SetCAContext'> <EndFunc Name='SetCAContext' Return='T' GetLastError='203'> Doing Action: ValidateUpgrade PerfTime Start: ValidateUpgrade : Tue Feb 27 09:47:13 2007 <Func Name='ValidateUpgrade'> <Func Name='updateFeatureSellection'> <Func Name='SqlComponentUpgrade'> <Func Name='SetCAContext'> <EndFunc Name='SetCAContext' Return='T' GetLastError='203'> <Func Name='ProcessHeaderTable'> <Func Name='ProcessScriptTable'> <Func Name='GetFileTargetPath'> <Func Name='GetFileTargetPath'> <Func Name='GetFileTargetPath'> <Func Name='GetFileTargetPath'> <Func Name='GetFileTargetPath'> <Func Name='GetFileTargetPath'> <Func Name='GetFileTargetPath'> <Func Name='ProcessScriptTable'> <Func Name='GetFileTargetPath'> MSI (s) (34!60) [09:47:13:296]: Note: 1: 2205 2: 3: _sqlSqlUpgradeInstallSequence MSI (s) (34!60) [09:47:13:296]: Note: 1: 2228 2: 3: _sqlSqlUpgradeInstallSequence 4: CREATE TABLE `_sqlSqlUpgradeInstallSequence` (`Action` CHAR(255) NOT NULL, `Sequence` INT NOT NULL, `Param` CHAR(0), `Retryable` INT NOT NULL, `Fatal` INT NOT NULL PRIMARY KEY `Action`, `Sequence`) MSI (s) (34!60) [09:47:13:296]: Note: 1: 2262 2: _sqlSqlUpgradeInstallSequence 3: -2147287038 <Func Name='GetFileTargetPath'> MSI (s) (34!60) [09:47:13:328]: PROPERTY CHANGE: Adding Sql_sqlSqlUpgradeInstallSequence property. Its value is '15000000'. MSI (s) (34!60) [09:47:13:328]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '15000000'. Its new value: '15040000'. MSI (s) (34!60) [09:47:13:328]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '15040000'. Its new value: '15050000'. MSI (s) (34!60) [09:47:13:343]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '15050000'. Its new value: '85050000'. MSI (s) (34!60) [09:47:13:343]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '85050000'. Its new value: '265604600'. MSI (s) (34!60) [09:47:13:343]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '265604600'. Its new value: '280604600'. MSI (s) (34!60) [09:47:13:343]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '280604600'. Its new value: '310604600'. MSI (s) (34!60) [09:47:13:343]: PROPERTY CHANGE: Modifying Sql_sqlSqlUpgradeInstallSequence property. Its current value is '310604600'. Its new value: '310704600'. Couldn't find SQL Agent service SQLAgent$GATEKEEPER. Skipping service stop <EndFunc Name='SqlComponentUpgrade' Return='0' GetLastError='0'> Added REPL to SqlUpgrade property <Func Name='updateFeatureSellection'> Attempt to start service when it is already running SQL service MSSQL$GATEKEEPER started successfully waiting for SQL service to accept client connections 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.
Setting status of unmanaged components and removing unmanaged resources Failed to modify installer view 1: 2259 2: 3: 4:
Error Code: 1627 MSI (s) (34!60) [09:53:40:125]: Product: Microsoft SQL Server 2005 Express Edition -- Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed
Error 2259. The installer has encountered an unexpected error. The error code is 2259. Database: Table(s) Update failed <Failure Type='Fatal' Error='1627'> <EndFunc Name='LaunchFunction' Return='1627' GetLastError='203'>
#####
I have installed the same SP2 on another machine (Both XP SP2) without further problems. The only difference between the two machines is the one with errors has another instance of SQL 2005 (Not express) as the default instance and the Express named instance I am upgraded. The second machine only has Express named instance.
When I run SharePointRS.msi it ends and rolls back with a failure. Looking at the log i get the following:
copyappbincontents command completed successfully. Adding Report Server feature to farm. Install error: Failed to find the XML file at location '12TemplateFeaturesReportServerfeature.xml' Uninstalling Report Server feature. Uninstalling Report Server feature. Report Server feature was uninstalled. Stopping W3SVC service. Removing Report Server web application files Removed file d:InetpubwwwrootwssVirtualDirectories8088App_GlobalResourcesReportServer.resx. Removed file d:InetpubwwwrootwssVirtualDirectories80App_GlobalResourcesReportServer.resx. Removed file d:InetpubwwwrootwssVirtualDirectories8080App_GlobalResourcesReportServer.resx. Removed file d:InetpubwwwrootwssVirtualDirectories36881App_GlobalResourcesReportServer.resx. Removing DocIcon.xml file updates Beginning uninstall of cab files. Cab files uninstalled successfully. Starting W3SVC service. SSRSCustomActionError: Failed to find the XML file at location '12TemplateFeaturesReportServerfeature.xml'
Any ideas on how to fix this? I would have thought that the FeaturesReportServerfeature.xml file would be created by the installer.
I have tried redownloading and re running the installer.
This is running on SQL 2005 with SP2 and MOSS 2007 on the same box.
I have attempted to install SP1 on to my SQL 2005 Server numerous times and cannot get it to be successful. It failes on database services everytime and the log and event log report that my account cannot change permissions on the Data directory. My system is running Server 2003 R2 Ent x64. I have a Cluster setup with no second node at this time (future additon). I am also using a mount point inside the Data directory for logs. I have monitored the install using FileMon and do not see any file access issues during the installation process. I have also looked at the files and directories within the Data directory and all security ACLs seem fine. I am running the install with an account that has admin permission on the box. The service account I am using to run the sql service does not have admin permission but it is in the groups that SQL sets up at install time and those groups are assigned to the Data directory and other directories that the install configures. Any and all help us greatly appriciated!!
I've been bulldozing thru a SQL Dev Ed Install. Now I am at the point that many services have been installed but overall the install failed. I do install from cmd prompt (command line). This is how I ran it:
This cmd line is actually a one after a small correction. The clause highlighed was put before ADDLOCAL=ALL. I assumed that cause the problem and changed the position of the clause but now when I tried to run the same command again I got an error that access was denied. This is the first time I got this error.
These are error messages from summary.txt of the run that I consider to be partially successful:
Machine : DDMNVT61 Product : SQL Server Database Services Error : Could not access network location INSTALLSQLDIRData. -------------------------------------------------------------------------------- Machine : DDMNVT61 Product : SQL Server Database Services Error : Could not access network location INSTALLSQLDIRData. -------------------------------------------------------------------------------- Machine : DDMNVT61 Product : Microsoft SQL Server 2005 Product Version : 9.00.1399.06 Install : Failed Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_DDMNVT61_SQL.log Last Action : CostFinalize Error String : Could not access network location INSTALLSQLDIRData. Error Number : 1606 ---------------------------------------------------------------------------------
Machine : DDMNVT61 Product : Analysis Services Error : SQL Server Setup could not validate the service accounts. Either the service accounts have not been provided for all of the services being installed, or the specified username or password is incorrect. For each service, specify a valid username, password, and domain, or specify a built-in system account. -------------------------------------------------------------------------------- Machine : DDMNVT61 Product : Analysis Services Error : SQL Server Setup could not validate the service accounts. Either the service accounts have not been provided for all of the services being installed, or the specified username or password is incorrect. For each service, specify a valid username, password, and domain, or specify a built-in system account. -------------------------------------------------------------------------------- Machine : DDMNVT61 Product : Microsoft SQL Server 2005 Analysis Services Product Version : 9.00.1399.06 Install : Failed Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0005_DDMNVT61_AS.log Last Action : Validate_ServiceAccounts Error String : SQL Server Setup could not validate the service accounts. Either the service accounts have not been provided for all of the services being installed, or the specified username or password is incorrect. For each service, specify a valid username, password, and domain, or specify a built-in system account. The logon account cannot be validated for the service Analysis Services. Error Number : 28075
When I checked the Program FilesMicrosoft Sql Server folder I saw no Sql instance MSSQLMSSQL.1 as I used to see in SqlExpress. therefore no DATA folder was created. Was it because I messed up the order of the clauses? If this is the case, then how shall I go about correcting the mishap? Now it seems the access is denied.
I can delete the registry keys and delete the folders again. I did it before while trying to get rid of SQL Express. The Browser (Management Studio) was corrupted and caused many problems.. Is this the way to go, to delete the registry keys?
I am trying to analyze log files from a failed install of Sql Server Dev. Ed. on 4/1/08. I have a Windows Installer Verbose Log Anlyzer for that.
The core log says in part: Running: OpenPipeAction at: 2008/4/1 13:56:3 Complete: OpenPipeAction at: 2008/4/1 13:56:33, returned fals Error: Action "OpenPipeAction" failed during execution Running: CreatePipeAction at: 2008/4/1 13:56:3 Complete: CreatePipeAction at: 2008/4/1 13:56:33, returned fals 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 I appears named pipes failed. My question is why?
From Core_log (Local) in part: <Func Name='PerformDetections' 0 <EndFunc Name='PerformDetections' Return='0' GetLastError='0' Error: Action "InvokeSqlSetupDllAction" threw an exception during execution Failed to find feature:ADDLOCAL=ALL : 7000 Message displayed to use The feature(s) specified are not valid for any SQL Server products Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DDMNVT61_.NET Framework 2.0.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code : Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DDMNVT61_.NET Framework 2.0 LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code : Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DDMNVT61_.NET Framework Upgrade Advisor.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code : Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DDMNVT61_.NET Framework Upgrade Advisor LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code : Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DDMNVT61_.NET Framework Windows Installer.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code : Error: Failed to add file :"C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0001_DDMNVT61_.NET Framework Windows Installer LangPack.log" to cab file : "C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGSqlSetup0001.cab" Error Code : Delay load of action "UploadDrWatsonLogAction" returned nothing. No action will occur as a result Message pump returning: 7000 Message pump returning: 7000
There are other log files but I've decided to limit the "damage."
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
D:WINDOWSMicrosoft.NETFrameworkv2.0.50727InstallUtil.exe SQLAgent.exe by running it from a command prompt.
and got an error that the system could not find the file or one of its components. It is a farily new install. I do not think I've lost any files any time.
I seem to have gotten myself between a rock and a hard place. I have tried everything I know and am sending this post as a last resort before wiping my computer drive and re-installing everything. This would not be the end of the world. All the software on my computer is registered and legal and all that, but getting things set up again is not something I look forward to. Here's the situation ..... I have been trying out SQL Server 2005 Express on a test server and have worked out all kinds of good things, including working remotely, over our network, from my computer. We decided to get the full version (SQL Server 2005 Standard) before going any further so that I could have all the cool tools and stuff. We got the full version installed on a new server
and I have been working on it using SQL Server Management Studio Express to get things started. Yesterday I decided I was ready to start going thru the tutorials for SSIS and SSAS, so I uninstalled the Express version of Management Studio and all other segments of Express that were on my local computer, got out the Standard version CDs and installed the workgroups segment on my computer. After several false-starts (re having to load things like IIS and reload .NET framework and then restart the SQL Server installation) I thought I finally made it all the way thru. During this last time thru a message popped up about not enough virtual memory, but the installation continued - so I left it going. When the "finish" screen came up and I clicked "finish", I first went to Surface Config and set things up as I had them before, then tried going to Managment Studio, but it was not in the programs list. I went back to Config. Manager and tried to see if something just needed to be turned on, or whatever, and started getting application failure errors, with a message to look at the install log. In that log there is a message about installation failure due to memory shortage. I should not be getting this problem, as far as I can tell. My hard drive has 24 gigs free and I have 1 gig of ram. In any case, I tried un-installing (thru add/remove programs) and when I do I get a failure error there too. Finally, I tried running the install again, figuring - as I have experienced on other software - that sometimes the second time thru straightens things out. No such luck, and another try at un-install gave the same results. I realize I am being somewhat vague about the error messages. I can get them if I need to, but I thought I would just toss this situation out to you all first, since it may not matter exactly what the failure messages are! Any suggestions?
I am a member of the Administrators group, and there is plenty of space in all hard drives, plus the temp directory is open for "everybody" to full-control it. Yet the Service Pack 2 database engine fails, all other components upgrade fine.
---------------------------------------------------------------------------------- Product : Database Services (MSSQLSERVER) Product Version (Previous): 3033 Product Version (Final) : Status : Failure Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGHotfixSQL9_Hotfix_KB921896_sqlrun_sql.msp.log Error Number : 29506 Error Description : MSP Error: 29506 SQL Server Setup failed to modify security permissions on file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData for user SYSTEM. To proceed, verify that the account and domain running SQL Server Setup exist, that the account running SQL Server Setup has administrator privileges, and that exists on the destination drive. -