Re: Stored Packages - MSDB Access

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/knight_reign/archive/2006/01/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


.

Relevant Pages

  • Re: Stored Packages - MSDB Access
    ... I have written the SSIS Project and created the ... I have successfully deploy the package to MSDB, ... can not browse MSDB either locally on the server from SQL Server Management ... why is it saying that anything about remote ...
    (microsoft.public.sqlserver.dts)
  • Re: Permission to run DTS packages from Application Server
    ... guest is already a user in msdb unless you've removed him/her. ... You can therefore unless you've save the packages with a password simply ... Permissions then are based on what the package does. ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) ...
    (microsoft.public.sqlserver.dts)
  • Re: Restoring individual DTS Packages
    ... If I knew I was going to want to restore individual packages every time then ... As Sue says MSDB as a whole will need to be restored. ... If you want to have them backed up as a SQL Server backup then how about ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP) ...
    (microsoft.public.sqlserver.dts)
  • Re: Can I restore msdb from another sqlserver s backup
    ... Tibor Karaszi, SQL Server MVP ... "Karin W" wrote in message ... > We have the same problem with a suspected MSDB. ... > droped because it'a a system database. ...
    (microsoft.public.sqlserver.server)
  • Re: Installing DTS packages
    ... But if they are in files, then restoring the msdb database would not restore ... There is one DTS item in the sysdtspackages and that is the one listed ... exec msdb..sp_enum_dtspackages, but that is not one of the packages ...
    (microsoft.public.sqlserver.dts)