Analysis Center

Version 2.7

Release Notes

Revised: August 20, 2008

This version of the NetIQ Analysis Center product (Analysis Center) provides several new features. This version also improves usability and extends several capabilities. These improvements have been 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 that our products meet all your needs.

This document outlines why you should install this version, provides additions to the documentation, and identifies any known issues. We assume you are familiar with previous versions of this product. For more information about installing Analysis Center, see the User Guide for Analysis Center.

Why Install This Version?

This version of Analysis Center provides the following new features or enhancements:

Data Mart and Data Warehouse Support on SQL Server 2005 Service Pack 2

Analysis Center now supports the Data Mart and Data Warehouse on SQL Server 2005 Service Pack 2.

64-bit Support

In addition to 32-bit platforms, Analysis Center now supports 64-bit versions of Windows Server 2003 with Microsoft SQL Server 2005 Service Pack 2.

Upgrading from Previous Versions

You can upgrade from Analysis Center version 2.6 to Analysis Center version 2.7, with the Data Extension, Data Warehouse, Web Service, Console, and Data Mart, on a single computer or in a distributed environment. Ensure that each Analysis Center component meets the system requirements.

For more information about upgrading to Analysis Center version 2.7, see the "Upgrading from Analysis Center version 2.6" section in the User Guide for Analysis Center.

For migrating data from Analysis Center version 2.6 to Analysis Center version 2.7, see the NetIQ Knowledge Base article: NETIQKB71220.

Additions to Documentation

Windows 2008 Support

Analysis Center also supports 32-bit and 64-bit versions of Windows Server 2008 with Microsoft SQL Server 2005 Service Pack 2. However, the Analysis Center Web Part is not supported on Windows 2008.

Installing Analysis Center on Windows 2008

You can install Analysis Center on a single computer or in a distributed environment. Ensure that each Analysis Center component meets the system requirements. The system requirements except for installing the Web Service on Windows 2008 are the same for installing Analysis Center on Windows 2003 and on Windows 2008. For more information about installing the Data Extension, Data Warehouse, Console, and Data Mart on Windows 2008, see the User Guide for Analysis Center.

To install all components of Analysis Center on a single computer or in a distributed environment:

1. Run the Analysis Center Setup program.
2. To install the Analysis Center Web Service, install IIS version 7.0 on the Windows 2008 computer with the following Role Services selected:
• Application Development: ASP.NET
• Security: Windows Authentication
• IIS 6 Management Compatibility
3. Enter the required credentials to proceed with the installation.

The product documentation is up-to-date and provides the latest information.

Viewing Documentation Files

When viewing the documentation files in the installation kit, you may observe the following issues:

• The installation kit provides some documentation in PDF files. To view these documentation files, you need Adobe Acrobat or Adobe Reader installed. You can download Adobe Reader from the Adobe Web site (www.adobe.com).
• When you view the documentation files through the setup program, the snap-in for Internet Explorer may display some hidden text, such as index entry tagging, in the files. To hide this hidden text:
  1. On the Tools menu, click Options.
  2. Clear the All and Hidden Text check boxes, and then click OK.

Known Issues

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 NetIQ Technical Support (www.netiq.com/support).

You Do Not Have Permissions to Manage the Analysis Center Console if you Install Analysis Center on Windows 2008 Using a Valid Domain Administrator User Account

If you install Analysis Center on Windows 2008 using a valid domain admin user account, you do not have permissions to manage the Analysis Center Console.

To resolve this issue:

1. In the location where the Analysis Center Console is installed, right click NQConsole.exe and select Run as Administrator.
2. Go to File > Manage Security.
3. Select the domain user from Accounts and click Modify.
4. Select Administrator and click Modify.
5. Close the Analysis Center Console.
6. Start the Analysis Center Console without using the Run as Administrator option. You might still need to use the Run as Administrator option to deploy reports into SQL Server Reporting Services.

ACWebPartConfiguration.xml Not Found

Analysis Center may display an error message when the ACWebPartAdmin.exe tool cannot find the ACWebPartConfiguration.xml file with the IP address in the Web Server.

To resolve this error, use the host name instead of the IP address of the server.

OLAP Processing Job Fails Intermittently In Step 7

The OLAP Processing Job fails intermittently in Step 7, and recovers automatically in the next OLAP Processing Job cycle.

To resolve this issue, do not run the OLAP and ETL Processing Jobs at the same time. For assistance on this issue, contact NetIQ Technical Support and see the NetIQ Knowledge Base article: NETIQKB71216.

Installation Known Issues

The following installation issues are currently being researched.

Installation of Analysis Center on Windows 2008 requires IIS 7.0

For more information, see Windows 2008 Support under Additions to Documentation.

Analysis Center Does Not Display the Version of Windows in the Requirement Check Dialog Box

If you are installing Analysis Center on Windows 2008, the installer does not display the installation summary. To install Analysis Center on Windows 2008, refer the "Installing Analysis Center on Windows 2008" section, and ensure that all the components meet the system requirements.

Cannot Create a Data Mart in a SQL Server 2005 Service Pack 2 Named Instance when a SQL Server 2000 Default Instance Coexists in the Same Computer

When there is a default instance of SQL Server 2000 and other named instances of SQL Server 2005 Service Pack 2, the packages are created in the default instance, even if the Data Marts are installed on the named instances, and the ETL Processing Job fails.

To resolve this issue, if you install the Data Mart in a SQL Server 2005 Service Pack 2 named instance where a SQL Server 2000 default instance coexists, upgrade the SQL Server 2000 default instance to SQL Server 2005 Service Pack 2, else the ETL job fails.

Analysis Center Web Part on x86 Computers Fails on ASP .NET 1.1

Analysis Center may display an error message when adding Web Parts on SharePoint Sites that have ASP.NET 1.1.

To resolve this error, use ASP.NET 2.0 on SharePoint Sites where the Analysis Center Web Part is installed.

Add Data Source Fails when the Data Mart Server Contains Only the Named Instance

Analysis Center may display an error message when trying to add a Data Source.

To resolve this error, while entering the Data Mart server name, ensure that SQL Server Integration Services is installed and running on this Data Mart SQL Server, and change the appropriate xml tag in the MsDtsSrvr.ini.xml file. For more information, see the Help.

Installation Fails when you Provide a Full Domain Name for the Web Service Account

During installation of the Analysis Center Web Service, if you provide the domain name for the Web Service account in the domain.com\user format, the installation program displays an error message.

To resolve this error, when you install Analysis Center, provide the domain name in the domain\user format.

Cannot Log On to the Analysis Center Console After Installing SharePoint

If you do not install SharePoint at the time you install the Analysis Center Web Service or the Reporting Services Data Extension, and you subsequently install SharePoint, the Windows SharePoint Services or SharePoint Portal Server 2003 intercepts requests that should be handled by IIS. When this happens, you might be unable to log on to the Analysis Center Console or access SQL Reporting Services.

To resolve this issue:

1. Exclude Analysis Center virtual directories using the following commands:
   1. stsadm -o addpath -url http://localhost/ACWebService -type exclusion
   2. stsadm -o addpath -url http://localhost/Reports -type exclusion
   3. stsadm -o addpath -url http://localhost/ReportServer -type exclusion

   For information about excluding managed paths, see http://support.microsoft.com/kb/828810/.

2. Open web.config located in inetpub\wwwroot, and then make the following changes:
   1. Change wss_minimaltrust to Full in the following tag: <trust level="wss_minimaltrust" originUrl="">.
   2. Remove the comment tags (<!-- ... -->) in the following tag: <add name="Session" type="System.Web.SessionState.SessionStateModule">.
   3. Add the following information between the <system.web> </system.web> tags to enable the session state flag: <pages enableSessionState="true" enableViewState="true" enableViewStateMac="true" validateRequest="false"/>.

Analysis Center Does Not Support Web Part Installation to a Remote Web Site Host

During installation, you can choose to install the Web Part on a single SharePoint site or on multiple sites. If you choose to install the Web Part on multiple SharePoint sites, all of the URLs that you provide should point to existing SharePoint sites on the local host. If you specify a valid URL on a remote host, Web Part installation fails.

To install the Web Part on SharePoint sites that are located on different hosts, run the Setup program on each host.

DO Not Install More than One Data Warehouse on an Analysis Server

If you install more than one Data Warehouse on a single Analysis Server, the cube processing jobs for each Data Warehouse fail.

Dbsizeverification.exe Cannot be Started From a Network Server

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 Utilities\ACPreCheckUtility folder where you installed Analysis Center. This tool must reside on the host from which it is started. If you want to run it on a host other than the Data Warehouse host, copy the ACPreCheckUtility folder to that host.

Error Message during Installation Failure

Analysis Center may display an error message if there is a failure during installation. While the error message does indicate a failure of the installation, the rollback of the installation completes successfully.

Domains and Accounts for Case-sensitive SQL Servers

When you are providing <domain>\<account> information for connection to a case-sensitive SQL Server, the domain and account name must match the case for the account name on the target SQL Server. If a login name is DOMAIN\account, then you must identify it as DOMAIN\account. For example, domain\account does not work.

Fully-qualified Domain Names Cause Installation to Fail

When you identify an account during installation that requires the <domain>\<account> format, you cannot identify the portion of the account with a fully-qualified domain name. For example, my.test.domain\account is not valid.

Installation/removal Fails without Warning when SQL Server and SQL Server Agent Services Are Not Running

When installing or removing components for which SQL Server is a system requirement, the installation/removal aborts without warning if the SQL Server and SQL Server Agent services are not running. If you experience this failure, restart the SQL Server and SQL Server Agent services, and then run the installation/removal again.

Console Warning when Web Service Is Configured to Use the Secure Socket Layer (SSL)

If the Web Service is configured to use SSL, during Console installation you get a warning message that Web Service could not be verified. This message can be safely ignored. The Console reaches your SSL-configured Web Service without problems.

During Installation of Analysis Center, Anti-virus Programs May Detect VBScript as a Virus

When VBScript is executed during installation of Analysis Center, some anti-virus programs might interpret the execution of the script as a virus. You can, however, successfully proceed with the installation.

It is recommended that you turn off anti-virus programs during installation.

Uninstallation Does Not Completely Remove Analysis Center

Removing a Beta version of Analysis Center does not always remove all components that were added as part of the installation. If components have been left behind, you cannot perform a new installation. The installation attempts to perform an upgrade under these circumstances.

To completely remove an installation of Analysis Center, at each Analysis Center computer:

1. Use Add/Remove Programs in the Control Panel to remove Analysis Center.
2. Delete any remaining Analysis Center folders (for example, Program Files\NetIQ\Analysis Center).
3. In the Program Files\Installshield Installation Information folder, delete the folder {B93606A0-9A8E-4E03-9588-04199362FAEB}.
4. From the root of the registry, search for and delete any Analysis Center or AnalysisCenter keys or values.
5. From the root of the registry, search for and delete any {B93606A0-9A8E-4E03-9588-04199362FAEB} keys or values.
6. If the optional Web Part component has been installed, run this command on the SharePoint server: stsadm -o deletewppack -name NQACWebPart
7. If Analysis Center reports have been displayed in SharePoint, manually remove them using the Administration Tools > Central SharePoint Administration tool.

Use SQL Server Enterprise Manager to verify if:

• All Analysis Center-related databases are deleted
• All Analysis Center-related local DTS packages are deleted
• All Analysis Center-related SQL Server Agent jobs are deleted

Uninstalling the Web Part Causes SharePoint Error Messages

If you uninstall the Analysis Center Web Part while it is still included in one or more Web Part pages, those pages display an error message.

To resolve this error, manually remove the Analysis Center Web Part from all Web Part pages.

Uninstalling the Web Part Does Not Remove Web.config Entries

Installation of the Web Part includes making a number of entries to the Web.config file. Uninstalling the Web Part removes the code but does not remove the entries made to the Web.config file. This is because it is not known how many changes might have been made to Web.config after the Web Part was installed. Complete removal of the Web Part content from Web.config is a manual operation. For more information, see the Microsoft Web Service and SharePoint documentation.

Upgrade Known Issues

The following upgrade issues are currently being researched.

Upgrade Fails when SQL Analysis Service Is Running as user@domain.com

If the SQL Analysis Services, MSSQLServerOLAPService, is running using the user@domain.com account format, the upgrade program displays an error message when you try to upgrade Analysis Center to version 2.6.

To upgrade Analysis Center successfully, provide the domain name in the domain\user format for the SQL Analysis Service account.

If a Data Mart SQL Agent is Down During an Upgrade, the ETL Job Is Not Created and the OLAP Job Fails

Before beginning an upgrade to Analysis Center 2.5, verify that the SQL Agent is running on any Data Mart computers. If the problem has already occurred, restart the Data Mart SQL Agent, which automatically recreates the ETL and OLAP jobs.

After an Upgrade, the OLAP Processing Job Fails until All Data Marts Are Also Upgraded

After you upgrade to Analysis Center 2.5, each Data Mart is upgraded the next time its related ETL job runs. During this period while the individual Data Marts are being upgraded, the OLAP Processing job fails until it recognizes that the versions of all Data Marts match the version of the Data Warehouse. When all versions are the same, the OLAP Processing job completes successfully. You do not need to take any action during this upgrading of the Data Marts.

In addition, you should not create any new Data Sources until all of the existing Data Marts have been upgraded.

Report Known Issues

The following reporting issues are currently being researched.

Cannot Export Reports when Analysis Center Is Installed on Windows 2008 x64 Computers

In Windows 2008 x64 computers, you cannot export reports from the Analysis Center Console, because the Export option is disabled.

To resolve this issue:

• In the Windows Registry, go to HKEY_LOCAL_MACHINE\SOFTWARE\NetIQ\AnalysisCenter\2.0\DataWarehouse.
• Double-click DataWarehouseInstallPath and copy the Value data.
• Go to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\NetIQ\AnalysisCenter\2.0.
• Create a new key with the name DataWarehouse.
• In DataWarehouse, create a new String Value with the name DataWarehouseInstallPath.
• Double-click DataWarehouseInstallPath and paste the Value data that you have copied.
• Close the Options dialog box and open it under Tools > Options. The Export option is enabled.

Some Report Wizard Reports Are Shown in the ReportMigration.log when You Use the Report Migration Utility on x86 Computers

• Reports created by the Report Wizard in Analysis Center version 2.6 are in the log of reports migrated by the Report Migration Utility after upgrading to Analysis Center version 2.7.
• Reports created by the Report Wizard in Analysis Center version 2.6 and imported to Analysis Center version 2.7 are in the log of reports migrated by the Report Migration Utility.

Some Report Wizard Reports Are Shown in the Log when You Use the Report Migration Utility on x64 Computers

Reports created by the Report Wizard in Analysis Center version 2.6 and imported to Analysis Center version 2.7 are in the log of reports migrated by the Report Migration Utility.

Links for Drill-down reports Are Lost after Upgrading to Analysis Center 2.7 on x86 Computers

If you save Analysis Center version 2.6 Drill Down reports using the Save As option, and you link those reports from the TOC report, the links are lost after upgrading to Analysis Center version 2.7.

To update the links in the TOC report:

1. In the Navigation pane, expand Reports. Locate the Drill Down and TOC reports saved in Analysis Center version 2.6.
2. Select the TOC report.
3. In the Tasks pane, click the Properties tab.
4. On the Properties tab, click Column Rules and then click [...]. Analysis Center displays the Column Rules dialog box.
5. In Members, select the member. The properties of the member are displayed.
6. Select the Source attribute.
7. Repeat steps 5 and 6 for each member of Column Rules.
8. Save the report.

Improper Data Displayed for Some Reports

Analysis Center displays a red cross instead of the chart or table for some generated reports.

To resolve this issue, when a red cross is displayed instead of the chart or table, restart the Analysis Center Console.

The w3wp.exe Application Consumes 100% CPU and High Memory when Reports Have Old Data

The w3wp.exe application consumes 100% CPU and high memory when:

• 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

Check whether:

• The report has to process several data points
• The parameters you have selected for the report are correct.

Duplicated Values Displayed in the Y-Axis of Reports

Analysis Center displays duplicate values in the Y-Axis of Analysis Center reports. To view the Y-Axis values correctly, modify the numeric format of the report.

To manually increase the number of decimals that display in the Y-Axis:

1. Log on to Analysis Center Console.
2. From the Navigation pane, select a report in the Report folder.
3. On the Report Properties tab, select Display > NumericFormat.
4. Modify the value in the NumericFormat field to F4 or greater.
5. Regenerate the report.

Timeout Error from SharePoint Web Part when Opening a Report

SharePoint sets a default open timeout of 7 seconds (7000 milliseconds) for Web Part content items. If an Analysis Center report at a SharePoint site takes longer than the open timeout to display, Analysis Center may display an error message.

To resolve this issue, open the Web.config file located in the Web Service folder of the Analysis Center installation folder, and then locate this line:

<WebPartWorkItem Timeout="7000" />

Increase the value appropriately. For more information about setting timeout values, see the User Guide for Analysis Center.

Sharepoint Displays Very Large Reports

SharePoint technology is not designed to process large amounts of data. A report that requires more than 15 seconds to execute may not be displayed in a Web Part.

Displaying a Trend and Prediction Report in a Web Part Breaks Other Analysis Center Web Parts on the Same Page

You can add multiple Web Parts to a SharePoint page. Displaying a Trend and Prediction report in a Web Part can cause an error message to be displayed in another Web Part on the same page. To resolve this error, remove and re-add the Web Part.

Cannot Configure 3-D Charts from the Analysis Center SharePoint Web Part

Analysis Center supports both 2-D and 3-D charts. To configure 3-D charts within the Analysis Center console, use the chart toolbar. However, the Analysis Center SharePoint Web Part does not display the chart toolbar, so you cannot configure 3-D reports from within the Web Part.

To resolve this issue, configure a report to display a 3-D chart using the Analysis Center Console, save the report, and then display it within the Web Part.

Export Reports Option Disabled in a Distributed Environment

Exporting reports requires that the [installation path]\console folder on the Analysis Center Console computer contain the following files:

• XMLCheckIn.exe
• XMLCheckIn.exe.config
• XMLCheckInLib.dll
• Win32Security.dll

If you install the Console and Data Warehouse components on the same computer, these files reside in this folder.Otherwise, the files reside in the \bin folder inside the installation folder of the Data Warehouse computer. To enable report export, copy the files to the \console folder on the Console computer.

In addition, when the Console and Data Warehouse computers are different, configure them to communicate through SQL port 1433.

Windows Graphics Device Interface (GDI) Displays Errors when Using the Print Preview Command for a Chart

If a chart contains a large number of data rows and you use the Print Preview command for that chart, a GDI error message is displayed. When you close the error message, the chart is no longer displayed in the Analysis Center Console.

To resolve this issue, install the latest Microsoft Update.

Charts Are Sometimes Not Displayed for a Report

If a report that has previously displayed a chart fails to do so upon a subsequent execution, close and restart the Analysis Center Console.

Deployed Dashboard Reports May Vary Somewhat between Analysis Center Versions

When you deploy a dashboard report that contains a table, Reporting Services may render the table with a different number of rows than you have configured in Analysis Services. Regardless of how drill-through properties are defined for individual Analysis Center reports, when you deploy a dashboard report, you can drill through from the report title to a full version of the report, but you cannot then drill further into the report.

Deploying a Cached Report Sometimes Fails

To resolve this issue, immediately before you deploy a report, generate the report.

Deploying a Cached Report that Has Been Renamed Produces an Error

If you rename a cached report, Analysis Center displays an error message when you attempt to deploy the report.

To resolve this issue, generate a report immediately before renaming it. Then the report deploys as expected.

The SortExpression Property Is Not Supported in Date/Time-based Reports

The SortExpression property indicates the column name and the direction in which the column is sorted. This property is not effective for Date/Time-based reports executed in the Console, nor in the deployed versions of those reports (for example, reports like Server Event Over Time).

Chart Y axis in Deployed Reports Can Vary from Console Display

Reporting Services currently uses an older version of the chart control used in Analysis Center. This older version can cause differences in how scaling of the Y axis is handled in each environment. For example, you might set the AxisY>Minimum property to 0 and the AxisY>Maximum property to 25.5 in Analysis Center, and the scale in Reporting Services is Minimum = 0, Maximum = <no value displayed>.

Threshold Indicator Incorrect for Charts with Data Values Between 0 and 0.003

If you are using threshold indicators for thresholds above 0.001 and you have data values between 0 and 0.003, the threshold indicators in the chart are incorrect.

Using Percentage Y-Axis Labels with System Uptime Reports

You can set y-axis labels to percentage values. With this setting, the System Uptime reports can be misleading. This is because these reports display the value 1 for up and 0 for down.

Changing the NumericFormat to P5 (percentages with five decimal places) causes the table to display incorrect values.

Report Queries May Fail while the OLAP Processing Job is Running

If a report attempts to execute a query of the Data Warehouse cubes at the same time the OLAP Processing job is running, the report may fail with a 4005 error.

To resolve this issue, temporarily stop the OLAP Processing job, or alter its schedule via SQL Server Enterprise Manager so that it runs at a time when reports are not running.

Refresh Command Does Not Work for Some Context Controls

The Refresh command is not implemented for the Group and Metric context controls.

Component Distribution and Configuration Known Issues

The following component distribution and configuration issues are currently being researched.

In a Clustered Environment, the ETL Job May Fail or You May Not Be Able to Create the Data Mart Successfully

If you run into problems while creating a Data Mart, or if the ETL job fails in a clustered environment, see the Help for Managing a Data Source.

Cannot Deploy or View Reports without Administrator Privileges

If you log on to the Analysis Center Console without administrator privileges, you cannot deploy reports to SQL Reporting Services. You also cannot view reports in SQL Reporting Services 2005 Service Pack 2.

To resolve this issue:

1. Create a new role in SQL Reporting Services 2005 Service Pack 2, which has permissions to view and deploy the reports.
2. Assign this role to yourself.
3. Log on to the Analysis Center Console with the same account.
4. Deploy the report to SQL Reporting Services and view the report in SQL Reporting Services 2005 Service Pack 2.

Password Pass-through Authentication Is Untested

For backward compatibility, Microsoft still supports an undocumented user authentication methodology known as password pass-through. While it might be possible for you to configure Analysis Center to work in environments where this connection methodology is used, NetIQ Corporation has not tested the methodology and cannot verify that Analysis Center would work in these environments.

Collation Settings for Data Mart SQL Servers Must Match the Collation Settings for the Corresponding AppManager Repository SQL Servers

To prevent data from being corrupted while it is being copied from an AppManager repository to a Data Mart, the collation settings of the Data Mart SQL Server and the corresponding AppManager repository SQL Server must match.

Coexistence issue with AppManager, AppManager Control Center, and AppAnalyzer

If you:

• Install Analysis Center components on a computer, and then
• Install AppManager, AppManager Control Center, or AppAnalyzer components on the same computer

Restart the computer before removing any Analysis Center components. If you do not restart the computer before removing Analysis Center components, removal of those components deletes the registry keys for AppManager, AppManager Control Center, and AppAnalyzer, leaving those applications inoperable.

SQLOLEDB Errors when Analysis Center Components Are Distributed between Windows 2000 Service Pack 4 and Windows 2003 Service Pack 1 environments

If you have some Analysis Center components installed on Windows 2000 Service Pack 4 computers and other components installed on Windows 2003 Service Pack 1 computers, you can encounter SQLOLEDB errors when you select either the Enterprise or Data Sources node, or any individual data source node in the Navigation pane.

To eliminate the problem, you have to configure the Component Services security in the following manner:

1. On the Windows 2003 SP1 computer, click Start > Programs > Administrative Tools > Component Services.
2. Expand Component Services.
3. Right-click My Computer, and then click Properties.
4. Select the MSDTC tab.
5. Click Security Configuration.
6. Select the following options:
   • Network DTC Access
   • Allow Remote Clients
   • Allow Remote Administration
   • Allow Inbound
   • Allow Outbound
   • No Authentication Required
   • Enable XA Transactions

Creating a Data Mart on a SQL Server Failover Cluster, and Then Selecting the Data Sources Node or the Related Individual Data Source in the Console, can generate an “MSDTC on server ‘VSQL’ is unavailable” error

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.

Incorrect Information May be Displayed About Transfer of Data between a Data Source and Data Mart

When the Data Sources node is selected in the Navigation tree, the Results pane shows the status of the Data Sources that have been added to Analysis Center. The status sometimes includes the message ETL has run, but no data was transferred even if data has in fact been transferred from the Data Source to its Data Mart. Additionally, the Oldest Data and Newest Data fields are blank, even if you have retrieved the data.

If the Data Extension and Reporting Services Are Installed on a Computer Whose IIS Server has Implemented the Secure Sockets Layer, the Report Server Icon that is Displayed When You Select the Enterprise Node May Display an Error

This is due to a possible error in how the Default Report Server Location is defined in the Options dialog box.

To verify that the correct URL is used for the Report Server location:

1. Open the Console.
2. Click Tools > Options.
3. Select Reporting Services.
4. In the Default Report Server Location field, make sure that the URL for the Report Server begins with https rather than http.

Local Users May Not be Able to Start the Console

If you attempt to start the Console with a local user account that does not have Read permissions for its local TEMP folder (as defined in the system environment variables for the account), you may see an error.

A new DLL is created for each login attempt, and so the name of the DLL changes with each error. This problem is due to the fact that the XMLSerializer functionality of Microsoft’s Common Language Runtime Compilation (CLR) is used to implement the Analysis Center Web Service. To implement the Web Service, XMLSerializer creates a temporary DLL in the user’s local TEMP folder. CLR has permission to create the DLL, but the process that CLR is running on behalf of the user trying to start the Console does not have permission to read the DLL if the local user account does not have Read permissions for its local TEMP folder.

To resolve this issue, ensure that each local user account that is expected to start the Console has Read permissions for its local TEMP folder. (Check the system environment variables for an account to verify the location of its TEMP folder. The location is usually \WINNT\TEMP.)

Modifying the Default .NET Runtime Security Policy can Cause the Console to Crash

If you modify the default .NET Runtime Security Policy, the Console may crash with an error message.

It is Possible to Start the Console Without Specifying a URL for the Web Service in the Logon Dialog Box

You can start the Console without entering a Web Service URL in the Console Logon dialog box. If you leave the Web Service field blank, the default URL for the Web Service is used.

The default URL for the Web Service is established when you install the Console and stored in the Windows registry in the following location: (HKEY_LOCAL_MACHINE\SOFTWARE\NetIQ\AnalysisCenter\2.0\Console\WebServiceURL)

Console Must be Restarted after Folder Deletion

The Tree window displays the folders and reports that are already deleted. To view the contents in the Tree window correctly, you may refresh the Tree window and then restart the Console.

Security Settings Are Not Refreshed when Changes Are Made From Another Instance of the Console

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.
• User B’s new permissions for the report node do not take effect in Console 2 - he can still view the Reports node.
• The new permissions for User B are enforced the next time he logs in to the Console.

