I have a install for my software that depends on SQL. I want to install SQL 2008 or 2012 express versions if SQL does not exist on the system. However, it is possible and likely that the system has been configured in a way that causes the SQL install to fail. I want to run a pre-install check to make sure SQL has the correct permissions to install before I attempt the install. Is there a way to call the SQL install so that you can get a return of errors without actually installing SQL. Or is there a program I can run as part of my install to check the system will not block the SQL install. My ultimate goal is to problematically set the polices and  permissions of the system, Install SQL and then reset the computer permissions to the way they were before the install.

I have just updated the installation of SQL Server 2008 Developer Edition on my PC to SQL Server 2012 Developer. During the process, a small dialogue box popped up asking me to insert a VS2010 CD. I was running VS2010 at the time and did not relate this dialogue box to the SS2012 installation. I therefore cancelled the dialogue box.

However, it became clear later that a VS2010-related part of the SQL Server 2012 had failed. Everything else was fine.

My problem is that that I have no idea how to fix that failure. Any advice would be much appreciated.

David

Hi All,

I have created a cube using SSDT in SQL Server 2012.

Now for deployment, I was told that the client cannot provide SQL Server 2012 and will just use SQL Server 2008 R2 Standard Edition instead.

I have tried restoring the backup file (.abf) and I got "Instance versions used are incompatible".

Is there any way or tool that can downgrade cube? Just like for db, I can use SSMS and generate script and specify the SQL Server version.

Regards,

Charllemagne

I built a brand new Standard Server 2012 SP1 virtual machine in a VMWare 5.1 clustered environment.  No problems with the server itself.  No errors, no issues.  I patched to SP1 with all the latest KB's.  I start the installation of SQL 2012 Standard.  Install goes fine.  I set up domain service accounts to run the server and agent on, set them up as administrators on the box.  At the end of the installation it can't start the services.  SQL Server Agent wont start.  SQL Server wont start...  I am logged in as a domain admin.

There is NOTHING else installed on this server, not even antivirus.

"Windows could not start the SQL Server (MSSQLSERVER) service on local computer.  Error 5: Access is denied."

I found a posting about someone having a similar issue Here.   There was something about permissions of the guest in VMWare.  The fix for them was "changing all of the sql server services to log on as local system" which is NOT an option for me.  I did change permissions on the SQL install folder, and that didn't help.

So I wrapped up the installation....

Tried to start the service and got the above error.  Here is the event: (Sanitized for your protection)

Log Name:      System
Source:        Service Control Manager
Date:          3/4/2013 4:16:34 PM
Event ID:      7000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      ComputerName.Domain
Description:
The SQL Server (MSSQLSERVER) service failed to start due to the following error: 
Access is denied.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Service Control Manager" Guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" EventSourceName="Service Control Manager" />
    <EventID Qualifiers="49152">7000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8080000000000000</Keywords>
    <TimeCreated SystemTime="2013-03-04T22:16:34.412450700Z" />
    <EventRecordID>1921</EventRecordID>
    <Correlation />
    <Execution ProcessID="508" ThreadID="2348" />
    <Channel>System</Channel>
    <Computer>ComputerName.Domain</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="param1">SQL Server (MSSQLSERVER)</Data>
    <Data Name="param2">%%5</Data>
    <Binary>4D005300530051004C005300450052005600450052000000</Binary>
  </EventData>
</Event>

Just before this in the security logs (When I tried to start the service:)

Log Name:      Security
Source:        Microsoft-Windows-Security-Auditing
Date:          3/4/2013 4:15:19 PM
Event ID:      4656
Task Category: File System
Level:         Information
Keywords:      Audit Failure
User:          N/A
Computer:      ComputerName.Domain
Description:
A handle to an object was requested.

Subject:
Security ID: DOMAIN\MyUserID
Account Name: MyUserID
Account Domain:FNTS
Logon ID: 0xC86050

Object:
Object Server:Security
Object Type: File
Object Name: C:\Windows\System32\services.msc
Handle ID: 0x0
Resource Attributes:-

Process Information:
Process ID: 0xfdc
Process Name: C:\Windows\System32\mmc.exe

Access Request Information:
Transaction ID:{00000000-0000-0000-0000-000000000000}
Accesses: READ_CONTROL
SYNCHRONIZE
WriteData (or AddFile)
AppendData (or AddSubdirectory or CreatePipeInstance)
WriteEA
ReadAttributes
WriteAttributes

Access Reasons:READ_CONTROL:Granted byD:(A;;0x1200a9;;;BA)
SYNCHRONIZE: Granted byD:(A;;0x1200a9;;;BA)
WriteData (or AddFile):Not granted
AppendData (or AddSubdirectory or CreatePipeInstance):Not granted
WriteEA: Not granted
ReadAttributes:Granted by ACE on parent folderD:(A;;0x1301bf;;;BA)
WriteAttributes:Not granted

Access Mask: 0x120196
Privileges Used for Access Check:-
Restricted SID Count:0
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
    <EventID>4656</EventID>
    <Version>1</Version>
    <Level>0</Level>
    <Task>12800</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8010000000000000</Keywords>
    <TimeCreated SystemTime="2013-03-04T22:15:19.640384100Z" />
    <EventRecordID>1730094</EventRecordID>
    <Correlation />
    <Execution ProcessID="516" ThreadID="524" />
    <Channel>Security</Channel>
    <Computer>ComputerName.Domain</Computer>
    <Security />
  </System>
  <EventData>
    <Data Name="SubjectUserSid">S-1-5-21-1724424548-855808307-1441089987-1194</Data>
    <Data Name="SubjectUserName">MyUserID</Data>
    <Data Name="SubjectDomainName">DOMAIN</Data>
    <Data Name="SubjectLogonId">0xc86050</Data>
    <Data Name="ObjectServer">Security</Data>
    <Data Name="ObjectType">File</Data>
    <Data Name="ObjectName">C:\Windows\System32\services.msc</Data>
    <Data Name="HandleId">0x0</Data>
    <Data Name="TransactionId">{00000000-0000-0000-0000-000000000000}</Data>
    <Data Name="AccessList">%%1538
%%1541
%%4417
%%4418
%%4420
%%4423
%%4424
</Data>
    <Data Name="AccessReason">%%1538:%%1801D:(A;;0x1200a9;;;BA)
%%1541: %%1801D:(A;;0x1200a9;;;BA)
%%4417: %%1805
%%4418: %%1805
%%4420: %%1805
%%4423: %%1811D:(A;;0x1301bf;;;BA)
%%4424: %%1805
</Data>
    <Data Name="AccessMask">0x120196</Data>
    <Data Name="PrivilegeList">-</Data>
    <Data Name="RestrictedSidCount">0</Data>
    <Data Name="ProcessId">0xfdc</Data>
    <Data Name="ProcessName">C:\Windows\System32\mmc.exe</Data>
    <Data Name="ResourceAttributes">-</Data>
  </EventData>
</Event>

"If at first you don't succeed, get a bigger hammer."

System: Windows 7 64-bit

My first mistake was trying tro install SQL Server 2008(64-bit) 180 day evaluation. It never worked, couldn't get it to connect in SQL Managment Studio. There were always different errors, the main one seems to be :
TITLE: SQL Server Setup failure.
------------------------------

SQL Server Setup has encountered the following error:

The given key was not present in the dictionary.

I get this error whether I try to repair, add or uninstall. I tried every article I could find from MSDN and other blog sites. I was at one time able to uninstall things and remove registry keys. I then tried to reinstall SQL Server Express thinking maybe it was easier. I got the same problem. I was able to get an instance to connect, but it wouldn't allow me to install reporting services. So after three weeks I went back to a earlier restore point now I have the same mess I started with. I have too much data to try and reformat my drive. If some one could tell me how to fully remove all aspects of SQL and then how to install SQL Server Express w/Advanced Services. Another thing I noticed is when I tried to install SQL Server Express 64-bit, it kept telling me there were compatibility issues. I then tried to install SQL Server Express SP1 as was advised by MS, but none of this has helped. I think I have so much stuff installed over other installs that I am hopelessly lost. If you can help please let me know. If you need error logs or event logs let me know how to get them and I will provide what I can.

