sign in sign up
<<
Home , Event Viewer

IBM Tivoli Composite Application Manager for Applications: . Data Collector 7.3.2 Fix Pack 6

Troubleshooting Guide

IBM

Note Before using this information and the product it supports, read the information in “Notices” on page 23.

This edition applies to version 7.3.2.5 of IBM® Tivoli® Composite Application Manager for Microsoft Applications: .NET Data Collector (product number 5724-U17) and to all subsequent releases and modifications until otherwise indicated in new editions. © Copyright International Business Machines Corporation 2012, 2020. US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents

Tables...... v

Chapter 1. Problems and workarounds...... 1 .NET Data Collector configuration changes not reflected in operation...... 1 No events are received from the .NET Data Collector...... 1 .NET Data Collector event 1022...... 1 SVC node is disconnected if SOAP is disabled...... 2 Static nodes might be seen in the transaction topology...... 2 Multiple play icons might be seen in transaction topology...... 2 Empty folder structure of the .NET Data Collector remains after uninstallation...... 2 The .NET Data Collector is not installed if .dll files of previous versions are used...... 2 Database node details might vary according to the database and connection ...... 3 Incorrect information is displayed for a call to WCF service...... 3 Pseudo node with an asynchronous arrow is seen...... 3 Transaction Name is displayed in an incorrect in transaction topology...... 3 Asynchronous arrow is displayed when authentication fails...... 3 Asynchronous arrow is displayed when a web service or a web page fails to process...... 4 Error occurs while processing a SOAP call...... 4 Failed MVC redirected transactions and failed WCF services with NetTcpBiding are not monitored...... 4 ASP.NET MVC application fails...... 4 Nodes in the transaction topology are displayed in an incorrect format ...... 5 A duplicate node is generated in the transaction topology...... 5 A separate instance for each call is displayed in the instance topology...... 5 One way transactions that are done by using the NetTcpBinding are not monitored...... 5 A dashed asynchronous arrow is displayed in the transaction topology...... 5 One way transactions that are done by using the WebHttpBinding are not monitored...... 5 An error related to the ttapi.dll file is generated...... 6 ASP .NET impersonation is not enabled...... 6 Visual Studio 2008 runtime environment is required before you upgrade the .NET Data Collector V7.3.1...... 6 Component name is shown as Microsoft.NET in the Transactions workspace...... 6 The ADO.NET nodes are not generated...... 7 Status of .NET Data Collector components is displayed as Error...... 7

Chapter 2. Support information...... 9

Chapter 3. The .NET Data Collector: Property Configuration window messages...... 11

Chapter 4. Selective Filtering messages...... 13

Chapter 5. Event log messages...... 15

Chapter 6. .NET Data Collector messages: BWMNT*...... 17

Appendix A. ITCAM for Microsoft Applications documentation library...... 21 Prerequisite publications...... 21 Related publications...... 22 Tivoli Monitoring Community on Service Management Connect...... 22 Other sources of documentation...... 22

iii Notices...... 23 Trademarks...... 24 Terms and conditions for product documentation...... 25 IBM Online Privacy Statement...... 25

Index...... 27

iv Tables

1. Selective Filtering messages...... 13

2. Event log messages of the .NET Data Collector...... 15

v vi Chapter 1. Problems and workarounds

Problems can occur during installation, configuration and uninstallation of the .NET Data Collector. .NET Data Collector configuration changes not reflected in operation The problem: You updated the .NET Data Collector configuration using configdc activateconfig but your changes are not reflected in the operation of the .NET Data Collector. The solution: Verify your changes by using the configdc getconfig –active command on the system where you configured the .NET Data Collector. If the configuration changes are not updated, configure the .NET Data Collector again by using the configdc activateconfig command. No events are received from the .NET Data Collector The problem: No events are received from the .NET Data Collector. The solution: Ensure that the following actions are complete: • Verify that the prerequisites for the .NET Data Collector are met. • After installation, verify that the .NET Data Collector is registered by using the configdc registerdc command. • Verify that the .NET Data Collector is connected to the correct Transaction Collector by using the configdc ttserver command, and then run the configdc activateconfig command. • Ensure that network connection exists between the computers where the .NET Data Collector and the Transaction Collector are installed. • Ensure that you restart the application that you want to monitor after registration. You must restart the IIS after you make configuration changes. .NET Data Collector event 1022 The problem: The Windows Application event log contains .NET runtime events with 1022 event ID, and the following event log message: Failed to CoCreate profiler. The solution: In the Windows event log, events with 1022 event ID are generated if the .NET Data Collector is unregistered or uninstalled, and one or .NET applications are not restarted. Restart all .NET applications. Restart the computer to ensure that all .NET applications are restarted. If .NET Profiler is not installed and the event is displayed again, verify that the following environment variables are not specified: • COMPLUS_ProfAPI_ProfilerCompatibilitySetting • COR_ENABLE_PROFILING • COR_PROFILER If the environment variables are displayed, open the command prompt, enter the set c command to remove the variables. If the environment variables are displayed in the list again, manually remove the environment variables from the System variables, and restart the system. See Windows for the procedure to delete system environment variables.

