SQL Server 2005 Fails While Installing On A Cluster.
Jan 23, 2006
I'm building an SQL Server 2005 cluster on a Windows 2003 cluster. Windows 2003 cluster and MSDTC service are all up and running properly. No problems there, but when I try to install SQL Server 2005 as a cluster service, it fails. The installation goes past the stage where it validates both the nodes and doesn't find any issue there, but when it tries to install fiels it fails. It fails on node 2. When I checked the scduled installer job it creates on node2 to install, the job never seems to run and fails. I'm using only one user account to setup windows cluster MSDTC and SQL Server. Now the complications: It is 64 bit Windows 2003 and SQL Server 2005. Also, the node 1 is built to be a domain controller as well.
We have successfully been using MSCS with MSSQL7 (SP1) running under NT4 EE (SP6a), installed in an active/active configuration using, two DELL PowerEdge 6350 machines. Recently I installed MSSQL7 (SP2), I followed the instructions that came with SP2, and unclustered the SQL nodes using the Failover Cluster Wizard, and installed SP2, this was uneventful, and appeared to install correctly. Next I tried to recluster the SQL nodes using the Failover Cluster Wizard as directed. This failed with: "Could not run setup on remote machine. SQL Cluster Setup failed." So I began the usual research using the usual resources, and have found articles that discusses this error, and the things to look for when it happens. I have exhausted all suggestions without success. I appear to have everything correctly configured. I have enabled Cluster Logging (level 3), following are the two things I have found that indicate something is wrong:
1. In the SQL Error Log the following gets logged when I run the wizard: "Attempting to initialize Distributed Transaction Coordinator." "Failed to obtain TransactionDispenserInterface: XACT_E_TMNOTAVAILABLE"
2. In the Cluster Log I see the following message repeatedly: "[ClRtlCopySecurityDescriptor] MakeSelfRelativeSD failed, 0x00000551"
3. In the sqlclstr.log I see the following, without an indication of which file is missing: "[reghelp.h:235] : 2 (0x2): The system cannot find the file specified." "[clushelp.cpp:166] : 259 (0x103): No more data is available." "[validate.cpp:147] DeleteTestGroup:OpenClusterResource: 5007 (0x138f): The cluster resource could not be found." "~~~ XXX InstallRemote failed"
Does anyone have any ideas about what could be causing this problem? Many thanks in advance.
I have been trying to install Visual Web Developer 2005 Express Edition and SQL Server 2005. The Web Developer installs ok but the SQL Server installation fails. I can't figure out why. I have (I think...) uninstalled my previous beta intallations. The must be something else that prevents the installation. Can anyone point me to some FAQ or something that can give me some ideas on how to handle the installation./anders
Hi, Trying to install SQL Server 2005 SP1 on a windows 2003 box and it fails for database services and reporting services patch. It installs successfully other components of the patch.
Following errors are logged in the event log.
1) 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 2) Product: Microsoft SQL Server 2005 -- Error 29506. SQL Server Setup failed to modify security permissions on file C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLData for user birendraa. 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.
3) Product: Microsoft SQL Server 2005 Reporting Services -- Error 29561. SQL Server Setup failed to retrieve the SSL Certificate Name.
4) Product: Microsoft SQL Server 2005 Reporting Services - Update 'Service Pack 1 for SQL Server Reporting Services 2005 ENU (KB913090)' could not be installed. Error code 1603. Additional information is available in the log file C:WINNTHotfixRS9LogsRS9_Hotfix_KB913090_sqlrun_rs.msp.log.
The account running SQL server setup has admin privileges on that box.
I am installing SSRS 2005 with the following scenario:
- Report Server and Report Manager will be installed on web server
- The repository databases (ReportServer and ReportServerTempDB) will be hosted in SQL2005 cluster server.
Both servers are running Win2003 SP1, SQL/SSRS 2005 SP1
When I try to browse the ReportServer virtual directory from IIS on the web server, the system keep asking username and password. After 3 times trials and it failed eventhough the username and password is correct.
The error message is:
HTTP Error 401.1 - Unauthorized: Access is denied due to invalid credentials. Internet Information Services (IIS)
I've been searching on the web and found couple of articles talking about this issue. I've tried some of them like: http://support.microsoft.com/kb/887993 or even this one: http://groups.google.ca/group/microsoft.public.sqlserver.reportingsvcs/browse_frm/thread/991c9178ceab8f58/8f1a447aa60ad837?lnk=st&q=reporting+services+the+server+is+not+responding&rnum=3&hl=en#8f1a447aa60ad837
But this doesn't work.
I've checked both event viewer both web server and SQL server, but I can't see any information that tell me what had happened.
I also look at BOL, but doesn't help much.
Is there anyone can help me or point me to the right direction? Is there any guide document that explains step-by-step how to install SSRS in my scenario or similiar?
I have no idea how to apply "fixes" or updates to SQL Server when it is running on a cluster.
We are currently running SQL Server 2005 with SP2. The version would be Microsoft SQL Server 2005 - 9.00.3042.00 (X64) Feb 10 2007 00:59:02 Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
I am hoping that someone can tell me of a document that exists, that includes the very basics, on how to do this. I need something that says go to the cluster and do these steps in this order, etc. from start to finish.
I can't seem to get all of the SQL9_Hotfix_KB913090_sqlrun_sql.msp.log to post (too big), but I can post the SQL9_Hotfix_KB913090.log file...hope that helps and which seems to me might contain the clue as to what's going. Any ideas would be appreciated. This is happening on a fresh install of Win Server 2003 and SQL Server standard 2005.
Thanks,
Steve
04/09/2007 16:14:30.562 ================================================================================ 04/09/2007 16:14:30.578 Hotfix package launched 04/09/2007 16:14:33.312 Product discovery successfully completed during the install process for MSSQLSERVER 04/09/2007 16:14:33.328 SP Level check successfully completed during the install process for MSSQLSERVER 04/09/2007 16:14:33.359 Product language check successfully completed during the install process for MSSQLSERVER 04/09/2007 16:14:33.390 Product version check successfully completed during the install process for MSSQLSERVER 04/09/2007 16:14:33.421 Command-line instance name check completed during the install process 04/09/2007 16:14:33.437 Baseline build check completed during the install process 04/09/2007 16:16:52.828 Attempting to install instance: MSSQLSERVER 04/09/2007 16:16:52.875 Attempting to install target: TURBULENT2 04/09/2007 16:16:53.015 Attempting to stop service: SQLSERVERAGENT 04/09/2007 16:16:58.171 Successfully stopped service: SQLSERVERAGENT 04/09/2007 16:16:58.203 Attempting to stop service: MSSQLServer 04/09/2007 16:17:00.250 Successfully stopped service: MSSQLServer 04/09/2007 16:17:00.281 Attempting to check for locked files: sqlrun_sql.msp 04/09/2007 16:17:00.468 Attempting to check for locked files: \TURBULENT2f$9104ddf6956f8b22663aHotFixSQLFilessqlrun_sql.msp 04/09/2007 16:17:00.500 Creating MSP locked file check log at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.out 04/09/2007 16:17:38.125 MSP returned 1602: The user cancels installation. 04/09/2007 16:17:38.328 Successfully checked file: \TURBULENT2f$9104ddf6956f8b22663aHotFixSQLFilessqlrun_sql.msp 04/09/2007 16:17:38.359 Successfully opened registry key: SystemCurrentControlSetControlSession Manager 04/09/2007 16:17:38.421 Failed to read registry key: PendingFileRenameOperations 04/09/2007 16:17:38.468 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnxmlfilt.dll 04/09/2007 16:17:38.515 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnThaWBrkr.dll 04/09/2007 16:17:38.562 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnquery.dll 04/09/2007 16:17:38.609 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnls400.dll 04/09/2007 16:17:38.687 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnlhtml.dll 04/09/2007 16:17:38.734 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsir5jp.dll 04/09/2007 16:17:38.765 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftesql.exe 04/09/2007 16:17:38.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftepxy.dll 04/09/2007 16:17:38.843 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsftefd.exe 04/09/2007 16:17:38.875 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnmsfte.dll 04/09/2007 16:17:38.890 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnLangWrbk.dll 04/09/2007 16:17:38.921 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnkorwbrkr.dll 04/09/2007 16:17:38.937 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinninfosoft.dll 04/09/2007 16:17:38.968 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnFTERefFTERef.dll 04/09/2007 16:17:39.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnCHTBRKR.DLL 04/09/2007 16:17:39.015 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnChsBrkr.dll 04/09/2007 16:17:39.046 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMResources1033REPLRES.rll 04/09/2007 16:17:39.062 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM eplrec.dll 04/09/2007 16:17:39.093 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COM plisapi.dll 04/09/2007 16:17:39.156 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 04/09/2007 16:17:39.171 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.DataStorage9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.DataStorage.dll 04/09/2007 16:17:39.203 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 04/09/2007 16:17:39.218 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstall C:Program FilesMicrosoft SQL Server90COMqrdrsvc.exe 04/09/2007 16:17:39.250 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMsnapshot.exe 04/09/2007 16:17:39.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 04/09/2007 16:17:39.296 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90COM ablediff.exe 04/09/2007 16:17:39.328 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90COM2005.90.2047.0 C:Program FilesMicrosoft SQL Server90COMDISTRIB.exe 04/09/2007 16:17:39.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnDatabaseMail90.exe 04/09/2007 16:17:39.390 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 04/09/2007 16:17:39.406 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 04/09/2007 16:17:39.437 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 04/09/2007 16:17:39.453 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 04/09/2007 16:17:39.484 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 04/09/2007 16:17:39.515 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 04/09/2007 16:17:39.531 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 04/09/2007 16:17:39.562 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlaccess.dll 04/09/2007 16:17:39.578 Failed to read version information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinn6.6.3.5 C:Program FilesMicrosoft SQL Server90Sharedmsxmlsql.dll 04/09/2007 16:17:39.609 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 04/09/2007 16:17:39.640 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 04/09/2007 16:17:39.656 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 04/09/2007 16:17:39.687 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnsqlsvc90.dll 04/09/2007 16:17:39.703 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 04/09/2007 16:17:39.734 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 04/09/2007 16:17:39.765 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 04/09/2007 16:17:39.796 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 04/09/2007 16:17:39.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 04/09/2007 16:17:39.843 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAgentMail90.rll 04/09/2007 16:17:39.875 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 04/09/2007 16:17:39.906 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 04/09/2007 16:17:39.921 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnResources1033SQLAGENT90.RLL 04/09/2007 16:17:39.953 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 04/09/2007 16:17:39.984 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 04/09/2007 16:17:40.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAgentMail90.dll 04/09/2007 16:17:40.031 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 04/09/2007 16:17:40.062 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 04/09/2007 16:17:40.078 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLBinnSQLAGENT90.EXE 04/09/2007 16:17:40.140 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90SharedResources10339.0.2047.0 C:Program FilesMicrosoft SQL Server90Sharedmsmdrdir.dll 04/09/2007 16:17:40.156 Failed to read version information for the following file: C:Program FilesCommon FilesSystemole db2.0.3609.0 C:Program FilesCommon FilesSystemole dbxmlrw.dll 04/09/2007 16:17:40.171 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 04/09/2007 16:17:40.203 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 04/09/2007 16:17:40.218 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsmdlocal.dll 04/09/2007 16:17:40.265 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 04/09/2007 16:17:40.281 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 04/09/2007 16:17:40.296 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlbrowser.exe 04/09/2007 16:17:40.312 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 04/09/2007 16:17:40.328 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 04/09/2007 16:17:40.359 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedmsasxpress.dll 04/09/2007 16:17:40.375 Failed to read version information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90enMicrosoft.AnalysisServices.AdomdClient.xml 04/09/2007 16:17:40.390 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft.NETADOMD.NET90Microsoft.AnalysisServices.AdomdClient.dll 04/09/2007 16:17:40.421 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices.AdomdClient9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.AdomdClient.dll 04/09/2007 16:17:40.437 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033 C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033sqlcm.xml 04/09/2007 16:17:40.453 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 04/09/2007 16:17:40.484 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 04/09/2007 16:17:40.500 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources1033SqlManager.rll 04/09/2007 16:17:40.515 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 04/09/2007 16:17:40.531 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 04/09/2007 16:17:40.546 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSqlManager.dll 04/09/2007 16:17:40.578 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 04/09/2007 16:17:40.593 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 04/09/2007 16:17:40.609 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnatchparser90.dll 04/09/2007 16:17:40.625 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinnResources10332005.90.2047.0 C:Program FilesMicrosoft SQL ServerMSSQL.1MSSQLInstallsysdbupg.sql 04/09/2007 16:17:40.656 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 04/09/2007 16:17:40.671 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 04/09/2007 16:17:40.687 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90ToolsinnSQLSVC90.DLL 04/09/2007 16:17:40.703 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2.0.3609.0 C:Program FilesMicrosoft SQL Server90ToolsBinnSQLdiag.exe 04/09/2007 16:17:40.718 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90ToolsBinn2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsvc~1.dll 04/09/2007 16:17:40.765 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 04/09/2007 16:17:40.781 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 04/09/2007 16:17:40.796 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlsecacctchg.dll 04/09/2007 16:17:40.812 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 04/09/2007 16:17:40.843 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 04/09/2007 16:17:40.875 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsqlftacct.dll 04/09/2007 16:17:40.890 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 04/09/2007 16:17:40.906 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 04/09/2007 16:17:40.937 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedisacctchange.dll 04/09/2007 16:17:40.968 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 04/09/2007 16:17:40.984 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 04/09/2007 16:17:41.000 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90Sharedsvrenumapi.dll 04/09/2007 16:17:41.015 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared2005.90.2047.0 C:Program FilesMicrosoft SQL Server90Sharedsqlsqm.exe 04/09/2007 16:17:41.046 Failed to read version information for the following file: C:Program FilesMicrosoft SQL Server90Shared9.0.2047.0 C:Program FilesMicrosoft SQL Server90Shareddbghelp.dll 04/09/2007 16:17:41.062 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 04/09/2007 16:17:41.125 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 04/09/2007 16:17:41.171 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlDumper.exe 04/09/2007 16:17:41.203 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Rmo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Rmo.dll 04/09/2007 16:17:41.234 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.AnalysisServices9.0.242.0__89845dcd8080cc91Microsoft.AnalysisServices.DLL 04/09/2007 16:17:41.250 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.DataWarehouse.Interfaces9.0.242.0__89845dcd8080cc91Microsoft.DataWarehouse.Interfaces.DLL 04/09/2007 16:17:41.265 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.RegSvrEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.RegSvrEnum.dll 04/09/2007 16:17:41.281 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 04/09/2007 16:17:41.312 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 04/09/2007 16:17:41.328 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_32Microsoft.SqlServer.BatchParser9.0.242.0__89845dcd8080cc91microsoft.sqlserver.batchparser.dll 04/09/2007 16:17:41.359 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.ServiceBrokerEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.ServiceBrokerEnum.dll 04/09/2007 16:17:41.375 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.WmiEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.WmiEnum.dll 04/09/2007 16:17:41.406 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SqlEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SqlEnum.dll 04/09/2007 16:17:41.421 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.SmoEnum9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.SmoEnum.dll 04/09/2007 16:17:41.453 Failed to read associated hotfix build information for the following file: C:WINDOWSassemblyGAC_MSILMicrosoft.SqlServer.Smo9.0.242.0__89845dcd8080cc91Microsoft.SqlServer.Smo.dll 04/09/2007 16:17:41.484 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedSqlSAC.exe 04/09/2007 16:17:41.515 Failed to read associated hotfix build information for the following file: C:Program FilesMicrosoft SQL Server90SharedMicrosoft.SqlSac.Public.dll 04/09/2007 16:17:41.687 Attempting to install file: sqlrun_sql.msp 04/09/2007 16:17:41.750 Attempting to install file: \TURBULENT2f$9104ddf6956f8b22663aHotFixSQLFilessqlrun_sql.msp 04/09/2007 16:17:41.765 Creating MSP install log file at: C:WINDOWSHotfixSQL9LogsSQL9_Hotfix_KB913090_sqlrun_sql.msp.log 04/09/2007 16:17:41.796 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 04/09/2007 16:17:41.812 Failed to read registry key: Debug 04/09/2007 16:19:50.187 MSP returned 1603: A fatal error occurred during installation. 04/09/2007 16:19:50.250 Successfully opened registry key: SoftwarePoliciesMicrosoftWindowsInstaller 04/09/2007 16:19:50.265 Failed to read registry key: Debug 04/09/2007 16:19:50.296 Unable to install MSP file: \TURBULENT2f$9104ddf6956f8b22663aHotFixSQLFilessqlrun_sql.msp 04/09/2007 16:19:50.312 The following exception occurred: Unable to install Windows Installer MSP file Date: 04/09/2007 16:19:50.312 File: depotsqlvaultsetupmainsetupsqlsesqlsedllcopyengine.cpp Line: 856 04/09/2007 16:19:50.437 04/09/2007 16:19:50.468 Product Status Summary: 04/09/2007 16:19:50.500 Product: SQL Server Native Client 04/09/2007 16:19:50.546 SQL Server Native Client (RTM ) - Success 04/09/2007 16:19:50.578 04/09/2007 16:19:50.609 Product: Setup Support Files 04/09/2007 16:19:50.640 Setup Support Files (RTM ) - Success 04/09/2007 16:19:50.656 04/09/2007 16:19:50.687 Product: Database Services 04/09/2007 16:19:50.734 Database Services (SP1 2047 ENU) - Failure 04/09/2007 16:19:50.750 Details: Unable to install Windows Installer MSP file 04/09/2007 16:19:50.781 Reporting Services (SP1 2047 ENU) - Not Applied 04/09/2007 16:19:50.812 04/09/2007 16:19:50.843 Product: Client Components 04/09/2007 16:19:50.890 Client Components (SP1 2047 ENU) - Not Selected 04/09/2007 16:19:50.921 04/09/2007 16:19:50.953 Product: MSXML 6.0 Parser 04/09/2007 16:19:50.968 MSXML 6.0 Parser (RTM ) - Not Selected 04/09/2007 16:19:51.015 04/09/2007 16:19:51.046 Product: SQLXML4 04/09/2007 16:19:51.078 SQLXML4 (RTM ) - Not Selected 04/09/2007 16:19:51.109 04/09/2007 16:19:51.125 Product: Backward Compatibility 04/09/2007 16:19:51.140 Backward Compatibility (RTM ) - Not Selected 04/09/2007 16:19:51.171 04/09/2007 16:19:51.203 Product: Microsoft SQL Server VSS Writer 04/09/2007 16:19:51.265 Microsoft SQL Server VSS Writer (RTM ) - Not Selected 04/09/2007 16:19:51.296 04/09/2007 16:29:32.812 Hotfix package closed
I've installed Windows 2003 SP2 in a stand-alone cluster (will be adding a second node later). I'm now installing SQL Server 2005 Developer Edition 64-bit extended and would like to have the "Create a SQL Server Failover Cluster" box to not be grayed out. Even when I check the "SQL Server Database Services" box, it still has the cluster box grayed out.
I have a Windows 2003 Server SP1, Active Directory, Application Server and RIS installed on my computer. After installing SQL Server 2005 April CTP my DHCP Service fails to start. In the Event Viewer I see the following Events.
Is it possible to install and configure the MSDTC resource in a SQL Server 2000 cluster after SQL is installed and running?
When I recently went through a rebuild of my cluster, I forgot to install the resource before installing SQL Server. Now, if I install and bring online the MSDTC resource the SQL disk groups will not fail over correctly. The SQL Server resource will not come online.
Thanks in advance for any help. I would really like to avoid rebuilding again.
I am trying to install SQL failover cluster on one of my nodes so it should install sql on the 2nd node. It keeps coming back saying setup failed to start on the remote machine. When I look in scheduled tasks it is listed as could not run. Can someone please help.
am trying to install sql 2005 with cluster option in win 2003 R2 servers and keep getting sql database setup failed error.Summary log show that it failed with error number 67. It doesn't even create a SQLSetup0004_M2MTPONE_SQL.log file. core log shows
Complete: DetectLocalBootstrapAction at: 2006/5/1 18:15:31, returned true Running: LaunchLocalBootstrapAction at: 2006/5/1 18:15:31 Error: Action "LaunchLocalBootstrapAction" threw an exception during execution. Error information reported during run: "C:Program FilesMicrosoft SQL Server90Setup Bootstrapsetup.exe" finished and returned: 67 Aborting queue processing as nested installer has completed Message pump returning: 67
We have two machines in running enterprises version of R2 in a cluster. I tried running the setup from both machines and got the same error.
I am trying to find a solution for more than week but no luck. Any help is appreciated.
thanks - Kailash
Part of Summary log: --------------------------------------------------------------------------------
Machine : M2MTPONE Product : Microsoft SQL Server 2005 Backward compatibility Product Version : 8.05.1054 Install : Successful Log File : C:Program FilesMicrosoft SQL Server90Setup BootstrapLOGFilesSQLSetup0004_M2MTPONE_BackwardsCompat_1.log --------------------------------------------------------------------------------
I need to install the SSIS components on the referenced database server. I believe the SSIS components are cluster aware, so I was planning on just doing add/remove and selecting the components. Rather than breaking the cluster apart to patch the components back to SP1, I was thinking of just running the SP2 install right over the top of the running cluster to bring everything up to SP2.
I'm looking for any suggestions/comments on whether this is the proper way to proceed or if I'm going to have a problem.
I have DBA that is convinced that they need domain admin rights to install SQL 2005 into an existing cluster. The domain groups and service accounts for SQL have been created already. Is having domain admin rights required during the install of SQL 2005 in a cluster?
Hello All,If SQL Server is installed on a cluster will it be able to utilize the CPU and memory of all of the servers that are part of the cluster. For example, currently we run SQL Server on one server and at certain peak time the server CPU is maxed out. Will a cluster environment allow SQL Server to utilize mutiple servers for processing eliminating this problem?Thanks, Gary
Hi all, Im new here so il start with a little introduction of myself, My name is Arjan im 19 years old from Holland, and i work for a company to compleet my ICT Education.
My situation:
My boss gave me a server with server 2003 standard and Sql server 2005 and visual studio 2005 installed already, he asked me if i could figure out how the 'new' reporting services work, Im pretty new to SQL and the reporting service but i figured out i had to install asp.net / frameworks and IIS.
So right now i wanna start the Reporting Services Configuration Manager and i get an error that says 'Invalid namespace' and when im trying to approach by using my browser i get 'page not found' so obviously their is Alot wrong. I asked my boss if i could not reinstall everything and do it in the correct order (IIS / ASP.net / Frameworks before installing SQL server 2k5 but that was not an option because we dont seem to have the cd's anymore.
The server is not connected to any network or the internet.
My Question:
Is their any way to fix this? and if yes could anyone tell me where to start
Thanks in Advance!
ps if their is information or logs that u need in order to help me just say so :-)
I posted this to the ms sql clustering news group, but I thought I'dpost it here just in case someone here knew the answser. This problemhas had me baffled for 5 months, and I'm not seeing any supportarticles from Microsoft on it, yet. Anyone here got a clue?About 5 months ago, I posted a query to this group after experiencingfailures with my database maintenance plans (during the verify phase)that run on SQL Clusters on Windows 2003(http://groups-beta.google.com/group...9b?dmode=source)I was re-posting this in hopes that someone knows of a fix besidescoding a home-brew verify step in to the backup job to check the file'sintegrity?Thanks,TW
if it is supported to install Reporting Services on both the active and passive nodes in an SQL Server Failover Cluster and use the non-active node as a warm standby?We have relatively simple reporting requirements so the idea would be that if Node 1 went down, we could just repoint our users are Node 2 temporarily. Both reporting services instances would be configured to target the same SSRS database running on the SQL Cluster.
We are planning to upgrade the SQL Server in our production environment from SQL Server 2000 to SQL Server 2005. This is a 4 Node cluster environment with 3 Databases on 3 Virtual instances. The main requirement is to achieve this with no/minimal downtime.
Could you please suggest or direct me to any documentation for the best practices used to upgrade such an environment?
I just upgraded ACT database and it needs SQL Server. I just keep getting "SQL Server Setup Failed". I downloaded SQL from Microsoft, went to install and get the same error. It then refers to a summary txt log which I have had a look at but to be quite honest means nothing to me.
We're upgrading a SQL Server 2000 cluster (Active/Passive) running on Windows 2000 Server to a SQL Server 2005 Cluster running on Windows Server 2003. We can't purchase new hardware and we have no spare hardware. We also need to move from Windows 2000 Server to Windows 2003 Server at the same time. We want to keep downtime to a bare minimum.
What we were thinking was the following steps... Anyone try this?
1. Break the link between the servers.
2. Install a fresh copy of windows 2003 server on one side along with SQL Server 2005. While this step is running, the active node would still be live on Windows 2000 Server and SQL Server 2000 serving our customers.
3. Restore a copy of a backup from the active production side to the node we're upgrading and at that point we would bring the active node down, switching the active node to be the newly upgraded server.
4. As a final step, the old active node would now have the link to it broken, we would install a fresh copy of windows 2003 server on it and sql server 2005. At this point we would bring it back into the cluster and the cluster would be complete again.
Need your help and guidence for doing upgrading SQL Server 2000 Cluster to SQL Server 2005 Cluster.
Let me explain my current environment.
1. Currently SQL Server 2000 Cluster environment is running on Windows 2000 Server we need to upgrade this to SQL Server 2005 on Windows 2003 Server. >>> Production environment.
My Plans:
1. On Testing Environment Install SQL Server 2000 cluster on Windows 2003 Server and do a restore of databases from the produciton environment.
2. Upgrade In-Place from SQL Server 2000 Cluster to SQL Server 2005 Cluster.
My doubts
1. Can i install SQL Server 2000 Cluster on Windows 2003 Server. Is it possible or not.
We have SQL cluster installed on top of windows cluster on VM environment. Node1 and Node2 under Windows Failover Cluster. SQL instance is currently on node2 the instance is up and running, but SQL Cluster service remains online pending and it restarts the instance on every 5 minutes.
SQL Browser service are running successfully.TCP/IP ports are enabled and configured.If we start the SQL server agent it is on for seconds and stopped immediately  .Cluster Service is attempt to connect to the SQL service every few minutes (setting in SQL cluster resource) for the IsAlive check, if this fails then the SQL resource is restarted even if the instance was online. Hope this is what happening exactly.
[sqsrvres] ODBC Error: [08001] [Microsoft][SQL Server Native Client 11.0]SQL Server Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. (268435455) 00001024.00053314::2015/10/30-19:57:50.772 ERR  [RES] SQL Server <SQL Server (SIMAH_COMMDB)>: [sqsrvres] ODBC Error: [HYT00] [Microsoft][SQL Server Native Client 11.0]Login timeout expired (0) 00001024.00053314::2015/10/30-19:57:50.772 ERR  [RES] SQL Server <SQL Server (SIMAH_COMMDB)>: [sqsrvres] ODBC Error: [08001] [Microsoft][SQL Server
Native Client 11.0]A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books
Online. (268435455) 00001024.00053314::2015/10/30-19:57:50.772 INFOÂ [RES] SQL Server <SQL Server (SIMAH_COMMDB)>: [sqsrvres] Could not connect to SQL Server (rc -1
We have a SQL 2000 cluster running on WIn2003. in a normal sql install you install Outlook client on SQL Server for Agent to use to send messages. Do you have to do something different for a clustered environment?
I am trying to configure a 2 node SQL cluster. MSCS is configured and is failing over correctly, however when I start the installation of SQL Server, and specify the IP address of the virtual server and hit next, the installation hangs, and stops responding. I have configured MS DTC and verified that it shows up in the cluster administrator. I am not sure what else to do, please help.
I want to install SQL Server SP2 on the cluster (Active-Passive). This is my production server. Can anyone tell me how much downtime is involved while installing SP2.
How does sp2 installation works on the cluster? Does it install on the primary node first and then on the secondary node (i.e one node at a time).
I I know during installation it restarts the sql server service. So while installing on 1st node, does it fail over to second node?
I am trying to install SQL 2005 in a 2-node virtual Windows 2003 cluster. I set the cluster up through Virtual Server 2005 with 2 virtual nodes and one virtual domain. The nodes can connect to each other as well as the physical machine. When I try to install a fresh copy of SQL 2005 on my cluster, I get an error every time. The error stops the installation while checking system configuration after installing prerequisites. The log file entry is as follows:
******************************************* Setup Consistency Check Report for Machine: --SERVERNAME-- ******************************************* 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: IIS Feature Requirement, Result: Warning Description: IIS is not installed, therefore Report Server feature will be disabled Action: Install IIS in order for Report Server feature to be enabled Article: Pending Reboot Requirement, Result: CheckPassed Article: Performance Monitor Counter 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 <Func Name='PerformDetections'> 1 Loaded DLL:C:Program FilesMicrosoft SQL Server90Setup Bootstrapsqlsval.dll Version:2005.90.1399.0 Error: Action "InvokeSqlSetupDllAction" threw an exception during execution. Error information reported during run: 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 "ComputerList" {"SqlComputers", "", ""} in cache Source File Name: datastoreclusterinfocollector.cpp Compiler Timestamp: Fri Sep 16 13:20:12 2005 Function Name: ClusterInfoCollector::collectClusterVSInfo Source Line Number: 883 ---------------------------------------------------------- Failed to detect VS info due to datastore exception. Source File Name: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56 ---------------------------------------------------------- Failed to find a cluster group that owned shared disk: J: WinException : 2 Error Code: 0x80070002 (2) Windows Error Text: The system cannot find the file specified. Source File Name: datastoreclustergroupsproperties.cpp Compiler Timestamp: Fri Jul 29 01:13:49 2005 Function Name: ClusterGroupScope.SharedDisks Source Line Number: 56
We have been using Sql Server 2005 Compact Edition 3.1 RDA synchronization method successfully on Sql Server 2000 database. Recently we moved the database to Sql Server 2005, sync doesn't work anymore, it just hangs on one table. On further investigation, we found out that it's the index on that table that causes this. We removed the index, it works fine. We are wondering the root cause, removing the index is not a solution for us. Any thoughts?. Thanks.
I'm trying to install SQL into a new cluster. The cluster service is up and running fine. I can even fail it from Node 1 to Node 2 with no problem.
However, when I try to install SQL, I get a screen that tells me that SQL is performing required operations on the cluster nodes...this may take a few minutes.
After hanging on that message for a looong time, SQL comes up with a generic message that the install failed and that SQL is cleaning up. Then, nothing. No error message, nothing that I can track down.
Some system information: Node 1. Dell PE2650, 2x 2.8 GHz, 2 GB RAM - Windows 2000 Advanced Server - Dell Perc3/DC RAID/SCSI Controller - Dell Perc3/DI Integrated RAID Controller
Shared Storage. Dell PV220 - Q: Quorum (1 GB) - S: Data (136 GB) - T: Logs (20 GB)
Additional Notes: 1. I am using a checklist from Dell and another from MS. 2. I have also downloaded and read the checklist from sql-server-performance.com. 3. I have ensured that the comclust.exe was run on both nodes prior to starting the SQL installation 4. I am using SQL Enterprise Edition. We used the same CD to install a cluster server two weeks ago.
Questions: 1. Where can I find an installation error log that might point more specifically to where the problem might be? 2. Any thoughts on what the problem might be? 3. Anyone ever experience something similar?
Have SQL 2000 SP4 clustered instance running now. Attempted inplace upgrade to SQL 2K5 standard edition. Boxes are Windows 32 bit Ent Edition, SP2. Install wizard installed pre-req's just fine, and I got past the "components to install" box of the install wizard. When I clicked next, the current 2000 instance (already installed component) was grayed out and I could not select it. Checking the messages in the install wizard, I saw that my "upgrade was blocked". I cancelled out of the install wizard to verify all requirements.
Bounced both boxes, and now when I try to run the install wizard, it tried to install the required support files (ASP.net 2.0, SQL Native Client and what not) and then the install wizard hangs..... and never comes back. I have to kill it from taskmgr. Bounced the boxes and tried again, same thing. Install wizard hangs forever.
Yes, I am running from the active node holding the cluster resources. Yes, SQL 2000 instance is cold. Yes, I've checked add/remove programs and there is nothing to uninstall. Checked event viewer and I see the following errors:
Hanging application setup.exe, version 2005.90.1399.0, hang module hungapp, version 0.0.0.0, hang address 0x00000000.
Fault bucket 238575085.
I've reached out to our TAM, but any help would be appreciated. No matter how many times I try, the install wizard now chokes and never comes back.