Thanks. 

Hi,

We have setup a domain service account during SQL Server installation and everything works fine except that users can't connect from other instances to this machine using their somain account (user domain account have read only access to database) and get "cannot generate SSPI context", when I modify the default service account for "SQL Server" service to localsystem and then it works fine but we don't want to use localsystem account. What can be the possible issue that is causing this error when using domain account as service account for SQL Server i.e. do we need to some command to give access or need some different priveleges for this account?

Hello All

Is it required the Active directory for config the transaction replication  on b/w two different servers.

Hi,

We installed the following in this order:

Windows 2012

SQL Server 2008 as named instance

SQL Server 2012 as default instance

SQL Server 2012 configuration manager is installed but only showing me services for names instance(2008) and not for SQL Server 2012, what can be the possible issue?

I recently installed winxp mode on my windows 7 (32 bit) laptop.  Within the XPmode I installed sql server and it is working fine.

Now I would like to access those sql tables on application installed on the win7 side.  For instance, I use MS Access and would like to link the sql tables.  When I try to use the sql server dsn configuration, the xpmode sql server is available but I can not connect to it.  I've tried installing loopback adapters but I can't get a connection.

Can anybody help with this situation

Thanks,

I am working through Administering Microsoft SQL Server 2012 Databases Training Kit from Microsoft Press.

In chapter 1 we install a core Windows Server 2008 R2, then we use the command prompt (because their is no GUI on a core install) to install SQL Server 2012. The base install of SQL Server 2012 has Named Pipes and TCP/IP access disabled, but the exercises require that I connect from a remote machine using SQL Server Managerment Studio. Obviously, being a core install, I can't use the SQL Server Configuration Manager to change this.

How do I enable Named Pipes and TCP/IP from the command prompt on a core Windows Server 2008 R2 install? I can uninstall SQL Server then reinstall with the setting enabled, but that would be impractical in a production environment so there must be a way.

Somehow I think I made a mistake and installed 32 bit SQL Server C:\Program Files (x86)\Microsoft SQL Server\MSSQL11.MSSQL2012\MSSQL\Binn\sqlservr.exe on Windows 7 64 bit OS instead of 65 bit SQL Server. Is it possible to have a 32 bit and a 64 bit SQL Server 2012 installation on the same computer? If not, should I change it to 64 bit SQL Server and if so how can I do that?

My SQL Server 2008 R2 instance is 64 bit. C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQL2008R2\MSSQL\Binn\sqlservr.exe

Patrick Wood,
Founder, Gaining Access Technologies http://gainingaccess.net/

I've tried installing Security Update for SQL Server 2005 Service Pack 4 (KB2716427) to our SQL Server 2005 Server which is currently runing 9.0.5292, but it fails.

It manages to install the Integration Services and Tools, but Database services fails to install with this message:

Product Installation Status
Product                   : SQL Server Database Services 2005 (MSSQLSERVER)
Product Version (Previous): 5292
Product Version (Final)   :
Status                    : Failure
Log File                  : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Hotfix\SQL9_Hotfix_KB2716427_sqlrun_sql.msp.log
Error Number              : 11032
Error Description         : Unable to install Windows Installer MSP file

Looking in HotFix.Log I can see:

03/05/2013 12:05:06.018 Copy Engine: Error, unable to install MSP file: f:\f728e69179bd8bda133a04855b7de1cf\HotFixSQL\Files\sqlrun_sql.msp
03/05/2013 12:05:06.080 The following exception occurred: Unable to install Windows Installer MSP file  Date: 03/05/2013 12:05:06.080  File: \depot\sqlvault\stable\setupmainl1\setup\sqlse\sqlsedll\copyengine.cpp  Line: 807