© Copyright IBM Corp. 2012, 2020 1 SVC node is disconnected if SOAP is disabled The problem: The SVC node is disconnected when an ADO\LDAP \HTTP\SOAP call is made from the WCF service. The solution: No solution exists for this problem. It is a known limitation. If HttpModule and Profiler are enabled, and SOAP is disabled during an ADO\LDAP \HTTP\SOAP call that is made from the WCF service, SVC node is not linked with ADO\LDAP \HTTP\SOAP. Static nodes might be seen in the transaction topology The problem: When the IIS Server processes ASP.NET pages, static nodes might be seen in the transaction topology. The solution: No solution exists for this problem. It is a known limitation. When the IIS Server processes ASP.NET pages, the HTML content is generated that is sent to the browser. If the HTML page contains any static content, the static node might be seen in the transaction topology. Multiple play icons might be seen in transaction topology The problem: When IIS 7.x is run in the classic mode with ISAPI, multiple play icons might be seen in the transaction topology. The solution: No solution exists for this problem. It is a known limitation. Even if all the transaction tracking events occur properly, multiple play icons might be seen in the topology of a transaction. Empty folder structure of the .NET Data Collector remains after uninstallation The problem: After you uninstall the .NET Data Collector, the empty folder structure of the .NET Data Collector remains in the installation directory. The solution: No solution exists for this problem. It is a known limitation. You can delete the folders after the uninstallation is complete. The .NET Data Collector is not installed if .dll files of previous versions are used The problem: If the dll files of the .NET Data Collector V7.3.0 are present on the computer where you want to upgrade the .NET Data Collector V7.3.0 to V7.3.1, the upgradation fails. You must restart the IIS Server before installing and uninstalling the .NET Data Collector. The solution:

Restart IIS before installation Before you install the .NET Data Collector, ensure that the following tasks are complete: • The libcclog_64.dll, libcclog.dll, and corproflog.dll files are not being used by any applications. • Go to > Run, and then run iisreset command.

Restart IIS before uninstallation • Open the command prompt. • Change the directory to CANDLE_HOME\TMAITM6\K4\bin.

2 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide • Run the configdcunregisterdc command, and then run the iisreset command. Database node details might vary according to the database and connection type The problem: The database node details depend on the combination of a database and the connection type that is used in an application to access the database. The solution: No solution exists for this problem. It is a known limitation. On the Transaction Reporter, under the database node, the following values are displayed: • Application • Transaction • Component • Server The values are derived from the data source of an application that is used to access a database. The values might vary according to the database, such as DB2 Server, SQL Server, or Oracle, and the connection type that is used in an application to access the database, such as OLEDB or ODBC. Incorrect information is displayed for a call to WCF service The problem: When a call is made to a WCF service, the request fails with HTTP status code 415 and incorrect information is displayed in the transaction topology. The solution: If a call is made to a WCF service and the value of the content-type parameter in the request is not accepted by the web server, the request is not processed as an SOAP request. The request is processed as an HTTP request with an HTTP status code 415 to indicate that the content-type of the request is not accepted. Because no SOAP request is processed, the status of the WCF service is displayed as failed, the transaction names are displayed in the *.svc format, and an async arrow is displayed between the WCF service and the client.

Pseudo node with an asynchronous arrow is seen The problem: A dashed arrow that indicates an pseudo request is displayed when a call is made from ASP.NET web forms to WCF by using an Async method. The solution: This problem is a known behaviour in the .NET Data Collector.

Transaction Name is displayed in an incorrect format in transaction topology The problem: When a call is made to a one-way WCF/ASMX web service, the Transaction Name is displayed as webservice1.asmx in the transaction topology. The solution: No solution exists for this problem. It is a known limitation.

Asynchronous arrow is displayed when authentication fails The problem: An asynchronous arrow is displayed in the transaction topology when the authentication fails in an ASP.NET web service or while processing an HTTP web request. The solution: This problem is a known behaviour in the .NET Data Collector. If authentication fails in an ASP.NET web service or while processing an HTTP web request, an outbound event is generated and an asynchronous arrow is displayed in the transaction topology. A pseudo node is displayed if the request does not pass through the IIS pipeline.

Chapter 1. Problems and workarounds 3 Asynchronous arrow is displayed when a web service or a web page fails to process The problem: An asynchronous arrow is displayed in the transaction topology when an ASP.NET web service or a web page fails to process. The solution: This problem is a known behavior in the .NET Data Collector. A solid or a dashed asynchronous arrow might be displayed in the transaction topology between an ASP.NET web service or a web page, and the source of the ASP.NET web service or a web page.

