SSIS installed on 64 bit SQL Clustered Node.

Question

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

Answer 1

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