And then in the actual sql.msp.log file itself:

MSI (s) (0C:88) [12:05:05:488]: Windows Installer installed an update. Product Name: Microsoft SQL Server 2005 (64-bit). Product Version: 9.4.5000.00. Product Language: 1033. Manufacturer: Microsoft Corporation. Update Name: Hotfix 5324 for SQL Server Database Services 2005 (64-bit) ENU (KB2716427). Installation success or error status: 1603.

MSI (s) (0C:88) [12:05:05:519]: Note: 1: 1729
MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (0C:88) [12:05:05:519]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:519]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (0C:88) [12:05:05:534]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:534]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:534]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (0C:88) [12:05:05:534]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:534]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (0C:88) [12:05:05:534]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:534]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (0C:88) [12:05:05:534]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:534]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (0C:88) [12:05:05:534]: Transforming table Error.

MSI (s) (0C:88) [12:05:05:534]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (0C:88) [12:05:05:534]: Product: Microsoft SQL Server 2005 (64-bit) -- Configuration failed

I can't see any other relevant error messages - I have a 7MB Log file but it's not at all clear what is causing the error. Any ideas?

Is it ok to restart the agent service any time (i need to restart it for enabling the email alert option in sql agent properties..otherwise it doesnt work)? Does restarting sql agent affect replication jobs and other scheduled jobs? Are there any issues restarting agent on production?  

Thanks Ranveer Katiyar

Hello !

I tried to install SQL Server 2008 R2 Express (Runtime Only) SQLEXPR-x86DEU.execompletely new.

It doesn't work and I tried to uninstall (Control Panel) and install it again, more times. Last Installation I made the mistake and give anohter name for the SQL instance (MSSQLExpress)

Now I have in Folder c:\..\Programme(86)\Microsoft SQL Server\
\80
\90
\100
\MSSQL10SQLEXPRESS
\MSSQL10_50.MSSQLEXPRESS

I tried to uninstall in Control Panel and I uninstall separate components, but I can not properly uninstall SQL Server Express.
I see only one component to uninstall: SDK.
However I get the Message that there is not funtions to uninstall (..Setup  Bootstrap\log\ConfigurationFile.ini)

My Question:
Can I uninstall manually with:
  Setup.exe Action = uninstall /FEATURES SDK /INSTANCENAME = Instance_Name = SQLEXPRESS
or
  Setup.exe Action = uninstall /FEATURES TOOLS /INSTANCENAME = Instance_Name = SQLEXPRESS

and the same for  Instance_Name = MSSQLEXPRESS

Is there anything I can try before I begin to touch the registry Keys ?
I want to uninstall everything related to SQL without damage the Windows installation. I prefer not to touch the registry Keys.

Thank you !  (sorry for my bad english)

Logs Files:

Summary file:
-------------------------------
Detailed results:

Rules with failures:

Global rules:

There are no scenario-specific rules.

Rules report file:               C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20130311_151547\SystemConfigurationCheck_Report.htm

Exception summary:
The following is an exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented

Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
    Message:
        Der Benutzer hat den Vorgang abgebrochen.
    Stack:
        bei Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
        bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
        bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
        bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
        bei Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
        bei Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
        bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
--------------------------------

