Cannot Expanding MSDB in SSIS

Hi,
I am trying to expanding MSDB under SSIS and getting following error:
TITLE: Microsoft SQL Server Management Studio
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click:
[url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476[ /url]
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.
TCP Provider: No connection could be made because the target machine
actively refused it. (MsDtsSrvr)
My sql server is clustered and SSIS is clustered also.
Thanks in advance!
Yuhong
Is SSIS in the same resource group as the SQL Server? Is the SQL Server the
default instance or a named instance?
Denny
MCSA (2003) / MCDBA (SQL 2000)
MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
Microsoft Office SharePoint Server 2007: Configuration)
MCITP (dbadmin, dbdev)
"Yuhong" wrote:

> Hi,
> I am trying to expanding MSDB under SSIS and getting following error:
> TITLE: Microsoft SQL Server Management Studio
> --
> Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
> For help, click:
> [url]http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476[ /url]
> --
> 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.
> TCP Provider: No connection could be made because the target machine
> actively refused it. (MsDtsSrvr)
> --
> My sql server is clustered and SSIS is clustered also.
> Thanks in advance!
> --
> Yuhong
|||SSIS is in the same resource group as the SQL Server. I think it is a named
instance in the cluster. I don't think I have a default instance configured
in the cluster. Is there a work around so I can expand the msdb with out
reconfigure the servers?
Thanks for helping!
Yuhong
"mrdenny" wrote:
[vbcol=seagreen]
> Is SSIS in the same resource group as the SQL Server? Is the SQL Server the
> default instance or a named instance?
> --
> Denny
> MCSA (2003) / MCDBA (SQL 2000)
> MCTS (SQL 2005 / Microsoft Windows SharePoint Services 3.0: Configuration /
> Microsoft Office SharePoint Server 2007: Configuration)
> MCITP (dbadmin, dbdev)
>
> "Yuhong" wrote:
|||This is a fairly easy fix, I actually just posted a blog entry walking
through the fix. The problem is that SSIS is not clusterable, and the
config files on the active node are pointing MSDB to the node itself.
The config files need to point to the cluster name.
http://www.sqlstop.com/index.php/2007/07/16/clusters-last-stand/
That details exactly how to fix the problem.
Thanks,
Shawn
*** Sent via Developersdex http://www.codecomments.com ***
|||Shawn,
Thanks so much for the information. I got it working. I almost gave up and
decided to store everything in File System.
It is surprising that there are not much informaton about this online, at
least I did not find any. Thanks again!!!!
Yuhong
"Shawn m" wrote:

> This is a fairly easy fix, I actually just posted a blog entry walking
> through the fix. The problem is that SSIS is not clusterable, and the
> config files on the active node are pointing MSDB to the node itself.
> The config files need to point to the cluster name.
> http://www.sqlstop.com/index.php/2007/07/16/clusters-last-stand/
> That details exactly how to fix the problem.
> Thanks,
> Shawn
> *** Sent via Developersdex http://www.codecomments.com ***
>
|||*** Sent via Developersdex http://www.codecomments.com ***
sql