VDA is unable to Register with DDC with error: Failed to start WCF services

Server VDA machine does not get registered. Following Error is thrown on the VDA Event viewer

Error details:

Failed to start WCF services. Exception ‘Object reference not set to an instance of an object.’ of type ‘System.NullReferenceException’

COM component was unable to Load StackManager.ConnectToStackControlComServerAndVerify: COM exception System.InvalidCastException: Unable to cast COM object of type ‘System.__ComObject’ to interface type ‘Citrix.StackControlService.StackControl’. This operation failed because the QueryInterface call on the COM component for the interface with IID ‘{BEE5F9CD-A777-47C7-BA5A-CDD82FFEC4D8}’ failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)). at Citrix.Cds.BrokerAgent.AgentToStack.ConnectToStackControlCOMServer() at Citrix.Cds.BrokerAgent.StackManager.ConnectToStackControlComServer(StackCapabilities& actualStackCapabilities, Int32 retryCount)

Related:

Virtual Apps 7.15 -VDA is unable to Register with DDC

Server VDA machine does not get registered. Following Error is thrown on the VDA Event viewer

Error details:

Failed to start WCF services. Exception ‘Object reference not set to an instance of an object.’ of type ‘System.NullReferenceException’

COM component was unable to Load StackManager.ConnectToStackControlComServerAndVerify: COM exception System.InvalidCastException: Unable to cast COM object of type ‘System.__ComObject’ to interface type ‘Citrix.StackControlService.StackControl’. This operation failed because the QueryInterface call on the COM component for the interface with IID ‘{BEE5F9CD-A777-47C7-BA5A-CDD82FFEC4D8}’ failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)). at Citrix.Cds.BrokerAgent.AgentToStack.ConnectToStackControlCOMServer() at Citrix.Cds.BrokerAgent.StackManager.ConnectToStackControlComServer(StackCapabilities& actualStackCapabilities, Int32 retryCount)

Related:

Citrix Server VDI : Failed to start wcf services. Exception object reference not set to an instance of an object

The following System.InvalidCastException is thrown as BrokerAgent starts up, creates our StartWorkerAgentThread, Initializes LaunchManager, and attempts to ConnectToStackControlCOMServer:

COM exception System.InvalidCastException: Unable to cast COM object of type ‘System.__ComObject’ to interface type ‘Citrix.StackControlService.StackControl’. This operation failed because the QueryInterface call on the COM component for the interface with IID ‘{BEE5F9CD-A777-47C7-BA5A-CDD82FFEC4D8}’ failed due to the following error: Error loading type library/DLL. (Exception from HRESULT: 0x80029C4A (TYPE_E_CANTLOADLIBRARY)).

This is caused either by a missing StackController type library or by incorrect registry entries relating to the same.

Related:

7021687: ActiveX Error: “Object does not support…”

This document (7021687) is provided subject to the disclaimer at the end of this document.

Environment

Reflection for HP version 13.0 through 14.x

Reflection for UNIX and OpenVMS version 13.0 through 14.x

Situation

When using Reflection’s ActiveX control in a Window’s form, users may see one of the following errors when loading the ActiveX application:

"Object does not support this property or method."

or

"Failed to load control r2winctrl from r2axctrl.ocx. Your version r2axctrl.ocx may be out dated. Make sure you are using the version of the control that was provided with your application."

Resolution

To resolve this error, either re-compile the ActiveX application using the version of Reflection that resides on the end user’s workstation, or upgrade the end user workstation so that it is running the same version of Reflection that was used to compile the ActiveX application.

Cause

These errors occur when the version of Reflection’s ActiveX control used in the Window’s form does not match the version of Reflection ActiveX installed on the end user’s workstation.

Additional Information

Legacy KB ID

This document was originally published as Attachmate Technical Note 1754.

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

7019010: Event ID 10016 while settting up O365 PowerShell Script 4.2

This document (7019010) is provided subject to the disclaimer at the end of this document.

Environment

Retain 4.2

O365 PowerShell Script 4.2

Windows Server 2016

Situation

When running the script for the first time the Scheduled Task does not run at the end of the script as expected.

In the Event log an error similar to the below appears:

The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID {D63B10C5-BB46-4990-A94F-E40B9D520160} and APPID {9CA88EE3-ACB7-47C8-AFC4-AB702511C276} to the user NT AUTHORITYLOCAL SERVICE SID (S-1-5-19) from address LocalHost (Using LRPC) running in the application container Unavailable SID (Unavailable). This security permission can be modified using the Component Services administrative tool.

Resolution

Disclaimer

This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.

Related:

Event ID 5485 — COM+ General Functionality

Event ID 5485 — COM+ General Functionality

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

COM+ applications use Microsoft Component Object Model (COM) technology in Microsoft Windows operating systems to communicate and take advantage of Windows services. COM technologies include COM+, DCOM, and ActiveX Controls.

Event Details

Product: Windows Operating System
ID: 5485
Source: Microsoft-Windows-Complus
Version: 6.1
Symbolic Name: ID_COMCAT_PARTITION_LOOKUP_FAILED
Message: COM+ failed to find the correct partition for the admin SDK. The admin SDK will use the base partition. Check that users are configured into partitions correctly. See your documentation for details.%1%0

Resolve

This is a normal condition. No further action is required.

Related Management Information

COM+ General Functionality

Application Server

Related:

Event ID 5379 — COM+ General Functionality

Event ID 5379 — COM+ General Functionality

Updated: February 22, 2008

Applies To: Windows Server 2008

COM+ applications use Microsoft Component Object Model (COM) technology in Microsoft Windows operating systems to communicate and take advantage of Windows services. COM technologies include COM+, DCOM, and ActiveX Controls.

Event Details

Product: Windows Operating System
ID: 5379
Source: Microsoft-Windows-Complus
Version: 6.0
Symbolic Name: IDS_W_TXF_TMDOWN
Message: The server process has lost its connection with Microsoft Distributed Transaction Coordinator (MS DTC) service. This is expected if MS DTC has stopped, or if MS DTC failover has occurred on a cluster.%1%0

Resolve

This is a normal condition. No further action is required.

Related Management Information

COM+ General Functionality

Application Server

Related:

Event ID 5378 — COM+ General Functionality

Event ID 5378 — COM+ General Functionality

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

COM+ applications use Microsoft Component Object Model (COM) technology in Microsoft Windows operating systems to communicate and take advantage of Windows services. COM technologies include COM+, DCOM, and ActiveX Controls.

Event Details

Product: Windows Operating System
ID: 5378
Source: Microsoft-Windows-Complus
Version: 6.1
Symbolic Name: IDS_W_UNKNOWN_EXTERNAL_ERROR
Message: An external error has been reported to COM+ services.%1%0

Resolve

This is a normal condition. No further action is required.

Related Management Information

COM+ General Functionality

Application Server

Related:

Event ID 5377 — COM+ General Functionality

Event ID 5377 — COM+ General Functionality

Updated: February 22, 2008

Applies To: Windows Server 2008

COM+ applications use Microsoft Component Object Model (COM) technology in Microsoft Windows operating systems to communicate and take advantage of Windows services. COM technologies include COM+, DCOM, and ActiveX Controls.

Event Details

Product: Windows Operating System
ID: 5377
Source: Microsoft-Windows-Complus
Version: 6.0
Symbolic Name: IDS_E_UNKNOWN_EXTERNAL_ERROR
Message: An external error has been reported to COM+ services.%1%0

Resolve
Report the internal error to Microsoft

If this problem persists and continues to be an issue, contact Microsoft Customer Service and Support (CSS). For information about how to contact CSS, see Enterprise Support (http://go.microsoft.com/fwlink/?LinkId=52267).

Verify

You can verify that your COM+ application is installed and working properly by using the Component Services administrative tool.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To open Component Services and verify that your application is installed:

  1. Click Start, and then click Run.
  2. Type comexp.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. To locate your application, click Component Services, click Computers, click My Computer, and then click COM+ Applications.

In addition, you can verify that the COM+ operating system component is installed and working properly.

To verify that COM+ is working properly:

  1. In the console tree of Component Services, click Services (Local).
  2. Scroll through the list of service names to find the following services: COM+ Event System (optional), COM+ System Application, DCOM Server Process Launcher, and Remote Procedure Call (RPC).
  3. Confirm that the status of each service is Started.

Related Management Information

COM+ General Functionality

Application Server

Related:

Event ID 4869 — COM+ General Functionality

Event ID 4869 — COM+ General Functionality

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

COM+ applications use Microsoft Component Object Model (COM) technology in Microsoft Windows operating systems to communicate and take advantage of Windows services. COM technologies include COM+, DCOM, and ActiveX Controls.

Event Details

Product: Windows Operating System
ID: 4869
Source: Microsoft-Windows-Complus
Version: 6.1
Symbolic Name: IDS_E_EVENTFILTERERROR
Message: The COM+ event filter encountered an unexpected error. The system event will not be fired. %1%0

Resolve
Report the internal error to Microsoft

If this problem persists and continues to be an issue, contact Microsoft Customer Service and Support (CSS). For information about how to contact CSS, see Enterprise Support (http://go.microsoft.com/fwlink/?LinkId=52267).

Verify

You can verify that your COM+ application is installed and working properly by using the Component Services administrative tool.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To open Component Services and verify that your application is installed:

  1. Click Start, and then click Run.
  2. Type comexp.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. To locate your application, click Component Services, click Computers, click My Computer, and then click COM+ Applications.

In addition, you can verify that the COM+ operating system component is installed and working properly.

To verify that COM+ is working properly:

  1. In the console tree of Component Services, click Services (Local).
  2. Scroll through the list of service names to find the following services: COM+ Event System (optional), COM+ System Application, DCOM Server Process Launcher, and Remote Procedure Call (RPC).
  3. Confirm that the status of each service is Started.

Related Management Information

COM+ General Functionality

Application Server

Related: