SSIS install on one node of a Cluster

Phil

2009-09-18 19:17:59 UTC

You're deploying to a SQL server package store right? This requires a
connection to a SQL Server database (msdb in fact). Normally the Integration
Services service is installed along with a database so when the package is
deployed via a manifest its simply stored in the local msdb database. By the
sounds of it you've installed SSIS on its own and in that case, as it says
here http://msdn.microsoft.com/en-us/library/ms137789.aspx:

the Integration Services service is configured to manage packages in the
msdb database of the local, default instance of the Database Engine.

If you have no default instance because you didn't install it (or if you
stop it - like I just have) you get the error you described. The solution is
in the link posted above - change the config file in
%ProgramFiles%\Microsoft SQL Server\100\DTS\Binn to point to an appropriate
SQL Server database.

HTH

Phil.
--
Phil

http://www.clarity-integration.com | http://www.phil-austin.blogspot.com

Post by jc
Not looking to install SSIS as a clustered service.
So I add the component from the 64 bit install.
Everything went perfectly. I then install SP2. great
I install my package (from the manifest file) great.
I go to add a job step, and when I refernce the package and after a
TITLE: SSIS Execution Properties
------------------------------
An OLE DB error 0x80004005 (Login timeout expired) occurred while
enumerating packages. A SQL statement was issued and failed.
------------------------------
An OLE DB error 0x80004005 (Login timeout expired) occurred while
enumerating packages. A SQL statement was issued and failed.
Thinking maybe the issue is that my package is 32 bit and server is 64
bit, I go to remove the package and when I explore to Stored Packages
TITLE: Microsoft SQL Server Management Studio
------------------------------
Failed to retrieve data for this request.
(Microsoft.SqlServer.SmoEnum)
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476
------------------------------
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)
Cluster related?
Did I maybe aggrevate the problem by registering 32 bit version of
dts.dll dtsutil.dll per some instuctions I found?
Any way to manually remove the package outside of management studio to
see if that is cause?
Thanks for any help or information.