none
DCOM - RPC Server unavailable 800706BA RRS feed

  • Question

  • Hi, have a program that get a RPC error, its a program that use DCOM

    Windows Server 2016 has the prgram that it should connect to over DCOM (Application server)

    Windows Server 2016 RDS has the client (Terminal server)

    It works with domain admins but not with users even when users are local admin on the application and terminal server, but if user login directly on the application server it works. If a domain admin logon to terminal server it works, but not if users login to terminal servers. No firewall on application server or terminal server.

    The error is

    Creating an instance of the COM component with CLSID {93C50421-6CB0-11D2-9455-00104B304599} from the iClassFactory failed due to the following error: 800706ba The RPC server is unavailable. (Exeption from HRESULT: 0x800706BA).

    There isnt anything in eventviewer on application or terminal server. The users have all rights inn dcom, both 32 and 64 bit.

    Another program running on the same terminalserver that comunicate to the same application server and the same program on the application server that also use DCOM works ok.

    Wednesday, June 12, 2019 10:25 AM

All replies

  • I'd reach out to the application developer for help with setup on an RDS server.

     

     



    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows Server] Datacenter Management

    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees, and confers no rights.

    Wednesday, June 12, 2019 12:27 PM
  •  but if user login directly on the application server it works. 

    That would seem to indicate that on the app server the users have local launch rights, but not remote launch. Right click "my computer", properties, COM security, review both "edit limits" rights.

    Wednesday, June 12, 2019 12:48 PM
  • All settings on both 32 and 64 bit dcom are correct.

    Thursday, June 13, 2019 9:55 AM
  • The problem was that the program wanted access to the root folder of the shared folder where the program is. The share is like \\data2$\customer\master

    When i added the users and set it to modify on data2$ it started to work. If i remove users from hiddenshare$ the program will still start 4-5 min after that. The developer says the program shouldnt need any access to the root share. Its started from a mapped drive F:.

    The UNC path to the program is like \\mfil01\data2$\customer\program\master\testmaster.exe

    The F drive is mapped to \\mfil01\data2$\customer\program and the program is run from F:\master\testmaster.exe

    This is from a process monitor

    When its working

    07.30.40,0576141    TestMaster.exe    21344    CreateFile    \\mfil01\data2$\    SUCCESS    Desired Access: Read Data/List Directory, Synchronize, Dis, Options: Directory, Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a, OpenResult: Opened    

    When its not working

    07.24.58,9183319    TestMaster.exe    8020    CreateFile    \\mfil01\data2$\    ACCESS DENIED    Desired Access: Read Data/List Directory, Synchronize, Dis, Options: Directory, Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a  

    Thursday, June 13, 2019 10:11 AM
  • The problem was that the program wanted access to the root folder of the shared folder where the program is. The share is like \\data2$\customer\master


    I'm confused. What does this have to do with a DCOM error? 

    If you are getting an ACCESS DENIED, right click a file in that share and view advanced security. In the effective access tab, select an end user's account and verify that they have the necessary permissions.

     

    Thursday, June 13, 2019 2:43 PM
  • The developer said it was a dcom error and the error message said it was RPC so then i thought it was DCOM error. There wasnt any thing that pointed to a shared folder access error. There isnt any files in that share, and nothing in the program point to the root of the share and it runs from a mapped drive.
    Friday, June 14, 2019 5:03 AM
  • Hi,

    Please run the following command to see what is the RPC high range of ports configured:
    Netsh int ipv4 show dynamicportrange tcp

    As per IANA standards, it should look like this:

    Protocol tcp Dynamic Port Range
    ---------------------------------
    Start Port      : 49152
    Number of Ports : 16384

    If not, run the command below to set the high range ports back to normal:
    netsh int ipv4 set dynamicport tcp start=49152 num=16383

    Besides, in order to have further identification about the problem network tracing is necessary, tools such as network monitor can be considered. 

    Best Regards,
    Eve Wang

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, June 19, 2019 9:23 AM
    Moderator
  • Hi,

    How things are going there on this issue?

    Please let me know if you would like further assistance.

    Best Regards,
    Eve Wang  

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Monday, June 24, 2019 1:15 AM
    Moderator
  • Hi,

    Is there any update?

    Best Regards,
    Eve Wang



    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, June 26, 2019 7:33 AM
    Moderator