Sql2k8 (dev x64) fails on PassPidBackFromComponentUpdate 0x80070006 (E_HANDLE) - by oj-Updated

Status : 

 


2
0
Sign in
to vote
ID 360855 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 8/6/2008 3:20:37 PM
Access Restriction Public

Description

An attempt to install sql2k8 rtm (dev x64) fails with the 0x80070006 error. 

2008-08-06 15:03:39 Slp: Running Action: PassPidBackFromComponentUpdate
2008-08-06 15:03:39 Slp: Pass the flag CuPidDisplayed to the main setup
2008-08-06 15:03:39 Slp: PID value specified, trying to pass the value to main setup
2008-08-06 15:03:39 Slp: Error: Action "PassPidBackFromComponentUpdate" threw an exception during execution.
2008-08-06 15:03:39 Slp: Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: The handle is invalid. (Exception from HRESULT: 0x80070006 (E_HANDLE)) ---> System.Runtime.InteropServices.COMException (0x80070006): The handle is invalid. (Exception from HRESULT: 0x80070006 (E_HANDLE))
2008-08-06 15:03:39 Slp:    at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
2008-08-06 15:03:39 Slp:    at Microsoft.SqlServer.Configuration.BootstrapExtension.PassPidBackFromComponentUpdateAction.ExecuteAction(String actionId)
2008-08-06 15:03:39 Slp:    at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2008-08-06 15:03:39 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2008-08-06 15:03:39 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2008-08-06 15:03:39 Slp:    --- End of inner exception stack trace ---
2008-08-06 15:03:39 Slp:    at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
2008-08-06 15:03:39 Slp: Received request to add the following file to Watson reporting: C:\Documents and Settings\OJ\Local Settings\Temp\tmpBA.tmp
2008-08-06 15:03:39 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
2008-08-06 15:03:39 Slp: Inner exceptions are being indented
2008-08-06 15:03:39 Slp: 
2008-08-06 15:03:39 Slp: Exception type: System.Runtime.InteropServices.COMException
2008-08-06 15:03:39 Slp:     Message: 
2008-08-06 15:03:39 Slp:         The handle is invalid. (Exception from HRESULT: 0x80070006 (E_HANDLE))
2008-08-06 15:03:39 Slp:     Stack: 
2008-08-06 15:03:39 Slp:         at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
2008-08-06 15:03:39 Slp:         at Microsoft.SqlServer.Configuration.BootstrapExtension.PassPidBackFromComponentUpdateAction.ExecuteAction(String actionId)
2008-08-06 15:03:39 Slp:         at Microsoft.SqlServer.Chainer.Infrastructure.Action.Execute(String actionId, TextWriter errorStream)
2008-08-06 15:03:39 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
2008-08-06 15:03:39 Slp:         at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)

Sign in to post a comment.
Posted by Microsoft on 8/26/2011 at 8:51 AM
this issue has beed addressed in future SPs and major versions.
Posted by Shital Shah on 9/22/2008 at 7:03 PM
Got this when installing...
Posted by Microsoft on 8/15/2008 at 3:40 PM
Thanks for contacting us, we look at addressing this issue in the next major release of SQL Server.

Thanks,
Peter Saddow [Microsoft]
Posted by oj-Updated on 8/6/2008 at 3:28 PM
Found the problem.

This is a MSDN version so the product key is pidded but it is not enabled as read-only. So, when you're presented with the product key dialog, you can muck it up.

To reproduce, simply select the "Specify a free edition" radio button without changing the shown PID, then reselect the "Enter the product key" radio button (again without changing the PID) and continue with the installation.

I expect this bug exists in all MSDN editions.