CA Storage Resource Manager Release Notes - Bookshelf

Release Notes Service Pack 12.7.01

CA Storage Resource Manager

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the “Documentation”) is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION “AS IS” WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with “Restricted Rights.” Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2013 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

CA Technologies Product References

This document references the following CA Technologies products:

■ CA Storage Resource Manager (CA SRM)

■ CA ARCserve® Backup (CA ARCserve Backup)

■ CA Business Intelligence

Contact CA Technologies

Contact CA Support

For your convenience, CA Technologies provides one site where you can access the information that you need for your Home Office, Small Business, and Enterprise CA Technologies products. At http://ca.com/support, you can access the following resources:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ CA Support policies and guidelines

■ Other helpful resources appropriate for your product

Providing Feedback About Product Documentation

If you have comments or questions about CA Technologies product documentation, you can send a message to [email protected].

To provide feedback about CA Technologies product documentation, complete our short customer survey which is available on the CA Support website at http://ca.com/docs.

http://www.ca.com/support

mailto:[email protected]

http://www.ca.com/docs

http://www.ca.com/docs

Documentation Changes

The following documentation updates have been made since the last release of this documentation:

Sections Updated Description of Change

Supported Certifications (see page 11)

Added this section with new feature information.

Dropped Features in This Release (see page 17)

Updated this section with the dropped features information.

Operating System Support (see page 19)

Updated this section with the Microsoft Windows 2012, Microsoft 8, and Solaris 11 OS support information.

Application Server Considerations (see page 23)

Updated this section with the added OS support information.

Windows Client Considerations (see page 24)


Upgrade Support (see page 25) Updated this section with the upgrade support information.

CA SRM Web Reporter Data Bridge (see page 27)

Updated this section with the updated release informaton.

Application Server - Software Requirements (see page 32)


Windows Client - Software Requirements


Windows Agent - Software Requirements (see page 36)


Supported CA SRM Versions (see page 36)

Updated this section with the supported versions information.

Application Server Data Collection (see page 43)

Updated this section with the supported versions information.

ARCServe Enhancements (see page 15)

Added this section with changed feature information.

Query Performance (see page 14) Added this section with changed feature information.

Virtual Host Data Collection (see page 16)


Sections Updated Description of Change

Customized File Storage Analysis (see page 16)


RO55825 (Allocated value is incorrect) (see page 29)

Added this section with the published fix information.

RO56073 (Data collection fails after continuous execution for four days) (see page 29)


RO49181 (HDS VSP disk array certification) (see page 29)


RO49191 (Trend upload is partial on Web Reporter Database) (see page 29)


RO55322 (Top level directory query results are incorrect) (see page 30)


Moving CA SRM Server from Workgroup to a Domain (see page 55)

Added this section with the known issue information.

SAN Volume Controller Enhancements (see page 13)


Dell PowerVault Disk Array (see page 50)

Added this section with a known issues information.

Report Schedule Error (see page 81)

Updated this section with additional information on the workaround.

Contents 7

Contents

Chapter 1: New Features 11

Supported Certifications ............................................................................................................................................ 11

Chapter 2: Changes to Existing Features 13

SAN Volume Controller Enhancements ...................................................................................................................... 13

Query Performance .................................................................................................................................................... 14

ARCServe Enhancements ........................................................................................................................................... 15

Virtual Host Data Collection ....................................................................................................................................... 16

Customized File Storage Analysis ............................................................................................................................... 16

Chapter 3: Dropped Features in This Release 17

Chapter 4: Operating System Support 19

Certified Device List .................................................................................................................................................... 22

Chapter 5: Installation Considerations for CA SRM 23

Application Server Considerations ............................................................................................................................. 23

Windows Client Considerations ................................................................................................................................. 24

Portal Server Compatibility ........................................................................................................................................ 25

Uninstall Considerations ............................................................................................................................................ 25

Upgrade Support ........................................................................................................................................................ 25

Chapter 6: Installation Considerations for CA SRM Web Reporter 27

CA SRM Web Reporter Server .................................................................................................................................... 27

CA SRM Web Reporter Data Bridge ........................................................................................................................... 27

Chapter 7: Published Fixes 29

RO55825 (Allocated value is incorrect) ...................................................................................................................... 29

RO56073 (Data collection fails after continuous execution for four days) ................................................................ 29

RO49181 (HDS VSP disk array certification) ............................................................................................................... 29

RO49191 (Trend upload is partial on Web Reporter Database) ................................................................................ 29

RO55322 (Top level directory query results are incorrect) ........................................................................................ 30

8 Release Notes

Chapter 8: System Requirements for CA SRM 31

Application Server ...................................................................................................................................................... 31

Hardware Requirements ..................................................................................................................................... 31

Software Requirements ...................................................................................................................................... 32

Windows Client .......................................................................................................................................................... 34



Windows Agent .......................................................................................................................................................... 35



Chapter 9: System Requirements for CA SRM Web Reporter 39

Hardware Requirements ............................................................................................................................................ 39

Software Requirements ............................................................................................................................................. 39

Supported CA SRM Versions ...................................................................................................................................... 41

Chapter 10: Cross-Version Compatibility 43

Windows Client Connectivity ..................................................................................................................................... 43

Application Server Data Collection ............................................................................................................................. 43

Chapter 11: Known Issues for CA SRM 45

General Issues ............................................................................................................................................................ 45

Application Server ............................................................................................................................................... 45

CA ARCserve Release 12 Primary Server Registration ........................................................................................ 46

CA ARCserve Release 12 Data Collection ............................................................................................................ 46

BOS Service Fails to Start .................................................................................................................................... 46

CA ARCserve Backup ........................................................................................................................................... 47

Capacity-Based Licensing .................................................................................................................................... 48

Computer Registration ........................................................................................................................................ 49

EMC Disk Arrays .................................................................................................................................................. 49

Dell PowerVault Disk Array ................................................................................................................................. 50

HBA Port Performance Statistics ......................................................................................................................... 50

Hicommand Disk Arrays ...................................................................................................................................... 51

Hitachi Data Systems Disk Arrays ........................................................................................................................ 51

IBM DB2 .............................................................................................................................................................. 52

IBM Disk Arrays ................................................................................................................................................... 52

Indirect Collection (NFS/DFS) .............................................................................................................................. 52

iSponsors for Backup Management .................................................................................................................... 53

iSponsor Server Error .......................................................................................................................................... 53

Contents 9

Legato NetWorker ............................................................................................................................................... 53

Licensing .............................................................................................................................................................. 53

Lotus Domino ...................................................................................................................................................... 53

LSI Disk Arrays ..................................................................................................................................................... 54

Microsoft Exchange 2000/2003 .......................................................................................................................... 54

Microsoft SQL Server .......................................................................................................................................... 54

Microsoft .Net Install Creates Dummy Folders ................................................................................................... 55

Moving CA SRM Server from Workgroup to a Domain ....................................................................................... 55

NetApp ................................................................................................................................................................ 57

NetWare .............................................................................................................................................................. 57

Non-English Operating Systems .......................................................................................................................... 58

Oracle .................................................................................................................................................................. 58

Portmapper Service............................................................................................................................................. 59

QLogic HBA Drivers ............................................................................................................................................. 60

Registration Wizard ............................................................................................................................................. 60

SMI-S Providers ................................................................................................................................................... 60

SUN Disk Arrays ................................................................................................................................................... 61

Sybase ................................................................................................................................................................. 61

TSM ..................................................................................................................................................................... 62

Trend Data Consolidation ................................................................................................................................... 63

UNIX and Linux .................................................................................................................................................... 63

Upgrading ............................................................................................................................................................ 64

Veritas NetBackup ............................................................................................................................................... 64

Virtual Host Servers............................................................................................................................................. 65

Windows ............................................................................................................................................................. 65

Service Issues ............................................................................................................................................................. 66

Automate Service ................................................................................................................................................ 66

File Group ............................................................................................................................................................ 67

File Scanning ....................................................................................................................................................... 67

General ................................................................................................................................................................ 67

Query Service ...................................................................................................................................................... 67

Windows Client Usage Issues ..................................................................................................................................... 68

General ................................................................................................................................................................ 68

Multi-byte Issues ................................................................................................................................................. 69

Chapter 12: Known Issues of CA SRM Web Reporter 71

Add SRM Server Fails - SQL Named Instance ............................................................................................................. 71

Add SRM Server Fails – SQL Target principal name is incorrect ................................................................................. 72

BOS Service Failed to Start ......................................................................................................................................... 73

CA Business Intelligence Upgrade from r2.x to r3.3 Fails with the CMS error STW00213 ......................................... 73

Post-installation Steps (Optional): ...................................................................................................................... 74

10 Release Notes

CA SRM Web Reporter Control Panel Dependencies ................................................................................................. 74

CA SRM Web Reporter Data Bridge Install Fails in RP4 .............................................................................................. 75

Duplicate Y-axis Scaling in Reports ............................................................................................................................. 75

Extreme Date Values .................................................................................................................................................. 75

Manual Import of Predefined Reports ....................................................................................................................... 75

Login Error-Reports ............................................................................................................................................. 80

Report Schedule Error ................................................................................................................................................ 81

Report Hangs (Heap size, Out of Memory, and Expansion Limit) .............................................................................. 81

Time out Errors in Web Reporter ............................................................................................................................... 82

Updating CA SRM Domain Credentials in Web Reporter ........................................................................................... 82

Chapter 13: Documentation 85

Chapter 14: International Support 87

Chapter 1: New Features 11

Chapter 1: New Features

CA SRM Service Pack 12.7.01 provides an integrated solution set for enterprise reporting, monitoring, and managing the storage infrastructure across multiple data centers and regional offices. CA SRM expands its storage management capabilities further through extended operating environment, device, application, and internationalization support.

For more information about changes to the existing features, see the Changes to Existing Features (see page 13) chapter.

This section contains the following topics:

Supported Certifications (see page 11)

Supported Certifications

CA SRM Service Pack 12.7.01 supports the following certifications:

■ Microsoft Windows 2012 Server and Windows 8 operating systems

■ Tivoli Storage Manager Release 6.3

■ Sybase Release 15.7

■ Solaris 11 as a managed agent

■ Microsoft Exchange Server 2010 and 2013

■ ESX Release 5.x

■ Java Release 7

■ EMC PowerPath 5.5

■ Veritas DMP Release 6.0

■ EMC Networker Release 8.0

■ IBM DB2 Version 10

■ IBM Storwize V7000 Disk System Version 6.3

■ IBM System Storage SAN Volume Controller Version 6.4

■ IBM General Parallel File System (GPFS) Version 3.5 on Linux

■ Microsoft SQL Server 2012

■ Resilient File System (ReFS) Support on Windows 2012


Chapter 2: Changes to Existing Features

This section describes the changes that are made to existing features for CA SRM Service Pack 12.7.01.

Note: For more information about the changed features, see the CA SRM User Guide.


SAN Volume Controller Enhancements (see page 13) Query Performance (see page 14) ARCServe Enhancements (see page 15) Virtual Host Data Collection (see page 16) Customized File Storage Analysis (see page 16)

SAN Volume Controller Enhancements

The SAN Volume Controller (SVC) model has been enhanced in the current release to include the following objects:

■ Internal Disk

■ Storage Performance

■ VDisk (volume) Copy

■ Host Mapping

Query Performance

14 Release Notes

In addition, some new fields are added to the following existing objects:

■ Cluster

The following fields are added to the Cluster object:

– Total Internal Capacity

– Total Spare Capacity

– Total Used Capacity

– Total Virtual Capacity

■ MDisk Group

The following fields are added to the MDisk Group object:

– Virtual Capacity

– Real Capacity

– User Capacity

■ Node

The following fields are added to the Node object:

– Failure Node Name

– iSCSI Name (IQN)

■ VDisk

The following fields are added to the VDisk object:

– Is Thin

– Is Compressed

– Copy Count

Query Performance

The current release enhances the performance of the non-file query execution significantly.

ARCServe Enhancements


ARCServe Enhancements

The current release supports enhanced ARCserve data collection. The new object, Cloud Connections is added to get the cloud-related information. Zooms are added from the ARCserve servers and the Drives objects to the Cloud Connections object and vice versa. In addition, some new fields are added to the following existing objects:

■ Drives

The following fields are added to get more information about the de-dupe and cloud devices:

– Data file path

– Index file path

– Cloud folder

– Device type

■ Job

The Compression Ratio field is added for the de-dupe jobs.

■ Sessions

The following fields are added to get more information about compression ratio and migration-related details:

– Compression Ratio

– Purge Date

– Migration Due Date

– Migration Status

Virtual Host Data Collection

16 Release Notes

Virtual Host Data Collection

The current release supports enhanced virtual host data collection. The following two new objects are added to capture more details of the Virtual Guest.

■ Virtual HBAs

■ Virtual Guest Data Files

In addition, the following new field is added to the existing object--Storage Devices, to get more information about the storage device.

■ State

The state of the path (Active / Standby / Disabled / Dead / N/a / Unknown) used by the storage device.

Note: In a storage device with multiple paths, all paths are traversed to find an active path. If the path is found, the state is set to Active, otherwise it is set to the state of last traversed path.

Customized File Storage Analysis

This release supports customized file level storage analysis for volumes of computers / NetApp filer shares.

Chapter 3: Dropped Features in This Release 17

Chapter 3: Dropped Features in This Release

CA SRM Service Pack 12.7.01 no longer supports Microsoft Windows 2000 Server support.


Chapter 4: Operating System Support

CA SRM provides support for managed computers on the following operating environments:

Name Edition Ver Rev X86 Itanium/ Itanium2 (IA64)

Opteron (AMD64)

Intel 64 (EM64T)

SPARC PowerPC RISC z/OS / z/390

AIX 5.3 NA X

6.1 NA X

7.1 NA X

HP-UX NA 11.11 (11i v1)

NA X

11.23 (11i v2)

NA X X

11.31 NA X X

Red Hat Linux

NA 7.3 NA X

8 NA X

9 NA X

Red Hat Linux

Enterprise

4 NA X X X X X

5 NA X X X X

6 NA X X X X

Suse Linux

NA 8 NA X

9 NA X

10 NA X X

Suse Linux

Enterprise

9 NA X X X X X

10 NA X X X X X

11 NA X X X X X


20 Release Notes


Opteron (AMD64)

Intel 64 (EM64T)


NetWare NA 5.x NA

6 NA

6.5 NA

Solaris NA 9 NA X

10 NA X X X X

11 NA X X

Windows 2003

Standard NA SP1 optional

X X X X

Enterprise

NA SP1 optional

X X X X

Data center

NA NA X X X X

Storage NA SP1 optional

X

Small Business Server

NA SP1 optional

X

Web Edition

NA SP1 optional

X

Windows 2003 R2

Standard NA NA X X X X

Enterprise

NA NA X X X X

Data center

NA NA X X X X

Storage NA NA X


NA NA X

Web Edition

NA NA X




Opteron (AMD64)

Intel 64 (EM64T)


Windows XP

Professional

NA SP1, SP2 optional

X X X

Windows 2008 * / 2008 R2

Standard NA NA X X X

Enterprise

NA NA X X X

Data center

NA NA X X X

Web Server

NA NA X X X

For Itanium-based systems

NA NA X

Windows 7

Standard NA SP1 Optional

X X X X

Enterprise

NA SP1 Optional

X X X X

Data center

NA NA X X X X

Storage NA SP1 Optional

X


NA SP1 Optional

X

Web Edition

NA SP1 Optional

X

Windows 8

Professional

NA

Ultimate NA

Certified Device List

22 Release Notes


Opteron (AMD64)

Intel 64 (EM64T)


Enterprise

NA

Windows 2012 Server

Enterprise

NA

Standard NA

Data center

NA

* Only full installations of Windows 2008 / 2012 are supported. Server Core (minimal) installation is not supported.

CA supports these operating systems during their lifecycle (until CA announces that they dropped support). Visit our website at http://support.ca.com for the latest information about supported operating systems.


Certified Device List (see page 22)

Certified Device List

The Certified Device List (CDL) for CA SRM is available at http://ca.com/support. As CA SRM adds support for new devices, the CDL will be updated and posted to this website.




Chapter 5: Installation Considerations for CA SRM

The following sections provide information about installation prerequisites, configurations, and issues to consider before installing CA SRM.

Note: Installation may fail on Microsoft Windows Server 2003 if the Terminal Server service is licensed.


Application Server Considerations (see page 23) Windows Client Considerations (see page 24) Portal Server Compatibility (see page 25) Uninstall Considerations (see page 25) Upgrade Support (see page 25)

Application Server Considerations

Following list includes the CA SRM Application Server considerations:

■ You cannot install CA SRM on a computer that either has multibyte characters in the computer name, or the multibyte characters appear in the directory path.

■ When the Control Panel is open during the CA SRM installation, an "ODBC Driver Manager" error occurs. Click OK and continue with the installation, reboot the computer, and reinstall CA SRM, ensuring that the Windows Control Panel is not open.

■ In some situations, antivirus software fails the installation with an "InstallShield -115 error". Stop the antivirus software, and restart the installation.

■ Enter the valid domain security during the Application Server installation to enable the Application Server computer to be registered as a managed computer. Make sure that you enter the password in the correct case.

■ You can install iGateway 4.7.2.3 to any path you choose.

Windows Client Considerations

24 Release Notes

■ All of the .ini files in the \BrightStor SRM Data\Database\Configuration directory are overwritten after upgrading. However, your original .ini files are backed up to \BrightStor SRM Data\Database\TMP\configuration (for Application Server) or \BrightStor SRM Data\TMP\configuration (for Agent).

■ After upgrading the CA SRM Application Server, you must manually update the launcher's data. To do so, open the Activity Monitor, select the Application Server BOS under Application Server Launchers and perform Update Launcher Data from the Launcher menu.

■ CA SRM requires Microsoft .NET Framework 3.5 on Windows 2012. To install and configure Microsoft .NET Framework, use Role Management Tool.

Note: In this release, GNS Service has became part of BOS Service that is, no separate GNS service exists. So when you stop BOS service, the Application Server running in Application mode that is, the standalone and Windows Client must be restarted.

Windows Client Considerations

Following list includes the Windows Client considerations:

■ The Application Server installation program creates a share named BSRM in the CA SRM directory of the Application Server computer. Access rights to this share are given to the user installing the Application Server and to users who log in from remote Windows Clients.

■ CA SRM cannot be installed to a directory where multibyte characters appear in the path.

■ In some situations, antivirus software may cause the installation to fail with an InstallShield -115 error. Stop the antivirus software, and restart the installation.

■ Regional settings (in particular, date, time, decimal symbol, and digit grouping symbol) of Windows Clients must be the same as the settings of the Application Server.

■ CA SRM cannot be installed on a computer that has multibyte characters in the computer name, or to a directory where multibyte characters appear in the path.

■ If you are installing standalone Windows Client for Open Systems from Windows Client folder of SRM builds, use the SetupSRM.bat file instead of Setup.exe file. If you install the Setup.exe file, the SQL Native Client pre-requisite will not be verified before install and hence Windows Client will not be able to connect to Application Server. Install the SQL Native Client first for Windows Client to connect to the Application Server.

■ CA SRM requires Microsoft .NET Framework 3.5 on Windows 2012 / Windows 8. To install and configure Microsoft .NET Framework, use Role Management Tool.

Portal Server Compatibility


Portal Server Compatibility

Due to changes in some of the underlying common components used by both CA SRM r11.7 and CA Portal r11.1, several updates are necessary to CA Portal for it to remain compatible with these changes. For more information, see the Readme_first.txt and InstallNotesContent.html files located at the root of the iSponsor CD released with CA SRM r11.7. In addition, these documents have been consolidated with other iSponsor documents and published on http://ca.com/support as Installation Notes for iGateway and iSponsor.

Uninstall Considerations

Uninstall considerations include the following:

■ We recommend that you reboot after uninstalling the Application Server to release locked files.

■ Sometimes, when uninstalling the Windows Agent, the Add or Remove Programs window remains locked on the screen, and to be closed from the Task Manager. This action does not affect the Windows Agent uninstallation process, which terminates normally.

Upgrade Support

Upgrade support includes the following versions:

■ CA SRM r12.7

■ CA SRM r12.6 SP1

■ CA SRM r12.6

■ CA SRM r11.8

■ CA SRM r11.7

Chapter 6: Installation Considerations for CA SRM Web Reporter 27

Chapter 6: Installation Considerations for CA SRM Web Reporter

This section contains information about installation prerequisites, configurations, and issues to consider before installing CA SRM Web Reporter:


CA SRM Web Reporter Server (see page 27) CA SRM Web Reporter Data Bridge (see page 27)

CA SRM Web Reporter Server

The following considerations are related to installing the CA SRM Web Reporter Server:

■ You can install the CA SRM Web Reporter Server on Windows 2003 and 2008 server operating systems.

■ Installation includes CA Business Intelligence.

■ When there is a version older than 3.3 exists, while installing CA SRM Web Reporter, upgrade BIEK to version 3.3. This may affect existing universe and reports.

Note: For more information on upgrading CA Business Intelligence, refer to the CA Business Implementation Guide which is available from CA SRM Web Reporter DVD at <…\CABIEK\Windows\Docs\ENU\>.

■ MS SQL Server 2005 and 2008 are the supported central databases for CA SRM Web Reporter.

CA SRM Web Reporter Data Bridge

Consider the following aspect before installing the CA SRM Web Reporter Data Bridge:

■ The Web Reporter Data Bridge is automatically installed as part of SRM r11.8 and later Application Server installations.

Note: For more information about Web Reporter Data Bridge, see the CA SRM Web Reporter Installation Guide.

Chapter 7: Published Fixes 29

Chapter 7: Published Fixes

The complete list of published bug fixes for this product can be found through Published Solutions on the CA Technologies support site.

This chapter lists the issues that have been resolved in this release.


RO55825 (Allocated value is incorrect) (see page 29) RO56073 (Data collection fails after continuous execution for four days) (see page 29) RO49181 (HDS VSP disk array certification) (see page 29) RO49191 (Trend upload is partial on Web Reporter Database) (see page 29) RO55322 (Top level directory query results are incorrect) (see page 30)

RO55825 (Allocated value is incorrect)

The Allocated field of All Storage Systems view shows incorrect data for the disk arrays.

RO56073 (Data collection fails after continuous execution for four days)

Any CA SRM object data collection (age.exe) process that runs more than four days fails.

RO49181 (HDS VSP disk array certification)

The Allocated/Unallocated files show incorrect values and the port speed shows the wrong value in the disk array record.

RO49191 (Trend upload is partial on Web Reporter Database)

During the CA SRM Server registration in the Web Reporter control panel, if the file size is greater than 5 GB, the trend upload is partial on the CASRMCetralDB database.

RO55322 (Top level directory query results are incorrect)

30 Release Notes

RO55322 (Top level directory query results are incorrect)

The top-level directory query results are incorrect. The data in the Level and the Total Size fields does not match with the actual data.


Chapter 8: System Requirements for CA SRM

The following sections contain detailed hardware and software requirements for installing CA SRM.


Application Server (see page 31) Windows Client (see page 34) Windows Agent (see page 35)

Application Server

The tables in the following sections provide the Application Server hardware and software requirements.

Hardware Requirements

The Application Server is supported on the following hardware requirements:

Hardware Minimum Recommendations

CPU Dual Pentium 4-Class Processors 2.0-GHz

For large enterprise environments (over 250 managed servers), use Dual Pentium 4 processors or more.

RAM 2-GB 4-GB (or higher) is recommended for better performance and for large enterprise environments.

Application Server

32 Release Notes


Hard Drive (Free Space) 15-GB hard disk free space is required to allow for growth of the CA SRM database.

Depending on the number of objects that you plan to manage, and the level of detail that you want to collect, you may need excess of 10-GB to store information that is collected from the network, and to save detailed historical (trend) information.

You are encouraged to confirm that Microsoft supports installation of Windows software on the Application Server computer. You can access the list of Windows-compatible computers on the Microsoft website.

If you are upgrading from an earlier version, you need temporary storage of up to twice the size of your current database files for the database conversion.

Software Requirements

The Application Server is supported on the following operating systems:

Name Edition Revision

Microsoft Windows 2003, R2 (32/64 bit)

■ Standard

■ Enterprise

■ Small Business Server

SP1 and SP2

Microsoft Windows 2008 (32/64 bit)

■ Standard

■ Enterprise

■ Data center

SP1 and SP2

Microsoft Windows 2008 R2

■ Standard

■ Enterprise

■ Data center

Microsoft Windows 2012 ■ Standard

■ Enterprise

■ Data center

Note: Before you upgrade your operating system, review the supported operating systems to verify that CA SRM Service Pack 12.7.01 supports the new operating system.

Application Server


The Application Server is supported on the following databases:


Microsoft SQL Server 2005 (32/64 bit)

■ Standard

■ Enterprise

Microsoft SQL Server 2008 (32/64 bit)

■ Standard

■ Enterprise

Microsoft SQL Server 2008 R2

■ Standard

■ Enterprise

Microsoft SQL Server 2012 ■ Standard

■ Enterprise

The Application Server is supported on the following native clients:


MS SQL Native Client released with MS SQL Server 2005 or later

Note: SQL Native Client is required only if SQL Server is remote.

Ensure that you have the following requirements:

■ The operating system must also run the Microsoft Data Access Components (MDAC) version 2.8 or higher. You can download this software from the Microsoft support site. In addition, ensure that the Microsoft Jet database engine 4.0 is installed on your computer. You can download the Jet software from the same Microsoft website.

■ Internet Explorer 6.0 or later, which can be downloaded from the Microsoft website.

■ Install the CA SRM Application Server on a computer that has the network connectivity. The CA SRM Application Server can automatically distribute and manage agent components on Windows systems. The Windows systems are members of the domain where the Application Server is running, or are members of a domain with a trust relationship.

Windows Client

34 Release Notes

Windows Client

Each Windows Client communicates with the MS SQL Server database on the Application Server.


The Windows Client is supported on the following hardware requirements:


CPU Pentium 4-Class Processor 1.2-GHz

RAM 1-GB

Hard Drive (Free Space) 500-MB

You are encouraged to confirm that Microsoft supports installation of Windows software on the Windows Client is to installed on. You can access the list of Windows-compatible computers at the Microsoft website, http://www.microsoft.com/whdc/hcl/default.mspx.


The Windows Client is supported on the following operating systems:


Microsoft Windows XP Professional SP1, SP2, and SP3

Microsoft Windows 2003, R2

■ Standard

■ Enterprise

■ Data center

SP1 and SP2

Microsoft Windows Vista ■ Business

■ Ultimate

■ Enterprise

SP1 and SP2

Microsoft Windows 7 ■ Business

■ Ultimate

■ Enterprise

SP1

Windows Agent



Microsoft Windows 2008, R2

■ Standard

■ Enterprise

■ Data center

SP1 and SP2

Microsoft Windows 8 ■ Professional

■ Ultimate

■ Enterprise


■ Enterprise

■ Data center

Note: Before you upgrade your operating system, review the supported operating systems to verify that CA SRM Service Pack 12.7.01 supports the new operating system.

The Windows Client is supported on the following native clients:


MS SQL Native Client released with MS SQL Server 2005 or higher


You must have Adobe SVG Viewer to view storage summaries in the home page, and to view the web pages that are created by SRM Windows Client.

For more information about Adobe SVG Viewer stabilization by Adobe, refer the Adobe website.

Windows Agent

The following tables provide the Windows Agent requirements.

Windows Agent

36 Release Notes


The Windows Agent is supported on the following hardware requirements:


CPU Pentium 1.2-GHz, or higher, that supports the operating system you are running.

RAM 512-MB

Hard Drive (Free Space) 100-MB disk space is required to install the software.

Depending on the number of objects that you plan to manage, and the level of detail that you want to collect, you may need temporary storage space well in excess of 5-GB. To protect your managed computer, the CA SRM agent will not start when there is less than 150-MB free space available in the database directory.

Internet Explorer 6.0 or higher is also required.

To enable collection of dynamic disk information, install the Microsoft DiskPart utility. Visit the Microsoft's website and search for DiskPart.exe. If you choose not to install this utility, CA SRM will still collect all data, except for information that is specific to dynamic disks.


The Windows Agent is supported on the following operating systems:


Microsoft Windows XP Professional SP1 and SP2


■ Enterprise

■ Data center

Base, SP1, and R2

Windows Agent




■ Enterprise

■ Data center

Microsoft Windows 2008 R2

■ Standard

■ Enterprise

■ Data center


■ Ultimate

■ Enterprise

SP1


■ Ultimate

■ Enterprise


■ Enterprise

■ Data center

Internet Explorer 6.0 or higher is also required.

To enable collection of dynamic disk information, install the Microsoft DiskPart utility. Visit the Microsoft website and search for DiskPart.exe. If you do not install this utility, CA SRM still collects all data, except for information that is specific to dynamic disks.

Note: Before you upgrade your operating system, review the supported operating systems to verify that CA SRM r12.7 SP1 supports the new operating system.


Chapter 9: System Requirements for CA SRM Web Reporter

The following sections contain detailed hardware and software requirements for installing CA SRM Web Reporter.


Hardware Requirements (see page 39) Software Requirements (see page 39) Supported CA SRM Versions (see page 41)


The CA SRM Web Reporter Server is supported on the following hardware requirements:

Hardware Minimum

CPU 2.0 GHz Pentium 4-class Processor

RAM 2 GB RAM

Hard Drive (free space) 15 GB hard disk space


The CA SRM Web Reporter Server is supported on the operating systems:


Microsoft Windows 2003; Microsoft Windows 2008

■ Standard

■ Enterprise

■ Small Business Server

■ Datacenter

■ Storage

■ Web edition

Base, SP1, and R2


40 Release Notes

The CA SRM Web Reporter Server is supported on the following databases:


Microsoft SQL Server 2005 / 2008

Microsoft SQL server 2012

Note: Apply the CABI 3.3 SP1 patch to support MS SQL Server 2012.

The CA SRM Web Reporter Server is supported on the following native clients:


MS SQL Native Client released with MS SQL Server 2005 or later


Supported Browsers:

The CA SRM Web Reporter Server is supported on the following browsers:

Browser JVM version

IE 6.0 SP1 Sun 1.4.2_xx

Sun 1.5.0_xx

Sun 1.6.0_02+

IE 6.0 SP2 Sun 1.4.2_xx

Sun 1.5.0_xx

Sun 1.6.0_02+

IE 7.0 Sun 1.4.2_xx

Sun 1.5.0_xx

Sun 1.6.0_02+

Firefox 2.0 Sun 1.5.0_xx

Sun 1.6.0_02+

Firefox 3.0 Sun 1.5.0_xx

Sun 1.6.0_02+

Supported CA SRM Versions


Supported CA SRM Versions

The following versions of CA SRM are supported to work with CA SRM Web Reporter:


■ CA SRM r12.7


■ CA SRM r12.6

■ CA SRM r11.8


Chapter 10: Cross-Version Compatibility 43

Chapter 10: Cross-Version Compatibility

The following sections describe the compatibility between different versions of CA SRM components.


Windows Client Connectivity (see page 43) Application Server Data Collection (see page 43)

Windows Client Connectivity