Error occurs while processing a SOAP call The problem: An error occurs when a SOAP call is made from a computer where the .NET Data Collector is not installed to the computer where the .NET Data Collector is installed. The solution: This problem is a known behaviour in the .NET Data Collector. If a SOAP call is made from a computer where the .NET Data Collector is not installed to the computer where the .NET Data Collector is installed, an error occurs while processing the call. The following error message is displayed in the .NET Data Collector logs for SOA component: Object reference not set to an instance of an object. To view the log file, enable the following properties: kd4_dc.message.logging kd4_dc.trace.logging Tip: You can use the .NET Data Collector: Property Configuration window to enable the properties. For more information, see "Modifying configuration in the GUI" topic in the .NET Data Collector Reference. In the transaction topology, the web service nodes are displayed in *.asmx and *.svc format. Failed MVC redirected transactions and failed WCF services with NetTcpBiding are not monitored The problem: The .NET Data Collector does not monitor the failed MVC redirected transactions and the failed WCF services that are done by using the NetTcpBiding. The solution: This problem is a known behavior in the .NET Data Collector. No solution exists for this problem. ASP.NET MVC application fails The problem: If you manually set the maximum query string limit of an ASP.NET MVC application to a low value by using the IIS Server, the ASP.NET MVC application fails. The solution: By using the IIS Server, manually set the maximum query string limit of an ASP.NET MVC application to a higher value. If you do not want the .NET Data Collector to monitor the ASP.NET MVC application, complete one of the following steps: • In the dotNetDcConfig.properties file, specify the following property: System.Web.Mvc.RedirectToRouteResult.ExecuteResult.0.Enabled=false • Exclude the application from monitoring by using the selective filtering utility. For more information, see the "Selective filtering utility" chapter in the .NET Data Collector Reference.

4 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide Nodes in the transaction topology are displayed in an incorrect format The problem: The transaction name of a starting node of a transaction that is initiated from a one-way web service is displayed in a *.asmx or a *.svc format in the transaction topology. The solution: This problem is a known behaviour in the .NET Data Collector. No solution exists for this problem.

A duplicate node is generated in the transaction topology The problem: If a call is made from a one-way operation of a WCF web service, and the ASP.NET compatibility mode is not enabled for the web service, a duplicate node is generated in the transaction topology. The node represents the WCF web service. The solution: This problem is a known behaviour in the .NET Data Collector. No solution exists for this problem.

A separate instance for each call is displayed in the instance topology The problem: If multiple web service calls are made from a one-way web service, a separate instance for each call is displayed in the instance topology. The solution: This problem is a known behaviour in the .NET Data Collector. No solution exists for this problem. One way transactions that are done by using the NetTcpBinding are not monitored The problem: The .NET Data Collector does not monitor the one-way transactions that are done by using the NetTcpBinding binding. The solution: This problem is a known behaviour in the .NET Data Collector. No solution exists for this problem.

A dashed asynchronous arrow is displayed in the transaction topology The problem: If a call is made from a one-way web service that is located on a computer where the .NET Data Collector is installed to a web service that is located on a computer where the .NET Data Collector is not installed, a dashed asynchronous arrow is displayed in the transaction topology. The solution: This problem is a known behaviour in the .NET Data Collector. No solution exists for this problem.

One way transactions that are done by using the WebHttpBinding are not monitored The problem: The .NET Data Collector does not monitor the one-way transactions that are done by using the WebHttpBinding binding. The solution: This problem is a known behaviour in the .NET Data Collector. No solution exists for this problem.

Chapter 1. Problems and workarounds 5 An error related to the ttapi.dll file is generated The problem: If the ISAPI or HTTPModule components of .NET Data Collector are enabled and the .NET Framework 4.0 is installed on a server that runs on a 64-bit , error messages are generated when a web request is processed. If the ISAPI component is enabled, the following error message is displayed: Service Unavailable. If the ISAPI component is disabled, and the HTTPModule component is enabled, the following error message is displayed: Unable to load DLL 'ttapi.dll': This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1). The solution: Install the Microsoft Visual C++ 2005 Service Pack 1 Redistributable package (x64) on the computer where .NET Data Collector is installed. You can download this package from the Microsoft Download Center website. ASP .NET impersonation is not enabled The problem: When the WCF service for which the ASP.NET impersonation is not enabled is being processed, the application name is displayed as w3wp and the component name is displayed as Microsoft.NET in the Transactions workspace. The solution: Enable the ASP.NET impersonation for the service that is being processed. Visual Studio 2008 runtime environment is required before you upgrade the .NET Data Collector V7.3.1 The problem: Visual Studio 2008 runtime environment must be installed before you upgrade the .NET Data Collector from V7.3.1 to V7.3.2 or V7.3.2, Fix Pack 1 or V7.3.2, Fix Pack 2. When you unregister the .NET Data Collector, the .dll files of the Microsoft Visual C++ 2008 redistributable package are required. The solution: Install the Microsoft Visual C++ 2008 Service Pack 1 Redistributable package. For a 32-bit operating system, download the Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (x86) from the Microsoft Download Center website. For a 64-bit operating system, download the Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (x64) from the Microsoft Download Center website. Component name is shown as Microsoft.NET in the Transactions workspace The problem: When database calls are made by using ODBC, the component name is shown as Microsoft.NET in the Transactions workspace of the Transaction Reporter agent. This problem occurs due to aggregation of ODBC events. The solution: Disable the ADO Event Aggregation by completing the following steps: 1. Open the dotNetDcConfig.properties.inactive file. 2. Change the value of the ktj_ADOAggregation.Enabled property to false, such as: ktj_ADOAggregation.Enabled=false. 3. Open the command prompt, and browse to the bin directory of .NET Data Collector. 4. Run the configdc activateconfig command. 5. Restart all the .NET applications.

