Getting Started with Adobe After Effects - Part 6: Motion Blur
First Time? You can support us by signing up. It takes only 5 seconds. Click here to sign up. If you already have an account, click here to login.
Loading

1st Prize - Apple iPad


SQLServer Quiz 2011 - How do you fix "RPC Server is unavailable" error message?

  • When accessing SSIS Remotely, you might get an error RPC Server is unavailable what is the work around you would suggest in this case?

    Posted on 09-23-2011 00:00 |
    Hemantgiri S. Goswami
    109 · 1% · 467

8  Answers  

Subscribe to Notifications
  • Score
    5

    Cause of this issue

    The main cause of this issue is firewall restrict the SSIS services to access from remote computer.

    How to resolve this issues?

    When you connect to remote SSIS services, DCOM functionality of Windows operating system is used and dynamically port is assign to services. Due to dynamically allocation of port from range 1024 to 65535 , you need to open this range in firewall. In some cases you have hardware firewall and admin can't leave such a large number of ports open. So its bad idea to open such a large range. So, Add rule to execute MsDtsSrvr.exe program.

    Also, Client side applications discover the port associated with a particular object by connecting to and using the services provided by DCOM's Service Control Manager. SCM uses port 135 for TCP and UDP connection. So, Add rules to open port 135 as TCP & UDP.

    I think, How to open port in firewall is part of this answer so, I am just giving the link of how to open it. For more read: http://www.kodyaz.com/articles/ssis-integration-services-remote-connection-rpc-server-unavailable.aspx

    Replied on Sep 23 2011 2:05AM  . 
    Haresh Ambaliya
    121 · 1% · 428
  • Score
    7

    Problem is in DCOM functionality and fire wall. If windows fire wall is used the best way is to open TCP and UDP port 135 and add exception for program MsDtsSrvr.exe (located in SQL Server instance installation folder C:\Program Files\Microsoft SQL Server\100\DTS\Binn).

    If you have hardware firewall best way is to to configure a specific ports range for DCOM (DCOM use any port between 1024 and 65535 and it’s not good to leave such a large number of ports open). To configure a more specific ports range for DCOM use these steps:

    Click on Start | Run.

    Type dcomcnfg for the DCOM console to open.

    Go under Components Services | Computer | My Computer and then right click on My Computer and choose properties.

    Go to the Default protocols tab.

    Choose the properties of the Connection Oriented TCP/IP.

    Add the range you want DCOM to be listening at.

    Then on hardware fire wall open port 135 TCP and UDP and port range you specified for DCOM.

    Replied on Sep 23 2011 2:19AM  . 
    Ana
    120 · 1% · 430
  • Score
    8

    The reason for the " RPC Server Unavailable" status should be of any of the following reasons.

    1. Just ping the machine which you want to add and check whether you are able to reach the machine.

    2. Check any System firewall is running in the machine from which you want to collect the logs. If System Firewall is enabled in the machine which you need to monitor, then you need to execute the following command in the command prompt on that machine to enable RemoteAdmin for that machine.

      netsh firewall set service type=REMOTEADMIN mode=ENABLE profile=all ( This commend to be executed in client machine)

      After executing the above command in the client machine, kindly test that machine by using ping command from the machine, where the EventLog Analyzer server is running. Then test the same machine by using Verify Login in the Add Host Details page (from the EventLogAnalyzer UI).

    3. If any other firewall has blocked the machine then you need to open the following RPC ports.

      For DCOM RPC please enable TCP 135 in the firewall. DCOM RPC uses callback for the event receipt which chooses random ports 1024-65534. You can enable 135 for incomming and allow the above range for outgoing calls.

    4. Check DCOM is enabled on the remote machine. (DCOMCNFG->Default Properties-> Enable Distributed COM on this computer is checked).

    5. "The RPC server is unavailable" error message when you open Disk Management in Windows XP

    http://forums.manageengine.com/topic/the-rpc-server-is-unavailable

    1. restrict the ports on which SSIS on the server will try to create a connection
    2. configuring static DCOM ports for specific applications

    http://blogs.msdn.com/b/dataaccesstechnologies/archive/2010/01/28/connecting-to-remote-sql-server-integration-service-from-sql-server-management-studio.aspx

    Connect to SSIS Service on machine "{ServerName}" failed: The RPC server is unavailable. Windows Firewall configuration.

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

    You receive a "The RPC server is unavailable" error message when you open Disk Management in Windows XP

    http://support.microsoft.com/?kbid=884564

    Replied on Sep 23 2011 3:35AM  . 
    Mitesh Modi
    18 · 10% · 3080
  • Score
    2

    There are three possibilities

    1.The RPC server is unavailable may because of the service couldn't function properly .

    Because it's dependancy (server service) couldn't start. Check the dependencies

    through the server's properties and looked through services and start those

    required dependancies to start the server service,

    2.May because of the Windows Firewall is active on the remote computer.

    Configure the Windows Firewall on the remote computer, to connect to

    remote SSIS server.

    3.May because of Romote Procedure Call Locator is not started.

    start the Romote Procedure Call Locator in 'Control Panel > Services' on

    both the server and client.

    Replied on Sep 23 2011 5:57AM  . 
    Sineetha
    106 · 2% · 492
  • Score
    2

    You can add 1433 TCP port and 1434 UDP port from firewall to resolve this problem and then restart sql service .

    Replied on Sep 27 2011 1:12AM  . 
    harishs
    283 · 0% · 150
  • Score
    5

    Windows Firewlll is the culprit in this scenario.

    We can follow the the below listed steps to configure the Windows Firewall resolving the issue.

    How to Configure Windows Firewall for SSIS (SQL Server Integration Services) To enable remote connection for MS SQL Server Integration Services (SSIS), you can configure the Windows Firewall application by following the below steps.

    Open the Windows Firewall from the Control Panel menu. Click on the Exceptions tab. Click the “Add Program” button. And browse to the folder where the SQL Server instance installation folders. C:\Program Files\Microsoft SQL Server\100\DTS\Binn\MsDtsSrvr.exe is the default installation folder.

    Click Open then on the next screen click OK button to add the SSIS executable to the application exceptions list.

    Then the port # 135 should be added to the exceptions list as a TCP port. You can define any descriptive name on the Name textbox, but you should specify the port number 135 and define it as a TCP port.

    After these Microsoft Firewall configuration updates, I could successfully connect to the MS SQL Server 2008 Integration Services (SSIS) without any problem.

    Replied on Sep 27 2011 1:27AM  . 
    Manoj Bhadiyadra
    150 · 1% · 325
  • Score
    5

    Cause

    This problem is caused if Windows Firewall is active on the remote computer and SSIS application and the SSIS ports are not added in the firewall exception list. After proper configuration of Windows Firewall on the remote computer, connection to remote SSIS server will be established.

    How to Configure Windows Firewall for SSIS (SQL Server Integration Services)

    To enable remote connection for MS SQL Server Integration Services (SSIS), you can configure the Windows Firewall application by following the below steps.

    • Open the Windows Firewall from the Control Panel menu.
    • Click on the Exceptions tab.
    • Click the "Add Program" button.
    • Browse to the folder where the SQL Server instance installation folders. (..\DTS\Binn\MsDtsSrvr.exe )
    • Click Open then on the next screen click OK button to add the SSIS executable to the application exceptions list.
    • Then the port # 135 should be added to the exceptions list as a TCP port. You can define any descriptive name on the Name textbox, but you should specify the port number 135 and define it as a TCP port.

    After these Microsoft Firewall configuration updates, I could successfully connect to the MS SQL Server 2008 Integration Services (SSIS) without any problem.

    Replied on Oct 12 2011 1:12AM  . 
    ATif-ullah Sheikh
    132 · 1% · 391
  • Score
    10

    Several issues can lead to this error such as virus attack, firewalls, DCOM tunneling being disabled, and remote server registry faults. But our interest here is to focus on DCOM functionality and Firewall issues.

    First step is to make sure that two computers even communicate each other and this can be done by with ping command.

    Also we should check to make sure that Remote Procedure call Locater is not stopped, if it is not started, we should start the Romote Procedure Call Locator in 'Control Panel > Services' on both the server and client machine.

    When we try to connect to a remote SSIS service underneath we leverage the DCOM functionality on the Windows operating system. Most applications tend to have fixed TCP and UDP ports but DCOM is different. DCOM dynamically assigns a TCP port and a UDP port to each executable process serving DCOM objects on a computer. Client side applications discover the port associated with a particular object by connecting to and using the services provided by DCOM's Service Control Manager (SCM). The SCM always operates at a fixed network port 135 for both TCP and UDP on every computer. This DCOM's feature of dynamic port allocation provides programmers the flexibility of not hard coding applications for specific ports. The advantage is that different applications will not try to use the same port and end up with a clash. This same feature of DCOM doesn’t make it a good buddy of the firewall because it can choose any port between 1024 and 65535 .

    The important thing to note is that when the SSIS service makes a call back to the SSMS client, it creates a completely new connection to the client and sends method calls over that separate channel. This is similar to the generic client server call with role reversal. This time the server (SSIS Service) is the client and the client (SQL Server Management Studio) is the server.

    So if we shut down the firewall we will be able to overcome this error. Shutting down firewall is not at all an acceptable solution to any customer facing systems, and more over every system should be fully secured and it is not safe to turn off the firewall settings completely. Instead of this should add rule to execute MsDtsSrvr.exe executable program which is located in the installation folder of SQL Server Instance C\Program Files\Microsoft SQL Server\100\DTS\Binn.

    In some cases we might have a hardware fire wall in place and we can’t leave such a large number of ports open. System administrator will like opening ports from 1024 and 65535 on the firewall.

    Steps on how to configure a port range for DCOM

    In order to allow DCOM to operate efficiently we need to open these ports in the firewall:

    • Port 135 TCP and UDP
    • The ports range: 1024-5000 UDP

    Though network administrator and security administrators won’t be happy to do these changes and some might even refuse to open their firewall to this range. In that case, we can define a more specific ports range using these steps:

    • Click on Start -> Run.
    • Type DCOMCNFG for the DCOM console to open.
    • Go under Components Services ->Computer ->My Computer
    • Right click on My Computer and choose properties.
    • Go to the Default protocols tab.
    • Choose the properties of the Connection Oriented TCP/IP.
    • Add the range we want DCOM to be listening at.

    It is recommended that a minimum of minimum of 100 ports are set, between ports 1024 to 10000. In case if we receive COM+ related events or errors because of this setting we can revert it later or increase the ports range accordingly.

    Steps to Configure Windows Firewall for SSIS (SQL Server Integration Services)

    To enable remote connection for MS SQL Server Integration Services (SSIS), we can configure the Windows Firewall application by following the below steps.

    • Open the Windows Firewall from the Control Panel menu.
    • Click on the Exceptions tab.
    • Click the "Add Program" button.
    • And browse to the folder where the SQL Server instance installation folders. C:\Program Files\Microsoft SQL Server\100\DTS\Binn\MsDtsSrvr.exe is the default installation folder.

    It is shown in the figure: Figure 1: Step 1: Adding Firewall Rule

    Now Click Open then on the next screen click OK button to add the SSIS executable to the application exceptions list.

    It is shown in the figure: Figure 2: Step 2: Adding Firewall Rule

    Then the port # 135 should be added to the exceptions list as a TCP port. In the description name text box, give a name and then specify the port number 135 and define it as a TCP port.

    It is shown in the figure: Figure 3: Step 3: Adding Firewall Rule

    After these Microsoft Firewall configuration updates, we should be able to connect to the MS SQL Server Integration Services (SSIS) successfully.

    I hope these steps and workaround will cover the answer for this quiz question.

    Replied on Oct 15 2011 12:23PM  . 

    0 · 0% · 0

Your Answer


Sign Up or Login to post an answer.
Please note that your answer will not be considered as part of the contest because the competition is over. You can still post an answer to share your knowledge with the community.

Copyright © Rivera Informatic Private Ltd.