Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Relational algebra wikipedia , lookup
Entity–attribute–value model wikipedia , lookup
Microsoft Access wikipedia , lookup
Extensible Storage Engine wikipedia , lookup
Microsoft Jet Database Engine wikipedia , lookup
Clusterpoint wikipedia , lookup
Database model wikipedia , lookup
Team Foundation Server wikipedia , lookup
Open Database Connectivity wikipedia , lookup
Copyright International Business Machines Corporation 2016. All rights reserved. Component: IBM® Tivoli® Composite Application Manager for Microsoft® Applications: Version 6.3.1.8 Fix Pack: 0008 Component ID: 5724-U17 Date: Jan 22, 2016 1.0 General description This fix contains the APARs and defects that are specified in the "Problems fixed" section. This fix also includes the enhancements that are made in the V6.3.1.8 release of ITCAM for Microsoft Applications product. 2.0 Problems fixed The following problems are addressed by this fix. 2.1 APARs For the SQL Server agent: APAR: IV79444 Abstract: Server name is blank when the event for inactive server status is generated. Additional Information: Server name was not filled when a SQL Server Instance was Inactive. This event when generated gives a blank server name. This issue is with reference to PMR 22431, 004,000: MS SQL agent EIF missing server. For the Active Directory agent: APAR: IV72817 Abstract: Agent Shows wrong value for “DCA PDC Master ","DCA RID Controller Availability “attribute group Additional Information: Agent shows wrong value for "DCA PDC Master","DCA RID Master" and "DCA Infrastructure Master" attributes of "Domain Controller Availability" attribute group, when DNS name and NetBIOS name of Domain Controller machine are different. APAR: IV52452 Abstract: Domain Name of the host machine is not fetched by AD Agent. Additional Information: Agent is not able to fetch the domain name of the host machine because getaddrinfo API gives incorrect canonical name of host machine. APAR: IV52672 Abstract: Agent shows incorrect data for DNS ADIntegrated attribute group. Additional Information: Some SRV records (for Read only Domain Controller) which are specific to sites get added under sites not in the default location in DNS Manager. Hence agent fails to verify the SRV records of sites and incorrect data displays for some of the attribute of DNS ADIntegrated attribute group on TEP. APAR: IV53500 Abstract: Agent Shows wrong count of Global Catalog Servers in a Domain. Additional Information: Agent Shows wrong count of Global Catalog Servers in a Domain for Domain controller availability attribute group. Agent does not consider the RODC with GC configured as Global Catalog Server. APAR: IV60416 Abstract: Agent shows wrong data of "DRA INTERSITE PARTNER COUNT" attribute Additional Information: Microsoft Active Directory Agent shows wrong data of "DRA InterSite Partner Count" attribute. The Microsoft Active Directory Agent displays correct data initially, but sometimes it shows the incorrect value. APAR: IV74419 Abstract: Active Directory 64-bit Agent does not connect to Tivoli Enterprise Monitoring Server (TEMS) using IPSPIPE. Additional Information: Due to incorrect value of PATH environment Variable, Active Directory 64-bit Agent does not connect to Tivoli Enterprise Monitoring Server (TEMS) using IPSPIPE. For the Exchange Server agent: APAR: IV73298 Abstract: Microsoft Exchange Server Agent fails to fetch the data for Email Statistics attribute group. Additional Information: Microsoft Exchange Server Agent fails to fetch the data for Email Statistics attribute group when monitored server name has maximum allowed NETBIOS name. APAR: IV73296 Abstract: Microsoft Exchange server agent shows wrong data for "MS Exchange Reachability" attribute group. Additional Information: "MS Exchange Reachability" attribute group shows wrong data when user name having white spaces provided in the agent configuration panel. APAR: IV75572 Abstract: Microsoft Exchange Server Agent Guide shows incorrect configuration parameters' name in ‘Remote installation and configuration’ section. Additional Information: Microsoft Exchange Server Agent Guide shows incorrect name of below configuration parameters in ‘Remote installation and configuration’ section. 1. Existing Name: EXCHSETTINGS.exch_event_interval Correct Name: EXCHSETTINGS.exchange_event_interval 2. Existing Name: EXCHSETTINGS.exch_event_count Correct Name: EXCHSETTINGS.exchange_event_count For the IIS agent: APAR: IV76536 Abstract: IBM Tivoli Monitoring IIS Agent uses high CPU. Additional Information: With this patch we have restricted IIS agent from consuming high CPU. This APAR was delivered for ITCAMMA IIS agent V6.3.1.2. Now we have integrated this APAR in current release ITCAMMA IIS agent V6.3.1.8. For the Lync Server agent: Customer Requirement: 86423 Abstract: Nordea: MS Lync Agent (v8). Additional Information: Provided additional metrics and synthetic monitoring for the Lync infrastructure. 2.2 Defects For the SQL Server agent: Defect: 132699 Abstract: MSSQLDEV: Newly added attributes in 6312 release are visible on Table information and Additional Database Details workspaces with older versions of agent. Additional Information: When agent of version lower than 6312 was pointed to the ITM with support 6312 or higher, the Table information and Additional Database Details workspaces were showing newly added attributes in 6312 release on portal. Defect: 133141 Abstract: MSSQLDEV: Resource Pool Statistics Attribute group showing wrong values on portal Additional Information: Because of wrong calculation and wrong perfmon counter names, some of the attributes in Resource Pool Statistics attribute group were showing incorrect data on portal. Defect: 133142 Abstract: MSSQLDEV: Workload Group Statistics Attribute Group is showing wrong value on portal. Additional Information: Because of wrong calculation and wrong perfmon counter names, some of the attributes in Workload Group Statistics attribute group were showing incorrect data on portal. Defect: 132611 Abstract: MSSQLDEV: KOQTBLD Query failure while removing deleted tables from global map causing high memory. Additional Information: After failure of one of the query which gets the list of deleted tables, collector didn’t remove the deleted tables from global map and at the same time new tables entries were added to this map in every new interval. This was leading to high memory usage. To fix this made following changes: o When query used for finding deleted tables fails, delete all entries present in global map and collect complete data for KOQTBLD once again in global map. o In old algorithm, query execution was marked as failed when query returns more than 10,000 rows. Now this behavior is changed for all the queries used in KOQTBLD. If any of the queries used in KOQTBLD returns more than 10,000 rows then query will not fail. All the rows returned by query are considered for processing. o In old algorithm, first 10,000 rows collected for KOQTBLD were sent to portal without any sorting. This behavior is changed now. Now the row returned for KOQTBLD will be sorted based on environmental variable "COLL_TBLD_SORTBY". Possible value for this variable are as below: "frag" - Sort according "fragmentation percent" value in descending order "space" - Sort according "Space used" value in descending order "optsage" - Sort according "Optimizer Statistics Age" in descending order "rows" - Sort according "Number of Rows" in descending order If user does not specify any of these values or gives any wrong value for "COLL_TBLD_SORTBY", then by default sorting will be based on "fragmentation percent" Defect: 134274 Abstract: The agent and collector processes are not terminated and the data remains visible on the portal when an instance is removed from MTEMS configuration panel Additional Information: After un-configuring agent from MTEMS window, agent and collector services were not getting stopped and removed. Defect: 135345 Abstract: SVTMSOQ: Table details attribute group data is not updated successfully in case of database detach, attach scenario. Additional Information: Reattached tables were not getting listed on portal. For the .NET Data Collector: 1. Defect: 134740 Abstract: .NET DC makes WCF extensions entries in “machine.config” files even if WCF is unregistered using ServiceModelReg.exe utility. Additional Information: WCF component of a .NET Framework can be removed by using servicemodelreg.exe. This change cannot be detected by .NET Data Collector during configuration and it makes WCF related entries in machine.config file, making them anomalies for .NET Framework. 2. Defect: 134739 Abstract: DEVNETDC7323: Component name contains space for Microsoft.NET. Additional Information: When an event has component name Microsoft.NET, it contains a space between the two words. 2.3 Enhancements For the SQL Server agent: 1. Added support for Unicode characters so that SQL server with different collations can be monitored. 2. RFE 61001: MSSQL Agent - delivering wrong database status. Changed the source of server status so that sql agent can report accurate SQL server status and Database status in all the conditions. Changes have been made to fetch status of SQL server using WMI queries. 3. Jar files are signed with refreshed certificate. 4. Done some improvements in configuration panel window as mentioned below : Made "Windows Authentication" and "Support Long Live Connection" options true by default. Disabled "Login" and "Password" text boxes when "Windows Authentication" is selected. Made "Login" and "Password" fields mandatory when "Windows Authentication" is not selected. Made "Home Directory" , "Error Log File" , "Database Version" text boxes read-only when agent has found these settings successfully. Made ”Server Name” text box read only while configuring/reconfiguring the instance. Made functional behavior of all the buttons and list boxes present on configuration panel window identical. 5. Newly added attributes : a. The newly included attributes in SAAS release are included in ITM release: o In MS SQL Database Summary attribute group: Total Databases Critical: The total number of databases that are in critical state. The database is in critical state, if (lPctLogUsed is greater than 90) or (lPctDBUsed is greater than 90) or (dbStatus is equal to 1) or (dbState is equal to offline) or (dbState is equal to emergency) or (dbErrStatus is equal to yes) or (oldOpenTran is greater than 15) Total Databases Warning: The total number of databases that are in warning state. The database is in warning state, if (lPctLogUsed is greater than 70 and less than equal to 90) or (lPctDBUsed is greater than 70 and less than equal to 90) or (dbState is not equal to offline, online, and emergency) or (oldOpenTran is 6 – 15) o In MS SQL Job Summary attribute group : Jobs Executed Current Interval: The number of processed jobs in the current sampling interval. o Warning Jobs Current Interval: The number jobs that are cancelled or in unknown state in the current sampling interval. In MS SQL Server Properties attribute group : Instance Path: The installation path of the SQL server instance. Instance Port: The TCP/IP port number of the SQL server instance. b. Added one attribute in MS SQL Database Details attribute group so that mirroring role of each database can be monitored. Mirroring Role: The mirroring role of the database (mirror or principal). If database is not mirrored then value for this attribute will be Not Applicable. And for not accessible database this attribute will show value as Not Collected. For the Exchange Server agent: 1. APMUI77IF02 support: With MS Exchange Agent v6312IF01 agent, APMUI77IF02 (and onwards) will display only mandatory and configured services in Exchange APMUI dashboard. 2. Added following new attribute groups : i. MS Exchange Top Ten Senders: This data set provides information about top ten email senders. ii. MS Exchange Top Ten Receivers: This data set provides information about top ten email receivers. iii. MS Exchange Top Ten Largest Emails: This data set provides information about top ten largest emails. For the SharePoint Server Agent 1. Added detail information about web application through below attribute groups and workspace Web Application Details. Web Service Health Bucket Service Application Details The workspace “Web Application Details” is viewed by using a crosslink (web application name) from the workspace “SharePoint configuration”. For the .NET Data Collector 1. Added Support for URL based filtering of KD4SOAPHeaderV2. The web services present at such URLs will not be injected with .NET Data Collector’s SOAP header. 2. Added support for Silent and remote installation of .NET Data Collector. For the Active Directory Server Agent 1. Added support for DBCS character encoding. 2. RFE: 61487 Abstract: Timestamp comparison for "RPL Partner Last Success Time" and "RPL Partner Last Attempt Time" attribute in situation formula. Additional Information: Timestamp datatype is added for "RPL Partner Last Success Time" and "RPL Partner Last Attempt Time" attribute. Now timestamp comparison can be done in the situation formula for these attributes. For the Lync Server agent: 6. Added support for Lync Topology and Synthetic Transactions 7. Added support for the Edge Server, Mediation Server, Video Integration Server, and SQL Server 8. Added configuration panel 9. Added an enterprise level workspace for Synthetic Transactions 10. Added new attribute groups for the following roles of the Lync Server: Front- end Server Outlook web access (OWA) Web Conferencing Server Audio Video Conferencing Server 2.4 Superseded fixes 6.3.1-TIV-ITM_MSAPP-FP0002 2.5 APARs and defects included from superseded fixes 2.5.1 APARs For the SQL Server agent: APAR: IV54729 Abstract: Wrong Job Execution Duration. Additional Information: The SQL Server agent calculates incorrect value for the job execution duration as original value+3600 (1 hour of daylight saving in seconds). This problem occurs because of daylight saving. APAR: IV71563 Abstract: Collector crashing in Workload Group Statistics (KOQWGLS) and Resource Pool Statistics (KOQRPOOL) attribute groups. Additional Information: Fixed size container was used to store values of performance counter and instance names, the size of container was insufficient if maximum number of instances were created for 'SQL Server: Workload Group Stats' or 'SQL Server: Resource Pool Stats' perfmon counter object. APAR: IV71520 Abstract: Collector is crashing in Table Detail attribute group as query is failing for negative table id. Additional Information: Negative table ids were generated for tempdb database. This negative table id resulted in failure of query, this query failure was not handled properly which resulted in crash. APAR: IV70417 Abstract: Select query from 'Log Shipping Job Detail' attribute group is causing severe delay on SQL Agent jobs Additional Information: The problematic query was used to find job name from msdb.Sysjobhistory table by searching for the agent ID in the message column of Sysjobhistory. It was taking more time because msdb..sysjobhistory table was having millions of rows. APAR: IV69383 Abstract: Unable to trigger situation on attribute ‘Long Running Transactions Time (sec)’ of Database detail attribute group. Additional Information: Data type of this attribute in dockoq file was float. And every time the actual value of this attribute was getting divided by 100 while sending to portal that is why situation was not getting triggered. For the Active Directory agent: APAR: IV59165 Abstract: Agent shows wrong data of ADDB Percentage Free Disk Space for Log Files attribute. Additional Information: On the Tivoli Enterprise Portal incorrect values are displayed for the ADDB Percentage Free Disk Space for Log Files attribute, when the Active Directory database and logs are on different drives. For the Exchange Server agent: APAR: IV55905 Abstract: Exchange agent does not provide data for Event logs attribute group. Additional Information: The Exchange Server agent fails to retrieve data for the Event Logs attribute group, when the installation paths of the exchange services event sources are in different case(upper or lower). APAR: IV56602 Abstract: Exchange agent executes PowerShell command to get public folder details even if Public folders are not present. Additional Information: The Exchange Server agent runs the PowerShell command to get the public folder details even if public folders are not present. This results in generation of events in the events viewer. APAR: IV53603 Abstract: Exchange agent shows incorrect validation message during agent configuration. Additional Information: The Exchange Server agent shows incorrect validation message when it verifies the configured user rights. This issue is observed when the Microsoft Exchange Security Group organization unit is moved from its default location to some other container in the Active Directory. APAR: IV59380 Abstract: Microsoft Exchange Server Agent 6.3.1.1 consumes High CPU. Additional Information: The processor usage of the Exchange Server agent is high. 2.5.2 Defects For the SQL Server agent: Defect: 107312 Abstract: The collector process fails. Additional Information: When you run the collector.exe file with multiple database connections, the collector process fails. Defect: 100387 Abstract: The koqcoll utility fails. Additional Information: The koqcoll utililty fails when more than 10000 tables are created. Defect: 107629 Abstract: A single instance name shows twice in the SQL Server Configuration window. Additional Information: The MSSQL instance name is displayed twice in the SQL Server Configuration window. Defect: 123732 Abstract: Attribute Names and Data populated in it are mismatched for first collection when a custom query is assigned to the attribute group 'Filegroup Details' Additional Information: Issue was in the Filegroup Detail Workspace. So, changed the koq_pres.sql for Filegroup Detail attribute group Defect: 123739 Abstract: 'Total Devices' attribute shows incorrect value for database having file stream devices in 'Database Details' attribute group Additional Information: Filestream files were not considered while calculating freespace related attribute values in Database Details attribute group. Defect: 124586 Abstract: Collector crashing when instance of Object 'SQL Server: Locks' is returning no perfmon data. Additional Information: When instances of object 'SQL Server: Locks' returned no Performance Data (NULL) things were not handled correctly. Defect: 124593 Abstract: Issues found in table details attribute group data collection. Additional Information: Fixed following problems for 'Table Details': Renamed databases were not reflected in workspace. Newly imported tables were not visible in workspace Attribute group was not updated properly with Memory optimized tables. When SQL server was configured with case sensitive collation, data was not getting collected. Defect: 124594 Abstract: Collector is crashing when SQL server perfmon counters are not loaded. Additional Information: SQL server perfmon counters are used as data source for some of the attribute groups in agent. When these counters were not loaded, collector process was crashing. Defect: 124596 Abstract: Database deletion from back end causing collector crash. Additional Information: While database details attribute group data collection was in progress, if someone deleted database from back end, this could result in collector crash. Defect: 125046 Abstract: Collector crash occurs when SQL query fails. Additional Information: Collector crash could occur when TSQL query used for fetching data of attribute group failed. Defect: 125210 Abstract: Collector crash observed in case of SQL server connection error. Additional Information: Collector crash was observed if connection with SQL server terminated while fetching data from SQL Server. Ported APAR IV62810 Defect: 125211 Abstract: Collector process is getting crashed while fetching job details attribute group. Additional Information: collector crash occurred for job details attribute group when insufficient parameters were passed to the function. Defect: 125212 Abstract: Collector crash occurs while fetching data for server summary attribute group. Additional Information: collector crash occurred for server summary when insufficient parameters were passed to the function. Defect: 122998 Abstract: Issues while executing multiline customized SQL query. Additional Information: Execution of multiline customized SQL query fails when there is no space at end of each line or if query contains line comments. 2.5.3 Enhancements Enhancements in the SQL Server agent: 1. Added tolerance mode support for SQL Server 2014. 2. Added the following new attributes for monitoring the In-Memory OLTP feature of SQL Server 2014: a. Durability and Memory Optimized attributes in the Table Detail attribute group b. Transaction Isolation Level of Memory Optimized Tables attribute in the Additional Database Detail Attribute group 3. A new enumeration value is added for SQL Server 2014 in the Fragmentation attribute of the MS SQL Table Detail attribute group. 4. RFE: 59520: Support database of size more than 2.1 TB. Enhancements in the Lync Server agent: Added support to monitor the existing attributes on the Windows Server 2012 R2 operating system. Enhancements in the .NET Data Collector: 1. Added support to monitor .NET Framework 4.5.1. 2. Added support for the Windows Server 2012 R2 operating system. 3. Added support for the IIS V8.5. Enhancements in the Exchange Server agent: 1. Added support to monitor the existing attributes on Exchange Server 2013 SP1and its corresponding Exchange Server roles. 2. Added support for the Windows Server 2012 R2 operating system. Enhancements in the Tivoli Common Reporting (TCR): There are no enhancements in this section. For more information about Tivoli Common Reporting, see the "Tivoli Common Reporting for the monitoring agent" chapter in the agent reference guides at the following location on the SMC wiki: (https://www.ibm.com/developerworks/community/groups/service/ht ml/ communityview?communityUuid=0587adbc-8477-431f-8c689226adea11ed#fullpageWidgetId=W42ce7c6afdb9_42c2_a9ea_e1ba3 10bea8c) 3.0 Architecture and prerequisites For information about system requirements, go to the software product compatibility reports website, and search for the ITCAM for Microsoft Applications product: (http://publib.boulder.ibm.com/infocenter/prodguid/v1r0/clarity/index.html). 3.1 Prerequisites for this fix The minimum required version of IBM Tivoli Monitoring is V6.2.3, Fix Pack 3. 4.0 Image directory contents The following folder structure of the image is created: - WINDOWS folder This folder contains the binary files for installing the 32-bit and 64-bit agents. The folder also contains the Prereqchecker utility in the prereqchecker folder for the following agents: - Microsoft Active Directory agent - Microsoft BizTalk Server agent - Microsoft Cluster Server agent - Microsoft Exchange Server agent - Microsoft Hyper-V Server agent - Microsoft Internet Information Services agent - Microsoft .NET Framework agent - Microsoft SharePoint Server agent - Microsoft SQL Server agent - Microsoft Host Integration Server agent - Microsoft Lync Server agent - .NET Data Collector - Application LaunchPad and Discovery and Deployment support files - Network Devices agent - REPORTS folder This folder contains subdirectories that include the .zip files of the agents. The subdirectories are named according to the "K<agent code>" format. The .zip files contain Cognos data models and reports. - unix folder This folder contains the non-Windows agent support files for the Tivoli Enterprise Monitoring Server, Tivoli Enterprise Portal Server, Tivoli Enterprise Desktop client, and Tivoli Enterprise Browser client. The folder contains the agent support files for the 32-bit and 64-bit agents. 5.0 Installation instructions See the following publications for complete information: - IBM Tivoli Monitoring Installation and Setup Guide - Installation and configuration guides of agents. You can view the Installation and Configuration guides at the ITCAM for Microsoft Applications V6.3.1 Information Center (http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/ com.ibm.itcamms.doc_6.3.1/welcome_msapps631.html). 6.0 Additional installation information 6.1 Installation instructions for agent baroc file For information about installation and configuration of the baroc files, see "Setting up event forwarding to Tivoli Enterprise Portal" in the IBM Tivoli Monitoring Installation and Setup Guide. 6.2 Verifying the update 1. To verify whether the agent is updated correctly, use the tacmd command to view the current version of the agent after the agent is restarted. Ensure that you log on to the Tivoli Enterprise Monitoring Server before you view the agent version. For example, On UNIX systems, where $CANDLEHOME is the IBM Tivoli Monitoring installation directory, the default location is /opt/IBM/ITM. > $CANDLEHOME/bin/tacmd login -s <server> -u <itmuser> -p <password> > $CANDLEHOME/bin/tacmd listSystems -t OQ On Windows systems, where %CANDLE_HOME% is the IBM Tivoli Monitoring installation directory, the default location is C:\IBM\ITM. > %CANDLE_HOME%\bin\tacmd login -s <server> -u <itmuser> -p <password> > %CANDLE_HOME%\bin\tacmd listSystems -t OQ Note: The component (-t) for the tacmd listSystems command is specified as two characters (OQ), not three characters (KOQ). When the agent is updated, the agent version is changed to 06.03.01.08. After the agent is restarted, you can also use the GUI to verify whether the agent was updated. For the agent on Windows systems, the version number is 06.03.01.08. 2. To verify whether the agent support files are updated correctly, use the kincinfo command on Windows systems or the cinfo command on Linux or UNIX systems. On UNIX or Linux systems: To validate that all components have been installed, run the following command: $CANDLEHOME/bin/cinfo -i On Windows systems: To validate that all components have been installed, run the following command: %CANDLE_HOME%\bin\kincinfo –i 7.0 Known problems and workarounds For the Hyper-V Server agent: Abstract: The agent support files on the Tivoli Enterprise Portal cannot be upgraded to V6.3.1 Fix Pack 8 by using the self-describing agent feature. Problem: The self-describing agent feature for the Tivoli Enterprise Portal Server is enabled. When the Microsoft Hyper-V Server agent support files for the Tivoli Enterprise Portal Server are upgraded to V 6.3.1, Fix Pack 8, the support files are not automatically upgraded to V 6.3.1, Fix Pack 8. Workaround: Upgrade the Hyper-V Server agent support files for the Tivoli Enterprise Portal Server manually to V6.3.1, Fix Pack 8. For the BizTalk Server agent: Abstract: When you click cross-links in the views of the Databases workspace of the BizTalk Server agent, the target workspaces of the SQL Server agent do not open. Problem: The Databases workspace of the BizTalk Server agent contains the “Databases Information” and "Log and Space Information" cross-links in the following views: - Management Database - MessageBox Database - Rule Engine Database - BAM Database - Tracking Database - Single Sign On Database When you click the "Databases" and "Log and Space Information" cross-links in these views, the target workspaces of the SQL Server agent do not open. Workaround: Select the target workspaces manually. For the Exchange Server agent: Abstract: On the Tivoli Enterprise Portal, the status for the two situations is displayed as "problem”. Problem: The Tivoli Enterprise Portal shows the status as problem due to the incorrect formula that is specified in the Manage Situations window for the following situations: - EX_Replication_Failed_Warn - EX_Replication_Suspended_Warn Workaround: Modify the formula or create a custom situation with the correct formula. The correct formula is as follows: For the EX_Replication_Failed_Warn situation: Replication_Failed EQ Yes For the EX_Replication_Suspended_Warn situation: Replication_Suspended EQ Yes For the .NET Data Collector: All the limitations that are mentioned in the Problems and workarounds chapter in the .NET Data Collector Troubleshooting Guide V7.3.2 are still applicable. In addition to these problems and workarounds, the following problems and workarounds are applicable: Abstract: When only .NET Framework 4.0 is installed on a server that runs on a 64-bit operating system, an error that is related to the ttapi.dll is generated. Problem: If the ISAPI or HTTPModule components of the .NET Data Collector are enabled and the .NET Framework 4.0 is installed on a server that runs on a 64-bit operating system, error messages are generated while processing a web request. 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)" Workaround: Install the Microsoft Visual C++ 2005 Service Pack 1 Redistributable package (x64) on the computer where the .NET Data Collector is installed. You can download this package from the following web address: http://www.microsoft.com/en-us/download/details.aspx?id=18471 Abstract: When the WCF service is being processed, the application name is displayed as w3wp and the component name is displayed as Microsoft.NET in the Transactions workspace of the Transaction Reporter agent on the Tivoli Enterprise Portal. Problem: This problem occurs when a WCF service is processed for which ASP.NET impersonation is not enabled. Workaround: Enable ASP.NET impersonation for the service that is being processed. Abstract: When a one way web service is being processed, an asynchronous arrow from the client is displayed in the Transaction topology from where this method was initiated. In the Transactions workspace, the application name of the web service is displayed as .asmx. Problem: One way web services are called asynchronous and the user does not wait for a response from the server. As all the interception points of the SOAP component of the.NET data Collector are not called, the asynchronous arrow is seen in the Transaction topology. Workaround: None. Abstract: If a SOAP request is sent from a client computer where the .NET Data Collector is not installed, to a server where the .NET Data Collector is installed, the web service node is displayed as .asmx or .svc in the Transaction topology. Problem: If all interception points for the SOAP component of the .Net Data Collector are not called, the web service nodes are displayed as .asmx or .svc. If the .NET Data Collector KD4 logging is enabled, the following message is seen in the logs: object reference not set to an instance of an object Workaround: None. Abstract: Visual Studio 2008 runtime environment should 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. Problem: When you unregister the .NET Data Collector, the .dll files of the Microsoft Visual C++ 2008 redistributable package are required. Workaround: Install the Microsoft Visual C++ 2008 Service Pack 1 Redistributable package. For a 32-bit operating system, use the following web address to download the Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (x86): http://www.microsoft.com/en-us/download/details.aspx?id=5582 For a 64-bit operating system, use the following web address to download the Microsoft Visual C++ 2008 Service Pack 1 Redistributable Package (x64): http://www.microsoft.com/en-us/download/details.aspx?id=2092 Abstract: When the database calls are made by using ODBC, the component name is shown as Microsoft.NET in the Transactions workspace of the Transaction Reporter agent. Problem: This problem occurs due to aggregation of ODBC events. Workaround: Disable the ADO Event Aggregation by completing the following steps: 1. Open the dotNetDcConfig.properties.inactive file. 3. Change the value of the ktj_ADOAggregation.Enabled property to false, as shown: ktj_ADOAggregation.Enabled=false. 4. Open the command prompt and browse to the bin directory of .NET Data Collector. 5. Run the configdc activateconfig command. 6. Restart all the .NET applications. Abstract: When database calls are made from a stand-alone client, ADO.NET nodes are not generated. Problem: This problem occurs when ADO Event Aggregation is enabled in the properties file. When a database call is made from a stand-alone client, the instance at which the user closes the application is not known to the .NET Data Collector because of which the ADO events are not aggregated. Workaround: 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, as shown: 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. Abstract: After remote or silent installation, .NET Data Collector needs to be configured manually by going to a particular installed instance. Problem: .NET Data Collector is configured using its own utilities either by using “configdc” or by UI tool “KK4ConfigProperties.exe” present at “<CANDLE_HOME>\ k4\bin\PropertiesEditor”. In the ITM architecture there is no way provided to provide inputs to these configuration utilities remotely unlike any other agent using tacmd or TEP GUI. Workaround: Currently there is no work around for this problem. User has to manually configure the .NET Data Collector using either by “configdc” through command line or “KK4ConfigProperties.exe UI”. For the Lync Server agent: Abstract: Task Scheduler behavior at Daylight Saving Time transitions and other events. Problem: The behavior of the Microsoft Task Scheduler is not specified for tasks that are scheduled to run during the transition hours of the Daylight Saving Time. Other events can also affect the actual time at which a scheduled task runs. Workaround: There is no work around for this problem. It is a Microsoft limitation. For more information, refer the following link: https://support.microsoft.com/en-us/kb/325413 For Tivoli Common Reporting (TCR): There are no changes hence the agent package version is still 631FP2 8.0 Additional product information For the Active Directory agent: To run the agent as a non-administrator user, provide the following permissions to the user: - Read access to the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\ NTDS\Parameters directory - Read access to the C:\Windows\NTDS directory - Full access to the HKEY_LOCAL_MACHINE\SOFTWARE\Candle directory When you run the agent as a non-administrator user, the following attribute groups display incorrect data: - Active Directory Database Information - Moved or Deleted Organizational Unit - Password Setting Objects - Containers - LDAP Attributes To run a Take Aaction command, run the Active Directory agent as an administrator user. For the Hyper-V Server agent: The following attribute groups are not supported on the windows server 2012 R2 operating system: - Hyper V Virtual Machine Summary - Hyper V Task Manager Detail - Hyper V Task Manager Recent Time - Hyper V VM Association with Virtual Network - Hyper V Legacy Network Adapter The HV_VMMigrate_Info situation is not supported on the windows server 2012 R2 operating system. For the Lync Server agent: Partially supports archiving, monitoring, and CDR roles of the Lync Server for version 2013 and Skype for Business 2015 Does not support remote monitoring of the SQL RTC buffer manager To get data in the Lync Topology workspace, run the agent as a domain administrator, and change the agent startup from automatic to manual. For the configuration settings for the Synthetic Transaction, if a weekly scheduling frequency is set, then the scheduler will run on every Monday at the time that is configured by the user. If a monthly scheduling frequency is set, then the scheduler will run on the first day of every month at the time that is configured by the user. Configuration panel does not validate any parameters. The user must follow the guidelines that are mentioned at every field and enter the data in the correct format. For additional technical resources, see the following web addresses: - IBM Tivoli Monitoring Information Center: http://pic.dhe.ibm.com/infocenter/tivihelp/v61r1/topic/com.ibm.i tm.doc_6.3fp2/welcome.htm - Tivoli Composite Application Manager for Microsoft Applications Information Center: http://publib.boulder.ibm.com/infocenter/tivihelp/v24r1/topic/co m.ibm.itcamms.doc_6.3.1/welcome_msapps631.html - Tivoli Composite Application Manager for Microsoft Applications website: http://www.ibm.com/software/tivoli/products/monitoringmicrosoft-applications/ 9.0 Copyright and trademark information A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml. 10.0 Notices {Add or remove non-IBM trademark names as appropriate. Mark the first occurrence of IBM and special non-IBM trademark names with a '(R)'. See http://www.ibm.com/legal/copytrade.shtml for a complete list of non-IBM trademark names.} 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 time without notice. Microsoft, Windows, and Windows Server are trademarks of Microsoft Corporation in the United States, other countries, or both. Java and all Java-based trademarks and logos are trademarks or registered trademarks of Oracle and/or its affiliates. UNIX is a registered trademark of The Open Group in the United States and other countries. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. Third-Party License Terms and Conditions, Notices and Information The license agreement for this product refers you to this file for details concerning terms and conditions applicable to third party software code included in this product, and for certain notices and other information IBM must provide to you under its license to certain software code. The relevant terms and conditions, notices and other information are provided or referenced below. Please note that any non-English version of the licenses below is unofficial and is provided to you for your convenience only. The English version of the licenses below, provided as part of the English version of this file, is the official version. Notwithstanding the terms and conditions of any other agreement you may have with IBM or any of its related or affiliated entities (collectively "IBM"), the third party software code identified below are "Excluded Components" and are subject to the following terms and conditions: - The Excluded Components are provided on an "AS IS" basis - IBM DISCLAIMS ANY AND ALL EXPRESS AND IMPLIED WARRANTIES AND CONDITIONS WITH RESPECT TO THE EXCLUDED COMPONENTS, INCLUDING, BUT NOT LIMITED TO, THE WARRANTY OF NONINFRINGEMENT OR INTERFERENCE AND THE IMPLIED WARRANTIES AND CONDITIONS OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE - IBM will not be liable to you or indemnify you for any claims related to the Excluded Components - IBM will not be liable for any direct, indirect, incidental, special, exemplary, punitive or consequential damages with respect to the Excluded Components.