The Windows Client can only connect to an Application Server running at the same release level as the Windows Client.

Application Server Data Collection

The following table lists the compatibility between different versions of the Application Server and the CA SRM Windows Agent.

Application Server Version

Windows Agent Version Supported?

r12.7 SP1 r11.7, r11.8, r12.6, r12.6SP1, and r12.7

Yes

r12.7 r11.7, r11.8, r12.6, and r12.6 SP1 Yes

r12.6 SP1 r11.7, r11.8, and r12.6 Yes

r12.6 r11.7 and r11.8 Yes

r11.8 r11.6, r11.6FP1, r11.6 RP4, and r11.7 Yes


Chapter 11: Known Issues for CA SRM

The following sections describe any known technical problems and workarounds of SRM.


General Issues (see page 45) Service Issues (see page 66) Windows Client Usage Issues (see page 68)

General Issues

The following sections describe known issues that are platform-related.

Application Server

When you activate the Application Server Maintenance Utility from the Application Server desktop through the Terminal Service, the utility does not appear on the Terminal Service computer. It appears on the Application Server computer.

You can open the Maintenance Utility by the Terminal Service with the activation parameter/console. This is done by setting a shortcut to %SystemRoot%\System32\mstsc.exe /console.

Application Server Fail to Start Due to SQLDriverConnect Error:

In case of SQL Server Named Instance, if the SQL Server port number changes, application server fail to start and the system throws the following error:

"ODBC API 'SQLDriverConnect' failed with error ' while connecting to SRM database - [Microsoft][SQL Native Client]SQL Network Interfaces: Error Locating Server/Instance Specified [xFFFFFFFF]. '(46268415) : 302 (0x12E), error #46 of DBA component."

To resolve this, you can update the same in [DBA] section of BOS.ini file located at <\BrightStor SRM Data\Database\Configuration>

General Issues

46 Release Notes

Data Collection Fails in SRM Due to SQL Connection Error:

If any data collections fail in SRM due to the SQL server problem, the system throws the following message,

"E113: SQL Error while connecting to SRM database - [Microsoft][SQL Native Client] Unable to complete login process due to delay in opening server connection".

To resolve this error, change the configurable parameter 'SQLTimeout' under [DBA] section available in BOS.ini and increase the SQL Timeout value.

CA ARCserve Release 12 Primary Server Registration

You must register the CA ARCserve Release 12 Primary Server as managed computer with Host name. Registering with IP Address will cause problems in ARCserve discovery. This is because CA ARCserve Release 12 uses only host names for primary server/member server/standalone server and does not allow usage of IP Addresses.

CA ARCserve Release 12 Data Collection

The following are issues-related to ARCserve Release 12 Data Collection (17742755):

1. If you schedule jobs in JOB QUEUE object, the LAST RESULT attribute data is shown as UNAVAILABLE, since it is valid data from ARC Serve computer.

2. CA SRM does not collect the data for the Database Location field for ARCserve Release 12 versions.

3. Due to an existing issue with ARCserve, CA SRM may display incorrect value for the Database Size field for ARCserve Release 12 versions.

4. CA SRM does not collect the data for Product Name, Cartridge Type, and Group Name fields for ARCserve Drives object.

BOS Service Fails to Start

BOS service fails to start by enabling default SQL connections in CA SRM and Web Reporter:

General Issues


Problem:

1. Install SRM Application Server on any supported operating environment.

2. Stop Windows Client, NSMS, and BOS.

3. Enable all default connection options in SQL Server properties.

4. Restart SQL Server and try to start BOS.

BOS fails to start.

Workaround:

Do not enable the xact abort option in the SQL connection options. Restart SQL Server and try to start BOS.

BOS starts without any error.

CA ARCserve Backup

The following issues are related to integration with CA ARCserve Backup:

■ Cleaning tapes are not reported in the Media table.

■ On some operating environments, some CA ARCserve Backup 9, 11.1, and 11.5 fields may be empty.

■ iGateway 4.7.2.3 and the latest iSponsors must be installed on the backup servers prior to 11.5 version.

■ The data collection for computers running CA ARCserve Backup might fail with the status showing INCOMPLETE or FAILED. This is a result of duplicate entries for certain objects (for example, sessions, job number, media, and so forth) in the backup database (RAIMA only). If this happens, check the Messages table to see if the error "Key value already exists" appears and consult your backup administrator.

■ When a CA ARCserve Backup Job is in an Active state, the CA SRM data collection reports the End Time for this specific job as 0 (ZERO).

■ The Full Name field in the Job Queue displays as JobQueue_NA{index}@BABservername.

■ There is problem with ca_backup.exe in CA ARCserve Backup r11.5 SP1. As a result, CA SRM backup driving for volumes will fail with CA ARCserve Backup r11.5 SP1. If, for example, you try to back up the root path C: the backup does not work. This was correct in CA ARCserve Backup r11.5 SP2.

■ To use CA SRM with CA ARCserve Backup r11.1 SP1 for NetWare, you must apply text fix T50A032.

General Issues

48 Release Notes

Capacity-Based Licensing

Capacity-based licensing not working in Windows 64 bit operating systems:

Problem:

Current SRM iSponsor is unable to detect 64 bit iGateway running on windows 64 bit operating systems and hence it is not getting installed.

This blocks the capacity-based licensing feature functionality.

(This is the scenario when you already have 64 bit iGateway running on the computer before SRM install, else the 32 bit iGateway which is bundled with SRM build gets installed).

Also, SRM iSponsor is built for 32 bit operating environment and does not work with 64 bit iGateway.

Workaround:

Use 32 bit iGateway if you want to run Capacity-based licensing in 64 bit operating systems.

To run capacity-based licensing in Windows 64 bit operating system

1. Uninstall 64 bit iGateway.

Note: If any other applications are using this iGateway, uninstalling the same affects those applications functionality.

2. Install 32 bit iGateway available in SRM dump in the Portal Support folder.

3. Install SRM iSponsor available in SRM dump in the Portal Support folder.

4. Run Capacity-based licensing.

Problem:

As SRMiSponsor is a 32 bit binary, it is compatible to work with only 32 bit iGateway version on either 32 bit or 64 bit operating system.

In case of 64 bit operating systems, if the computer has already iGateway 64 bit version installed prior to installing SRM, the SRMiSponsor will not be installed. In this case Capacity based licensing module will not run and throws a network error and exits.

General Issues


Workaround:

To check capacity-based licensing in Windows 64 bit operating system

1. Uninstall the 64 bit iGateway and install 32 bit iGateway and SRMiSponsor from SRM build dump.

Note: If any other applications are using this iGateway, uninstalling the same affects those applications functionality.

2. Make sure the iGateway is started and running.

3. Check Capacity-based licensing.

Computer Registration

While registering any application in SRM, you must make sure that you register both the application and computer either with IP address or with host name.

Example:

If you register a computer with IP address and the application with host name, then the zoom option from computer for application will not return any data.

EMC Disk Arrays

EMC Disk Array issues include the following:

■ SymCli version 4.3, or higher, must be installed on the computer that acts as the proxy collector.

■ Environment variables that need to be set for SymCli use are:

– SYMCLI_CONNECT should be set to what is defined in the symapi\config\netcnfg file

– SYMCLI_CONNECT_TYPE should be set to REMOTE

■ The disk to RAID Group association may be inaccurate with EMC Solutions Enabler 5.0 and 5.0 may cause incorrect figures for the LDEVs.

General Issues

50 Release Notes

■ You must install the EMC Solutions Enabler 6.0 when configuring CA SRM to collect data from EMC Symmetrix disk arrays using SYMAPI. When you install the EMC Solutions Enabler 6.0 onto the CA SRM system, make sure that you do not select the SMI-S provider option. If you install the SMI-S provider option, it may interfere with the SMI-S data collection of the other disk arrays such as LSI, SUN, or HP which also use SMI-S.

■ If the unallocated value is negative for EMC Symmetrix Disk Arrays, it is a result of a bug EMC has in the API version 5.0. You need to upgrade to version 6.0 or higher.

■ With the current release, all new disk array data collections can only be done using SMI-S.

Dell PowerVault Disk Array

CA SRM data collection status for Dell PowerVault Disk Array shows INCOMPLETE. The SMI-S provider returns duplicate entries for a disk when it's status is By-Passed, hence the collection status in SRM shows INCOMPLETE. This issue is found with the latest the Dell SMI-S provider version 10.27.G6.03. This issue is logged with the Dell Support.

HBA Port Performance Statistics

■ The data discovered in SRM for QLogic HBA port performance statistics is mismatching with the QLogic vendor UI. This issue is a known issue with the QLogic vendor for the QLA2340 model. For more information, see the knowledge base article KB:1915 in the QLogic support site.

■ Oracle does not support the common HBA API for collecting data for the Solaris HBA Port performance attributes. For more information, see the CR 7159194 in the Oracle Support site.

However, limited performance data can be collected in CA SRM on the Solaris HBA port using CLI commands.

■ The AIX HBA API returns incorrect information in the CA SRM for the following attributes:

– Transmitted Fiber Channel Words

– Received Fiber Channel Words

IBM has provided an ifix in the HBA API. For more information, see the Operating System release AIX 7.1 TL: 07 SP: 05.

General Issues


Hicommand Disk Arrays

Hicommand Disk Arrays 5.8 provider includes the following issues:

■ Disk Array WWN is null and not supported.

■ Storage ports are not updated under the processor.

■ With the current release, all new disk array registrations can only be done using SMI-S. However, the disk arrays which are already registered using SYMAPI or HICommand, when upgraded to the current release, continue to get collected by the original collection mechanism. This collection is required for backward compatibility. But, storage performance information is not collected with the SYMAPI or Hi command XML API collection mechanisms.

Hitachi Data Systems Disk Arrays

Hitachi disk array issues include the following:

■ When using the SMI-S management interface, the date collected is partial and does not include:

■ Disk array raw size

■ Spindle information

■ Connection between LDEVs and RAID groups

This is due to limitations in the HDS SMI-S Provider. We recommend that you use the HiCommand interface to manage HDS disk arrays.

■ The number of controllers displayed in SRM for Hitachi NSC55 disk arrays does not match the number of controllers reported by the array's native software.

■ The size of the RAID disks displayed in SRM for Hitachi disk arrays does not match the size of the RAID disks reported by the array's native software.

■ With the current release, all new disk array data collections can only be done using SMI-S.

General Issues

52 Release Notes

IBM DB2

IBM DB2 issues include the following:

■ The data collection fails when you use the DB2 8.1 server as a proxy collector for a DB2 server on another host. This failure occurs with the error: 'SYSTEM' user does not have privilege for data collection.

When this occurs do one of the following:

– Use a computer where only the 8.1 client is installed as the proxy collector for DB2 data collection.

– Manually catalog all of the databases on the instance that the 8.1 server computer is a proxy collector for. The data collection works successfully after cataloging even though the dbwin produces the error: cataloging of database failed as 'SYSTEM' user does not have privilege to catalog.

This problem does not occur with DB2 8.2 servers and clients.

■ When two or more application servers try to perform data collection on the same DB2 instance at the same time, one of the collections fails with the following error:

User does not have enough privileges

This error occurs because DB2 does not allow more than one storage snapshot of a database to be taken at any one time.

The only way to prevent this problem from happening is to ensure that no two data collections are scheduled on the same DB2 instance at the same time. You must also ensure that you allow enough time between data collections so that the first collection finishes before the second collection starts.

IBM Disk Arrays

There is a discrepancy in the RAID Disk Size for IBM DS6000 and DS8000 as reported by the IBM Web GUI and CA SRM. This is because IBM uses 1000 instead of 1024 when converting bytes to KB, MB, GB, TB and so forth.

Indirect Collection (NFS/DFS)

The following list includes the Indirect collection issues:

■ You cannot drill down to NFS volumes when the server that was used for data collection is no longer available.

■ In order to modify the collector for indirect-collected computers (NFS or DFS), delete the indirect computer and reregister it with the new collector.

General Issues


iSponsors for Backup Management

CA SRM uses agents called iSponsors to collect information about backup applications. In version r11.6, the iSponsors for all backup applications have been updated substantially. If you are running r11.5 versions of iSponsors, you must upgrade these to the r11.6 versions for the backup management functionality in CA SRM r11.6 to work properly. The new iSponsors are located on a CD included in the CA SRM r11.6 product box. For instructions on how to upgrade the iSponsors, see the section, "Upgrade the iGateway and iSponsors" in the Installation Guide.

Important! You cannot upgrade r11.1 iSponsors to r11.6 iSponsors. If you have r11.1 iSponsors, you must uninstall them before installing the r11.6 iSponsors.

iSponsor Server Error

Due to iTech incompatibilities, you might get iSponsor Server error when you run Capacity-based licensing.

To resolve this problem, you need to add SRM\bin path to LIBPATH and restart the iGateway service.

Legato NetWorker

CA SRM only collects partial information from devices that are part of a storage pool. Additionally, pooled devices are not counted toward the total device count.

Licensing

It is possible to accidentally register a computer twice by registering it once using its IP address, and once using its resolved host name. If this happens, the computer will appear twice in the Capacity-based Licensing Report, and each instance will count toward your total managed capacity.

Lotus Domino

Lotus issues include the following:

■ If the you do not have any Cluster related information and you select the Cluster field in the Lotus Domino Server View and Output Definition Fields dialog, the entire Domino Server record fails to appear.

■ If you try to use a Lotus Client 6.x computer as a proxy collector for data collection of Domino Server 7.x, then the database type information in the Domino Database object cannot be obtained and CA SRM shows it as N/A.

General Issues

54 Release Notes

LSI Disk Arrays

LSI issues include the following:

■ If you have multiple arrays configured in CA SRM via the same SMI-S provider, we recommend that you do not schedule them all to collect data at the same time. This helps to avoid communication problems on the provider.

■ CA SRM does not correctly report the amounts of allocated and unallocated space when the disk array is using an SMI-S provider prior to version 09.16.G0.17. To work around this problem, please upgrade your LSI provider to version 09.16.G0.17 or higher. At the time of this writing, the latest SMI-S providers for external LSI RAID arrays can be downloaded from http://www.lsi.com/storage_home/products_home/external_raid/management_software/smis_provider/index.html

■ The LSI disk array provider does not provide information on snapshot repository volumes to CA SRM. A snapshot repository volume is a temporary, symbolic placeholder for changes made to an array while a snapshot is being taken. Thus, when you compare the data in SRM with the data obtained from the disk array's native interface, it may appear as though SRM is not getting information on all the LDEVs in the array. In fact, the LDEVs that are not reported on are these temporary volumes.

Microsoft Exchange 2000/2003

Remote collection of Microsoft Exchange 2000/2003 is expected to experience some latency (hours).

Microsoft SQL Server

SQL Server issues include the following:

■ Discovery works only within a Domain. SQL Servers that do not belong to a Domain must be registered manually, using the SQL security definitions.

■ The registration wizard does not discover a SQL 2005 / 2008 / 2012 "Named Instance". The discovery works fine for all default SQL instances. In this situation you should use the manual registration.

General Issues


Microsoft .Net Install Creates Dummy Folders

When you install SRM, the following dummy folders and files are created as a part of Windows Client install (during the Microsoft .Net installation).

amd64 and i386 folders in SRM database folder with the following files:

■ xpssvcs.dll

■ mxdwdrv.dll

■ msxpsinc.ppd

■ msxpsinc.gpd

■ msxpsdrv.inf

■ msxpsdrv.cat

■ filterpipelineprintproc.dll

Note: These files do not get deleted, even if you un-install SRM from your computer. For more information about the .Net installation issues and fixes, see http://support.microsoft.com/default.aspx/kb/951847/.

Moving CA SRM Server from Workgroup to a Domain

The following workaround helps you running the CA SRM server after successful movement in the following scenarios:

■ Workgroup to a domain

■ Domain to a workgroup

■ Domain to a domain

Example:

The following example explains the successful movement from a workgroup to a domain.

Prerequisites:

■ Take backup of the existing CA SRM Application Server before moving it in a domain.

■ Register any computer as a managed host from the domain where the SRM server to be moved. This adds an entry for the new domain in the domain table.

■ Register at least one managed computer other than an SRM server from the Workgroup as a proxy collector for the Workgroup, after moving to a domain. This task can also be done after moving to the new domain.

General Issues

56 Release Notes

After you successfully move the SRM server (example, from any workgroup to a domain), follow these steps to run an SRM server without any impact on object data collections.

1. Ensure that the BSRM share folder must have a similar access right to a domain as an administrator of Workgroup.

Otherwise, you may encounter an error and the application server does not start. Provide sharing and security permissions to the new domain user, to avoid this error.

2. After the application server and windows client starts, verify the domain proxy entry for both Workgroup and new domain from the domain's table.

3. Open the dbm32.exe from the bin folder of CA SRM.

4. Reset the domain proxy collector for a new domain as the SRM server name as follows:

■ Open the computer table and update the BELONGS_TO_DOMAIN field of SRM server’s computer record with the new domain id and save the record.

■ Open the domain table and update the domain record by modifying the DOMAIN_SERVER field to the SRM server computer Id and save the record.

5. Reset the domain proxy collector for Workgroup as a computer from the Workgroup domain.

■ Open the domain table and update the Workgroup record by modifying the DOMAIN_SERVER field to the computer id that belongs to a Workgroup domain and save the record.

6. Verify the updated changes on the windows client from the domain, modify wizard.

You can now see the new domain proxy collectors for the Workgroup and new domain records.

7. Modify the SRM server computer's user credentials to apply the latest domain user details for the next collection.

General Issues


NetApp

NetApp issues include the following:

■ You may encounter a failure with data collection using SSH if the system messages are returned as an output of the command the collection is running.

■ Some information might be missing from the Quota Specifier field when using the ONTAPI protocol for data collection.

NetWare

NetWare issues include the following:

■ The computer that is selected as the proxy collector must be registered in the CA SRM database as a managed computer.

■ In accordance with Novell's recommendation, CA SRM must not be used with IntranetWare Client 4.3. Use newer releases such as Novell® Client 4.91.

■ Mounted CD-ROM drives on NetWare 6.5 are displayed in the Volumes table.

■ Owner-related Storage Analysis reports are not available for NetWare volumes. These reports include all that are listed under Analysis By Owner. To obtain owner-related information for NetWare volumes, use the Query Service and select the Rescan File System Every Time option.

■ When defining a file query from Netware based on file-system cache, you cannot see file ownership columns.

■ The File Scan mechanism does not support full name files over 256 characters.

■ When you try to add Netware computers using the Add computer option from the Setting Data Collection Properties dialog, verify that the bindery context is set to the context used to log in to the NDS tree. If you do not want to set the bindery context, add the Netware computers from the list of candidates displayed in the Selecting Computers to be Managed dialog.

■ CA SRM does not collect information of files and directories whose full path length exceeds over 256 characters.

■ CA SRM does not collect information from Netware servers which are configured in IPv6 environment, but collects data from only IPv4 Netware server.

General Issues

58 Release Notes

Non-English Operating Systems

Non-English operating system issues include the following:

■ On non-English operating systems, you may encounter a problem with iGateway discovery. To correct this you need to Add/Modify the administrator group name tag to the iControl.conf file located in the installed iTechnology folder. Put the corresponding "localized" Administrator Group Name between the tags <AdminGroupName></AdminGroupName>.

■ CA SRM does not collect information from backup products running on HP-UX with a Japanese locale.

Oracle

Oracle issues include the following:

■ When creating the Oracle service with the Net Configuration Assistant, choose the Local Net Service Name Configuration option.

■ If an Oracle instance is backed up by CA ARCserve Backup and both the Oracle instance and CA ARCserve Backup are registered in CA SRM, the Oracle agent displays the information regarding the number of backups, restores, errors, and so forth.

The Oracle agent, however, displays the details about backups only for Windows servers. This is because CA ARCserve Backup does not return the values for Session information correctly on LINUX and the format that the session information reports on for Windows and UNIX is different.

■ When you change the proxy collector for the Oracle agents registered in CA SRM, the discovery of defined services is not supported in the following scenario.

You registered the Oracle instance in CA SRM using a service defined with the Oracle server hostname and the Oracle instance name combination.

On another proxy computer, you defined a service to this instance with the IP address of the Oracle server computer and the Oracle instance name.

During the proxy collector change, the service defined on the second computer is not discovered as a service. This is because the hostname to IP address (and also the IP address to hostname) conversion is not built into the modify dialog component.

General Issues


Portmapper Service

CA SRM Application Server requires a recognized Portmapper to be installed and active.

During SRM Application Server Installation, Install package copies NobleNet Portmapper binary (portserv.exe) to <Windows>\system32 directory.

If there is no Portmapper service (which listens on port 111) exists, SRM install package creates a NobleNet Portmapper service. Otherwise, SRM will make use of existing foreign Portmapper service provided it is recognized by SRM.

SRM installation program currently recognizes following Portmappers:

■ ONC Portmap

■ portmap

■ NobleNet Portmapper for TCP

■ NetManage Chameleon32NFS Portmapper

■ NobleNet Portmapper

■ CATIRPC

■ CA Remote Procedure Call Server

■ nsrexecd

■ eAudit Portmap

■ eTrust Audit Portmap

■ PowerRPC Portmapper

■ CASportmapper

Note: For any reason, if the above foreign Portmapper is removed or failed to work, then NobleNet Portmapper service should be created by the user manually for SRM Application server to work properly.

To install NobleNet Portmapper service manually, run following command on DOS prompt.

sc create "NobelNet Portmapper for TCP" binpath= <Windows>\system32\portServ.exe

type= own start= auto

After creating service user should start the Portmapper and SRM services.

General Issues

60 Release Notes

QLogic HBA Drivers

If you find any inconsistent data for the QLogic SAN paths, download and install the latest QLogic HBA driver.

Note:This behavior is observed only on Microsoft Windows OS.

Registration Wizard

During the registration of a new computer, if you cancel the installation of the CA SRM Windows Agent to a remote computer, you might receive the following message on the remote computer:

Error loading ctor.dll

To fix this issue

1. Restart the agent installation on the target computer. You can do this locally or remotely.

To start the installation locally:

a. Run the base installation program ("setup.exe" on the product CD).

b. Click Install Products, Agents and Options, then Install CA SRM Windows Agent.

To start the installation remotely, re-register the target computer by running the Computer Registration Wizard.

2. Complete the installation of the agent on the target computer.

The agent is installed on the target computer and the error no longer appears.

If you do not want the agent to remain on the target computer, you can now uninstall it using Add / Remove Programs on the target computer.

■ When registering a UNIX or Linux computer, if you make any changes to the computer's configuration before it has been registered, then the computer will not be registered. You must wait until after the UNIX or Linux computer has been successfully registered before making any configuration changes.

SMI-S Providers

SMI-S Providers based on the SMI-S 1.0.3 specification, do not support disk sparing mode. Consequently, CA SRM does not report on RAID Group Spare Disks.

General Issues


SUN Disk Arrays

The spindles/disk drives reported for SUN 6920 Disk Array SMI-S Provider are virtual disk drives. Information to correlate Physical Disk Drives to other logical elements of the disk array such as Raid Groups or Volumes is not available from the SUN 6920 SMI-S Provider which supports SMI-S 1.02 specification. As a result, CA SRM discovers the virtual disk drives from the disk array and correlates to other logical entities within the array. Since the disk array size, usable space, and free space are rolled-up information based on this unavailable relationship, they will be wrong.

Sybase

Sybase database issues include the following:

■ The free space values in the CA SRM Sybase Database table does not match with the Sybase GUI values when using the Adaptive Server Enterprise plug-in: 15.0 Build option: GA Build 1 EBF 12783 GA.

There is a bug in this Sybase build. You can resolve the bug by upgrading to the Adaptive Server Enterprise 15.0 ESD #1 EBF 12949. After this patch upgrade, the CA SRM free space values will match with the Sybase GUI. You can download this patch from sybase.com. Navigate to downloads, then to EBF/Maintenance, and then to Adaptive Server.

■ When you change the proxy collector for the Sybase agents registered in CA SRM, the discovery of defined DSNs is not supported in the following scenario.

You registered the DSN in CA SRM using a service defined with the Sybase instance hostname and port number.

On another proxy computer, you defined a service to this DSN with the IP address and the port number of the Sybase instance.

During the proxy collector change, the DSN defined on the second computer is not discovered. This is because the port number to IP address (and also the IP address to port number) conversion is not built into the modify dialog component.

■ When Sybase ASE 15.0 server and Sybase 12.5.2 drivers are installed on the same computer, use Sybase 15.0 drivers for data collection. If you use the 12.5.2 drivers, the data collection might fail with Socket Closed errors. Success or failure of the data collection is not predictable in this scenario. We recommend using Sybase 15.0 drivers with Sybase ASE 15.0 server data collection.

General Issues

62 Release Notes

TSM

When you change the proxy collector for the TSM agents registered in CA SRM, the discovery of defined DSN is not supported in the following scenarios:

■ You registered the DSN in CA SRM using a service defined with the TSM server hostname and the port number.

■ On another proxy computer, you defined a service to this DSN with the IP address and the port number of the TSM server.

■ During the proxy collector change, the DSN defined on the second computer is not discovered.

This happens because the port number to IP address (and also the IP address to port number) conversion is not built into the modify dialog component.

Note: TSM 5.5 supports only partial IPv6, as few functions use IPv4 address communication. Refer the following link for vendor details:

http://www.redbooks.ibm.com/redbooks/pdfs/sg247447.pdf

Data collection does not happen

Occasionally, the data collection for TSM Server or for few TSM objects does not happen. The data collection not happening is a known issue in TSM 6.1.5. For more information about resolving this error, see https://www-304.ibm.com/support/docview.wss?uid=swg21420344

For more information about querying tables, see the TSM Server Admin Reference Guide.

General Issues


Trend Data Consolidation

Due to the date issue in all the trend tables, the trend data is not getting consolidated in r12.6. You can fix this problem by removing all the data and can get the latest trend date from the SRM server.

Follow these steps:

1. Open the Web Reporter Control Panel and disable the SRM application server.

2. Navigate to the <Drive>:\Program Files\CA\BrightStor SRM\Bin from the DOS command prompt.

3. Run the following ClearTrendData.sql script from the command prompt:

> sqlcmd -S <SQL instance name where CASRMCentralDB exists> -U <user> -P <password>

-i CleanTrendData.sql -v SRMSERVER=<SRM Database Server Host Name>

The script executes the procedure under the Databases, CASRMCentralDB, Programmability, Stored Procedures, SRM_REMOVE_TREND.

Note: You can also execute the same procedure by logging in to the SQL Server management studio where CASRMCentralDB resides.

4. Enable the SRM application server.

This action adds the trend data into CASRMCentralDB.

UNIX and Linux

UNIX issues include the following:

■ Occupied space for dynamic disks in the physical disks table is always shown as 100percent.

■ Storage Analysis on Veritas File Systems is not supported for volumes with layout version 6. This version is the default for Veritas VM 4.1. To find out the layout version of a volume use the Unix command: fstyp.

■ For Linux on z/OS, there is no DB2 agent

■ Host data collection fails if any NFS mounts on that host are inaccessible.

General Issues

64 Release Notes

Upgrading

Upgrade issues include the following:

■ If the Windows Client is installed on a Windows XP computer, and you are upgrading to Windows Vista, you must uninstall the Windows Client before you upgrade the operating system to Windows Vista. After the operating system upgrade is complete, reinstall the Windows Client.

■ Due to some changes in the CA SRM r11.7 database, user-defined views from pervious versions of CA SRM might not work following an upgrade. If a user-defined view no longer works following an upgrade, you can delete the view and try to re-create it using the fields and options available in CA SRM r11.7.

■ If you are upgrading to CA SRM r11.7 from CA SRM r11.5 SP2 on Windows 2003, a program named DBM32.exe might appear in the taskbar. We recommend that you do not open this window. If you do, the upgrade process might become unresponsive.

■ If you upgraded to r11.5 SP2 from CA SRM r11.1, your disk arrays might not appear in the Windows Client following an upgrade to CA SRM r11.7.

If this happens, re-register your disk arrays, and they will re-appear in the Windows Client with all their data intact.

Important! To avoid the loss of historical data on your disk arrays, do not delete any of their previous records.

Veritas NetBackup

If you are using a remote computer as a proxy collector for Veritas NetBackup, and the proxy collector is running a version of the CA SRM Windows Agent earlier than r11.6 RP4, data collection fails if the NetBackup environment contains a robot or a drive with a serial number longer than 32 characters.

Similarly, if the proxy collector is running the r11.6 RP4 version of the CA SRM Windows Agent, but the Application Server version is not r11.6 RP4, then any serial numbers longer than 32 characters are truncated to 32 characters.

For the above reasons, we recommend that you upgrade both the Application Server and the copy of the CA SRM Windows Agent running on the Veritas NetBackup proxy collector to r11.6 RP4.

Note: Veritas NetBackup does not support IPv6. Refer the following link for information:

http://www.symantec.com/business/support/index?page=content&id=TECH43402&key=15141&actp=LIST

General Issues


Virtual Host Servers

Virtual Host Servers include following issues:

■ For some Virtual Host Servers, CA SRM displays Virtual Center Name as "N/A" in VHS table, because SDK does not return any virtual center name.

■ If VMWare tools are installed on the Virtual Guest, CA SRM reports VHS Virtual Guest State, IP address, and Hostname correctly, otherwise it displays as "N/A".

Note: If VMWare tools are not installed on the Virtual Guests, SDK itself does not return the Virtual Guests State, IP address, and hostname.

■ CA SRM does not report any information about the Virtual Guests that are in orphaned, inaccessible, and invalid state in the Virtual Guests table.

■ For Hyper-V Virtual Guest, the Operating System type, Operating System family, Hostname, and Network address details display based on the return values of WMI methods mentioned in the following link:

http://msdn.microsoft.com/en-us/library/cc136898(v=vs.85).aspx

■ For Hyper-V Virtual Guest, the Virtual Guest Type is set as Not Available by default.

■ The usage space for VHS_virtual host server covers only the VMFS volumes. The Non VMFS volume space is not provided with VI SDK and hence not considered here.

Windows

Windows issues include the following:

■ When using the Windows Client on Vista to register Windows hosts, CA SRM may fail to discover any candidate hosts if the domain contains a many computers. This is due to a problem with the implementation of the "net view" command on Windows Vista. If this happens, you need to add each host manually. You can check for this problem by issuing the following command on the problem domain:

net view /D:<domain-name>

If this command fails, CA SRM cannot discover computers in the domain, and you must add them manually.

■ Windows Agent registration on computers where a CA SRM Windows Client is already installed is not recommended. Use agentless collection if desired.

■ Unused space is not displayed correctly for physical disks that reside on partitions that do not have a drive letter.

■ Logical volumes that reside on partitions that do not have a drive letter are not displayed correctly.

■ "Total Directory Entries", "Free Directory Entries", and "Total Number of Files" information is not available for Windows volumes.

Service Issues

66 Release Notes

■ Support of Windows Server 2003 R2 is within the same scope of Windows Server 2003 SP1.

■ If you invoke the Application Server Maintenance Utility through Terminal Services, it only appears on Session 0 (the console). In order to use the Application Server Maintenance Utility remotely, you must open the terminal services as a console (mstsc/console).

■ The following attributes are not collected by the Query service, when using cached data:

– File Short Name

– File Number of Streams

– File Reparse Point Type

– Owner Type

– Domain Owner

■ When you zoom from any of the storage analysis reports to files on a Windows 2008 OS system, an interactive service detection dialog opens. To avoid getting this dialog, disable the interactive service detection service in the services.msc console.

■ Windows Agent registration on computers where a CA SRM Windows Client is already installed is failing on Windows Vista, Windows 2008, and Windows 7.

Problem:

Computer registration fails with the following error message:

"Error connecting to remote machine: Failed to connect to the service control

manager on <hostname>. The account specified does not have administrator

privileges."

This problem occurs when you install agent on a host that has only Windows Client installed using non-administrator account.

Solution:

To get rid of this error, you must run Windows Client using "Run as administrator" option and push agent on this Windows Client host using Computer Registration Wizard.

Service Issues

The following sections list known issues associated with services.

Automate Service

The Automate service has the following issue, "User Above Quota" doesn't compile.

Service Issues


File Group

The Query service has the following issue for File Group service, when the classes involve directories and the scope is given as a list of volumes, it will not compile.

File Scanning

The cache may not refresh when you attempt to add a large folder using Windows Explorer. This can occur when both of these conditions exist:

■ Incomplete coping of files because of limited free space.

■ The journaling option is not turned on for the same target volume.

As a result, when you do not set the "access time analysis," then the new files that you just copied are not included in the cache.

General

General services issues include the following:

■ Service names should not contain reserved EDL words, such as keywords, object names, or attribute names.

■ When using MAPI mail, the mail client login dialog will always be activated when email attentions are distributed using Lotus Notes.

■ Services and classes cannot be defined using multi-byte characters in the name.

Query Service

Query service issues include the following:

■ Exporting to MDB files using ODBC may fail if the data contains text longer than 255 characters. This happens because the Jet ODBC driver always defines CHAR fields as "Text" style fields, which cannot contain more than 255 characters. Use the "Export to MDB" option instead.

■ When exporting to DB2, make sure that column names are shorter than 18 characters, because DB2 limits column names to 18 characters. You can shorten a column name using an EDL AS clause in the query definition:

COMPUTER_LAST_UPDATE_DATE as COMP_UPDATE_DATE

■ The file scan executed by the query service is unable to access paths which contain UNICODE characters that cannot be translated using the current code page.

■ Trend history for queries that include Computer operating system don't work.

Windows Client Usage Issues

68 Release Notes

■ The query duration time is wrongly displayed in the activity monitor when the query is executed during normal to Daylight Saving Time (DST) shift and vice versa.

■ If the data collection frequency is scheduled between 2:00 A.M to 3:00 A.M during normal to DST shift, the next DC time will be wrongly displayed between 2:00 A.M to 3:00 A.M in the activity monitor as it is invalid. The query execution will start from 3:00 A.M onwards and the next execution time for query will be between 2:00 A.M to 3:00 A.M.


The following sections list known issues related to Windows Client usage.

General

General Windows Client issues include the following:

■ The Windows installer may prompt for the Microsoft Office CD-ROM after starting the Windows Client. This can occur if your computer is running Microsoft Windows 2000, and you have installed Microsoft Office 2000 from a CD-ROM. Refer to Microsoft Knowledge Base Article 298385, available from http://support.microsoft.com, for a resolution to this problem.

■ If you receive a Communication Error from the Windows Client, it might be because another application on the network is using the same TCP ports as CA SRM (one such application is Laplink RemoteAssist™). If this happens, you will need to change CA SRM's TCP ports.

For instructions on how to change CA SRM's TCP ports, see the section "Change the TCP Ports" in the Troubleshooting chapter of the User Guide.

■ The product has some limitations regarding activation of the Windows Client through Microsoft Terminal Server. In order to activate more than one session of the Windows Client, you should use a different user ID for each Windows Client session.

■ Printing a report to a printer defined as a file and not a real printer may result in the need to restart the Windows Client.

■ You cannot apply a filter to some of the fields in the Total reports of Storage Analysis.

■ On Windows 2003 r2 computers, the Windows Client Help cannot display the “XML table” links found in object topics. You can manually access the XML tables by navigating to this directory ..CA\BrightStor SRM\xmlhelp.



■ If you have assigned drive letters from a to z, then when you try to connect the Windows Client to the Application Server, an error like this displays:

Cannot initialize the Windows Client.

This problem occurs when all of the drive letters are assigned. You need an unmapped drive letter. Free a drive letter and restart the Windows Client.

■ In some dialogs and wizards using the Tab key and Shift+Tab key combination to navigate may cause a runtime error.

Multi-byte Issues

Multi-byte issues include the following:

■ Some Traditional Chinese multi-byte characters cannot be displayed properly.

■ Multi-byte names for Services, Classes, Views, Solutions and all other user-defined constructs are not permitted. They all must have single-byte names.

■ Japanese language multi-byte characters cannot be used:

– In numeric fields in the User View Definition dialogs.

– In the IP Address field of the Disk Array Registration Wizard.

■ Graphs where attributes use multi-byte characters might not be displayed properly.

■ Times that contain the Japanese "AM" and "PM" characters are not recognized correctly by the Schedular.

■ SAN logical disks that have multi-byte characters in their names might not be displayed properly.


Chapter 12: Known Issues of CA SRM Web Reporter

The following are the known issues reported for CA SRM Web Reporter:


Add SRM Server Fails - SQL Named Instance (see page 71) Add SRM Server Fails – SQL Target principal name is incorrect (see page 72) BOS Service Failed to Start (see page 73) CA Business Intelligence Upgrade from r2.x to r3.3 Fails with the CMS error STW00213 (see page 73) CA SRM Web Reporter Control Panel Dependencies (see page 74) CA SRM Web Reporter Data Bridge Install Fails in RP4 (see page 75) Duplicate Y-axis Scaling in Reports (see page 75) Extreme Date Values (see page 75) Manual Import of Predefined Reports (see page 75) Report Schedule Error (see page 81) Report Hangs (Heap size, Out of Memory, and Expansion Limit) (see page 81) Time out Errors in Web Reporter (see page 82) Updating CA SRM Domain Credentials in Web Reporter (see page 82)

Add SRM Server Fails - SQL Named Instance

The Add SRM Server fails in Web Reporter with SQL Named Instance:

In case of SQL Server Named instance, adding SRM servers that belong to different subnet may fail due to connection string failure with the error "Failed to add SRM server... Error ID: 44932, Error Description: A timeout occurred while executing request."

Add SRM Server Fails – SQL Target principal name is incorrect

72 Release Notes

To resolve this problem:

1. Configure SQL Named Instance on a static port.

2. Specify the above port number in WRCP.ini file on Web Reporter computer. The WRCP.ini file has an entry called WRCP_CDB_SQL_SERVERNAME which represents SQL Server Instance Name.

You have to specify the port number with Server Name\Instance Name separated by comma. You can locate the WRCP.ini file in the Control Panel installed path and in case of default installation, it will be in C:\Program Files\CA\CA SRM Web Reporter.

Example:

[WRCP_CONFIG]

WRCP_CDB_AUTH_MODE=0

WRCP_CDB_SQLSERVERNAME=srm15\Instance,1557

Note: For configuring a SQL Server to listen on a Specific TCP Port, please refer to below link:

http://msdn.microsoft.com/en-us/library/ms177440(SQL.90).aspx

3. Restart the Web Reporter Control Panel after adding SQL server port number in WRCP.ini file.

4. Restart the WRDB on SRM computer, before adding the SRM server again in the Web Reporter Control Panel.

You can restart the WRDB by giving stop & start commands to WRDBController.exe from command prompt.

You can locate this executable file in "x:\..\BrightStor SRM\bin" folder.

Example: C:\Program Files\CA\BrightStor SRM\bin>wrdbController.exe [stop | start]

Add SRM Server Fails – SQL Target principal name is incorrect

During the SQL Server installation, when you add SRM servers in the Web Reporter Control Panel with Windows authentication and if you select to run the SQL services in domain account instead of local system account, then you might receive the following error message:

[SQL Native Client] SQL Network Interfaces: The target principal name is incorrect.

This is a Windows error, so refer to Microsoft's Help and Support site for troubleshooting: http://support.microsoft.com/?id=811889

BOS Service Failed to Start


BOS Service Failed to Start

If you install CA SRM and Business Objects on same computer, you might encounter a port conflict if a BO service uses port 1245. This port needs to be available for use only by the BOS service. If any service other than BOS uses port 1245, you must reassign that service to a different port. For more information refer to Business Objects' documentation: http://help.sap.com/

CA Business Intelligence Upgrade from r2.x to r3.3 Fails with the CMS error STW00213

Symptom:

Installation of CA Business Intelligence r3.3 in an existing CA Business Intelligence r2.x environment fails with the CMS error:

The Central Management Server has failed to start. Press ‘Retry’ to attempt to start

it again or ‘Cancel’ to skip any actions dependent on the Central Management Server.

STW00213

Solution:

Cancel the existing Web Reporter installation (the Cancel button has to be clicked twice to abort the installation) and clean up the installation directory before reinstallation.

Follow these steps:

1. Open the Central Configuration Manager for CA Business Intelligence 2.x.

2. Right-click one of the services, then select Properties.

3. Select the start-up type as "Automatic," then click OK.

4. Repeat steps 2 and 3 for all of the services.

5. Restart all the services.

CA SRM Web Reporter Control Panel Dependencies

74 Release Notes

6. For a successful upgrade from CA Business Intelligence r2.x to CA Business Intelligence r3.3, the password for the BusinessObjects Administrator user must be set to blank. Use the following steps to reset to blank password:

a. Log in to the CMC Application of CA Business Intelligence r2.x.

b. Navigate to Authentication, Enterprise.

c. Clear the following options:

■ Enforce mixed-case passwords

■ Must contain at least N Characters.

d. Save the changes using the Update button.

e. Reset the password to blank for Administrator user.

7. Trigger the Web Reporter installation again which should successfully upgrade from CA Business Intelligence r2.x to CA Business Intelligence r3.3.

Post-installation Steps (Optional):

Revert Blank Password to Non-blank Password

Follow these steps:

1. Log in to CMC Application of CA Business Intelligence r3.3.

2. Navigate to Preferences, Change Password to reset the password from blank to a non-blank password:

a. Log in to CMC Application of CA Business Intelligence r3.3

b. Navigate to Preferences, Change Password to reset the password from blank to a non-blank password.

CA SRM Web Reporter Control Panel Dependencies

When you un-install SRM from a computer where Web Reporter is installed, then the following Active X Controls would also be un-installed along with SRM un-installation.

■ MSWINSCK.OCX

■ richtx32.ocx

■ TABCTL32.OCX

Cause

When the above listed Active X Controls are un-installed, (as part of SRM un-installation), the Web Reporter Control Panel would not work.

CA SRM Web Reporter Data Bridge Install Fails in RP4


Resolution

Manually copy and register MSWINSCK.OCX, richtx32.ocx, TABCTL32.OCX to system32 directory to continue working with the Web Reporter Control Panel GUI.

CA SRM Web Reporter Data Bridge Install Fails in RP4

If you install the Web Reporter Data Bridge on SRM r11.6 RP4 Application Server computer, when the SRM trap service is running, the installation fails and the system throws an access denied error message. The SRM trap service used the dba_w32.dll that fails the installation, when it is running. To avoid this error, stop the SRM trap service and continue the Data Bridge installation.

Duplicate Y-axis Scaling in Reports

In some cases where you have small amount of data, it may appear that there are duplicate y axis values, but in reality you need to configure the report to increase the decimal place to see the value for more accuracy.

Please refer to the Business Objects documentation to adjust Y- axis scale in Web Intelligence Reports.

Extreme Date Values

Extreme date values that display in the CA SRM GUI as N/A are not displayed as N/A in reports you create from the Business Objects Universe. This is a limitation of Business Objects, not an error in CA SRM Web Reporter.

Due to the above mentioned issue, the date and time for the Last_Backup_Time field might show as 1/1/70 00:00:00.

Manual Import of Predefined Reports

When you install a new or upgraded version of CA SRM, certain situations such as incorrect Business Objects credentials or insufficient memory could cause a failure to import the BIAR file. If you encounter this situation, you need to manually import the BIAR file.


76 Release Notes

To manually import the BIAR file

1. Click Start, All Programs, BusinessObjects <release>, BusinessObjects Enterprise, Import Wizard.

Note: <release> indicates installed version of BusinessObjects Enterprise.

Import wizard welcome screen opens.

2. Click Next.

The Source Environment dialog opens.

3. Click the Source drop-down arrow and select the source Business Intelligence Archive Resource (BIAR) File from which you are going to import the report.

Note: In this example we are using the BIAR file as the source.

4. Click the ... button to open the search dialog, navigate to, and select the BIAR file, and then click Next.

The Destination Environment dialog opens.

5. Complete the CMS Name, User Name, and Passwords fields for the destination computer.



6. Select the authentication mode by selecting from drop-down menu and then click Next.

The Select Objects to Import dialog opens.


78 Release Notes

7. Select the import options you want to use, and then click Next.

The Import Scenario dialog opens.

8. Select the appropriate import scenario and click Next.

The Incremental Import dialog opens.



9. Select the overwrite options as necessary for your situation and click Next.

The Users and Groups dialog opens.

10. Select the applicable Groups and Users, and then click Next.

The Folders and Objects dialog opens.

11. Navigate and select the respective folders to import, and then click Next.

The Import options for universes and connections dialog open.

12. Select the following option:

Import the universes and connections that the selected Web Intelligence and Desktop Intelligence documents use directly. In the next dialog box, you can select additional universes that are not used by any imported document

Click Next.

The Universe Folder and Universes dialog opens.

13. Select the CA SRM central database universe and then click Next.

The Import Options for Publications dialog opens.


80 Release Notes

14. Select the following option:

Import recipients used by selected publications

Click Next.

The Ready to import dialog opens.

15. Verify the information, and then click Finish.

The import process completes.

Note: You might encounter a Universe Connection Error when you open a report after manual import. Refer the Login Error-Report (see page 80) to resolve this problem.

Login Error-Reports

When you open any report after manual import, you might encounter the following universe connection error:

To resolve report login error

1. After completion of the manual import of Biar file, open the Designer from the following path:

<Start, All Programs, BusinessObjects <release>, BusinessObjects Enterprise>.

Note: <release> indicates installed version of BusinessObjects Enterprise.

2. Open Connections from Tools menu.

The Connections List dialog populates list of available connections.

3. Select SRM_ODBC and click Test.

4. You might encounter server not responding error, click OK.

5. Click Edit in the Connections List dialog.

6. Edit the login parameters and save.

7. Ensure that the Test Connection is successful.

Report Schedule Error


Report Schedule Error

When you schedule a Web Intelligence report with prompts set to default values, the following error message appears:

"An internal error occurred while calling the 'processDPCommands' API. (Error: WIS 30270) BOException caught:RESULT=80004005;WHAT=RefreshBatch failed"

Cause

The default prompts that are set in the Web Intelligence report at design time are not being properly propagated to the Web Intelligence scheduler. This is a known issue with Web Intelligence XI. This issue has been assigned Track ID ADAPT00801580.

Resolution

The work-around for this issue is to manually set the prompt values when scheduling the report. When you schedule the report, click Modify on the Prompt tab, located on the left pane of the Schedule page to set the prompt values. Even if the prompt values exist in the Prompts section of the Scheduling page, re-select the prompt values that you wish the report to be scheduled with.

In Web Reporter reports, prompt values are not set by default. When you schedule a report, set the prompts manually. After you save the report with a prompt value, you would not get this error, since the report uses the default prompt set in the report.

Report Hangs (Heap size, Out of Memory, and Expansion Limit)

The following issues might occur when dealing with large amounts of data. There are various JRE Settings for resolving the issues (Heap size, OutofMemory, and Expansion Limit)

Note: The problem occurs mainly with JRE versions less than 1.5, while the following issues occur when reports have huge amounts of data to be obtained from the database or to be displayed.

Reports with huge data hangs:

Problem Resolution

Exception "Parser has reached the entity expansion limit 64,000 ( this happens in JRE version 1.4.0x).

Set the JRE argument -DentityExpansionLimit value to 1000000. By default the value is set to 64,000.

Time out Errors in Web Reporter

82 Release Notes

Problem Resolution

Exception in thread "AWT-EventQueue-2" java.lang.OutOfMemoryError: Java heap space" happening after the report was created and this exception happens when you try to go to the next page of report.

Change the maximum heap size (-Xmx1024m). If the JVM fails, that means the computer does not have enough memory. So reduce the value and try again. This has to be done at the Applet JRE arguments. Close all web browsers and redo the test.

Exception in thread "AWT-EventQueue-2" java.lang.OutOfMemoryError: Java heap space". The report is not created and the dialog box says that document is decoding.

Please set -Xmx1024m in theTomcat configuration settings. Make sure to add this in a separate line and add no spaces after that. If this is not done properly, Tomcat server would not start. After this change, restart tomcat server.

When you try to open a report with large amount of data in the InfoView, the progress bar on the Retrieving Data dialog runs without displaying the report. You need to close the InfoView and logon again.

Check the control tab in the Universe parameters. "Limit execution time to", if the query is taking much time, and this option might be checked then you would get "Partial Results" at report. To get complete results, clear all the check boxes in this tab or set the values appropriate for your environment.

Time out Errors in Web Reporter

At times Add SRM and Refresh WRDB status fails and pop-up messages appear with error codes like 44931 or 44932.

WRDB may not respond at that instance of time, and you need to check whether the BOS.exe or WRDB.exe are running on the SRM server.

Updating CA SRM Domain Credentials in Web Reporter

Internal operation error in Control Panel GUI is expected when it fails to validate the credentials in below instances:

1. There is any change in SRM Domain credentials

Action: Please update the credentials in SRM Windows Client.

■ Open CA SRM Windows Client on the application server computer.

■ Expand the Network Storage object and then select the Domain table from work-set tree on left hand pane.

■ Select the modify option on the domain record.

■ Update Installation password and Data Collection password in the Modify dialog and then save the changes.

Updating CA SRM Domain Credentials in Web Reporter


2. SQL Server credentials

Action: You must have permissions to access the CASRMCentralDB on the SQL Server computer

■ Open CA SRM Web Reporter Control Panel.

■ Click File -> Settings and navigate to the Modify Credentials tab.

■ Validate the credentials by typing the modified password.

3. BSRM share permissions

Action: You must have access permissions to read and write the BSRM shared folder

■ Explore BrightStor SRM Data folder in the CA SRM Application Server computer.

■ Check whether you have access permissions to read and write the BSRM shared folder.

Chapter 13: Documentation 85

Chapter 13: Documentation

Updated guides for this product are available at http://ca.com/support.

The HTML bookshelf for this product contains HTML and PDF versions of the following deliverables:

■ Installation Guide for Service Pack1 (SRM_Install_SP_ENU.pdf)

■ Overview Guide (SRM_Overview_ENU.pdf)

■ Release Notes (SRM_Release_ENU.pdf)

■ User Guide (SRM_User_ENU.pdf)

■ Windows Client User Guide (SRM_WC_User_ENU.pdf)

■ Web Reporter User Guide (SRMWR_User_ENU.pdf)

■ Web Reporter Installation Guide (SRMWR_Install_ENU.pdf)

■ Web Reporter Installation at a Glance (SRMWR_Installation at a Glance.pdf)

■ We provided HTML files that contain the CA SRM universe objects and attributes which are for your reference when building custom reports. You can find these in the installed Web Reporter documentation folder; click the file index.html to launch.

To view PDF files, you must download and install the Adobe Reader from the Adobe website if it is not already installed on your computer.



Chapter 14: International Support 87

Chapter 14: International Support

An internationalized product is an English product that runs correctly on local language versions of the required operating system and required third-party products, and supports local language data for input and output. Internationalized products also support the ability to specify local language conventions for date, time, currency and number formats.

A translated product (sometimes referred to as a localized product) is an internationalized product that includes local language support for the product's user interface, online help and other documentation, as well as local language default settings for date, time, currency, and number formats.

In addition to the English release of this product, CA supports only those languages listed in the following table.

Language Internationalized Translated

Brazilian-Portuguese Yes No

Chinese (Simplified) Yes No

Chinese (Traditional) Yes No

French Yes No

German Yes No

Italian Yes No

Japanese Yes No

Korean Yes No

Spanish Yes No

Note: If you run the product in a language environment not listed in the table, you may experience problems.

The Application Server, the Windows clients, the managed computers and the managed applications must run on the same Language zone (code-page).

The system can only support English and one of the certified languages on any managed computer. You need to set the Language zone (code-page) to this language for this to work.

Documents

CA Storage Resource Manager Release Notes - Bookshelf