6 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide The ADO.NET nodes are not generated The Problem: When database calls are made from a stand-alone client, the ADO.NET nodes are not generated. This problem occurs when the ADO Event Aggregation is enabled in the dotNetDcConfig.properties.inactive properties file. The .NET Data Collector cannot track the instance when a user closes the application. Therefore, the ADO events are not aggregated. The Solution: Disable the ADO Event Aggregation by completing the following steps: 1. Open the dotNetDcConfig.properties.inactive file. 2. Change the value of the ktj_ADOAggregation.Enabled property to false, such as: ktj_ADOAggregation.Enabled=false. 3. Open the command prompt and browse to the bin directory of .NET Data Collector. 4. Run the configdc activateconfig command. 5. Restart all the .NET applications. Status of .NET Data Collector components is displayed as Error The problem: When you run the configdc getconfig command, the status of some or all of the .NET Data Collector components is displayed as Error. The solution: This problem occurs if a .NET Data Collector component or components are not registered correctly. To resolve this issue, the .NET Data Collector components need to be registered again. 1. Run the command prompt in administrator mode, and go to Candle_Home%\TMAITM6\k4\bin 2. Run configdc unregisterdc all 3. Register the required components one after the other by running the following command: configdc registerdc , where the is Profiler, HttpModule, Soap, and Isapi. 4. Run configdc getconfig to verify the status of components.

Chapter 1. Problems and workarounds 7 8 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide Chapter 2. Support information

If you have a problem with your IBM software, you want to resolve it quickly. IBM provides the following ways for you to obtain the support you need: Online The following websites contain troubleshooting information: • Go to the IBM Software Support website (http://www.ibm.com/support/entry/portal/software) and follow the instructions. • Go to the Application Performance ksManagement Wiki (http://www.ibm.com/developerworks/ servicemanagement/apm/index.html). Feel free to contribute to this wiki. IBM Support Assistant The IBM Support Assistant (ISA) is a free local software serviceability workbench that helps you resolve questions and problems with IBM software products. The ISA provides quick access to support-related information and serviceability tools for problem determination. To install the ISA software, go to the IBM Support Assistant website (http://www.ibm.com/software/support/isa).

© Copyright IBM Corp. 2012, 2020 9 10 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide Chapter 3. The .NET Data Collector: Property Configuration window messages

Information messages and error messages are displayed when you use the .NET Data Collector: Property Configuration window for modifying the configuration settings of the .NET Data Collector.

Message Description Changes are not saved. Are you sure you This message is displayed when you close want to ? the .NET Data Collector: Property Configuration window without saving the changes that you made in the configuration settings. Error while activating the properties. This message is displayed when an invalid Invalid properties found in property or an invalid property value is specified "dotNetDcConfig.properties.inactive" in the file. The configuration settings that dotNetDcConfig.properties.inactive you changed are saved in the file. "dotNetDcConfig.properties.inactive" file but they are not applied to the .NET Data Collector. Failed to the properties file. This message is displayed when you do not have Ensure that the properties file exists the read and write permissions to copy the and your account has Read and Write dotNetDcConfig.properties.inactive permissions to copy this file. The file. configuration settings that you changed are saved in the "dotNetDcConfig.properties.inactive" file but they are not applied to the .NET Data Collector. For more information, check CANDLE_HOME\ TMAITM6\k4\logs\configDC_trace.log Failed to open the trigger file. Ensure This message is displayed when you do not have that the trigger file exists and your the read and write permissions to access the account has Read and Write permissions trigger file. to update this file. The configuration settings that you changed are saved in the "dotNetDcConfig.properties.inactive" file but they are not applied to the .NET Data Collector. For more information, check CANDLE_HOME\ TMAITM6\k4\logs\ configDC_trace.log. Following invalid properties are found This message is displayed when the in the dotNetDcConfig.properties.inactive file "dotNetDcConfig.properties.inactive" contains invalid properties. file: An error occurred while activating the This message is displayed when the configuration. configuration is not activated.

© Copyright IBM Corp. 2012, 2020 11 Message Description An error has occurred while opening the This message is displayed when the KK4ConfigProperties.exe. For more KK4ConfigProperties.exe file is not opened information, check the event logs. properly. This error may occur if the dotNetDcConfig.properties.inactive file is not present in the installation directory of the .NET Data Collector.

12 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide Chapter 4. Selective Filtering messages

Information messages are displayed when you use the Selective Filtering utility.

Table 1. Selective Filtering messages Message Description Filter list is set for selected Displayed when the selected application pools are application pools. saved for filtering. Note: After the application pools are saved for filtering, you must reset the IIS Server. Reset the IIS Server by running the iisreset command.

Application pools filter list is Displayed when no application pool is selected for cleared. filtering and Save Selected for Filtering button is clicked. Note: The filtering process is automatically disabled. For more information, see the Enabling the application pools filtering topic in the .NET Data Collector Reference.

The Selective filtering value is Displayed when an application automatically changed from some external program modifies the state of the selective filtering. instance. Currently it is not in Note: The Selective Filtering utility disables the enabled state. So selected application selective filtering and the changes that you made in pools cannot be set for filtering. application pool filter list are not saved.

Some exception occurred while setting Displayed when the selected application pools are the filter list. Please see event log not saved. See event log for more information for exception. about the error. No items in the list to perform the Displayed when one of the following task is current action. performed: • When no application pools are listed in the Application Pools area and Select All is clicked. The Selective Filtering Utility cannot fetch the application pools list, and you must fetch the available application pools by clicking Fetch Application Pools. • When no application pools are listed in the Application Pools area and Invert Selection is clicked. This message indicates that the Selective Filtering Utility did not fetch the application pools list, and you must fetch the available application pools by clicking Fetch Application Pools.

.NET Data Collector is not installed Displayed when the .NET Data Collector is not on the computer. Install .NET Data installed on the computer where you run the Collector before using the Selective Selective Filtering utility. Filtering utility.

© Copyright IBM Corp. 2012, 2020 13 14 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide Chapter 5. Event log messages

Errors that occur while using the .NET Data Collector are saved as event log messages in the system. You can view the errors in the Event Viewer utility of Windows.

Table 2. Event log messages of the .NET Data Collector Event log message Description CCLogger Constructor: CCgGetObject : + Cause: An unmanaged CCLogger object is created (EXCEPTION) in the Byte Code Injection (BCI) engine. Consequence: No bci.trace logs are generated for the Profiler component of the .NET Data Collector.

Initialize: Error initializing message Cause: A managed CCLogger object is created in logger. +(EXCEPTION) the KTJDotNet assembly. Consequence: No ktj.trace logs are generated for HttpModule and Profiler components of the .NET Data Collector.

KD4dcagent : Error creating trace Cause: A managed CCLogger object or the file: +(EXCEPTION) KD4.trace log file is created in the KD4DcAgent assembly. Consequence: No kd4.trace logs are generated for the SOAP component of the .NET Data Collector.

KD4dcagent : Could not initialize Cause: IBM Tivoli Composite Application Manager KD4SoapHandler: +(EXCEPTION) for SOA or the .NET Data Collector installation directory is not found and the configuration initialization for IBM Tivoli Composite Application Manager for SOA fails. Consequence: The SOAP component does not work properly and SOA events that are generated while calling web services are missed.

KD4dcagent : Error retrieving process Cause: The KD4DcAgent assembly fails to read the information: +(EXCEPTION) process information. Consequence: A problem occurred while creating a log file for the kd4.trace logs. The problem affects the logging of SOAP component.

© Copyright IBM Corp. 2012, 2020 15 Table 2. Event log messages of the .NET Data Collector (continued) Event log message Description Initialize: Error setting tracing Cause: The tracing level of trace logs is set to an level. +(VALUE) unsupported value. The following values are supported: • DEBUG_MIN • DEBUG_MID • DEBUG_MAX Consequence: Creation of CCLogger object might fail because of the unsupported tracing level and the ktj.trace logs are not generated for HttpModule and Profiler components of the .NET Data Collector.

Initialize: Error opening File: + Cause: The log file garbage collector is unable to (EXCEPTION) read the configuration file of the .NET Data Collector. The file is not present in the system_root\drivers\etc\ directory or access to the file is denied. Consequence: The log file garbage collector is not able to access the.NET Data Collector installation directory therefore, the log file garbage collector cannot delete the log files.

Error: Malformed Properties File: Cause: The dotNetDcConfig.properties file PropertyFile: +(Property value) was tampered with an external utility and the configuration key and the value are not separated by an = sign. Consequence: The .NET Data Collector is not able to read the properties file. The data collector might generate unexpected results and event generation might be affected.

SelectiveFiltering: Cause: Selective Filtering utility is not enabled GetAppPoolFilterList since the .NET Data Collector was installed, and you searched for event log entries that are related to the Selective Filtering utility in the Windows Event Viewer utility. Consequence: This message is an information message, and it does not affect functioning of the .NET Data Collector.

16 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide Chapter 6. .NET Data Collector messages: BWMNT*

BWMNT0022W Only one .NET Profiler may be failure can be due to insufficient registered on this system and user authority to run another .NET Profiler is already tool, a missing DLL file, or a registered. Use the -f option to corrupted DLL file. register the .NET Profiler over any Explanation: existing .NET Profiler. System failed to run the Regsvr32 program of 64-bit Explanation: Windows. The error might occur because of The .NET Data Collector uses only one .NET Profiler to insufficient user permissions to run Regsvr32 tool, a capture transaction information. Therefore, only missing .dll file, or a corrupted .dll file. one .NET Profiler can be registered on the computer. User response: User response: Ensure that you have the permissions to run the Ensure that you install the .NET Profiler that is most Regsvr32 program. Install the .NET Data Collector critical for your system operation. again to update missing or corrupt .dll files. BWMNT0100E Error setting the BWMNT0104E The execution of the 32-bit value. Ensure that you are using an Windows Regsvr32 tool failed with account with sufficient a return value of retValue. This permissions to update the failure can be due to insufficient Windows Registry. user authority to run Regsvr32 tool, a missing .dll file, or a Explanation: corrupted DLL file. The Windows RegSetValueEx API failed. Explanation: User response: System failed to run the Regsvr32 program of 32-bit Ensure that you have the permissions to update the Windows. The error might occur because of Windows Registry. insufficient user permissions to run Regsvr32 tool, a BWMNT0101E Enabling the Global environment missing .dll file, or a corrupted .dll file. variables failed with a return value User response: of: dwReturnValue. Ensure that you Ensure that you have the permissions to run the are using an account with REGSVR32 program. Install the .NET Data Collector sufficient permissions to update again to update missing or corrupt .dll files. the environment variables. BWMNT0105E There was an error removing the Explanation: Windows registry value. Ensure The Windows SendMessageTimeout API failed. that you are using an account with User response: sufficient permissions to update Ensure that you have the permissions to update the the Windows Registry. environment variables. Explanation: BWMNT0102E Error opening the Windows The Windows RegDeleteValue API failed. registry. Ensure that you are using User response: an account with sufficient Ensure that you have the permissions to update the permissions to access the Windows Registry. Windows Registry. BWMNT0106E Unable to write to the .NET Explanation: Tracking configuration file. Ensure The Windows RegOpenKeyEx API failed. that the configuration file exists User response: and that your account has Ensure that you have the permissions to access the sufficient permissions to update Windows Registry. this file. BWMNT0103E The execution of the Windows 64- Explanation: bit Regsvr32 tool failed with a System failed to write to the return value of retValue. This dotNetDcConfig.properties file.

© Copyright IBM Corp. 2012, 2020 17 User response: assemblies to the Global Assembly Ensure that the configuration file exists and that you Cache. have the permissions to update the file. Explanation: BWMNT0107E Failed to open the Trigger File The net20gac.exe failed to execute. triggerFile. Ensure that the trigger User response: file exists and that your account Ensure that you have the permissions to add has sufficient permissions to assemblies to the Global Assembly Cache. update this file. BWMNT0112E The assyName assembly could not Explanation: be removed from the Global System failed to open the refresh.signal file. Assembly Cache. Ensure that you User response: are using an account with Ensure that the trigger file exists and that you have the sufficient permissions to remove permissions to update the file. assemblies from the Global Assembly Cache. BWMNT0108E Unable to read the .NET Tracking configuration file. Ensure that the Explanation: configuration file exists and that Windows failed to run the net20gac program. your account has sufficient User response: permissions to read this file. Ensure that you have the permissions to remove Explanation: assemblies from the GAC. System failed to read the BWMNT0113E The launch of enable_iisdc.cmd dotNetDcConfig.properties file. failed with a return value of: User response: retValue. Ensure that the Ensure that the configuration file exists and that you enable_iisdc.cmd file exists and have the permissions to read the file. that you are using an account with sufficient permissions. BWMNT0109E cliString failed to copy the properties file with a return value Explanation: of: retVal. Ensure that the Windows failed to execute the enable_iisdc.cmd properties file exists and that your file. account has sufficient permissions User response: to copy this file. Ensure that the enable_iisdc.cmd file exists and Explanation: that you have the permissions to execute the file. System failed to copy the BWMNT0114E The launch of dotNetDcConfig.properties file. disable_iisdc.cmd failed with a User response: return value of: retValue. Ensure Ensure that the properties file exists and that you have that the disable_iisdc.cmd file the permissions to copy the file. exists and you are using an account with sufficient BWMNT0110E The launch of configNETDC.bat permissions. failed with a return value of: retValue. Ensure that you are using Explanation: an account with sufficient Windows failed to execute the disable_iisdc.cmd permissions. file. Explanation: User response: The configNETDC.bat file failed to execute. Ensure that disable_iisdc.cmd file exists, and that you have permissions to execute the file. User response: Ensure that you have the permissions to update the BWMNT0115E The registerdc command failed. file. Please correct any errors and retry the command. BWMNT0111E The assyName assembly could not be installed into the Global Explanation: Assembly Cache. Ensure that you The registerdc command failed to execute. Some are using an account with portions of the processing might have completed. sufficient permissions to add User response: 18 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide Either execute the unregisterdc command to return BWMNT0120E Please restart the IIS for the to an unregistered .NET Data Collector state, or correct changes to take effect. To restart any errors and retry the registerdc command. IIS run 'iisreset' command. BWMNT0116E The unregisterdc command Explanation: failed. Please correct any errors The changes that you made in the configuration do not and retry the command. take effect unless you restart IIS. Explanation: User response: The unregisterdc command failed to execute. Some To restart IIS, go to Start > Run, and run the processes in the batch might have completed. iisreset command. User response: BWMNT0122E This command will only work for Either execute the registerdc command to return to IIS 6 on 64-bit machines. an registered .NET Data Collector state, or correct any errors and retry the unregisterdc command. Explanation: The 64-bit version of IIS 6 is a prerequisite for this BWMNT0117E The launch of command. enable_profilerEvents.cmd failed with a return value of: User response: retValue. Ensure that the Ensure that you have installed the 64-bit version of IIS enable_profilerEvents.cmd 6. file exists and that you are using BWMNT0124E .NET Data Collector will not be an account with sufficient configured. You have to configure permissions. it manually after installation. Explanation: Explanation: Windows failed to execute the The configuration of .NET Data Collector failed. When enable_profilerEvents.cmd file. you install the .NET Data Collector, the components of User response: the .NET Data Collector are not registered. Ensure that file enable_profilerEvents.cmd file User response: exists and that you have the permissions to execute You must manually register the required components the file. after installation. BWMNT0118E The launch of BWMNT0125E Please provide the valid disable_profilerEvents.cmd hostname. failed with a return value of: Explanation: retValue. Ensure that the Hostname should be in IPv4 format or a computer disable_profilerEvents.cmd name. file exists and you are using an account with sufficient User response: permissions. Provide a valid hostname. Explanation: BWMNT0127E Could not Configdc.exe. Windows failed to execute the Installation will continue with disable_profilerEvents.cmd file. default configuration. User response: Explanation: Ensure that the disable_profilerEvents.cmd file The system could not find the Configdc.exe file. exists and that you have the permissions to execute Installation will continue with the default the file. configuration. BWMNT0119E The build version is: buildlevel. User response: Explanation: None. Displays the internal build version. BWMNT0128E Please provide the valid Port User response: Number. Use the configDC getVersion command to get the Explanation: internal build version. The port number that you provided is invalid. User response: Provide a valid port number.

Chapter 6. .NET Data Collector messages: BWMNT* 19 BWMNT0137E Following invalid properties are BWMNT0138E .NET Data Collector will not work found in the properly if all the required dotNetDcConfig.properties.inactiv properties are not present in e configuration file. These dotNetDcConfig.properties file. properties will not be reflected in Explanation: dotNetDcConfig.properties file A property in the during activating the dotNetDcConfig.properties.inactive file configuration. should be in the key=value format. If a property is Explanation: not in the correct format, the property string is A property in the truncated. dotNetDcConfig.properties.inactive file User response: should be in the key=value format. If a property is Verify whether the properties and the values in the not in the correct format the property string is dotNetDcConfig.properties.inactive file are truncated. in correct format. You can use the Property Editor tool User response: to verify the accuracy of the Verify whether the properties and the values in the dotNetDcConfig.properties.inactive file. dotNetDcConfig.properties.inactive file are in correct format. You can use the Property Editor tool to verify the accuracy of the dotNetDcConfig.properties.inactive file.

20 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide Appendix A. ITCAM for Microsoft Applications documentation library

Various publications are relevant to the use of ITCAM for Microsoft Applications. For information about how to access and use the publications, see Using the publications (http:// www.ibm.com/support/knowledgecenter/SSTFXA_6.3.0.1/com.ibm.itm.doc_6.3/common/ using_publications.htm). To find publications from the previous version of a product, click Previous versions under the name of the product in the Contents pane. Documentation for this product is in the ITCAM for Microsoft Applications Knowledge Center (http:// www.ibm.com/support/knowledgecenter/SSDKXQ_6.3.1/com.ibm.itcamms.doc_6.3.1/ welcome_msapps631.html) • Quick Start Guides • Offering Guide • Download instructions • Links to Prerequisites • Installation and Configuration Guide for each agent • Link to Reference information for each agent • Link to Troubleshooting Guide for each agent Prerequisite publications To use the information about the agents effectively, you must have some prerequisite knowledge. See the following information the IBM Tivoli Monitoring Knowledge Center (http://www.ibm.com/ support/knowledgecenter/SSTFXA_6.3.0.2/com.ibm.itm.doc_6.3fp2/welcome.htm) to gain prerequisite knowledge: • IBM Tivoli Monitoring Administrator's Guide • IBM Tivoli Monitoring Installation and Setup Guide • IBM Tivoli Monitoring High Availability Guide for Distributed Systems • IBM Tivoli Monitoring: Installation and Configuration Guides for the following agents: Operating System agents and Warehouse agents • IBM Tivoli Monitoring: User's Guides for the following agents: Agentless OS monitors, Log file agent, System p agents, Systems Director base agent • IBM Tivoli Monitoring Agent Builder User's Guide • IBM Tivoli Monitoring Command Reference • IBM Tivoli Monitoring: Messages • IBM Tivoli Monitoring Troubleshooting Guide • IBM Tivoli Monitoring: References for the following agents: Operating System agents and Warehouse agents • IBM Tivoli Monitoring: Troubleshooting Guides for the following agents: Operating System agents and Warehouse agents • Tivoli Enterprise Portal User's Guide

© Copyright IBM Corp. 2012, 2020 21 Related publications The publications in related information centers provide useful information. See the following information centers, which you can find by accessing Tivoli Documentation Central (https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/Tivoli %20Documentation%20Central): • Tivoli Monitoring • Tivoli Application Dependency Discovery Manager • Tivoli Business Service Manager • Tivoli Common Reporting • Tivoli Enterprise Console® • Tivoli Netcool/OMNIbus Tivoli Monitoring Community on Service Management Connect Service Management Connect (SMC) is a repository of technical information that is organized by communities. Access Service Management Connect at https://www.ibm.com/developerworks/servicemanagement. For information about Tivoli products, see the Application Performance Management community (http:// www.ibm.com/developerworks/servicemanagement/apm/index.html). Connect, learn, and share with Service Management professionals. Get access to developers and product support technical experts who provide their perspectives and expertise. You can use SMC for these purposes: • Become involved with transparent development, an ongoing, open engagement between other users and IBM developers of Tivoli products. You can access early designs, sprint demonstrations, product roadmaps, and prerelease code. • Connect one-on-one with the experts to collaborate and network about Tivoli and the (enter your community name here) community. • Read blogs to benefit from the expertise and experience of others. • Use wikis and forums to collaborate with the broader user community. Other sources of documentation You can obtain additional technical documentation about monitoring products from other sources. See the following sources of technical documentation about monitoring products: • IBM Integrated Service Management Library (http://www.ibm.com/software/brandcatalog/ismlibrary/) is an online catalog that contains integration documentation as well as other downloadable product extensions. • IBM Redbook publications (http://www.redbooks.ibm.com/) include Redbooks® publications, Redpapers, and Redbooks technotes that provide information about products from platform and solution perspectives. • Technotes (http://www.ibm.com/support/entry/portal/software), which are found through the IBM Software Support website, provide the latest information about known product limitations and workarounds.

22 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide Notices

This information was developed for products and services offered in the US. This material might be available from IBM in other languages. However, you may be required to own a copy of the product or product version in that language in order to access it. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive, MD-NC119 Armonk, NY 10504-1785 US For license inquiries regarding double-byte character set (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd. 19-21, Nihonbashi-Hakozakicho, Chuo-ku Tokyo 103-8510, Japan INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some jurisdictions do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any without notice. Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk. IBM may use or distribute any of the information you provide in any way it believes appropriate without incurring any obligation to you. Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Director of Licensing IBM Corporation North Castle Drive, MD-NC119 Armonk, NY 10504-1785 US

© Copyright IBM Corp. 2012, 2020 23 Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. The performance data discussed herein is presented as derived under specific operating conditions. Actual results may vary. Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non- IBMproducts. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products. Statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. This information is for planning purposes only. The information herein is subject to change before the products described become available. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to actual or business enterprises is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrate programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. The sample programs are provided "AS IS", without warranty of any kind. IBM shall not be liable for any damages arising out of your use of the sample programs. Each copy or any portion of these sample programs or any derivative work must include a copyright notice as follows: © (your company name) (year). Portions of this code are derived from IBM Corp. Sample Programs. © Copyright IBM Corp. 2012, 2016. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. Linux® is a trademark of Linus Torvalds in the United States, other countries, or both. Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries.

24 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide Java™ and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. Terms and conditions for product documentation Permissions for the use of these publications are granted subject to the following terms and conditions.

Applicability These terms and conditions are in addition to any terms of use for the IBM website.

Personal use You may reproduce these publications for your personal, noncommercial use provided that all proprietary notices are preserved. You may not distribute, display or make derivative work of these publications, or any portion thereof, without the express consent of IBM.

Commercial use You may reproduce, distribute and display these publications solely within your enterprise provided that all proprietary notices are preserved. You may not make derivative works of these publications, or reproduce, distribute or display these publications or any portion thereof outside your enterprise, without the express consent of IBM.

Rights Except as expressly granted in this permission, no other permissions, licenses or rights are granted, either express or implied, to the publications or any information, data, software or other intellectual property contained therein. IBM reserves the right to withdraw the permissions granted herein whenever, in its discretion, the use of the publications is detrimental to its interest or, as determined by IBM, the above instructions are not being properly followed. You may not download, export or re-export this information except in full compliance with all applicable laws and regulations, including all United States export laws and regulations. IBM MAKES NO GUARANTEE ABOUT THE CONTENT OF THESE PUBLICATIONS. THE PUBLICATIONS ARE PROVIDED "AS-IS" AND WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, NON-INFRINGEMENT, AND FITNESS FOR A PARTICULAR PURPOSE. IBM Online Privacy Statement IBM Software products, including software as a service solutions, ("Software Offerings") may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering's use of cookies is set forth in the following paragraphs. Depending upon the configurations deployed, this Software Offering may use session cookies that collect each user's user name for purposes of session management, authentication, and single sign-on configuration. These cookies can be disabled, but disabling them will also likely eliminate the functionality they enable. If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek

Notices 25 your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent. For more information about the use of various technologies, including cookies, for these purposes, See IBM's Privacy Policy at http://www.ibm.com/privacy and IBM's Online Privacy Statement at http:// www.ibm.com/privacy/details the section entitled "Cookies, Web Beacons and Other Technologies" and the "IBM Software Products and Software-as-a-Service Privacy Statement" at http://www.ibm.com/ software/info/product-privacy.

26 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide Index

A SMC, See Service Management Connect Application Performance Management community on SMC 22 T Technotes 22 D troubleshooting ITCAM for Microsoft Applications documentation, See publications NET Data Collector configuration 3 Troubleshooting NET Data Collector 1 I NET Data Collector configuration 1, 7 IBM Tivoli Composite Application Manager for Microsoft NET Data Collector event logging 1 Applications NET Data Collector monitoring 3–6 NET Data Collector messages 17 NET Data Collector SVC node disconnected 2 Integrated Service Management Library documentation 22 NET Data Collector transaction topology 2 ITCAM for Microsoft Applications NET Data Collector uninstallation 2 troubleshooting NET Data Collector upgradation 2 NET Data Collector configuration 3 Problems and workarounds 1

M W messages wikis 22 NET Data Collector 17

N NET Data Collector messages 17 Problems and workarounds 1 troubleshooting 1 Troubleshooting 1–7

P prerequisite publications 21 publications IBM Tivoli Monitoring 21 Integrated Service Management Library 22 prerequisite 21 Redbooks 22 related 22 Service Management Connect 22 SMC, See Service Management Connect Technotes 22 wikis 22

R Redbooks 22

S Selective Filtering messages 13 Service Management Connect 22

Index 27 28 IBM Tivoli Composite Application Manager for Microsoft Applications: .NET Data Collector: .NET Data Collector: Troubleshooting Guide

IBM®