![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I have been trying for days to run the SQL 2008 setup on my machine. Basically, the setup program will not run. The first time it ran it did install a prerequisite (can't remember exactly what). Since then, though, when it tries to run, a command window appears for a fraction of a second, then it disappears, and that's all. I've looked at the log file that is created at %temp%\SqlSetup.log. In that file, I have confirmed that the correct versions of .NET and Windows Installer are present. See below: --> .Net version 3.5 is installed --> Windows Installer version detected: 4.5.6001.22159 I've compared this log file to a log file generated from a separate machine where I can successfully launch the setup program. The entries are identical except for the 4 entries noted below. Successful attempt: Timestamp: 20100322_095520 Process returned exit code: 0x00000000 Workflow LANDINGPAGE returned exit code: 0x00000000 Setup closed with exit code: 0x00000000 Unsuccessful attempt: Timestamp: 20100322_100545 Process returned exit code: 0xC0000022 Workflow LANDINGPAGE returned exit code: 0xC0000022 Setup closed with exit code: 0x84C40013 What do I need to do to resolve this issue and install SQL 2008? FYI... - I am trying to install en_sql_server_2008_developer_x86_x64_ia64_dvd_x14-88839.iso. - I have downloaded the image from MSDN twice, and I have copied an image that was known to work from another machine twice. - Before launching the .iso I think I unintentionally ran en_sql_server_2008_sp1_x86.exe. - I was able to run the file Z:\x86\Setup\SQLServer2008_BOL.msi to install "SQL Server Books Online". This was apparently successful, but none of the other .msi files seem able to execute directly. - I have tried "repairing" the installations of (1) Microsoft .NET Framework 3.5SP1, (2) Microsoft SQL Server 2008 Management Objects, (3) Microsoft SQL Server 2008 Books Online (English), and (4) "MSXML6.0 Parser". This hasn't helped. |
#3
| |||
| |||
|
|
I have been trying for days to run the SQL 2008 setup on my machine. Basically, the setup program will not run. The first time it ran it did install a prerequisite (can't remember exactly what). Since then, though, when it tries to run, a command window appears for a fraction of a second, then it disappears, and that's all. I've looked at the log file that is created at %temp%\SqlSetup.log. In that file, I have confirmed that the correct versions of .NET and Windows Installer are present. See below: --> .Net version 3.5 is installed --> Windows Installer version detected: 4.5.6001.22159 I've compared this log file to a log file generated from a separate machine where I can successfully launch the setup program. The entries are identical except for the 4 entries noted below. Successful attempt: Timestamp: 20100322_095520 Process returned exit code: 0x00000000 Workflow LANDINGPAGE returned exit code: 0x00000000 Setup closed with exit code: 0x00000000 Unsuccessful attempt: Timestamp: 20100322_100545 Process returned exit code: 0xC0000022 Workflow LANDINGPAGE returned exit code: 0xC0000022 Setup closed with exit code: 0x84C40013 What do I need to do to resolve this issue and install SQL 2008? |
#4
| |||
| |||
|
|
Craig Stewart (castewa (AT) newsgroups (DOT) nospam) writes: I have been trying for days to run the SQL 2008 setup on my machine. Basically, the setup program will not run. The first time it ran it did install a prerequisite (can't remember exactly what). Since then, though, when it tries to run, a command window appears for a fraction of a second, then it disappears, and that's all. I've looked at the log file that is created at %temp%\SqlSetup.log. In that file, I have confirmed that the correct versions of .NET and Windows Installer are present. See below: --> .Net version 3.5 is installed --> Windows Installer version detected: 4.5.6001.22159 I've compared this log file to a log file generated from a separate machine where I can successfully launch the setup program. The entries are identical except for the 4 entries noted below. Successful attempt: Timestamp: 20100322_095520 Process returned exit code: 0x00000000 Workflow LANDINGPAGE returned exit code: 0x00000000 Setup closed with exit code: 0x00000000 Unsuccessful attempt: Timestamp: 20100322_100545 Process returned exit code: 0xC0000022 Workflow LANDINGPAGE returned exit code: 0xC0000022 Setup closed with exit code: 0x84C40013 What do I need to do to resolve this issue and install SQL 2008? This may unfortunately be difficult to resolve. What happens if you run setup.exe /? from the command line? (Your current folder should of course be the one where setup.exe is located.) Normally setup.exe should list the various command-line options. If it exits without doing this, check the registry if you have this key: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Bootstrap And in such case delete it. In one case I know of where an MVP colleague saw this behaviour, deleting this key resolved the issue. But I cannot guarantee that it will help in your case. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx . |
#5
| |||
| |||
|
|
Running "setup.exe /?" generates what I assume would be the expected output. It starts with: --> Microsoft (R) SQL Server 2008 Setup 10.00.1600.22 --> Copyright (c) Microsoft Corporation. All rights reserved. -- --> Usage: and ends with a example of a full unattended installation followed by: --> Press any key to exit... The registry key you mentioned does not exist. I continued researching this yesterday and I think the cause of my issue may be the Cisco Security Agent (CSA) software that the company has installed on my laptop. It has log entries as follows: EventCode: HACL_OVERFLOW_TAG Text: The process 'Z:\x86\setup100.exe' (as user DOMAIN\LOGIN) attempted to call the function VirtualAlloc from a buffer (the return address was 0x79e72403). The code at this address is '7ae8e7f3 ffff8b3d 90333b7a 33db3bfb 0f850586 2400ff75 14ff7510 ff750cff 7508ff15 f412e779 8bf085f6 741666f7 45100010 740e8b0d 68323b7a 85c90f85' This either happens when a process uses self-modifying code or when a process has been subverted by a buffer overflow attack. The process was added to the application class a1-Potential Malware - Unsafe actions. followed by... EventCode: FACL_TERMINATE Text: The process 'Z:\x86\setup100.exe' (as user DOMAIN\LOGIN) attempted to access 'C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\in dex872.dat'. The attempted access was a read (operation = OPEN/READ). The operation was denied and process terminated. My account is in the Administrators group, and this is the first software I've ever had any difficult installing. My user account is not able to stop the CSA service from running. I asked the group that is supposed to support the CSA for our company, and their response is that the setup program "performs a buffer overflow, which we consider an unsafe action, and was terminated". Any suggestions? "Erland Sommarskog" wrote: Craig Stewart (castewa (AT) newsgroups (DOT) nospam) writes: I have been trying for days to run the SQL 2008 setup on my machine. Basically, the setup program will not run. The first time it ran it did install a prerequisite (can't remember exactly what). Since then, though, when it tries to run, a command window appears for a fraction of a second, then it disappears, and that's all. I've looked at the log file that is created at %temp%\SqlSetup.log. In that file, I have confirmed that the correct versions of .NET and Windows Installer are present. See below: --> .Net version 3.5 is installed --> Windows Installer version detected: 4.5.6001.22159 I've compared this log file to a log file generated from a separate machine where I can successfully launch the setup program. The entries are identical except for the 4 entries noted below. Successful attempt: Timestamp: 20100322_095520 Process returned exit code: 0x00000000 Workflow LANDINGPAGE returned exit code: 0x00000000 Setup closed with exit code: 0x00000000 Unsuccessful attempt: Timestamp: 20100322_100545 Process returned exit code: 0xC0000022 Workflow LANDINGPAGE returned exit code: 0xC0000022 Setup closed with exit code: 0x84C40013 What do I need to do to resolve this issue and install SQL 2008? This may unfortunately be difficult to resolve. What happens if you run setup.exe /? from the command line? (Your current folder should of course be the one where setup.exe is located.) Normally setup.exe should list the various command-line options. If it exits without doing this, check the registry if you have this key: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Bootstrap And in such case delete it. In one case I know of where an MVP colleague saw this behaviour, deleting this key resolved the issue. But I cannot guarantee that it will help in your case. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx . |
#6
| |||
| |||
|
|
did you try running setup.exe from a command prompt? you had said that the command window only flashed open for a split second. if you execute setup from there, your error may display for you and give you a clue if your support folks are on the right track with the buffer overflow or not. also, did you look in the windows event log for errors when you run setup? "Craig Stewart" wrote: Running "setup.exe /?" generates what I assume would be the expected output. It starts with: --> Microsoft (R) SQL Server 2008 Setup 10.00.1600.22 --> Copyright (c) Microsoft Corporation. All rights reserved. -- --> Usage: and ends with a example of a full unattended installation followed by: --> Press any key to exit... The registry key you mentioned does not exist. I continued researching this yesterday and I think the cause of my issue may be the Cisco Security Agent (CSA) software that the company has installed on my laptop. It has log entries as follows: EventCode: HACL_OVERFLOW_TAG Text: The process 'Z:\x86\setup100.exe' (as user DOMAIN\LOGIN) attempted to call the function VirtualAlloc from a buffer (the return address was 0x79e72403). The code at this address is '7ae8e7f3 ffff8b3d 90333b7a 33db3bfb 0f850586 2400ff75 14ff7510 ff750cff 7508ff15 f412e779 8bf085f6 741666f7 45100010 740e8b0d 68323b7a 85c90f85' This either happens when a process uses self-modifying code or when a process has been subverted by a buffer overflow attack. The process was added to the application class a1-Potential Malware - Unsafe actions. followed by... EventCode: FACL_TERMINATE Text: The process 'Z:\x86\setup100.exe' (as user DOMAIN\LOGIN) attempted to access 'C:\WINDOWS\assembly\NativeImages_v2.0.50727_32\in dex872.dat'. The attempted access was a read (operation = OPEN/READ). The operation was denied and process terminated. My account is in the Administrators group, and this is the first software I've ever had any difficult installing. My user account is not able to stop the CSA service from running. I asked the group that is supposed to support the CSA for our company, and their response is that the setup program "performs a buffer overflow, which we consider an unsafe action, and was terminated". Any suggestions? "Erland Sommarskog" wrote: Craig Stewart (castewa (AT) newsgroups (DOT) nospam) writes: I have been trying for days to run the SQL 2008 setup on my machine. Basically, the setup program will not run. The first time it ran it did install a prerequisite (can't remember exactly what). Since then, though, when it tries to run, a command window appears for a fraction of a second, then it disappears, and that's all. I've looked at the log file that is created at %temp%\SqlSetup.log. In that file, I have confirmed that the correct versions of .NET and Windows Installer are present. See below: --> .Net version 3.5 is installed --> Windows Installer version detected: 4.5.6001.22159 I've compared this log file to a log file generated from a separate machine where I can successfully launch the setup program. The entries are identical except for the 4 entries noted below. Successful attempt: Timestamp: 20100322_095520 Process returned exit code: 0x00000000 Workflow LANDINGPAGE returned exit code: 0x00000000 Setup closed with exit code: 0x00000000 Unsuccessful attempt: Timestamp: 20100322_100545 Process returned exit code: 0xC0000022 Workflow LANDINGPAGE returned exit code: 0xC0000022 Setup closed with exit code: 0x84C40013 What do I need to do to resolve this issue and install SQL 2008? This may unfortunately be difficult to resolve. What happens if you run setup.exe /? from the command line? (Your current folder should of course be the one where setup.exe is located.) Normally setup.exe should list the various command-line options. If it exits without doing this, check the registry if you have this key: HKEY_LOCAL_MACHINE\Software\Microsoft\Microsoft SQL Server\100\Bootstrap And in such case delete it. In one case I know of where an MVP colleague saw this behaviour, deleting this key resolved the issue. But I cannot guarantee that it will help in your case. -- Erland Sommarskog, SQL Server MVP, esquel (AT) sommarskog (DOT) se Links for SQL Server Books Online: SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx SQL 2000: http://www.microsoft.com/sql/prodinf...ons/books.mspx . |
#7
| |||
| |||
|
|
Running "setup.exe /?" generates what I assume would be the expected output. |
|
I continued researching this yesterday and I think the cause of my issue may be the Cisco Security Agent (CSA) software that the company has installed on my laptop. It has log entries as follows: |
#8
| |||
| |||
|
|
Craig Stewart (castewa (AT) newsgroups (DOT) nospam) writes: Running "setup.exe /?" generates what I assume would be the expected output. OK, then you are not the issue I had in mind. |
|
But I you understand that it was a shot in the dark. |
![]() |
| Thread Tools | |
| Display Modes | |
| |