NET Data Collector 7.3.2 Fix Pack 6
Total Page:16
File Type:pdf, Size:1020Kb
IBM Tivoli Composite Application Manager for Microsoft Applications: .NET 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 type................................. 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 format 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 Server 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 more .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 help 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