in Detail file :
--------------------------------
2013-03-11 15:16:40 Slp: Rules evaluation report is available now at C:\Program Files (x86)\Microsoft SQL Server\100\Setup Bootstrap\Log\20130311_151547\SystemConfigurationCheck_Report.htm
2013-03-11 15:16:43 Slp: Attempting to save the input setting 'CONFIGURATIONFILE' into datastore
2013-03-11 15:16:43 Slp: Setting source: UI
2013-03-11 15:16:43 Slp: Getting hosting object 'Microsoft.SqlServer.Configuration.SetupExtension.SlpChainerInputSettings' from datastore and updating property 'ConfigurationFile'.
2013-03-11 15:16:43 Slp: Serializing the hosting object back datastore.
2013-03-11 15:16:43 Slp: Update input setting store with the new source information
2013-03-11 15:17:00 Slp: Received cancel request from user, skipping remaining scheduled actions
2013-03-11 15:17:00 Slp: Error: Action "Microsoft.SqlServer.Configuration.UIExtension.WaypointAction" threw an exception during execution.
2013-03-11 15:17:00 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Der Benutzer hat den Vorgang abgebrochen. ---> Microsoft.SqlServer.Chainer.Infrastructure.CancelException: Der Benutzer hat den Vorgang abgebrochen.
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2013-03-11 15:17:00 Slp:    --- Ende der internen Ausnahmestapelüberwachung ---
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2013-03-11 15:17:00 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
2013-03-11 15:17:00 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Der Benutzer hat den Vorgang abgebrochen. ---> Microsoft.SqlServer.Chainer.Infrastructure.CancelException: Der Benutzer hat den Vorgang abgebrochen.
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2013-03-11 15:17:00 Slp:    --- Ende der internen Ausnahmestapelüberwachung ---
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2013-03-11 15:17:00 Slp: Error: Action "Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction" threw an exception during execution.
2013-03-11 15:17:00 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Der Benutzer hat den Vorgang abgebrochen. ---> Microsoft.SqlServer.Chainer.Infrastructure.CancelException: Der Benutzer hat den Vorgang abgebrochen.
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2013-03-11 15:17:00 Slp:    --- Ende der internen Ausnahmestapelüberwachung ---
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionEngine.RunActionQueue()
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.Workflow.RunWorkflow(WorkflowObject workflowObject, HandleInternalException exceptionHandler)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Configuration.BootstrapExtension.ExecuteWorkflowAction.ExecuteAction(String actionId)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionWithRetryHelper(WorkflowObject metaDb, ActionKey action, ActionMetadata actionMetadata, TextWriter statusStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2013-03-11 15:17:00 Slp:    bei Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2013-03-11 15:17:00 Slp: Received request to add the following file to Watson reporting: C:\Users\teubert\AppData\Local\Temp\tmp2C9.tmp
2013-03-11 15:17:00 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2013-03-11 15:17:00 Slp: Inner exceptions are being indented
2013-03-11 15:17:00 Slp:
2013-03-11 15:17:00 Slp: Exception type: Microsoft.SqlServer.Chainer.Infrastructure.CancelException
2013-03-11 15:17:00 Slp:     Message:
2013-03-11 15:17:00 Slp:         Der Benutzer hat den Vorgang abgebrochen.
2013-03-11 15:17:00 Slp:     Stack:
2013-03-11 15:17:00 Slp:         bei Microsoft.SqlServer.Configuration.UIExtension.Request.Wait()
2013-03-11 15:17:00 Slp:         bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.SubmitAndWait(Request request)
2013-03-11 15:17:00 Slp:         bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceProxy.NavigateToWaypoint(String moniker)
2013-03-11 15:17:00 Slp:         bei Microsoft.SqlServer.Configuration.UIExtension.UserInterfaceService.Waypoint(String moniker)
2013-03-11 15:17:00 Slp:         bei Microsoft.SqlServer.Configuration.UIExtension.WaypointAction.ExecuteAction(String actionId)
2013-03-11 15:17:00 Slp:         bei Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2013-03-11 15:17:00 Slp:         bei Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.ExecuteActionHelper(TextWriter statusStream, ISequencedAction actionToRun)

we are trying to install SQL server 2008 R2 in windows server 2008 R2, but while install following error occurred:

so we install and check following hot fix in our server, after check hotfix no error found. but till error occurred.

http://support.microsoft.com/kb/947821

so how to solve this issue.

Jey

I have a SQL Server 2008 developer edition which I had bough from MIcrosoft Store for US $50:00.  I want to get a SQL Server 2012 Developer Edition. I am not interested in SQL Server 2012 Express Edition or some Local DB edition; instead in Developer Edition which is supposed to have all the functionality of Enterprise Edition.

Seraching google I did not find one, so posting this question to experts.