![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
I'm sure there is a simple answer to this but it eludes me at the moment. I’m using the Developer Edition of SQL Server 2005. The MSDB node under Integration Services->Stored Packages refuses to open. It always fails with a login timeout message and that the connection was actively refused. I’ve run the SQL Server Surface Area Configuration tool and allowed remote and local access, even though it’s all installed on the local machine. This didn’t help. The next thing I did was to turn off all my firewalls and internet access control software and it’s still not working. I’m using integrated authentication and the user is part of the administrators group, any ideas how I can try and rectify this? Thanks Paul |
#3
| |||
| |||
|
|
Was there ever a solution for this? I have the exact same problem. Keehan "Paul" wrote: I'm sure there is a simple answer to this but it eludes me at the moment. I’m using the Developer Edition of SQL Server 2005. The MSDB node under Integration Services->Stored Packages refuses to open. It always fails with a login timeout message and that the connection was actively refused. I’ve run the SQL Server Surface Area Configuration tool and allowed remote and local access, even though it’s all installed on the local machine. This didn’t help. The next thing I did was to turn off all my firewalls and internet access control software and it’s still not working. I’m using integrated authentication and the user is part of the administrators group, any ideas how I can try and rectify this? Thanks Paul |
#4
| |||
| |||
|
|
I should add some notes. I have a simple DTS task to process an Analysis Services database. I have written the SSIS Project and created the deployment utility. I have successfully deploy the package to MSDB, but I can not browse MSDB either locally on the server from SQL Server Management Studio: Login timeout expired. Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client). or remotely from SQL Server Management Studio the SSIS registration fails with: Access denied. Regarding the local problem, why is it saying that anything about remote connections. I am on the same box. Regarding the remote problem, I found Kirk Haselden's work at: http://www.sqljunkies.com/WebLog/kni.../05/17769.aspx. I looked at the DCOM Config bits, but the local Administrators group already has all four options. I did find that the service is running as NT AUTHORITY\NetworkService. Is that OK? Thanks for any advice, Keehan "asnewbie+rs=argh" wrote: Was there ever a solution for this? I have the exact same problem. Keehan "Paul" wrote: I'm sure there is a simple answer to this but it eludes me at the moment. I'm using the Developer Edition of SQL Server 2005. The MSDB node under Integration Services->Stored Packages refuses to open. It always fails with a login timeout message and that the connection was actively refused. I've run the SQL Server Surface Area Configuration tool and allowed remote and local access, even though it's all installed on the local machine. This didn't help. The next thing I did was to turn off all my firewalls and internet access control software and it's still not working. I'm using integrated authentication and the user is part of the administrators group, any ideas how I can try and rectify this? Thanks Paul |
#5
| |||
| |||
|
|
I am getting this error also. I am on a 2003 64 Bit Cluster, and I can't browse to the MSDB folder of Stored Packages. Does not matter if I am on the system local or connect remote. Any help would be greatly appreciated. Thanks, Eric asnewbie+rs=argh wrote: I should add some notes. I have a simple DTS task to process an Analysis Services database. I have written the SSIS Project and created the deployment utility. I have successfully deploy the package to MSDB, but I can not browse MSDB either locally on the server from SQL Server Management Studio: Login timeout expired. Named Pipes Provider: Could not open a connection to SQL Server [2]. (Microsoft SQL Native Client). or remotely from SQL Server Management Studio the SSIS registration fails with: Access denied. Regarding the local problem, why is it saying that anything about remote connections. I am on the same box. Regarding the remote problem, I found Kirk Haselden's work at: http://www.sqljunkies.com/WebLog/kni.../05/17769.aspx. I looked at the DCOM Config bits, but the local Administrators group already has all four options. I did find that the service is running as NT AUTHORITY\NetworkService. Is that OK? Thanks for any advice, Keehan "asnewbie+rs=argh" wrote: Was there ever a solution for this? I have the exact same problem. Keehan "Paul" wrote: I'm sure there is a simple answer to this but it eludes me at the moment. I'm using the Developer Edition of SQL Server 2005. The MSDB node under Integration Services->Stored Packages refuses to open. It always fails with a login timeout message and that the connection was actively refused. I've run the SQL Server Surface Area Configuration tool and allowed remote and local access, even though it's all installed on the local machine. This didn't help. The next thing I did was to turn off all my firewalls and internet access control software and it's still not working. I'm using integrated authentication and the user is part of the administrators group, any ideas how I can try and rectify this? Thanks Paul |
#6
| |||
| |||
|
![]() |
| Thread Tools | |
| Display Modes | |
| |