Error when opening a Lookup in a Legacy DTS package

Hi all,

the SQL Management Studio keeps crashing out on me everytime i try to open a Lookup in one of my DTS packages i am using in the Legacy section.

I am copying the DTS package across and need to change the server connections (which i do), but then i was getting a permissions based error when the package ran when it tries to access the Lookup.

I tried to open the Lookup and the SQL Management Studio hanged when it tried to display the details for the lookup. It's done this many times and i have tried different files incase one was corrupted to no avail.

Anyone have any ideas of what i can try?

Thanks

Jordan

Hi Jordan,

Want to know the following:

1) Have you installed DTS 2000 Designer utility from the Feature Pack release?

2) Once the above utility is installed and then importing the DTS package into Legacy section of Management Studio, are you able to successfully decrypt the Package with password you have used to encrypt and open it successfully?

3) Assuming that this file is corrupt, another way is to embed your DTS Package in a newly created SSIS Package using DTS 2000 Task.

Hope ensuring the above steps should solve your problem.

Thanks

Subhash Subramanyam

|||

Hi Subhash,

1) How do i determine this? I can already view the DTS package in the Legacy section of 2005, does this mean it is already installed?

2) To install the package i have Saved it out of SQL 2000 as a DTS file and opened the package in SQL 2005 and saved it to the server. Should i be doing something else?

3) i haven't looked at SSIS yet. I'm not sure what that would involve.

Thanks

Jordan

Subhash512525 wrote:

Hi Jordan,

Want to know the following:

1) Have you installed DTS 2000 Designer utility from the Feature Pack release?

2) Once the above utility is installed and then importing the DTS package into Legacy section of Management Studio, are you able to successfully decrypt the Package with password you have used to encrypt and open it successfully?

3) Assuming that this file is corrupt, another way is to embed your DTS Package in a newly created SSIS Package using DTS 2000 Task.

Hope ensuring the above steps should solve your problem.

Thanks

Subhash Subramanyam

Error when execute the packages

All,

Could someone please tell me what to do with it and what might be causing it?

The packages were fine yesterday.

Here is the error message:

[Script Component 1 1 [3941]] Error: System.Runtime.InteropServices.COMException (0x80040154):

Retrieving the COM class factory for component with CLSID {A138CF39-2CAE-42C2-ADB3-022658D79F2F}

failed due to the following error:

80040154.at Microsoft.VisualBasic.Vsa.VsaEngine.CreateEngine()

at Microsoft.VisualBasic.Vsa.VsaEngine.CheckEngine()

at Microsoft.VisualBasic.Vsa.VsaEngine.set_RootMoniker(String value)

at Microsoft.SqlServer.VSAHosting.Runtime.CreateVsaEngine()

at Microsoft.SqlServer.Dts.Pipeline.ScriptRuntime..ctor(String projectName,

String moniker, String language, Boolean showErrorUI)

at Microsoft.SqlServer.Dts.Pipeline.ScriptComponentHost.CreateUserComponent()

Thanks in Advance

Check this KB:

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

Error when attempting to use SQL Server Import and Export Wizard

I'm unable to use SSIS packages after installing SQL Server 2005. Specifically when I first loaded a new Integration Services project in SQL Server Business Intelligence Development Studio the default SSIS package could not load, I get Package.dtsx in my tabbed document view but in the body of this window is a error message: "Microsoft Visual Studio is unable to load this document. QI for IEnumVARIANT failed on the unmanaged server."

If I try to use the SQL Server Import and Export Wizard shortly after the window to select your data source I get a pop-up error message:

This wizard will close because it encountered the following error:

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.SqlServer.Management.UI.WizardFrameworkErrorSR&EvtID=UncaughtException&LinkId=20476

ADDITIONAL INFORMATION:

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

Anyone have any ideas on how I can resolve this?

I have experienced the same problem. Have you found a solution yet?

I found other users experiencing similar problems, but apparently not the same issue. I tried the fix at 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

but had no luck.

Error when attempting to use SQL Server Import and Export Wizard

I'm unable to use SSIS packages after installing SQL Server 2005. Specifically when I first loaded a new Integration Services project in SQL Server Business Intelligence Development Studio the default SSIS package could not load, I get Package.dtsx in my tabbed document view but in the body of this window is a error message: "Microsoft Visual Studio is unable to load this document. QI for IEnumVARIANT failed on the unmanaged server."

If I try to use the SQL Server Import and Export Wizard shortly after the window to select your data source I get a pop-up error message:

This wizard will close because it encountered the following error:

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.SqlServer.Management.UI.WizardFrameworkErrorSR&EvtID=UncaughtException&LinkId=20476

ADDITIONAL INFORMATION:

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

Anyone have any ideas on how I can resolve this?

I have experienced the same problem. Have you found a solution yet?

I found other users experiencing similar problems, but apparently not the same issue. I tried the fix at 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

but had no luck.

error trying to import packages to the MSDB

When I try import a SSIS package into the MSDB I get the following error message:

TITLE: Microsoft SQL Server Management Studio

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

ADDITIONAL INFORMATION:

The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2005 Books Online.

The .Net Framework OleDb Data Provider requires Microsoft Data Access Components(MDAC) version 2.6 or later. Version 2.12.4202.3 was found currently installed. (MsDtsSrvr)

BUTTONS:

OK

I do have default instance installed and the SSIS servie is running. When I look at the SSIS service configuration it shows a period for the server which I thought meant local host. Also I have MDAC 2.8 installed. What else do I need to look at?

Try the MDAC version checker just to be sure you have the correct version. http://support.microsoft.com/default.aspx?kbid=301202

As you can see from the error message this is more likely to be an MDAC issue than an SSIS issue per se, but let's see what the version says first.

Donald

|||The version checker shows that 2.8 is installed but the Registry setting shows 2.1. We had this issue before and just had to install 2003 OS Sp 1 again.|||

So you think you may be able to fix this again? If so, great. If not, I think the SQL Server Data Access forum would be the right place to get help.

thanks

Donald

|||

Phil,

Do you have multiple instances installed on your server? If not you might try hard coding your server name into your SSIS configuration file

<ServerName>my-server-01</ServerName>

I had the same error when I tried to view an SSIS package on my server with 2 instances but I had no default instance, so my case was a little different than yours. The way I resolved my problem was by hard coding both instances into my config file

<ServerName>my-server-01\instance1</ServerName>
<ServerName>my-server-01\instance2</ServerName>

If you have a default instance and a named instance you might try something like this:

<ServerName>my-server-01</ServerName>
<ServerName>my-server-01\instance1</ServerName>

This did the trick for me, hopefully it will work for you.