Ajit Yadav blog

DTC : Component services error - No properties are available on this object.

Ajit Yadav — Mon, 11 Apr 2011 17:24:18 GMT

In the component services UI, under the clustered instances of MSDTC we are not able to see the properties of one of the instances of DTC. It appears blank with the message : No properties are available on this object.

Cause

Configuration issues with the cluster. The issue is related to the problem described in the KB article below :
Error message when you connect to a cluster virtual server by using the named pipes protocol: "The machines selected for remote communication is not available at this time.
https://support.microsoft.com/default.aspx?scid=kb;EN-US;306985

"SQL Server uses remapped pipe names. The issue occurs because these specific network names redirect the named pipe connections and can cause connectivity issues for anything other than SQL Server. Network Name resources that are created by the SQL Server Installation Wizard set the following registry value:
HKEY_LOCAL_MACHINE\Cluster\Resources\%ResourceGUID%\Parameters\RemapPipeNames

The SQL Network Name resource should be used only for SQL Server connectivity. Clients should not attempt to connect to this name for other functions (for example, file shares or the Computer Management utility), and no other non-SQL Server resources should be dependent on this Network Name resource. "

Resolution

Solution 1:

=====================

We can reverse the change SQL Server makes during its installation i.e. set “HKEY_LOCAL_MACHINE\Cluster\Resources\%ResourceGUIDFORSQLNETWORKNAME%\Parameters\RemapPipeName” to false for the SQL Network Name Resource. This could cause SQL named pipe communication delays.

Solution 2: (The preferred solution - the way SQL should implement it) :

=============================================================

If you prefer to leave the key named in solution 1 unchanged, then you can add the following key on each of the cluster nodes.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters

Name: NoRemapPipes

Type: REG_MULTI_SZ

Data: winreg svcctl eventlog

More Information

To validate either solution you can open “remote network registry” in “regedit” and choose a network name for any of the SQL cluster groups. It should open without any errors.

COM+ Queued component : Error 80080005 Server execution failed. Error Code = 0xc00e0003

Ajit Yadav — Fri, 24 Dec 2010 15:12:35 GMT

On a windows server 2003, we are not able to start a Queued COM+ application. It fails with the error: 80080005 Server execution failed.
In the event logs we see the following entries :

Event Type: Error
Event Source: COM+
Event Category: (115)
Event ID: 4811
Date: 12/24/2010
Time: 4:27:39 PM
User: N/A
Computer:
Description:
An unexpected error was returned by Message Queuing API indicated. Unable to retrieve the associated error message text. Message Queuing API return values are defined in Platform SDK file MQ.H.MQPathNameToFormatName

Server Application ID: {45445320-4154-4C41-4E54-455320382E30}
Server Application Instance ID:
{8AAA34A0-076F-4D41-9751-F7D973F5C81A}
Server Application Name: ACM80
Error Code = 0xc00e0003 :
COM+ Services Internals Information:
File: d:\nt\com\complus\src\comsvcs\qc\msmqrt\msmqrt.cpp, Line: 749
Comsvcs.dll file version: ENU 2001.12.4720.4045 shp

Event Type: Error
Event Source: COM+
Event Category: (104)
Event ID: 4811
Date: 12/24/2010
Time: 2:45:16 PM
User: N/A
Computer:
Description:
An unexpected error was returned by Message Queuing API indicated. Unable to retrieve the associated error message text. Message Queuing API return values are defined in Platform SDK file MQ.H.MQOpenQueue

Server Application ID: {45445320-4154-4C41-4E54-455320382E30}
Server Application Instance ID:
{21B51AB1-552F-4FDE-AEC4-9CD7ED000EF0}
Server Application Name: ACM80
The serious nature of this error has caused the process to terminate.
Error Code = 0xc00e0003 :
COM+ Services Internals Information:
File: d:\nt\com\complus\src\comsvcs\qc\listener\listener2.cpp, Line: 532
Comsvcs.dll file version: ENU 2001.12.4720.4045 shp

For more information, see Help and Support Center at https://go.microsoft.com/fwlink/events.asp.

Error code 0xc00e0003 indicates MQ_ERROR_QUEUE_NOT_FOUND.

We opened Computer management and checked the private queues. The private queues for the COM+ application were missing. Ideally, when we configure queuing on the COM+ application it creates the private queues for the COM+ application.
We unchecked the "Queued - This application can be reached by MSMQ queues" option on the COM+ application to disable queueing. Selected the option again to re-enable queueing. Checked the private queues and now we can see the private queues created for the COM+ application.
Started the COM+ application and boom.. it's started.

System.Security.SecurityException: Request for the permission of type System.Security.Permissions.SecurityPermission failed.

Ajit Yadav — Thu, 02 Dec 2010 17:53:00 GMT

WCF service Pieserver is hosted in IIS 7.5. It is using wshttpbinding.
client : console application.

We are able to add the service reference but get the exception below when we call any methods on the proxy object :

Error Message: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: The type initializer for 'OSIsoft.RtBaseline.DataService.ServerManager' threw an exception.
System.TypeInitializationException: The type initializer for 'OSIsoft.RtBaseline.DataService.ServerManager' threw an exception. ----> System.Security.SecurityException: Request for the permission of type 'System.Security.Permissions.SecurityPermission, mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' failed.
at System.Security.Principal.WindowsIdentity.GetCurrent() at OSIsoft.PIInstrumentation.LogWriter.WriteToEventLog(String source, String message, EventLogEntryType elType)
at OSIsoft.PIInstrumentation.LogWriter.WriteGeneralEventLog(String source, String message, Severity svrty, Boolean CheckSuppression) at OSIsoft.PIInstrumentation.RtBLSConfig.get_Setting() at OSIsoft.RtBaseline.DataService.ServerManager..cctor() --- End of inner ExceptionDetail stack trace --- at OSIsoft.RtBaseline.DataService.ServerManager.SetApplicationID(String appID) at PIWebServices.PID...). For more information, see Help and Support Center at https://go.microsoft.com/fwlink/events.asp.

The WCF service application files were hosted on a network share. CAS (Code Access Security) policy has been applied for the service. The PIWebServices.dll is trying to get the current windows identity and failing because the defined CAS policy does not grant ControlPrincipal permissions to it. To provide the permissions on the network share we ran the command below:

CasPol.exe -m -ag 1.2 -url file://\\eas.puget.com/PsePIWebServces/* FullTrust

Reference:

Using CasPol to Fully Trust a Share
https://blogs.msdn.com/b/shawnfa/archive/2004/12/30/344554.aspx https://blogs.msdn.com/b/shawnfa/archive/2004/12/30/344554.aspx

An extension of name clientcredentials already appears in extension collection, extension name must be unique.

Ajit Yadav — Wed, 02 Jun 2010 11:02:00 GMT

When we browse the web page it loads fine and continues working. Once we close the IIS manager and open it again, the following section gets added to the web.config file automatically :

.....................

......................

...................

..................

..............

................

..................

And now, when we browse the web page we get the exception :

"An extension of name clientcredentials already appears in extension collection, extension name must be unique.”

Resolution

We collected first chance exception dumps and process monitor log files when the issue occurred. The analysis from the dumps :

System_Configuration_ni!System.Configuration.Internal.WriteFileContext.DuplicateTemplateAttributes

System_Configuration_ni!System.Configuration.Internal.WriteFileContext.DuplicateFileAttributes(

System_Configuration_ni!System.Configuration.Internal.WriteFileContext.Complete

System_Configuration_ni!System.Configuration.Internal.InternalConfigHost.StaticWriteCompleted

System_Configuration_ni!System.Configuration.Internal.InternalConfigHost.System.Configuration.Internal.IInternalConfigHost.WriteCompleted

System_Configuration_ni!System.Configuration.Internal.DelegatingConfigHost.WriteCompleted

System_Configuration_ni!System.Configuration.UpdateConfigHost.WriteCompleted

System_Configuration_ni!System.Configuration.MgmtConfigurationRecord.SaveAs

System_Configuration_ni!System.Configuration.Configuration.SaveAsImpl(System.String, System.Configuration.ConfigurationSaveMode, Boolean)

System_Configuration_ni!System.Configuration.Configuration.Save(System.Configuration.ConfigurationSaveMode, Boolean)System_Web_ni!System.Web.UI.Control.OnLoad(System.EventArgs)

System_Web_ni!System.Web.UI.Control.LoadRecursive()

System_Web_ni!System.Web.UI.Page.ProcessRequestMain

System_Web_ni!System.Web.UI.Page.ProcessRequest(Boolean, Boolean)

System_Web_ni!System.Web.UI.Page.ProcessRequest()

System_Web_ni!System.Web.UI.Page.ProcessRequestWithNoAssert

System_Web_ni!System.Web.UI.Page.ProcessRequest

System_Web_ni!System.Web.HttpApplication+CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

System_Web_ni!System.Web.HttpApplication.ExecuteStep

System_Web_ni!System.Web.HttpApplication+ApplicationStepManager.ResumeSteps

System_Web_ni!System.Web.HttpApplication.System.Web.IHttpAsyncHandler.BeginProcessRequest

System_Web_ni!System.Web.HttpRuntime.ProcessRequestInternal

System_Web_ni!System.Web.HttpRuntime.ProcessRequestNoDemand

System_Web_ni!System.Web.Hosting.ISAPIRuntime.ProcessRequest

So looks like we are loading some control on the web page and that control is saving some changes to the web.config file using Configuration.Save method.

In the source files, we found following line of code that was saving the config settings everytime the page was loaded :

config.Save(ConfigurationSaveMode.Full, True)

We made the second parameter to false to avoid saving the changes everytime the page is loaded. After setting the second parameter to false we did not have the issue any more.

Reference

Configuration.Save Method (ConfigurationSaveMode, Boolean)

https://msdn.microsoft.com/en-us/library/system.configuration.configuration.save.aspx

Unable to install MSMQ : Error 0x8004e001 Triggers transactional component could not be registered in COM+

Ajit Yadav — Mon, 31 May 2010 19:35:13 GMT

We are unable to install MSMQ due to error: Triggers transactional component could not be registered in COM+. Error Code: 0x8004e001

Since the error message talks about the transactions, we checked if the MSDTC service is running fine. It was not and infact we were not able to start it. When we try to start DTC service we get the error :

Event Type: Error
Event Source: MSDTC
Event Category: Unknown
Event ID: 4209
Date: 1/20/2010
Time: 11:32:36 AM
User: N/A
Computer: USLILVM64SP07
Description:
A critical error occurred in an MS DTC component therefore the process is terminating. The category field identifies the component that encountered the error. Please contact Microsoft Product Support. Error Specifics: d:\nt\com\complus\dtc\dtc\msdtc\src\cservice.cpp:436, Pid: 5740
No Callstack,
CmdLine: C:\WINDOWS\system32\msdtc.exe

For more information, see Help and Support Center at https://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2b 00 11 80 +..€

Reinstalled MSDTC service using the commands :

msdtc -uninstall
msdtc -install
msdtc -resetlog

Tried to start DTC service, we got the error :

Event Type: Error
Event Source: MSDTC
Event Category: SVC
Event ID: 4197
Date: 1/20/2010
Time: 11:34:42 AM
User: N/A
Computer: USLILVM64SP07
Description:
Could not locate the MS DTC XA Transaction Manager contact object.

For more information, see Help and Support Center at https://go.microsoft.com/fwlink/events.asp.

Ran the command "msdtc -uninstall". Checked the registry key HKCR\CID to see if it is getting removed (msdtc -uninstall command removes the HKCR\CID key from the registry). It is not and infact there are more than 10 entries under that. Ideally we should have only 4 GUID entries under HKCR\CID.

We manually deleted the CID key. Ran the command "msdtc -install". DTC installed successfully and came up fine.
Ran the wizard to install MSMQ : SUCCESSFUL.

COM+ application intermittently stops responding while reading a registry key

Ajit Yadav — Mon, 31 May 2010 19:25:23 GMT

The COM+ application randomly stops responding. To fix the problem the COM+ application has to be restarted. After some observation the problem appeared to be with reading a custom registry key.
We were not able to read registry key while it is in use by a COM+ application. Also when we try to access the registry key using regedit we are not able to do it.

We were using RegOpenKeyEx() function to get the handle to the registry key.

Private Function GetKeyValue(ByVal KeyD As Long, ByVal Key As String, ByVal SubKey
As String) As String

Dim value As String
Dim length As Long
Dim hKey As Long

If RegOpenKeyEx(KeyD, Key, 0&, KEY_ALL_ACCESS, hKey) <> ERROR_SUCCESS Then
Err.Raise Err.Number, Err.Source, Err.Description
End If

length = 256
value = Space$(length)

If RegQueryValueEx(hKey, SubKey, 0&, 1&, ByVal value, length) <> ERROR_SUCCESS
Then
Err.Raise Err.Number, Err.Source, Err.Description
Else

value = Left$(value, length - 1)
GetKeyValue = value
End If

End Function

Resolution

LONG WINAPI RegOpenKeyEx(
__in HKEY hKey,
__in LPCTSTR lpSubKey,
DWORD ulOptions,
__in REGSAM samDesired,
__out PHKEY phkResult
);

phkResult
A pointer to a variable that receives a handle to the opened key. If the key is not
one of the predefined registry keys, call the RegCloseKey function after you have
finished using the handle.

We were reading one of the non-predefined keys so we need to explicitly close the handle to the key.

We implemented the RegCloseKey() function to explicitly release the handle to the registry key.
<https://msdn2.microsoft.com/en-us/library/ms724837.aspx>

This resolved the issue.

COM+ : 0x8004E002 : The root transaction wanted to commit, but transaction aborted.

Ajit Yadav — Mon, 31 May 2010 16:31:53 GMT

The COM+ application 'eConnect' is unable to complete distributed transactions successfully against the SQL server. It fails with the error :

(0x8004E002): The root transaction wanted to commit, but transaction aborted.

The eConnect COM+ application tries to send xml data to the SQL server on another server. Both the servers are Windows 2008. It runs for a while and then comes back with the error message :

System.Runtime.InteropServices.COMException (0x8004E002): The root transaction wanted to commit, but transaction aborted (Exception from HRESULT: 0x8004E002)
at System.EnterpriseServices.IRemoteDispatch.RemoteDispatchNotAutoDone(String s)
at System.EnterpriseServices.RemoteServicedComponentProxy.Invoke(IMessage reqMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.Dynamics.GP.eConnect.eConnectMethods.eConnect_EntryPoint(String ConnectionString, ConnectionStringType ConnectionType, String sXML,
SchemaValidationType ValidationType, String eConnectSchema)
at DirectDocSenderDotNet.FrmDocSender.btnSend_Click(Object sender, EventArgs e)
in C:\program files\Common Files\microsoft shared\eConnect 10\eConnect Samples\CSHARP DirectDocSender\frmDocSender.cs:line 379

Checked the DTC security settings under component services --> computers --> My computer --> local dtc --> security. Enabled Network DTC access and the other options :

Allow remote clients
Allow remote administrations
Allow inbound
Allow outbound
No authentication required

Enabled the same options on the SQL Server machine. Still the transaction would run for a while and then abort. The global transaction timeout of DTC was set to 360 seconds under component services --> computers --> My computer --> properties --> Options. Configured the same timeout on SQL server box. Still no luck.
We checked the C:\windows\system32\DTCTrace.log file and found that the transactions were being aborted by the SQL server box.

Resolution

We checked the transaction timeout on the COM+ components and they were set to 120 seconds. Changed them to 360 on all the transactional components. Ran the transaction and now it completed successfully.

DB2 XA transactions failure : : Failed to enlist on calling object's transaction.

Ajit Yadav — Mon, 31 May 2010 15:55:00 GMT

We are unable to run XA transactions with DB2 server. It fails with the error :

Source: Microsoft OLE DB Provider for ODBC Drivers
Parameters: -2147467259
[Microsoft][ODBC Driver Manager] Failed to enlist on calling object's transaction
Microsoft OLE DB Provider for ODBC Drivers

Few things to check

Checked the registry settings :
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\XADLL ] DB2cli.dll =
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\XADLL ] DB2app.dll =

They entries were good.

Added NT Authority\NetworkService account to local admin group and still got the same error, that rules out permissions issue with the MSDTC service logon account.
If we set the COM+ components to transaction support level of Supported or Disabled, the web page works. Setting it to Required causes it to fail. This is because when we use the Supported or Disabled setting the transaction is not using DTC service.

We were also getting the error :
Failed to enlist in DTC: SQL state , native error -5042, error message [IBM][CLI
Driver] SQL5042N One of the communication protocol server support processes failed to start up.”

Resolution

As the source of the error was IBM driver, suggested that we should include IBM support to check if the DB2 client is configured properly. Involved the IBM support and the error was resolved by running the correct command as :

db2 update dbm cfg using SPM_NAME sdawwi08

where
SPM_NAME = service name
sdawwi08 = server name

MSDTC : Oracle 10G client : New transaction cannot enlist in the specified transaction coordinator

Ajit Yadav — Mon, 31 May 2010 15:17:55 GMT

Using Oracle Client version 10g (Windows 2003 SP1) to communicate with the Oracle Database Server (OS : Unix). When we enable the option for Transaction Support to be "Required " in the COM+ application we get the error : New transaction cannot enlist in the specified transaction coordinator.

Checklist

1. Checked MSDTC Security Configuration and corrected them by following the KB article : https://support.microsoft.com/default.aspx?scid=kb;EN-US;899191
2. Checked the registry entries at the following keys :
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\XADLL -- > MTXOCI set to --> C:\WINNT\system32\mtxoci.dll
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSDTC\MTxOCI :
"OracleXaLib"="oraclient10.dll"
"OracleSqlLib"="orasql10.dll"
"OracleOciLib"="oci.dll"

All of the above entries look good.

3. Ran Filemon and Regmon tools.
4. Regmon looked fine. In Filemon log , got "File Not Found" error for "ORAMTS10.DLL".
5. Referred the KB article at :
https://support.microsoft.com/default.aspx?scid=kb;EN-US;843044 according to which :

The Oramts.dll file is used when you try to use Microsoft Transaction Server (MTS) in a distributed environment. The .NET Framework Data Provider for Oracle (System.Data.OracleClient) calls the Application Programming Interfaces (APIs) that are publicly exposed by the Oramts.dll file. The Oramts.dll file is only available in Oracle client connectivity software. To install it on your computer, you must explicitly select the "Oracle Services for Microsoft Transaction Server" component during the installation of Oracle client connectivity software.

Resolution

Reinstalled Oracle Client 10g and selected the checkbox "Oracle Services for Microsoft Transaction Server" during installation. The setup installed the "ORAMTS10.DLL" on the system and resolved the issue.

COM+ partitions : Retrieving the COM class factory for component with CLSID {GUID} failed due to the following error: 80040154.

Ajit Yadav — Fri, 26 Mar 2010 17:48:00 GMT

Environment

Windows server 2003 Enterprise Edition SP2
Two node windows cluster.

Problem

We browse a web service and then we hit on a method that takes us to a form. After passing parameters on the form and clicking on the submit button we get the error :

Retrieving the COM class factory for component with CLSID {GUID} failed due to the following error: 80040154.

The web service is running under a local user account that is a part of local administrators group. The apppool is also running under the same user.
Created Test.vbs to do a CoCreateInstance on the COM+ component and that failed too with the error : Activex component cannot create the object ''.
Deleted the component and added it back. Still fails.
Deleted the component again. Unregistered it and re-registered it using regsvr32.exe but we did not put it back in COM+.
Now the test.vbs worked. Web page worked too.
The COM+ package is under a partition named "QA partition" where we have configured some users under Roles but we are not using the roles as "Enable Enforce Access Checks". Even enabling that has no effect, still fails. Tried other COM+ components within the same partition and they are not working.

Resolution

The server had the problem with one particular COM+ application. Other COM+ applications within the same partition worked when the components are invoked from ASP.
We checked the web.config file for IIS virtual directory. Found that Impersonation was turned on with SetImpersonate=True, username= . All the web requests for the COM+ application was being made under this impersonated user. We created the mapping for this user under COM+ partition --> Roles. This resolved the issue.