QI for IEnumVARIANT failed on the unmanaged server. (CustomMarshalers)

I am getting the following message when I attempt to Export data in SQL Management Studio from my workstation. The error occurs as soon as I click Next to go to the Source Data Sources page of the Export wizzard. I am using SQL Server 2005 Management Studio. I get a similar error in Visual Studio 2005 when I attempt to open a SSIS project. When I click on the link in the error message the page at Micorsoft Help says there is no explanation. Any ideas on what might be wrong or what settings I am missing?

The error text is:

This wizard will close because it encountered the following error: (Microsoft SQL Server)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.UI.WizardFrameworkErrorSR&EvtID=UncaughtException&LinkId=20476

===================================

QI for IEnumVARIANT failed on the unmanaged server. (CustomMarshalers)

Program Location:

at System.Runtime.InteropServices.CustomMarshalers.EnumeratorToEnumVariantMarshaler.MarshalNativeToManaged(IntPtr pNativeData)
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSDBProviderInfos90.GetEnumerator()
at Microsoft.SqlServer.Dts.DtsWizard.DataSourceCombo.PopulateProviders(Boolean fSources, WizardInputs wizardInputs)
at Microsoft.SqlServer.Dts.DtsWizard.Step1.OnInitializePage(EventArgs e)
at Microsoft.SqlServer.Management.UI.WizardPage.RaiseEnterPage()
at Microsoft.SqlServer.Management.UI.WizardForm.NextPage(WizardPage nextPage)
at Microsoft.SqlServer.Management.UI.WizardForm.Next_Click(Object sender, EventArgs e)

Review this thread http://groups-beta.google.com/group/microsoft.public.dotnet.framework.setup/browse_thread/thread/a2ed96d68cb349f3/db810a1bcf8f66e4?q=qi+ienumvariant&_done=%2Fgroups%3Fhl%3Den%26lr%3Dlang_en%26safe%3Doff%26c2coff%3D1%26q%3Dqi+ienumvariant%26qt_s%3DSearch+Groups%26&_doneTitle=Back+to+Search&&d#db810a1bcf8f66e4 in other groups that might help to resolve the issue.

HTH

|||This may be due to InstallShield. Here is their solution: http://support.installshield.com/kb/view.asp?articleid=q106194

QI for IEnumVARIANT failed on the unmanaged server. (CustomMarshalers)

I am getting the following message when I attempt to Export data in SQL Management Studio from my workstation. The error occurs as soon as I click Next to go to the Source Data Sources page of the Export wizzard. I am using SQL Server 2005 Management Studio. I get a similar error in Visual Studio 2005 when I attempt to open a SSIS project. When I click on the link in the error message the page at Micorsoft Help says there is no explanation. Any ideas on what might be wrong or what settings I am missing?

The error text is:

This wizard will close because it encountered the following error: (Microsoft SQL Server)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.UI.WizardFrameworkErrorSR&EvtID=UncaughtException&LinkId=20476

===================================

QI for IEnumVARIANT failed on the unmanaged server. (CustomMarshalers)

Program Location:

at System.Runtime.InteropServices.CustomMarshalers.EnumeratorToEnumVariantMarshaler.MarshalNativeToManaged(IntPtr pNativeData)
at Microsoft.SqlServer.Dts.Runtime.Wrapper.IDTSDBProviderInfos90.GetEnumerator()
at Microsoft.SqlServer.Dts.DtsWizard.DataSourceCombo.PopulateProviders(Boolean fSources, WizardInputs wizardInputs)
at Microsoft.SqlServer.Dts.DtsWizard.Step1.OnInitializePage(EventArgs e)
at Microsoft.SqlServer.Management.UI.WizardPage.RaiseEnterPage()
at Microsoft.SqlServer.Management.UI.WizardForm.NextPage(WizardPage nextPage)
at Microsoft.SqlServer.Management.UI.WizardForm.Next_Click(Object sender, EventArgs e)

Review this thread http://groups-beta.google.com/group/microsoft.public.dotnet.framework.setup/browse_thread/thread/a2ed96d68cb349f3/db810a1bcf8f66e4?q=qi+ienumvariant&_done=%2Fgroups%3Fhl%3Den%26lr%3Dlang_en%26safe%3Doff%26c2coff%3D1%26q%3Dqi+ienumvariant%26qt_s%3DSearch+Groups%26&_doneTitle=Back+to+Search&&d#db810a1bcf8f66e4 in other groups that might help to resolve the issue.

HTH

|||This may be due to InstallShield. Here is their solution: http://support.installshield.com/kb/view.asp?articleid=q106194

QI for IEnumVARIANT failed on the unmanaged server