Console Not Updated when the ETL Job Completes

The Console is not updated to reflect the most-recent data in the Data Warehouse each time the ETL and OLAP processing jobs complete. For example, if you have a report open while a new view (such as SQL) or a new computer or server is added to the AppManager environment, and the ETL and OLAP processing jobs complete to add that information to the Data Warehouse, that new view, computer, or server is not automatically added to the Group context for that report. To work around this, you can select another report, and then reselect the original report - this causes the new view, computer, or server to be properly displayed.

If you have previously deployed the report and want the deployed version to include the new information, you must redeploy the report.

Error Message when attempting to Start the Console if the ACWebService Application Root is Not Properly Configured

If you receive the following error message (Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.) when attempting to start the Console, verify the configuration of the ACWebService application root.

The ACWebService node under the IIS Default Web Site must be configured as an application root. While Analysis Center installation typically configures this node as an application root, it is possible that the configuration may not be completed.

To verify the configuration:

1. Click Start > Programs > Administrative Tool > Internet Services Manager.
2. Expand the IIS Server hosting the Web Service.
3. Expand Default Web Site, and find the ACWebService node.
4. The icon for the node should indicate whether it is a virtual directory (folder with globe icon) or an application node (package icon).
5. Right-click the ACWebService node, the click Properties.
6. Click the Virtual Directory tab.
7. Under Application Settings, locate the Application Name field.

If the button to the right of the field is labeled Create, click the button. This action creates an application root from the virtual directory.

If the button to the right of the field is labeled Remove, then the node is already configured as an application root.

If Anonymous Access is Enabled for the ACWebService Virtual Directory, You Cannot Start the Console

By default, the ACWebService virtual directory (under the IIS Web site you have chosen to host the Web Service) is configured with anonymous access disabled. If you enable anonymous access for the ACWebService virtual directory, you cannot start the Console.

The ACWebService Virtual Directory Must have Windows Integrated Authentication Enabled

By default, the ACWebService virtual directory (under the IIS Web site you have chosen to host the Web Service) is configured with Windows Integrated authentication enabled. It must remain enabled in order to start the Console and successfully connect to the Web Service.

Memory-related Error Message Can be Addressed by Managing SQL Server Memory Usage

This error message is often related to memory usage by SQL Server. According to Microsoft, “SQL Server memory usage may continue to steadily increase and not decrease, even when activity on the server is low. Additionally, the Task Manager and Performance Monitor may show that the physical memory available on the computer is steadily decreasing until the available memory is between 4 to 10 MB.”

This is normal behavior for SQL Server when the Dynamically configure SQL Server memory option is selected. You can use other memory options to manage how SQL Server uses memory.

Consult SQL Server Books Online for information about setting memory options. The following URL also provides information about SQL Server memory usage:

http://www.support.microsoft.com/?id=321363

OLAP Job can Fail to Create Cubes if Application Log is Full

Under circumstances where there is an error with the OLAP job and an entry cannot be made to the Application log because that log is full, the OLAP job can fail to create cubes. To resolve this issue, open the Application log Properties, and select Overwrite events as needed.

Cannot Log in to Analysis Center if the Web Service is Installed on a Windows 2000 Domain Controller

Due to a .NET limitation, you cannot log on to Analysis Center if the Web Service is installed on a Windows 2000 Domain Controller.

Microsoft does provide a workaround if for some reason you must install the Web Service on a Windows 2000 Domain Controller. See http://support.microsoft.com/default.aspx?scid=kb;en-us;315158 for more information. You can also search the Microsoft Web site for references to issue Q315158.

Deleting Groups

An Analysis Center user with sufficient permissions can delete groups, thus preventing any subsequent logons to the program. If this happens, you can edit the Web.config file to add Analysis Center users. Those users can then log on, and add groups. The default location of the file is Program Files\NetIQ\Analysis Center\WebService\Web.config.

To edit the file to add users:

1. Open the file with a text editor.
2. Under the <appSettings> section near the beginning of the file, find the line:
<!--<add key="AC Administrators" value="{localcomputer}\{account},{domain}\{account}" />-->
3. Delete the comment tags:
<add key="AC Administrators" value="{localcomputer}\{account},{domain}\{account}" />
4. Set the key value to equal the users you want to add. Use the format <local computer>\<account name> or <domain>\<account name>. For example: <add key="AC Administrators" value="company domain\some user" />
5. Separate multiple users by commas. For example: <add key="AC Administrators" value="company domain\user_1,company domain\user_2" />
6. Save the file.

Any of the users added to the Web.config file can log on to Analysis Center.

Data Collected by Subsequently Deleted Knowledge Scripts is Not Copied from the AppManager Repository to the Data Warehouse

When you use a Knowledge Script to collect data, and then subsequently delete that Knowledge Script, the collected data is not copied from the AppManager repository to the Analysis Center Data Warehouse, and is not available for reports. This is due to the Knowledge Script name missing from the KS table in the AppManager repository.

To resolve this issue, recreate the deleted Knowledge Script at some point prior to the ETL job running for the Data Source that includes that AppManager repository -- once the ETL job has run, you cannot recreate the missing data.

If you Customize a Knowledge Script That Does Not return XML-formatted Dynamic Legend Data and Does Not Provide a Custom Legend Rule, the Data Mart Does Not Process the Data Collected by That Knowledge Script Correctly

