SQL Server Express 2008 with SP1 Setup fails with error code -213508975 - by RL Carter

Status : 

  Not Reproducible<br /><br />
		The product team could not reproduce this item with the description and steps provided.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.


0
0
Sign in
to vote
ID 471609 Comments
Status Closed Workarounds
Type Bug Repros 2
Opened 6/30/2009 10:58:25 PM
Access Restriction Public

Description

Log File: Detail_GlobalRules.txt
Error: Action "LoadExtensions" threw an exception during execution.
Microsoft.SqlServer.Setup.Chainer.Workflow.ActionExecutionException: Object of type 'Microsoft.SQL.Chainer.Package.PropertiesTypeProperty' cannot be converted to type 'Microsoft.SQL.Chainer.Package.PropertiesTypeProperty'.-> System.ArgumentException: Object of type 'Microsoft.SQL.Chainer.Package.PropertiesTypeProperty' cannot be converted to type 'Microsoft.SQL.Chainer.Package.PropertiesTypeProperty'.
at System.RuntimeType.CheckValue(Object value, Binder binder, CultureInfo culture, BindingFlags invokeAttr)
at System.Reflection.MethodBase.CheckArguments(Object[] parameters, Binder binder, BindingFlags invokeAttr, CultureInfo culture, Signature sig)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionDatastoreIntegration.SetPropertiesOnRunningAction(ActionKey key, TextWriter loggingStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifyInExecution(ActionKey actionRunning, TextWriter loggingStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
-End of inner exception stack trace-
at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
Exception stack listing the exceptions in outermost to innermost order
Inner exceptions are being indented
Exception type: System.ArgumentException
Message: Object of type 'Microsoft.SQL.Chainer.Package.PropertiesTypeProperty' cannot be converted to type 'Microsoft.SQL.Chainer.Package.PropertiesTypeProperty'.
Stack: at System.RuntimeType.CheckValue(Object value, Binder binder, CultureInfo culture, BindingFlags invokeAttr)
at System.Reflection.MethodBase.CheckArguments(Object[] parameters, Binder binder, BindingFlags invokeAttr, CultureInfo culture, Signature sig)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionDatastoreIntegration.SetPropertiesOnRunningAction(ActionKey key, TextWriter loggingStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionMetadata.NotifyInExecution(ActionKey actionRunning, TextWriter loggingStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.ActionInvocation.InvokeAction(WorkflowObject metabase, TextWriter statusStream)
at Microsoft.SqlServer.Setup.Chainer.Workflow.PendingActions.InvokeActions(WorkflowObject metaDb, TextWriter loggingStream)
Original Parameter Values 
Parameter 0 : SQL2008@RTM@ 
Parameter 1 : System.RuntimeType.CheckValue 
Parameter 2 : System.RuntimeType.CheckValue 
Parameter 3 : System.ArgumentException@-2147024809 
Parameter 4 : System.ArgumentException@-2147024809 
Parameter 5 : LoadExtensions 
Final Parameter Values 
Parameter 0 : SQL2008@RTM@
Sign in to post a comment.
Posted by Tim Owers on 11/4/2009 at 3:51 AM
This error is being discussed widely as it is such a common issue.
Microsoft MUST be aware of this but has said/done nothing.
On some machines the error is consistently reproducible. On other machines a failure may be followed by a success. It appears completely random. The OS is irrelevant, the SP is irrelevant, the installation folder location is irrelevant, the current user account SeDebugPrivelege security privilege level/membership is also irrelevant.
We need to ship this as part of our product installation(s) to tens of thousands of customers. In it's current state that is just not possible.
Microsoft - you really have to make this your number one priority and get this fixed. Until this happens we will have to continue with SQL 2005.
Posted by Microsoft on 8/25/2009 at 5:09 PM
I am going to resolve this issue as no repro since the logs have not been provided.

Thanks,
Peter Saddow [Microsoft]
Posted by Microsoft on 7/31/2009 at 8:57 PM
Sorry about the delay in responding. if you need help troubleshooting; please attached the setup log files.

Thanks,
Peter Saddow [Microsoft]