This version of NetIQ Analysis Center provides new features. Many of these improvements were made in direct response to suggestions from our customers. We thank you for your time and valuable input. We hope you continue to help us ensure our products meet all your needs. You can post feedback in the Analysis Center Forum on Qmunity, our community Web site that also includes product notifications, blogs, and product user groups.
For more information about this release and for the latest release notes, see the Analysis Center Documentation Web site. To download this product, see the following page on the NetIQ AppManager Product Upgrade Web site.
This version of Analysis Center provides support for the new logical server objects in Control Center management groups in AppManager 8.2. These logical server objects include the following object types:
The following VMware vCenter resources:
ESX hosts
Virtual machines
Datacenters
Clusters
Datastores
Datastore clusters
Root application objects that allow access to other objects within the application hierarchy (for example, SQL Servers or IIS servers)
SQL Server and Oracle databases
Applications you are monitoring with the AppManager ResponseTime for Windows (Windows-RT) module
Network and SNMP Toolkit devices
By including both the physical computers and logical servers as top-level objects, you can generate reports for the physical computers or for specific entities on those computers.
NOTE:Logical servers belong to QDBs upgraded to version 8.2 only. For more information about logical server objects, see the Control Center User Guide for AppManager, which you can download from the AppManager Documentation Web site.
Issue: Null values in the MCMachineName column in the MachineMntHistory QDB table caused the ETL job to fail. (ENG321598)
Fix: Analysis Center now filters the null values so that the ETL job does not fail.
For the list of software fixes and enhancements in previous releases, see Previous Releases.
This release requires NetIQ Analysis Center 2.7.5.
Before you upgrade to Analysis Center 2.8, ensure that you do the following tasks.
Analysis Center environments running Windows Server 2008 R2 or Windows Server 2008 require Internet Information Services (IIS) 7.0 on the Windows Server computer. Ensure that you select the following Role Services:
Application Development: ASP.NET
Security: Windows Authentication
IIS 6 Management Compatibility
Plan the installation for a time when you can upgrade all Data Marts so there is no version mismatch. After you install version 2.8, Analysis Center upgrades each Data Mart the next time its related ETL job runs. When all Data Mart versions match the Data Warehouse version, the OLAP processing job completes successfully. Until then, while individual Data Marts are being upgraded, the OLAP processing job fails. In addition, during installation do not create any new Data Sources until Analysis Center upgrades all the existing Data Marts.
For detailed information on hardware requirements and supported operating systems and browsers, see the NetIQ Analysis Center User Guide.
When you install this version, Analysis Center re-creates and runs the ETL processing job on each Analysis Center data source.
If you previously applied any hotfix listed in the Previous Releases section, Analysis Center does not re-create the AC_OLAP database after you install this release. If you did not apply any hotfix, Analysis Center re-creates the database and runs the OLAP processing job. You will be able to view your reports when the OLAP processing job has run successfully the first time after installing this release. This will take some time, depending on the amount of data to process.
Install Analysis Center 2.8 on all computers with the following components:
Console
Data Extension
Data Warehouse (AC_Warehouse database installed on a computer running Microsoft SQL Server)
Web Service
To install Analysis Center 2.8:
Ensure that there are no administrative tasks in process, such as the pending addition or deletion of data sources.
Using an account with administrative privileges, log on to the computer where you want to install Analysis Center 2.8.
Close all Analysis Center Consoles running on this computer.
Run the AC28.exe file.
Follow the wizard instructions.
Repeat steps 2 through 5 on each computer on which Analysis Center components are installed.
Complete the following steps to verify that the installation was successful.
For each computer on which Analysis Center components are installed, log on with a local administrator account.
Check the value of the following Windows Registry key:
My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\NetIQ\AnalysisCenter\2.0\ProductVersion
After you install this software version, the value of the ProductVersion key is 2.8.x.0.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
Analysis Center components require user credentials in the format domain\user. During installation of the Analysis Center Web Service, if you provide a fully qualified domain name for the Web Service account in the format domain.com\user, the installation program displays an error message.
When you upgrade Analysis Center, if the SQL Analysis Services, MSSQLServerOLAPService, is running using the format user@domain.com, the upgrade program displays an error message.
To resolve these errors, provide the domain name in the format domain\user for these accounts.
The DBSizeVerification tool helps estimate disk requirements for AppManager repositories that you want to use with Analysis Center. This tool is installed with the Data Warehouse, in the Utilities\ACPreCheckUtility folder where you installed Analysis Center, and it needs to reside on the host where you are running it. To run it on a host other than the Data Warehouse host, copy the ACPreCheckUtility folder to that host.
If you are installing the Web Service component on Windows Server 2003 and you enabled the NtfsDisable8dot3NameCreation registry setting, the setup program displays the following error: Cannot open C:\DOCUME~1\svc_dra\Local Settings\Temp\{83600-xxx-xxx-etc}\WebSites.txt. To correct this, disable the NtfsDisable8dot3NameCreation registry setting and use the 8.3 naming convention to create the TEMP folder for the installing user's profile. To apply this change, reboot the target computer before you run the setup program again.
For more information about disabling this setting, see the section “Disabling Automatic 8.3 Name Generation” in the following Microsoft TechNet article: http://technet.microsoft.com/en-us/library/cc875836.aspx (ENG276794).
If you install Analysis Center on Windows Server 2008, and you use a valid domain administrator user account, you do not have permissions to manage the Analysis Center Console.
To resolve this issue:
In the location where the Analysis Center Console is installed, right click NQConsole.exe and select Run as Administrator.
Go to File > Manage Security.
Select the domain user from Accounts and click Modify.
Select Administrator and click Modify.
Close the Analysis Center Console.
Restart the Console without using the Run as Administrator option. You might need to use the Run as Administrator option to deploy reports to SQL Server Reporting Services.
If you move your system to SQL Server Reporting Services (SSRS) 2008, and you deploy a report that you had previously created using the System Uptime Pie Chart template, SSRS displays a solid black chart in the report. To display the report correctly, create the report again using the System Uptime Pie Chart template and redeploy it.
Upgrading from SQL Server Reporting Services (SSRS) 2000 to SSRS 2008 changes the Analysis Center Data Source Type value from “NetIQ Analysis Center” to “NetIQAC”. This renders the SSRS Data Source connection configuration to Analysis Center invalid, and causes deployed reports to no longer function correctly. To resolve this issue, modify the Report Server web.config file and the Report Manager web.config file. For more information about modifying these files, see NETIQKB72315.
After migrating to a system running Analysis Center 2.8, Analysis Center does not retain some links to dashboard reports. To correct this, remove the links that do not work and add the reports to the dashboard again.
To fix broken links in a dashboard:
Open the dashboard in the Analysis Center Console.
In the Properties pane, go to DashItems and click the Edit button (...).
In the Configure Dashboard Members dialog box, select the report that is no longer linked in the dashboard. The Members list displays the report ID, and the Report value in the Attributes list is blank.
Click Remove to delete the report from the Members list.
Click Add to add a new item called [No Report Assigned] to the Members list.
In the Attributes list, go to Report and click the Edit button (...).
In the Pick Report dialog box, select the correct report and click OK.
In the Configure Dashboard Members dialog box, reconfigure any attributes and contexts for the newly added report and click OK.
Click Execute Report to execute the dashboard and display all its reports correctly.
On the toolbar, click Save.
If you have more than one Data Source and then upgrade to Analysis Center 2.8, the Create Data Mart job fails on Step 1 for one of the Data Sources, and records the error “Deadlocked on lock resources” in the log file. To correct this, run the failed Create Data Mart job manually, for each Data Source, one at a time.
You need to redeploy reports in the following scenario:
When you upgrade QDB first and then upgrade AC, you need to redeploy those jobs which were scheduled and were running just before AC upgrade began.
For example:
You have AC 2.7.5 with QDB 8.0.x, and you upgrade to QDB 8.2, and there is a job is running over LS object. Now, if you upgrade AC 2.7.5 to AC 2.8, the job that was running over QDB 8.2 will still be seen in the old stream. You will be able to view the data for LS objects such as 'master' and 'tempdb'.
In general, if you want to view any LS objects data, you need to redeploy jobs in AM as data for LS objects needs to be collected in the new stream. Irrespective of any upgrade scenario, you need to redeploy jobs in AM and collect data in new stream to view LS data.
The reports you have created and deployed in AC 2.7.5 for the QDB 8.2 objects (servers selected from application view) need to be redeployed after you upgrade to AC 2.8, to get the correct data in SSRS.
After upgrading Analysis Center, some reports created by the Report Wizard in Analysis Center 2.6 are displayed in the log of reports that the Report Migration Utility migrated. In addition, some reports created by the Report Wizard in Analysis Center 2.6 and imported to Analysis Center 2.7 are also in the log of reports that the Report Migration Utility migrated.
In a generated report, if Analysis Center displays a red cross instead of a chart or table, or is unable to display a chart that it had displayed previously, restart the Analysis Center Console.
The w3wp.exe application consumes 100% CPU and high memory in the following situations:
Reports have data older than one year
You run this report after setting the interval time as Minute or Hour and select several metrics
The report takes a longer time to run than expected or finishes with an error message
Confirm that you selected valid parameters for the report, and check whether the report has to process several data points.
Analysis Center displays duplicate values in the y-axis of Analysis Center reports. To view the y-axis values correctly, use the following instructions to modify the numeric format of the report.
To manually increase the number of decimals that display in the y-axis:
Log on to Analysis Center Console.
From the Navigation pane, select a report in the Report folder.
On the Report Properties tab, select Display > NumericFormat.
Modify the value in the NumericFormat field to F4 or greater.
Execute the report.
If you install Analysis Center in a distributed environment, Analysis Center installs the files required to export reports on the Data Warehouse computer, not the Console computer.
To enable report export, copy the following files from the bin folder on the Data Warehouse computer (typically in C:\Program Files\NetIQ\Analysis Center\bin) to the console folder on the Console computer (typically in path C:\Program Files\NetIQ\Analysis Center\console):
XMLCheckIn.exe
XMLCheckIn.exe.config
XMLCheckInLib.dll
Win32Security.dll
If you install the Console and Data Warehouse components on the same computer, these files are located in the correct folder.
The SortExpression property, which indicates the column name and sort direction of a column, is not effective for Date/Time-based reports, such as Server Event Over Time.
Setting y-axis labels to percentage values in the System Uptime reports can be misleading because these reports display the value 1 for up and 0 for down. In addition, changing the NumericFormat to P5 (percentages with five decimal places) causes the table to display incorrect values.
If you discover that any Drill-Down reports contain broken links, use the following instructions to restore the links manually.
To restore a link to a sub-report manually:
In the Reports tree, select the Drill-Down report that contains the broken link.
Click the Properties tab.
In the Display section of the Properties tab, click the Edit button (...) next to Column Rules.
In the Column Rules dialog box, select a column in the Members pane and click Remove.
Click Add and scroll to the Attributes section.
In the Attributes section, in the Source box, select a column name.
In the Links section, click the Edit button (...) next to Cell, and in the Pick Report dialog box select the sub-report with the broken link in the Drill-Down report.
In the Pick Report dialog box, click OK.
Repeat steps 4 through 8 for each broken link in the Drill-Down report.
In the Column Rules dialog box, click OK.
Click Report > Save Report.
Drill down functionality does not work for reports on Logical Server objects. It only works for reports on the Machine.
If you log on to the Analysis Center Console without administrator privileges, you cannot deploy reports to SQL Server Reporting Services (SSRS) or view reports in SSRS. To resolve this, follow these instructions to create a new role in SSRS that has permission to view and deploy the reports.
To add a user or group to an item role:
Start Report Manager or click Home to go to the Report Manager start page.
Click the Properties tab.
Click the Security tab.
Click New Role Assignment.
In the Group or User Name text box, enter a Windows domain user or group account in this format: domain\account. If you are using forms authentication or custom security, specify the user or group account in the format that is correct for your deployment.
Select the role definitions that describe how the user or group should access the report, and click OK. The Security page displays the newly created account in the Group or User list, along with its role. To create assignments for additional users or groups, repeat steps 4 through 6.
From the Analysis Center Console, redeploy the report and confirm that it deploys successfully in SSRS.
For more information about granting users access to Report Manager, see the following Microsoft article: http://msdn.microsoft.com/en-us/library/ms156034.aspx.
For backward compatibility, Microsoft still supports an undocumented user authentication methodology called Password Pass-Through. Although it might be possible to configure Analysis Center to work in environments with this connection methodology, NetIQ Corporation cannot verify that Analysis Center will work correctly in these environments.
To prevent the corruption of data while it is being copied from an AppManager repository to a Data Mart, the collation settings of the Data Mart SQL Server must match the collation settings of the corresponding AppManager repository SQL Server.
If you installed Analysis Center and AppManager on the same computer in the following order: Analysis Center first, followed by AppManager, AppManager Control Center, or AppAnalyzer components, you need to restart the computer before removing any Analysis Center components.
If you do not restart the computer first, removing Analysis Center components deletes the registry keys for AppManager, AppManager Control Center, and AppAnalyzer, which causes those applications to be inoperable.
If you create a Data Mart on a SQL Server Failover Cluster and then select the Data Sources Node or the related individual Data Source in the Analysis Center Console, Analysis Center might display the following error: MSDTC on server 'VSQL' is unavailable. This error occurs when the Virtual SQL Server comes online before the Distributed Transaction Coordinator service has started.
To resolve this issue, use the Cluster Administrator Console to take the Virtual SQL Server group offline, and then bring it back online.
You might get an error on the SQL Server Reporting Service (SSRS) icon when you select the Enterprise node in Analysis Center if the Data Extension and SSRS are installed on a computer whose IIS server implements the Secure Sockets Layer.
Verify that the correct Reporting Services URL is configured in the Options dialog box in Analysis Center.
To verify the URL:
Open the Analysis Center Console.
Select Tools > Options and click Reporting Services.
In the Default Report Server Location field, make sure that the URL for the Report Server begins with https instead of http.
If you have multiple instances of the Analysis Center Console open, and make changes to the security settings for a node from one Console, those changes are not reflected in the other open instances of the Console. Changes take effect the next time an instance of the Console is started.
For example:
User A is logged in to Console 1. User B is logged in to Console 2. Both have permission to view the Reports node.
User A changes the security settings for the Reports node to deny visibility to User B.
The new Reports node permissions for User B do not take effect in Console 2. User B can still view the Reports node.
The next time User B logs in to the Console, the new Reports node permissions take effect. User B cannot view the Reports node.
On any Windows Server 2003 or Windows Server 2008 computer hosting an Analysis Center-related SQL Server or Analysis Services server, you must configure MSDTC for network access, or the Console freezes when you select a Data Source that references the SQL or Analysis Services server on that computer. Use the following sets of instructions to configure MSDTC for network access on Windows Server 2003 and Windows Server 2008 computers.
To configure MSDTC for network access on Windows Server 2003:
Click Start > Programs > Administrative Tools > Component Services.
Expand Component Services > Computers. Right-click My Computer and click Properties.
Click the MSDTC tab and click Security Configuration.
Select the Network DTC Access check box.
Click OK to close the Security Configuration dialog box, and click OK to close the My Computer Properties dialog box.
Reboot the computer to apply the changes.
To configure MSDTC for network access on Windows Server 2008:
Click Start > Programs > Administrative Tools > Component Services.
Expand Component Services > Computers > My Computer > Distributed Transaction Coordinator. Right-click Local DTC and click Properties.
Click the Security tab and select the Network DTC Access check box.
Click OK to close the Local DTC Properties dialog box. Changes take effect immediately.
If you are running the Analysis Center setup program to install, modify, upgrade, or uninstall Analysis Center, and the account under which you are running the setup program contains a double-byte character (such as Japanese, Chinese, or Korean), you need to change the environment variable for that account to point to a Temp folder that does not contain any double-byte characters in either the folder name or in the path to the folder.
Typically, the environment variable for an account defines the Temp folder location as %USERPROFILE%\Local Settings\Temp. %USERPROFILE% contains the account user name. You can change the variable value to something like C:\ACInstallTemp for the purposes of running the setup program, and then change it back to its original value when the setup program is finished.
If you are using data from an AppManager repository installed on a computer using the Japanese locale (Windows Regional Options), the corresponding Data Mart computer must also use the Japanese locale. In addition, the system language settings for the Analysis Center Console computer must be set to include Japanese.
This hotfix also includes enhancements added in Hotfix 7011331, Hotfix 7008405, and Hotfix 7004799.
This hotfix resolves an issue in which ETL Step 16 fails because the UNIX agent on AIX computers incorrectly calculates bias time and returns data containing negative values. Analysis Center displays the following error: exec dbo.GetNewServerDowntime - Arithmetic overflow
Analysis Center now extracts only BiasedTime data containing positive values and ignores data with negative values. To resolve the source issue so that the UNIX agent calculates bias time data correctly, apply NetIQ UNIX Agent version 7.1 Hotfix 72471 on AIX computers. For more information about Hotfix 72471, see the description on the AppManager Suite Hotfixes Web page.
This hotfix resolves the following issue with the PointWidth property. In a report, if you change the value of the PointWidth property (under ChartSeries) to 75, and you run and save the report, the value reverts to Default (which is 50) in either of the following circumstances:
You select another report and then select the previously modified report
You close and reopen the Analysis Center Console, and then select the previously modified report
This hotfix resolves the following issues:
Resolves an issue in which the ETL job fails on Step 9 because the data is too long for certain tables in the AC_Warehouse and Data Mart databases.
Resolves an issue in which reports are moved to a deleted folder and are not accessible if you deleted a folder and then created a new folder with the same name.
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information Web site.
For general corporate and product information, see the NetIQ Corporate Web site.
For interactive conversations with your peers and NetIQ experts, become an active member of Qmunity, our community Web site that offers product forums, product notifications, blogs, and product user groups.
THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT ARE FURNISHED UNDER AND ARE SUBJECT TO THE TERMS OF A LICENSE AGREEMENT OR A NON-DISCLOSURE AGREEMENT. EXCEPT AS EXPRESSLY SET FORTH IN SUCH LICENSE AGREEMENT OR NON-DISCLOSURE AGREEMENT, NETIQ CORPORATION PROVIDES THIS DOCUMENT AND THE SOFTWARE DESCRIBED IN THIS DOCUMENT "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. SOME STATES DO NOT ALLOW DISCLAIMERS OF EXPRESS OR IMPLIED WARRANTIES IN CERTAIN TRANSACTIONS; THEREFORE, THIS STATEMENT MAY NOT APPLY TO YOU.
For purposes of clarity, any module, adapter or other similar material (“Module”) is licensed under the terms and conditions of the End User License Agreement for the applicable version of the NetIQ product or software to which it relates or interoperates with, and by accessing, copying or using a Module you agree to be bound by such terms. If you do not agree to the terms of the End User License Agreement you are not authorized to use, access or copy a Module and you must destroy all copies of the Module and contact NetIQ for further instructions.
This document and the software described in this document may not be lent, sold, or given away without the prior written permission of NetIQ Corporation, except as otherwise permitted by law. Except as expressly set forth in such license agreement or non-disclosure agreement, no part of this document or the software described in this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, electronic, mechanical, or otherwise, without the prior written consent of NetIQ Corporation. Some companies, names, and data in this document are used for illustration purposes and may not represent real companies, individuals, or data.
This document could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein. These changes may be incorporated in new editions of this document. NetIQ Corporation may make improvements in or changes to the software described in this document at any time.
U.S. Government Restricted Rights: If the software and documentation are being acquired by or on behalf of the U.S. Government or by a U.S. Government prime contractor or subcontractor (at any tier), in accordance with 48 C.F.R. 227.7202-4 (for Department of Defense (DOD) acquisitions) and 48 C.F.R. 2.101 and 12.212 (for non-DOD acquisitions), the government's rights in the software and documentation, including its rights to use, modify, reproduce, release, perform, display or disclose the software or documentation, will be subject in all respects to the commercial license rights and restrictions provided in the license agreement.
© 2013 NetIQ Corporation and its affiliates. All Rights Reserved.
For information about NetIQ trademarks, see http://www.netiq.com/company/legal/.