When you customize a Knowledge Script that does not return XML-formatted dynamic legend data, you must create a custom legend rule for each data stream returned by the script, and then use XMLCheckIn.exe to check those rules into the Data Warehouse. Otherwise, the data collected by that Knowledge Script is not processed accurately in the Data Mart, and is not available for reports.

You can find examples of legend rules in Analysis Center\Config\Legend.

For example, if you were to use NT_MemUtil as the basis for a custom Knowledge Script, you could then use the legend matching rules for NT_MemUtil as the basis for the rules for your new script. Those rules are found in the file NT.LEGEND.XML.

The following describes an existing rule for the % Physical Memory Usage data stream collected by NT_MemUtil:

<RULE ID="NT_MemUtil.1">

<EXPRESSION>^(Mem)?PhysUsage\^\^%$</EXPRESSION>

<ITEM IDX="0" LABEL="% Physical Memory Usage" MATCH="TRUE" />

<UNITS>%</UNITS>

<KSName>NT_MemUtil</KSName>

<ACApplication>NT</ACApplication>

<ACObject NAME="" />

<ACMetricCategory NAME="" />

<SampleHiddenLegend>MemPhysUsage^^%</SampleHiddenLegend>

<StaticDataDescription>Memory Utilization</StaticDataDescription>

<DynamicDataFormat>% Physical Memory Usage</DynamicDataFormat>

<Type NAME="NT_PagingFileFolder" />

<Type NAME="NT_PhysicalMemObj" />

<Type NAME="NT_VirtualMemObj" />

</RULE>

Note: The <EXPRESSION> tag contains a regular expression that must match the legend supplied by the Knowledge Script. This regular expression extracts variables from the legend that are used to define metric variables for the data stream as it appears in the cube. Variables are used to represent things like server or process names. The <ITEM> tag must correspond to the variables defined in the regular expression. Use the <StaticDataDescription> and <DynamicDataFormat> tags to define metric labels as they appear in the Metric context control in the Analysis Center Console. The <DynamicDataFormat> tag must correspond to the variables defined in the regular expression and in the <ITEM> tag.

Once you create the rule, save it in a file using the following format:

<CustomName>.LEGEND.XML (for example Custom.LEGEND.XML) where <CustomName> can be any name.

Once you create the XML file, check the contents of the file in to the Analysis Center Data Warehouse with the XMLCheckIn utility (located in Analysis Center\bin). Issue the following command:

XmlCheckIn <XML file>. For example, XmlCheckIn Custom.LEGEND.XML.

Data From the General_WMICounter Knowledge Script is Not Available for Analysis Center Reports

The legends for data streams collected by General_WMICounter do not contain OID values, and thus cannot be matched. This problem will be fixed in the next release of AppManager.

A SQL Server Instance Whose Name Contains Lower-case Non-English Characters, or Upper-case Non-English Characters Mixed With Any Lower-case Characters, is Not Recognized During Creation of a Data Source

You cannot use a SQL Server instance whose name contains lower-case non-English characters (for example, â, ê, ñ) as the SQL Server for a Data Mart database. When you try to create a Data Source and specify a SQL Server that uses that naming convention, the creation of the Data Source fails with an error message.

You can, however, use upper-case non-English characters (for example, Â, Ê, Ñ) for SQL Server instance names if the entire name is specified in upper-case letters (for example <COMPUTER NAME>\SQLSERVER_ÑÊÂ). If you combine upper-case non-English characters with any lower-case characters (for example, <COMPUTER NAME>\sqlserver_ÑÊÂ), the creation of the Data Source fails.

In a Distributed Environment, Connections to SQL Servers Using Windows-only Authentication Fail if the Connection Involves More than Two Computers.

For example, the OLAP processing job fails if:

• Analysis Services is installed on Computer A
• The Data Warehouse SQL Server is installed on Computer B
• The Data Mart is installed on Computer C

The credentials for the Windows account are valid for the connection from Computer A to Computer B, but are not valid for the subsequent connection from Computer B to Computer C.

The problem and a workaround are described on the Microsoft Web site at:

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q238/4/77.asp&nowebcontent=1

AppManager Support Issues

Analysis Center relies on AppManager to collect the data on which reports are based. If data that you expect to appear in a report is missing, a possible cause is a problem with AppManager. Check with NetIQ support to see whether Hotfixes are available for your product version(s). If AppManager Hotfixes are available, installing them might fix problems with your reports.

Data Collected By AppManager From the Following Applications is Not supported in Analysis Center

A number of older AppManager application modules are no longer supported by AppManager, and Analysis Center does not provide legend-matching rules for the data collected by these modules:

Antigen, AppCenter, BizTalk, Commerce, Conf, Domino-RT, End2End, FW1, HPNS, ISA, MSMQ, MTS, Netfinity, NetShield, NetWare, Proxy, SAP, ScanMailExch, WebServices, WinFrame, and WLBS

If you need legend-matching rules for any of these modules, contact NetIQ Technical Support or Professional Services. While these modules are no longer supported, it is possible to create rule files for them.

Some VoIP Modules Are No Longer Supported in Analysis Center

Analysis Center does not support the following VoIP modules:

• CiscoCNS
• CiscoIPTV
• CiscoICS

The Legend Processing Rules for NT/UNIX_TopCpuProcs and NT/UNIX_TopMemoryProcs Have Been Changed to Accurately Process Data that Includes a Dynamic Description

The legend processing rules processed AppManager version 5.0.1 data without providing a dynamic description, and processed AppManager version 6.0 data with a dynamic description. The rules have been updated to provide static and dynamic descriptions for both AppManager versions 5.0.1 and 6.0 data. These updates were included in Analysis Center 2.0 SP1, and are also in Analysis Center 2.5.

When you upgrade from Analysis Center version 2.0 to Analysis Center version 2.5, the new rules are implemented, and any data processed from that point on is processed correctly. However, the previously processed AppManager version 5.0.1 data cannot be reprocessed by default.

To reprocess the data, you must either:

• Uninstall Analysis Center version 2.0, and make a clean installation of Analysis Center version 2.5, OR
• Upgrade to Analysis Center version 2.5, delete the previous Data Source that referenced the AppManager version 5.0.1 data, and then create a new Data Source for that data.

If you are already running Analysis Center version 2.0 SP1 or 2.0 SP1a and previously went through this process while upgrading from Analysis Center version 2.0, you do not need to repeat this process when upgrading to Analysis Center version 2.5.

Data From the AppManager for Apache version 6.1 Was Not Processed Correctly by Analysis Center Version 2.0

Some of the data streams from the AppManager for Apache version 6.1 included dynamic data, while other data streams did not. In Analysis Center 2.0, the data streams that did include dynamic data were not processed properly (the data may have been assigned to the wrong instance or computer. The problem was fixed in Analysis Center version 2.0 SP1, and the fix is included in Analysis Center version 2.5 as well. Analysis Center version 2.5 correctly processes all data streams from AppManager for Apache 6.1. However, if you are upgrading from Analysis Center versions 2.0 to 2.5, the AppManager for Apache version 6.1 data is not processed correctly.

To ensure proper processing, you must either:

• Uninstall Analysis Center 2.0, and make a clean installation of Analysis Center 2.5, OR
• Upgrade to Analysis Center 2.5, delete the previous Data Source that referenced the AppManager for Apache 6.1 data, and then create a new Data Source for that data.

On a Data Warehouse SQL Server Computer Running Windows 2003, the OLAP Processing Job May Hang Due to Error Reporting Against XmlCheckIn.exe

If your OLAP Processing job hangs and you receive an error message related to XmlCheckIn.exe, stop the OLAP Processing job, disable error reporting for XmlCheckIn.exe, and then restart the OLAP Processing job. You can stop the OLAP Processing job from the Analysis Center Console, or from SQL Server Enterprise Manager.

To disable error reporting for XmlCheckIn.exe:

1. Click Start > Settings > Control Panel, then double-click System.
2. On the Advanced tab, click Error Reporting.
3. Click Choose Programs.
4. Under Do not report errors for these programs, click Add.
5. Enter XmlCheckIn.exe, then click OK.
6. Click OK to close the Choose Programs dialog box.
7. Click OK to close the Error Reporting dialog box.
8. Click OK to close the System Properties dialog box.
9. Once you have disabled error reporting for XmlCheckIn.exe, restart the OLAP Processing job.

On Any Windows 2003 Computer Hosting an Analysis Center-related SQL Server or Analysis Server, MSDTC Must be Configured for Network Access

On any Windows 2003 computer hosting an Analysis Center-related SQL Server or Analysis Server, you must configure MSDTC for network access, or the Console freezes when you select a Data Source that references the SQL or Analysis Server on that computer.

To configure MSDTC for network access:

1. Click Start > Programs > Administrative Tools > Component Services.
2. Expand Component Services; expand Computers; right-click My Computer, then click Properties.
3. Click the MSDTC tab.
4. Click Security Configuration.
5. Select the Network DTC Access check box.
6. Click OK to close the Security Configuration dialog box.
7. Click OK to close the My Computer Properties dialog box.
8. You must reboot the computer for the changes to take effect.

Internationalization Known Issues

The following internationalization issues are currently being researched.

If You Are Running the Analysis Center Setup Program With an Account that Contains a Double-byte Character (for example, a Japanese, Chinese, or Korean character), Then you Must Change the Environment Variable that Points to the Temp Folder for that Account

If you are running the 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, you must 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 once the setup program has run.

Japanese Characters Are Corrupted if Locale Settings for the AppManager Repository and Data Mart Computers Are Not Both Japanese

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.

Legal Notice

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.

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.

© 1995-2008 NetIQ Corporation, all rights reserved.

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.

Check Point, FireWall-1, VPN-1, Provider-1, and SiteManager-1 are trademarks or registered trademarks of Check Point Software Technologies Ltd.

ActiveAgent, ActiveAnalytics, ActiveAudit, ActiveReporting, ADcheck, AppAnalyzer, AppManager, the cube logo design, Directory and Resource Administrator, Directory Security Administrator, Domain Migration Administrator, Exchange Administrator, File Security Administrator, IntelliPolicy, Knowing is Everything, Knowledge Scripts, Mission Critical Software for E-Business, MP3check, NetConnect, NetIQ, the NetIQ logo, NetIQ Change Administrator, NetIQ Change Guardian, NetIQ Compliance Suite, NetIQ Group Policy Administrator, NetIQ Group Policy Guardian, NetIQ Group Policy Suite, the NetIQ Partner Network design, NetIQ Patch Manager, NetIQ Risk and Compliance Center, NetIQ Secure Configuration Manager, NetIQ Security Administration Suite, NetIQ Security Analyzer, NetIQ Security Manager, NetIQ Vulnerability Manager, PSAudit, PSDetect, PSPasswordManager, PSSecure, Server Consolidator, VigilEnt, Vivinet, Work Smarter, and XMP are trademarks or registered trademarks of NetIQ Corporation or its subsidiaries in the United States and other jurisdictions. All other company and product names mentioned are used only for identification purposes and may be trademarks or registered trademarks of their respective companies.