March 12, 2008 at 9:22 am
I keep getting the following error when I click on MSDB in Management Studio. I have allowed remote connections and BOL doesn't help a whole lot. I have a named instance of SQL2005. I just checked with microsoft.com and it says that I'm supposed to edit my registry file because I have a named instance. I've edited the configuration file and I still get the same error. SQL2005 is on E:\ and the configuration file is still in the default location (C:\Program Files\Microsoft SQL Server\90\DTS\Binn\MsDtsSrvr.ini.xml). What gives?
"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)"
March 12, 2008 at 9:33 am
OK, never mind. I found the error. I modified the file according to the MS Community article. I had to stop and start the SSIS service.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply