Cannot Debug SSIS packages in 64 bit mode.

Hi,
To anyone who may be able to help. We are using SQL server 2014 Enterprise addition. Visual studio 2013, SSDT latest version installed, all 64 bit tools installed. I have tried to run my packages with the "Run64bitRuntime"
set to true ( project properties-->Debugging-->Run64BitRuntime = True). Initially I thought it an issues with my package (we migrated them from SSIS 2008R2, they run fine with no issues within the 32 bit memory constraints) so I created
a super simple package with VS 2013 in the SSIS 2014 environment from scratch, a lookup and an OLEDB Data source that's it. Same problem. No matter what I do when I debug in SSIS the 32 bit process (DtsDebugHost.exe (32 bit)) fires up,
even though I have selected debug in 64 bit runtime I cannot get the 64 bit version of DtsDebugHost to run. This is an issue because I am debugging projects that will utilise more than 4GB of memory for say a particular set of lookups. Curiously
when I schedule the projects to run in the scheduler, it fires up a 64 bit process, and the package executes successfully, however if I can't debug in 64 bit mode and leverage the extra memory at the design stage,
this is useless. I have checked obvious things like the path environment variable, thinking perhaps SSIS debug doesn't know where the 64 bit exe is, but it is all fine paths are as they should be. All 64 bit tools/dll's are installed. I
have tested this directly on the server, and on the client machine that I use and the issue is the same. If no one can help me here I guess I can log a support ticket.
thanks in advance.

Hi des_77,
According to your description, you can only debug your SSIS package in 32 bit mode.
Based on my research, I think the issue is caused by 64bit SSIS runtime is not installed on your machine. We can verify the issue by seeing if DtsDebugHost.exe under <Installation Drive>\Program Files\Microsoft SQL Server\120\DTS\Binn or not.
To fix this issue, please install SQL Server and select Integration Services for installation, Setup installs all available 64-bit Integration Services features and tools. Then we can set the Debug Options property Run64BitRuntime to “True”, view the processes
in Windows Task Manager to verify the version of DTDebugHost.exe when debugging the package.
Besides, if the issue still existed, it is my pleasure to help you to reflect your recommendation to the proper department for their consideration. Please feel free to submit your situation on our product to the following link
https://connect.microsoft.com/SQLServer/. Your feedback is valuable for us to improve our products and increase the level of service provided.
References:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2014/05/22/ssis-packages-executed-from-visual-studio-business-intelligence-development-studio-bids-design-time-on-a-64bit-development-server-goes-to-unresponsive-state-during-package-execution.aspx
http://dougbert.com/blog/post/64-bit-considerations-for-sql-server-integration-services-final.aspx
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Similar Messages

Sql server agent job failing to connect excel connection manager of SSIS package by 32-bit mode run time

I am unable to succeed with sql agent job, I am trying to execute the SSIS package through sql agent job by ticking 32 bit runtime check box in 64 bit machine , even it does not worked..
could any one helpme on this?
Source: Excel Load Connection manager "Excel Connection Manager"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040154. An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class
not registered". End Error TS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Excel Connection Manager" failed with error code 0xC0202009. There may be error
messages posted before this with more information on why the AcquireConnection method call failed. End... The package execution fa... The step failed.

Hello Keerthi,
Can you please modify settings and set delay validation for Excel connection manager? I think its validating connection and failing because it might be picking that from some variable.
Alternatively, please run package using below and see what happens.
EXEC master..xp_cmdshell 'DTEXEC.exe /SQL "Folder\Package" /SERVER Servername'
I will recommend you to follow steps in below link.
http://www.sqlhammer.com/blog/running-ssis-packages-in-32-bit/
Regards,
Vishal Patel
Blog: http://vspatel.co.uk
Site: http://lehrity.com

Run SSIS programmatically in 32-bit mode on 64-bit server

Environment:
Windows Server 2003 64-bit
SSIS 32-bit & 64-bit installed
.NET 2.0 application (Platform target x86) which executes an SSIS package programatically (using Microsoft.SQLServer.ManagedDTS.dll)
The issue I am having is that we connect to a Sybase server and even though the .NET app is executing in 32-bit mode, the SSIS pack appears to try load Sybase 64-bit OLEDB drivers.
The error I receive is DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER
When I run on a 32-bit machine all runs fine or if I run using the 32-bit version of DTEXEC the package also runs fine.
Any ideas on how I can force SSIS to use 32-bit drivers when run on 64-bit server programatically?

Is there any solution to the above problem since i am facing a similar issue when trying to connect to Excel file.
The package is executed by managed code using the
Microsoft.SqlServer.Dts.Runtime namespace and Application class to load the package and execute.
The source of the data flow task in the pacakge is excel and destination is sql server database.
I tried changing ther registry settings to load the package in 32 bit mode but it seems this works only if you use DTExec utility not if you load and run the package programmatically using the above API.
Please let me know how can i load and execute the package in a 32 bit runtime"PROGRAMMATICALLY" so that 32 bit drivers like the one for Excel are available and can be loaded.
Set your custom application Platform target to: x86
SSIS Tasks Components Scripts Services | http://www.cozyroc.com/

How to Migrate SSIS packages from 32 bit to 64 bit environment

Hi,
We developed many SSIS packages in 32 bit environment using SQL 2008 on windows 2003 server 32 bit OS. In order to utilize the 64 bit features we wish to migrate these packages into a 64 bit. Wanted to know.
1. Whether we can execute these packages that are developed in 32 bit environment onto a 64 bit environment. If yes, then do we get the benefits of 64 bit environment. For ex. RAM utilization. If no, then what advantage do we get.
2. Is it possible to develop the packages directly in a 64 bit environment.
Thanks in advance,
Yog

One thing you need to make sure when migrating to 64 bit machines is to have drivers installed for 64 bit ie for providers like excel. One more thing to note is that SSDT/BIDS which is used for developing packages is by itself a 32 bit application. So
you may need to use 3 bit driver at design time and run packages with 64 bit runtime set to false at design time. And while deployed on server it can use 64 bit driver itself for its execution.
Please Mark This As Answer if it solved your issue
Please Mark This As Helpful if it helps to solve your issue
Visakh
My MSDN Page
My Personal Blog
My Facebook Page

SSIS Package opened in Design mode instantly going to MODIFIED

Hi,
I've got a really strange error - I've searched around and can't find anything relevent for it.
When I open a particular SSIS package in BIDS It loads and instantly goes to a modified state (asterisk next to file name). Nothing has changed in the package. I only have one package where this happens but it's one of my main ones.
Can anyone explain this to me? Expected behaviour? Why only this one file? Corruption? I'm using SQL Server 2012 Enterprise.
Thanks,
David

I just recently started experiencing the same behavior, and after some trial and error discovered that it's the ODBC Source component in the data flow. I'm able to replicate the problem simply by creating a new blank package, then adding a data flow task with
an ODBC Source (no actual setup of a real source/destination required).
There may be other components that result in the same behavior, and maybe it's specific just to my environment. It's a little annoying if you're the type that's paranoid about accidentally changing and saving a package, hopefully it'll be fixed in the next
iteration.

Cannot start LR2.2 in 32-bit mode (OS X)

I have been having memory leak issues as mentioned on many threads and saw that running LR in 32 bit mode can actually solve some of the issues.
So I followed the instruction, go to Info of LR in the Finder, and click Run in 32 bit mode... then run LR... Looked under Activity Monitor, still says 64 bit! Any idea?!

Hi Christopher,
Thanks for your suggestion. I already did try to repair permission!....
But I finally figured out why! I use XSlimmer and apparently after 'slimming' down LR, it can't run in 32bit mode! I reinstalled LR and is now able to run in 32 bit mode.
Thanks for your help.
ws

