December 20, 2006 at 3:14 pm
I have an SSIS server in another state. I can connect to SSIS in SQL Management Studio locally when I use terminal service to connect to the server. From my computer in local office in California I cannot connect to that server, getting the error "RPC server is unavailable". I have no problem connecting to SQL service on that server; the firewall between my office and the server in other state is not an issue. We set the firewall to accept traffic on all ports if coming from our office. I followed the link here http://www.sqljunkies.com/WebLog/knight_reign/archive/2006/01/05/17769.aspx but it didn't work after I made the changes. I found very little instructions from MSDN to setup this type of connection and none is working for me. Do you guys know how to make the connection work? Thanks.
December 21, 2006 at 7:35 am
Have you launched the surface area configuration tool and enabled remote connections unde the database engine? By default SSIS runs under NT AUTHORITY\Network Service - try changing to a domain account. Hope this helps.
Tommy
Tommy
Follow @sqlscribeDecember 21, 2006 at 12:15 pm
Tom,
The remote connections is already enabled. I changed the startup acct for SSIS to local admin acct; it didn't help.
At the remote location there are 2 servers in a workgroup. I logged into 2 servers using a local admin acct, let's say RemoteAdmin. Both servers have SQL and SSIS services. SSIS services on both servers use the same local admin RemoteAdmin as startup acct. I can connect to SSIS on local server and on the other server using the server NetBIOS name; however from one server I cannot connect to itself and the other using the alias name. So what role is the NetBIOS name in the conenction here? I thought I can use the same alias name when I connect to SQL engine on the server for SSIS but I was wrong. Both servers have TCP/IP, NamedPipes, and Shared Memory enabled.
Given the SSIS connection works only with NetBIOS name, how do I connect to SSIS on remote server in different domain?
Thanks.
December 21, 2006 at 3:06 pm
I finally see the remote servers. All I need to do is using public IP address of the server, not the alias name of the server. How dump I was but I never thought it would work.
Now I have the next problem. Seeing the remote servers is one thing, the second thing I still cannot connect to the servers. When I connect I got the error:
Failed to retrieve data for this request. (Microsoft.SQLServer.SmoEnum)
The object exporter specified was not found.
I have no clue what is wrong here.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply