DCOM Errors

From ThinManager Knowledge Base
Jump to: navigation, search

Contents

Enviornment

  • Windows 2003, 2008, 2008r2, 2012

Description

  • From within ThinManager, Terminal Servers are showing a WTSAPI32.dll connection failed error.

Cause

This error is thrown when ThinServer cannot make a DCOM connection to a specified terminal server. Typical causes include Permissions and Network Issues.

Permissions

DCOM requires a common user to function correctly.

  • Create a new user with Administrative Privileges with the same username and password on all Terminal Servers and ThinManager Servers. A common domain user would work as well.
  • Start > Run > services.msc > OK >Double-click on ThinServer to launch the ThinServer Properties page and configure the service to start with the newly created username/password.
  • Restart ThinServer
  • In ThinManager use the same account when defining the Terminal Services display servers.

Network Issues

By default, DCOM is blocked from within Windows Firewall. On Windows Server 2008 R2, there are two predefined rules that will allow COM access. To enable these:

  • Start > Administrative Tools > Windows Firewall with Advanced Security
  • Select Inbound Rules on the left side pane
  • Find COM+ Network Access (DCOM-In) and COM+ Remote Administration (DCOM-In)
    • Right click on each and click "Enable Rule"


Additionally, the WTSAPI32.dll error can be thrown if the terminal server is offline or unreachable on the network.

Personal tools
Namespaces

Variants
Actions
Navigation
Events
Toolbox