I have an SSIS project created with Beta 2 of VS2005. When I try to open the SSIS Package in the Designer with the final version of VS2005 I get the error message:

Microsoft Visual Studio is unable to load this document
QI for IEnumVARIANT failed on the unmanaged server

Before that happens there is a warning Message: "Document contains one or more extremely long lines of text. These lines will cause the editor to respond slowly when you open the file. Do you still want to open the file?"

When click on Yes to this question the above Error occurs. In the Beta I got the same warning message, but the package was still able to load in the designer.

Is there a way to recover or migrate my package so that I can use it in the final VS2005?

Torsten

I get a very similar problem. I'm just starting on my learning curve for SSIS and am trying to create a new package using the SQL Server Import Export Wizard. The wizard fails and reports the exact same error you mention.|||

Possible problem is InstallShield. Here is their solution: http://support.installshield.com/kb/view.asp?articleid=q106194

|||Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS|||

RoMoVi wrote:

Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS

These are English based forums. Please avoid the use of Spanish.

I don't believe NSIS is a solution to the InstallShield problem as a simple upgrade to InstallShield should suffice.

QI for IEnumVARIANT failed on the unmanaged server

I have an SSIS project created with Beta 2 of VS2005. When I try to open the SSIS Package in the Designer with the final version of VS2005 I get the error message:

Microsoft Visual Studio is unable to load this document
QI for IEnumVARIANT failed on the unmanaged server

Before that happens there is a warning Message: "Document contains one or more extremely long lines of text. These lines will cause the editor to respond slowly when you open the file. Do you still want to open the file?"

When click on Yes to this question the above Error occurs. In the Beta I got the same warning message, but the package was still able to load in the designer.

Is there a way to recover or migrate my package so that I can use it in the final VS2005?

Torsten

I get a very similar problem. I'm just starting on my learning curve for SSIS and am trying to create a new package using the SQL Server Import Export Wizard. The wizard fails and reports the exact same error you mention.|||

Possible problem is InstallShield. Here is their solution: http://support.installshield.com/kb/view.asp?articleid=q106194

|||Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS|||

RoMoVi wrote:

Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS

These are English based forums. Please avoid the use of Spanish.

I don't believe NSIS is a solution to the InstallShield problem as a simple upgrade to InstallShield should suffice.

QI for IEnumVARIANT failed on the unmanaged server

I have an SSIS project created with Beta 2 of VS2005. When I try to open the SSIS Package in the Designer with the final version of VS2005 I get the error message:

Microsoft Visual Studio is unable to load this document
QI for IEnumVARIANT failed on the unmanaged server

Before that happens there is a warning Message: "Document contains one or more extremely long lines of text. These lines will cause the editor to respond slowly when you open the file. Do you still want to open the file?"

When click on Yes to this question the above Error occurs. In the Beta I got the same warning message, but the package was still able to load in the designer.

Is there a way to recover or migrate my package so that I can use it in the final VS2005?

Torsten

I get a very similar problem. I'm just starting on my learning curve for SSIS and am trying to create a new package using the SQL Server Import Export Wizard. The wizard fails and reports the exact same error you mention.|||

Possible problem is InstallShield. Here is their solution: http://support.installshield.com/kb/view.asp?articleid=q106194

|||Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS|||

RoMoVi wrote:

Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS

These are English based forums. Please avoid the use of Spanish.

I don't believe NSIS is a solution to the InstallShield problem as a simple upgrade to InstallShield should suffice.

QI for IEnumVARIANT failed on the unmanaged server

I have an SSIS project created with Beta 2 of VS2005. When I try to open the SSIS Package in the Designer with the final version of VS2005 I get the error message:

Microsoft Visual Studio is unable to load this document
QI for IEnumVARIANT failed on the unmanaged server

Before that happens there is a warning Message: "Document contains one or more extremely long lines of text. These lines will cause the editor to respond slowly when you open the file. Do you still want to open the file?"

When click on Yes to this question the above Error occurs. In the Beta I got the same warning message, but the package was still able to load in the designer.

Is there a way to recover or migrate my package so that I can use it in the final VS2005?

Torsten

I get a very similar problem. I'm just starting on my learning curve for SSIS and am trying to create a new package using the SQL Server Import Export Wizard. The wizard fails and reports the exact same error you mention.|||

Possible problem is InstallShield. Here is their solution: http://support.installshield.com/kb/view.asp?articleid=q106194

|||Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS|||

RoMoVi wrote:

Bien!
Esa es la solución.

Recomendación: No usar InstallShield, un fallo como este es imperdonable

Prueba y aprende NSIS

These are English based forums. Please avoid the use of Spanish.

I don't believe NSIS is a solution to the InstallShield problem as a simple upgrade to InstallShield should suffice.