SSIS on a named instance


I ran into a fairly unique problem recently with SSIS in a clustered environment.
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 expiredAn 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)

SSIS is not clusterable, so when the install took place, SSIS was configured on the first node like a non cluster install.
To Fix it:
- Stop SSIS Service
- Edit: "C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml"
- Replace Server Name with Clustered Instance Name
- Start SSIS Service
Share on Google Plus

About Vittorio Pavesi

    Blogger Comment
    Facebook Comment

0 comments: