Cannot add QDB or Repository to the Control Center console. (NETIQKB46201)

Control Center displays Repository status as down.

Error: Fail to connect to QDB

Configuration Checker Distributed transaction test fails with OLEDB error: Server: Msg 7391, Level 16, State 1, Line 1The operation could not be performed because the OLE DB provider 'SQLOLEDB' was unable to begin a distributed transaction.[OLE/DB provider returned message: New transaction cannot enlist in the specified transaction coordinator. ]OLE DB error trace [OLE/DB Provider 'SQLOLEDB' ITransactionJoin::JoinTransaction returned 0x8004d00a].

Run the Control Center Pre-Installation check as a first step to troubleshoot Control Center connectivity. This Pre-Installation check reports any security or installation failures.  If your Pre-installation check completes, verify the following information:

1. You ran the Control Center Repository Upgrade on each Repository you want to monitor within Control Center.
2. Verify the DTC access and configuration information noted in the Control Center Readme file.

Below are links to the Microsoft articles that provide instructions to disabling RPC security and a link to a DTC tester:

If you have questions about DTC with Microsoft Windows 2003, please reference this Microsoft KB for more information: HOWTO: Enable DTC Between Web Servers and SQL Servers Running Windows Server 2003 (555017) 

To access the DTC Tool useful for testing your DTC transactions (which could assist in troubleshooting Control Center connectivity), please reference this Microsoft KB to download and use this utility: How To Use DTCTester Tool (293799)

If your DTC configuration is accurate, you could must confirm the SQL Server name for the SQL database matches the NetBIOS name.  The servername global value can be changed by first dropping the incorrect name from the list using the following SQL statement.

Warning : This SQL Query directly accesses your database and updates/deletes data. If the query is performed incorrectly it can cause irreparable harm to the database and may result in loss of data. If you are unfamiliar with SQL or how to run a SQL Query please contact NetIQ Technical Support directly.

Syntax

sp_dropserver [ @server = ] 'server'
[ , [ @droplogins = ] { 'droplogins' | NULL} ]

Arguments

[@server =] 'server' 
If the server is to be removed, the server is sysname. If it is with no default, the server must exist.

[@droplogins =] 'droplogins' | NULL
Indicates that related remote and linked server logins for server must also
be removed if droplogins is specified. Note: @droplogins is char(10), with a
default of NULL.

Return Code Values

0 (success) or 1 (failure)

NetIQ recommends dropping the server name listed, then use the SQL command sp_addserver with the @local = ] 'local' flag enabled to read the server.  Restart the SQL Server following this operation.  NOTE:  The computer does not require a reboot.

Next, use the Select @@ServerName command to verify that the machine name within the database is correct.

The problem occurs because Microsoft Distributed Transaction Coordinator (MS DTC) is not configured for network access. By default, the network access settings of MS DTC are disabled on new installations of SQL Server 2000 on computers running Windows Server 2003, Enterprise Edition.  Microsoft has documented this problem and has provided the steps required to resolve this problem in Microsoft KnowledgeBase article 329332.  Note: A reboot of the server is required to complete the configuration.

The SQL Server's name does not properly match the machine name.  This can be verified by issuing the following command in SQL Query Analyzer:

          SELECT @@SERVERNAME

The name that is returned must match the NETBIOS name of the computer hosting the SQL Server 

Required security permissions have not been set.

DTC has not been configured on the Control Center server or the AppManager Repository.

Formerly known as NETIQKB46201

For more information regarding changing servernames within SQL Server, refer to SQL Server's Books Online.

Using the DTC ping utility can be confusing to a clustered SQL instance.  For the tool work correctly, you must point the DTC Tool at the virtual server, but not the named instance.