How to change color of rows count dispalyed while debugging ssis packages

Hello,
in visual 2013 ssdt version I have row count displayed in white color on pale background: bit.ly/1oWP1Cm
I'd like to have it in black. I know it should be changeable in Options -> Fonts and Colors, but what option should I change from myriads available?
Thank you in advance.

My colleague had the same issue in that we couldn't see the numbers. We couldn't figure out why we couldn't see the numbers and the design screen was white. It looked like the numbers were displaying in white over the connections lines. So
we changed the color scheme to light and the numbers appeared in black. WHen we switched the color scheme back to dark, the canvas turned dark and the text was in white.
So there must be a bug when selecting the color scheme on the first run of Visual Studio 2013 in that it doesn't set the correct canvas color for the SSIS designer. Luckily toggling the color scheme resolves the issue.
Christian Jones Software Developer, former Network/Sys Admin

The requested OLE DB provider SQLNCLI10.1 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode.

Locally I have 32 bit windows and the server is 64 bit. When I try to change the provider locally to SQLNCLI11.1, the connection test succeeds but when I close the package and reopen it the provider is set to 10.1 again. Do I need to install a driver locally
to get the 11.1 version to work, or is this not the issue with the error message?
Thanks

Have you set the Run64BitRunTime configuration property?
Don't forget to mark helpful posts, and answers. It helps others to find relevant posts to the same question.
I don't see that property. Is it on the connection?

SSIS package runs from BIDS and by Executing package, but failing with Job

I have SQL Serve 2012 SSIS. I have problems to run from SQL Server Agent Job.
Steps runs SSIS package without configuration file. Package Run64BitRuntime is False in BIDS.
Package is runned by SQL Server Agent Service Account.
Server does not have Office 2010/2013 installed. Should it be installed?
ERROR1:
Description: The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered.
If the 64-bit driver is not installed<c/> run the package in 32-bit mode.
ERROR2: (here SSIS package is trying to import XML source, but cannot file file)
Description: An error occurred with the following error message: "Could not find file 'D:\Integration\Metadata\'.".
Kenny_I

Hi Kenny,
It seems like you are using Excel as source file right? If yes, then please follow below steps:
Edit the job step and Check the option: Use 32 bit run time. Below is the screenshot for the same.
Please let me know for any questions.
Thanks, Madhu

Output Error When Debugging the Package

Hi,
I just created my first SSIS Package, with OLE DB Connection pointing to our Oracle server and using SQL SERVER Destination. When I Debug, I get the following error:
SSIS package "C:\Users\Documents\SQL Server Management Studio\Packageload.dtsx" starting.
Information: 0x4004300A at Load Season, SSIS.Pipeline: Validation phase is beginning.
Error: 0xC0209303 at Packageload, Connection manager "ABCDEF": The requested OLE DB provider MSDAORA.1 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000.
An OLE DB record is available. Source: "Microsoft OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered".
Error: 0xC020801C at Load Season, OLE DB Source [46]: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "ABCDEF" failed with error code 0xC0209303. There may
be error messages posted before this with more information on why the AcquireConnection method call failed.
Error: 0xC0047017 at Load Season, SSIS.Pipeline: OLE DB Source failed validation and returned error code 0xC020801C.
Error: 0xC004700C at Load Season, SSIS.Pipeline: One or more component failed validation.
Error: 0xC0024107 at Load Season: There were errors during task validation.
Warning: 0x80019002 at Packageload: SSIS Warning Code DTS_W_MAXIMUMERRORCOUNTREACHED. The Execution method succeeded, but the number of errors raised (5) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches
the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "C:\Users\Documents\SQL Server Management Studio\Packageload.dtsx" finished: Failure.
I tried setting the DelayValidation property to True, but still getting same error.
Thanks
Parul

Hi Parul,
Regarding the error “Unable to bulk copy data. You may need to run this package as an administrator”, it is described in the KB article
http://support.microsoft.com/kb/2009672:
On systems where UAC is enabled, when an application (like SSIS) is launched by an account that is a member of the Administrators group, it gets two security tokens, one a low privileged token and another an elevated token. The elevated token is only
used when the application is explicitly run under an Administrator account by choosing “Run as Administrator” option. By default SSIS always uses the low privileged token resulting in a failure when connecting to a SQL Destination.
The solution is launch the tool (SQL Server Management Studio or Business Intelligence Development Studio or DTExecUI.exe or Command Prompt) as administrator.
Regarding the original error “The requested OLE DB provider MSDAORA.1 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode”, it is because Microsoft OLE DB Provider for Oracle has only 32-bit version. To avoid this issue,
you can either run the package in 32-bit runtime mode as you have done or install the 64-bit Oracle Provider for OLE DB.
If you use Enterprise edition of SSIS 2008 or higher, you can also install the Microsoft Connector for Oracle by Attunity:
http://www.microsoft.com/en-in/download/details.aspx?id=29283
Regards,
Mike Yin
TechNet Community Support

SQL Agent Job Fails To Run A SSIS Package

Hi,
I have a SSIS Package which basically truncates the table and re-loads it from an excel file .The job runs fine if i run it manually on visual studio.However, i try to shcedule a SQL Agent job and it fails with the following error
Description: The requested OLE DB provider Microsoft.ACE.OLEDB.12.0 is not registered. If the 64-bit driver is not installed, run the package in 32-bit mode. Error code: 0x00000000. An OLE DB record is available. Source: "Microsoft
OLE DB Service Components" Hresult: 0x80040154 Description: "Class not registered". End Error Error: 2014-10-22 14:47:41.15 Code: 0xC001002B Source: Package1 Connection manager "Excel
Connection Manager 1" Description: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine.
I am exactly not sure what it means?
Can someone please help me with any suggestions on this.
Thanks.

Thanks for trying that option . It looks like there is an issue with the driver . Can you try to install/uninstall the driver once again from http://www.microsoft.com/en-us/download/details.aspx?id=13255.
You can try this URL , where he has the similar problem
https://social.msdn.microsoft.com/Forums/sqlserver/en-US/8a40d329-0611-44e2-ae51-3bd9b0901754/ssis-the-requested-ole-db-provider-microsoftaceoledb120-is-not-registered?forum=sqlintegrationservices
Please mark this as answer if this helps to solve your problem

SSIS packages are failing after upgrade to SQL server 2014

Hi,
I have some SSIS packages running on SQL server 2012 .
After I upgraded to SQL server to 2014 from 2012 , the SSIS jobs are failing on the SQL agent.
And i can see its related to Data source connectivity to the SQL agent. I hope it not able to identify the connection manager in SQL agent. And connection adapter is not upgraded.
I read some articles about this and they say it not able to connect to SQL server agent job.
And, I can see that the package is running if i run manually using SQL 2012 run time.
Why its not running on SQL 2014 ?
did i miss anything while upgrading SQL server 2014 ?
Please give me some suggestions to solve this issue.
And is there any way i can change the SQL server agent 2014 to adapt this and run ?
Below is the error :
The Package filed to load due to error 0XC00100014 " One or more error occurres. There should be more specific errors preceding this one that expalins the details of the erroes. This message is used as a return value from functions that encounter
errors.: This occures when CPackage::LoadFormXML fails.
Regards,
Vinodh Selvaraj.

I think you have typed this error message by yourself.
Anyway, as it says there should be more error preceeding to this. Do you have any other errors which describles the exact issue stating at what task it fails?
If not, then there are various reasons behind this issue. 3rd party connection manager such as Oracle Attunity or it may be 32/64 bit issue.
You may try executing package in 32 bit mode from SQL Agent Job.
Please refer:
http://blogs.msdn.com/b/farukcelik/archive/2010/06/16/why-package-load-error-0xc0010014-in-cpackage-loadfromxml-error-appears-while-trying-to-run-an-ssis-package.aspx
http://www.bidn.com/blogs/timmurphy/ssas/1397/package-failed-to-load-due-to-error-0xc0010014
-Vaibhav Chaudhari

SSIS Package failure

Message
Executed as user: ABC\abcprod. Microsoft (R) SQL Server Execute Package Utility Version 9.00.5292.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 12:00:00 AM Progress: 2014-11-09 00:00:40.48
Source: {50E2FC2E-7266-46D3-9D9A-6034DEB03BEE} Executing query "DECLARE @Guid UNIQUEIDENTIFIER EXECUTE msdb..sp".: 100% complete End Progress Progress: 2014-11-09 00:09:39.69
Source: Execute T-SQL Statement Task Executing query "-- Cursor updates usage for all non system databas".: 100% complete End Progress DTExec: The package execution returned DTSER_FAILURE (1). Started:
12:00:00 AM Finished: 12:09:41 AM Elapsed: 581.156 seconds. The package execution failed. The step failed.
Upon research in google I found to change run value to "0" where as when I checked sp_configure"allow updates" it shows "0" so I don't think it is an issue.
I am running User Databases Optimization and Index Check Plan
SQL Version is:
Microsoft SQL Server 2005 - 9.00.5292.00 (Intel X86) Apr 13 2011 15:56:31 Copyright (c) 1988-2005 Microsoft Corporation Standard Edition on Windows NT 5.2 (Build 3790: Service Pack 2)
Thanks in advance.

Hi venkatesh1985,
As per my understanding, I think the issue can be caused by the current user account does not have the required permissions to make connections or access resources outside the SSIS package.
The package may not run in the following scenarios:
SQL Server Agent to schedule a SQL Server Integration Services package in a 64-bit environment. And the SSIS package is referencing some 32-Bit DLL or 32-Bit drivers which are available only in 32-bit versions, so the job failed. To run a package in 32-bit
mode from a 64-bit version of SQL Server Agent, we can add the contents of the Command box after you add the path like below (supposing the 32-bit version of the DTExec.exe utility is in the following folder: Drive\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn):
"C:\Program Files (x86)\Microsoft SQL Server\90\DTS\Binn\DTExec.exe" /FILE "C:\MyFolder\MyPackage.dtsx" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF
A SQL Server connection that uses integrated security fails because the current user does not have the required permissions.
File access fails because the current user does not have the required permissions to write to the file share that the connection manager accesses. In this scenario, we can create a SQL Server Agent proxy account. This proxy account must use a credential
that lets SQL Server Agent run the job as the account that created the package or as an account that has the required permissions.
References:
SSIS package does not run when called from a SQL Server Agent job step
Running a SSIS Package from SQL Server Agent Using a Proxy Account
How to use the 64-bit SQL Server Agent to schedule a SQL Server 2005 Integration Services package
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Getting Error while trying to execute SSIS package through sql agent

Hi,
I have created a package in SSIS 2008.
I have created sql Agent job which runs perfectly on my Pc.
I tried to create anew job on another pc which doesnot have SSIS.
When i tried to run the Job,
i am getting folowing error:
Executed as user: LT-MAGFIH$. tion. End Error DTExec: The package execution returned DTSER_FAILURE (1). Started: 8:51:31 PM Finished: 8:51:35 PM Elapsed: 4.024 seconds. The package execution failed. The step failed.
Please let me now how can i solve.

Hi AjayChigurupati,
I would suggest you check you are install or use the dtexec utility correctly:
On a 64-bit computer, Integration Services installs a 64-bit version of the
dtexec utility (dtexec.exe). If you have to run certain packages in 32-bit mode, you will have to install the 32-bit version of the
dtexec utility. To install the 32-bit version of the
dtexec utility, you must select either Client Tools or Business Intelligence Development Studio during setup.
By default, a 64-bit computer that has both the 64-bit and 32-bit versions of an Integration Services command prompt utility installed will run the 32-bit version at the command prompt. The 32-bit version runs because the directory path for the 32-bit
version appears in the PATH environment variable before the directory path for the 64-bit version. (Typically, the 32-bit directory path is
<drive>:\Program Files(x86)\Microsoft SQL Server\100\DTS\Binn, while the 64-bit directory path is
<drive>:\Program Files\Microsoft SQL Server\100\DTS\Binn.)
For detail information, please see:
http://technet.microsoft.com/en-us/library/ms162810(v=sql.105).aspx
To using SQL Server Agent to Run a Package, please refer to the steps in th article below:
http://technet.microsoft.com/en-us/library/ms138023(v=sql.105).aspx
If you have any feedback on our support, please click
here.
Elvis Long
TechNet Community Support

SSIS installed on 64 bit SQL Clustered Node.

I'm not looking to run SSIS as a clustered service. Initially I just want to install it on node1 of the cluster, eventually I will install on the second node.
So I install the SSIS component via add/remove programs and point to the 64 bit installation of sql server.
Following that, I installed SQL 2005 SP2.
Everything seemed to run though perfectly.
Next, I installed an SSIS package from 32 bit machine via a manifest file using file system method.. great no errors.
Now I go to create a job and I get:
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.
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr)
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
===
Suddenly, for reasons unknow, now when I attempt to create a new step, I can get into the menu, but if I attempt to select a package I get:
I'm not looking to run SSIS as a clustered service. Initially I just want to install it on node1 of the cluster, eventually I will install on the second node.
So I install the SSIS component via add/remove programs and point to the 64 bit installation of sql server.
Following that, I installed SQL 2005 SP2.
Everything seemed to run though perfectly.
Next, I installed an SSIS package from 32 bit machine via a manifest file using file system method.. great no errors.
Now I go to create a job and I get:
TITLE: Microsoft SQL Server Management Studio
Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
ADDITIONAL INFORMATION:
Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
If I attempt to explore SSIS pakages from management studio I get:
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.
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (MsDtsSrvr)
Login timeout expired
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client)
I'm wondering if this is because the package I deployed is 32 bit vs 64 bit? Or maybe I needed hot fixes in addion to SP2 after install the SSIS component after the original install?
Or maybe this was caused by registering of 32 bit DTS.dll files at some point trying to fix the original problem?
Thanks for any help or information.
TITLE: Microsoft SQL Server Management Studio
Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
ADDITIONAL INFORMATION:
Creating an instance of the COM component with CLSID {E80FE1DB-D1AA-4D6B-BA7E-040D424A925C} from the IClassFactory failed due to the following error: c001f011. (Microsoft.SqlServer.ManagedDTS)
If I attempt to explore SSIS pakages from management studio I get:
TITLE: Microsoft SQL Server Management Studio

Just a note here... while this is an issue, the same error can come up if there are multiple instances and the msdb has moved to a location such that more than one instance tries to share an msdb. If this is the case for example, Instance1 points to
C:\program files\microsoft sql server\mssql\data\msdbdata.mdf and instance2 also points there, you will get this error. Check with:
Select name, physical_name as location, state_desc from sys.master_files where name='N'msdb';
If they both point to the same location (mine did), stop both instances, make a copy of the msdbdata.mdf and msdblog.ldg, restart one of the instances (say instance2) and repoint the copy you just made... say c:\program files\microsoft sql server\mssql.instance2\data
as follows:
alter database msdb modify file(name-msdbdata,filename='c:\program files\microsoft sql server\mssql.instance2\data\msdbdata.mdf
do the same for the log. Restart Instance2 and Start Instance1 and it should resolve the problem.
R, J

Cannot Debug SSIS packages in 64 bit mode.

Similar Messages

Maybe you are looking for