Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / Services / Integration Services / February 2010

Tip: Looking for answers? Try searching our database.

can't connect to SSIS

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Andre - 01 Feb 2010 20:05 GMT
SQL2008

I have a VM (virtual PC) running XP that I use to connect to my office.  The
VM has been added to the domain and my user account is an admin on the local
box.
I'm sa on the SQL Server.  From SSMS I can connect to SQL just fine, using
trusted security.  From BI I can build packages and deploy them to SQL by
"save a copy" and pointing it to SQL.  My credentials work just fine.  But
from SSMS I can't connect to Integration Services.  I get the following
error:

Cannot connect to MySqlServerName.
Additional information:
    Failed to retrieve data for this request.
(Microsoft.SqlServer.Management.Sdk.Sfc)
        Connect to SSIS Service on machine "myserver" failed:
            Access is denied.

I've found several articles on the net, including one that mentions editing
dcom's MsDtsServer's properties.  For one thing, neither my local box nor
the SQL Server has MsDtsServer; they have MsDtsServer100.  The articles I've
found don't say if I should edit the properties on the server or on my local
box.  If this is my issue, do I need to edit the properties on the server,
and is it the MsDtsServer100's properties?

Any ideas?  Thanks in advance.

Andre
Jay - 01 Feb 2010 20:36 GMT
Have you looked at the server logs? I suspect that you're not logging in
with the ID you think you are, or the server isn't really setup for you the
way you think it is.

> SQL2008
>
[quoted text clipped - 24 lines]
>
> Andre
Andre - 02 Feb 2010 01:05 GMT
The SQL Logs don't have any information about this.  Also, all other users,
with computers on the domain, are unable to connect to Integration Services
from SSMS.   Please let me know if you have any other suggestions.

Andre
Jay - 02 Feb 2010 03:02 GMT
Sorry about that. I do have one suggestion though:
microsoft.public.sqlserver.integrationsvcs

> The SQL Logs don't have any information about this.  Also, all other
> users, with computers on the domain, are unable to connect to Integration
> Services from SSMS.   Please let me know if you have any other
> suggestions.
>
> Andre
Jay - 02 Feb 2010 06:13 GMT
OK, I'm an idiot. Didn't see the cross-post.

> Sorry about that. I do have one suggestion though:
> microsoft.public.sqlserver.integrationsvcs
[quoted text clipped - 5 lines]
>>
>> Andre
Andre - 02 Feb 2010 06:34 GMT
lol - I wondered what you meant. :)  Thanks for the suggestions anyway.

> OK, I'm an idiot. Didn't see the cross-post.
Gennadi Gretchkosiy - 08 Feb 2010 04:22 GMT
Hi there

Is your instance named? If yes - probably this link will help you

http://social.msdn.microsoft.com/Forums/en-US/sqlintegrationservices/thread/23c2
64d2-39eb-4d9a-8dba-83b0a555249d/


Regards,
Gennadi

> SQL2008
>
[quoted text clipped - 27 lines]
>
> .
Gennadi Gretchkosiy - 08 Feb 2010 04:27 GMT
PS Yes, I had similar problem and I could solve this by changing instance
name in MsDtsSrvr.ini.xml

> Hi there
>
[quoted text clipped - 36 lines]
> >
> > .
Andre - 15 Feb 2010 17:51 GMT
Gennadi,

Thanks for the reply, unfortunately I'm still in the same situation.  I'm
not running a named instance, but I went ahead and changed MsDtsSrvr.ini.xml
to my machine name instead of ".".   I followed the rest of the article's
suggestions but I still can't connect to SSIS from any remote PC.  Also as I
mentioned, in Component Services I don't have a Com object named
MsDtsServer; mine is named MsDtsServer100.  Is this my problem, or did MS
just change the name of the object in SQL 2008?

Thanks, Andre
Andre - 15 Feb 2010 21:23 GMT
I figured it out.  I added myself into the Administrator group on the SQL
Server box and the error changed from "access denied" to "the rpc server is
unavailable".  I then found this post that essentially told me I needed to
add DTS into the firewall - SSIS was already allowed by the way.

http://www.kodyaz.com/articles/ssis-integration-services-remote-connection-rpc-s
erver-unavailable.aspx


After I changed the firewall as described in this article I'm now able to
connect.

I'm just curious though - I have several users I want to have access to SSIS
from their workstation.  Is there a way to accomplish this w/o adding each
one of them to the Administrator group on the SQL Server box?

Andre
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2010 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.