Setting up the DCOM Access for ibmcol on the stand-alone Windows server

Complete the following steps to set up the DCOM Access for the user on the stand-alone Windows server.

  1. Open the Component Services Administrative Tool by running the dcomcnfg command.
  2. In the navigation tree, expand Component Services > Computers > My Computer.
  3. From the Action menu, click Properties, and go to the COM Security tab.
  4. In the Access Permissions section, click Edit Default.
  5. Add the ibmcol user to the list and ensure that it has the Local Access and Remote Access permissions enabled, and click OK.
  6. In the Access Permissions section, click Edit Limits.
  7. If the button is grayed out, complete the following steps:
    1. Open Local Security Policy by running the secpol.msc command.
    2. Expand Local Policies and click Security Options.
    3. Select the following policy: DCOM: Machine Access Restrictions in Security Descriptor Definition Language (SDDL) syntax.
    4. Right-click the policy and choose Properties from the menu. Then, click Edit Security.
  8. Add the ibmcol user to the list and ensure that the Local Access and Remote Access permissions are enabled, and click OK.
  9. In the Launch and Activation Permissions section, click Edit Default.
  10. Add the ibmcol user to the list and ensure that it has the Local Launch and Remote Launch permissions enabled, and click OK.
  11. In the Launch and Activation Permissions section, click Edit Limits.
  12. If the button is grayed out, complete the following steps:
    1. Open Local Security Policy by running the secpol.msc command.
    2. Expand Local Policies and click Security Options.
    3. Select the following policy: DCOM: Machine Launch Restrictions in Security Descriptor Definition Language (SDDL) syntax.
    4. Right-click the policy and choose Properties from the menu. Then, click Edit Security.
  13. Add the ibmcol user to the list and ensure that the Local Launch, Remote Launch, Local Activation, and Remote Activation permissions are enabled, and click OK.
  14. Restart the Windows server.